Skip to content
Ethen PlatformPreview

What every Ethen product stands on

The shared parts: reaching models, checking rules, asking before big steps and keeping a record.

Ethen Platform is the shared layer behind Ethen products: gateway, policy, approvals, flow, compute and computer use. Products such as Chat, Code and Founder rely on it instead of each keeping their own copy.

The Platform console is gated. It is not open to the public, and there is no self-serve sign-up on this site.

Select a part of the Platform

Arrow keys move between parts; Enter selects.

Authority mapIllustration

Entry and control

GatewayPreview

One governed entry point to supported models, with keys, routing, policy and usage records.

Open Gateway

Illustration of how the parts of the Platform relate. It explains the design; it is not a running system. Status marks follow the registry.

01Who decides what

One path, from request to receipt

Requests enter at the top. Nothing consequential runs until policy and, where needed, a person allow it. Select a step to follow it.

Steps from a product request to a kept receipt

Step 1 of 6
Authority pathIllustration

01 · Ethen products

A product asks

Chat, Code, Founder and other products send their requests to the Platform instead of each keeping their own copy of these parts.

02Index

Seven parts, and where each one stands

Each part has its own page and its own lifecycle in the status registry.
  1. 01Gateway

    One governed entry point to supported models, with keys, routing, policy and usage records.

    Preview
  2. 02Flow

    Connectors, vault, retrieval, automation and events. Contracts and an Activepieces bridge exist in development.

    In development
  3. 03Sentinel

    Policy and defensive security. Policies are evaluated with Cedar in development fixtures.

    In development
  4. 04GPU Compute

    A facade and templates for GPU workloads. Engine integration is in development.

    In development
  5. 05Computer

    An isolated, lease-governed browser worker. It is not a Chat feature.

    In development
  6. 06Approvals & evidence

    Approvals put a person in front of a consequential action before it runs, and receipts record what happened afterwards.

    Preview
  7. 07Security & trust

    How access, policy, human control, isolation and secrets are handled, and what we do not claim.

    In development

03Authority model

Authority model

Four tiers, top to bottom. Only the second tier decides; the others ask, carry out or record.
Illustration
  1. Tier 1Ethen products

    Asks. Products do not decide on their own.

    • Chat
    • Code
    • Founder
    • Other products
  2. Tier 2Entry and control

    Decides: the key, the policy and, where needed, a person.[1][2]

    • Gateway: keys, routing, usage
    • Sentinel policy (Cedar)
    • Approval service
  3. Tier 3Executors

    Carries out only what was allowed.[3]

    • Flow: connector registry, credential vault
    • GPU Compute facade
    • Computer worker (leased)
  4. Tier 4Evidence

    Records what was approved and what ran.[4]

    • Receipts and audit records
Four tiers, top to bottom. Ethen products send requests to the Platform. The Gateway checks keys and routes model requests. Sentinel policy (Cedar) and the approval service decide whether a consequential action may run. Three executors carry out work: Flow (connector registry and credential vault), the GPU Compute facade, and the isolated Computer worker. Receipts record what happened. Component names are real; the drawing explains the design and is not a screenshot.

Notes

  1. 1.Sentinel policies are evaluated with the open-source Cedar engine in development fixtures. Policy coverage in real Platform flows is not yet measured.↩
  2. 2.Approvals cover supported workflows only today. Approvals in front of Flow, Compute and Computer actions are planned.↩
  3. 3.Flow, GPU Compute and Computer are each in development. No connector, GPU service or computer-use task is available for general use.↩
  4. 4.Records are not established as complete or forensic-grade, and they have not been independently audited.↩

04Build on it

For developers, and the limits

The developer docs describe the Gateway API and workflows. Using them still needs console access, which is gated.

For developers

Approvals & evidence

Consequential actions are meant to stop for a person before they run, and receipts record what happened afterwards. Records are not established as complete or forensic-grade.

How approvals and receipts work

Limits

  • The Platform as a whole is in gated preview. Flow, Sentinel, GPU Compute and Computer are each still in development.
  • We publish no prices, service-level commitments or provider counts for the Platform.
  • A waitlist is documented, but this site does not link to it until its address passes our host check.

05Questions

Questions

  1. 01Is the Platform console open to the public?

    No. The console is gated. A waitlist is documented, but this site does not link to it until its address passes our host check. The availability page shows the current status of every part of the Platform.

  2. 02Is Computer part of Chat?

    No. Computer is a Platform worker with its own status, not a Chat feature.

Status and related pages

The Platform is in gated preview. Each part carries its own status in the registry.