Architecture
System architecture
The central control plane, dedicated runtime clusters, and the boundaries between them.
v1 design baseline. This page specifies intended behavior. Delivery and validation are tracked in the implementation plan; it is not a claim that the platform is already implemented.
HUMAN USERS
┌──────────────┴──────────────┐
│ │
Browser / Console Claude / ChatGPT / Codex
│ │
│ OAuth + MCP
│ │
┌───────▼─────────────────────────────▼───────┐
│ PUBLIC EDGE / INGRESS │
│ DNS, TLS, DDoS protection, origin shielding │
└───────┬─────────────────────────────┬───────┘
│ │
console/auth mcp endpoint
│ │
┌───────▼─────────────────────────────▼────────┐
│ CENTRAL CONTROL PLANE │
│ │
│ Laravel + Filament modular monolith │
│ Organization tenancy and authorization │
│ Identity broker / Entra OIDC / SCIM │
│ Apps, source, builds and deployments │
│ Policy, approvals, audit and metering │
│ Runtime orchestration │
│ │
│ PostgreSQL | Valkey | Object Storage │
│ Forgejo | KMS/Secrets | Artifact Registry │
└─────────────────────┬────────────────────────┘
│
outbound-initiated mTLS
desired state + commands
│
┌────────────────────▼─────────────────────┐
│ DEDICATED ORGANIZATION RUNTIME CLUSTER │
│ │
│ Runtime agent / reconciler │
│ App gateway + policy engine │
│ Static asset service/cache │
│ Sandboxed workerd application workloads │
│ Ephemeral sandboxed build workers │
│ SQLite/D1-like binding service │
│ Valkey/KV binding service │
│ Controlled egress proxy │
│ Telemetry collector │
└────────────────────┬─────────────────────┘
│
explicitly granted integrations
│
┌────────▼────────┐
│ Customer APIs │
│ Future ERP/API │
│ Future private │
│ network agent │
└─────────────────┘
The central control plane is multitenant. The pilot organization’s runtime cluster is not shared with unrelated customers.
A future customer-hosted runtime installs the same runtime agent and data-plane services but continues to consume desired state and policy from the central control plane.