cloud

A3S Cloud is a self-hosted, Agent-first developer platform. Its README describes a control plane where product and desired-state truth stay in Cloud, durable work is coordinated by A3S Flow, lifecycle contracts are defined by A3S Runtime, execution is handled by A3S Box, and A3S Gateway is the only public edge. The repository is licensed MIT and targets Rust 1.88 or later, PostgreSQL 17 or a compatible release, A3S Box, a pinned A3S Gateway revision, and NATS JetStream for production all, Worker or Relay roles. Bun is listed only for TypeScript client or CLI development. The architecture follows one path for every service: admit public traffic through Gateway and Identity; commit desired state, idempotency, audit evidence and Outbox facts to PostgreSQL through A3S ORM; coordinate durable waits, retry, replay, approval, compensation and cancellation through A3S Flow and Operations; place and execute through Workloads and Fleet with Runtime Task or Service units on Box; then publish versioned route snapshots through Edge and Gateway. Cloud never becomes a second request-byte proxy. Six product outcomes share two execution classes. AaaS covers conversations, executions, events, approvals, checkpoints, forks and provider bindings. WaaS covers ontology, immutable definitions and plans, WorkflowRun, HumanTask and typed node order. FaaS owns immutable Function release profiles and delegates invocations to Executions, Workloads or Connectors. Durable Cell provides a named, serialized, hibernatable state space for people and multiple Agents. Model Inference owns model revision, deployment, routing policy, usage and evaluation, with independent replicas and multi-node prefill/decode groups. Static Web serves immutable React, Vue and other admitted releases directly from Gateway, with SSR as an ordinary Service profile. The only general execution classes are Task and Service. Quick start uses just up for dependencies and a detached control plane, with health endpoints at /api/v1/health/live and /api/v1/health/ready, an OpenAPI endpoint at /api/v1/openapi.json, and a one-shot migrator that must run before serving processes. Bootstrap creates the first Organization, service Principal, owner Membership, API token, baseline platform-role policy and PlatformOwner binding. Mutations use Bearer authorization and an idempotency key. The CLI is run with Bun and reads credentials from environment variables or standard input, not from a CLI context file. Production publishes the API only through A3S Gateway. Platform capabilities described in the README include hosted Git authority plus external source revisions, webhooks, reproducible Box builds, provenance, pull-request previews, immutable artifacts and digest-preserving promotion. Supply separates Git, OCI Registry and A3S Use Registry authorities. Run and scale use one heterogeneous scheduler for CPU pools, GPU pools, accelerator and topology constraints, Claims, anti-affinity, gang placement, maintenance, quotas and preemption, with stateless scale-to-zero and stateful drain, fencing, checkpoint and recovery. Store and serve use one typed immutable-object client over external S3-compatible storage, Gateway-owned TLS and routing, and OpenTelemetry for logs, metrics, traces, SLOs and incidents. Governance covers tenant isolation, memberships, Resource Grants, quotas, credentials, audit, Outbox, lifecycle cleanup, a system-administrator RBAC plane, short-lived support grants, and workload identity revisions. The README states that A3S Cloud does not ship a management Dashboard; it does host immutable React/Vue and other tenant Web releases for Applications and Agents, which use the same Gateway and APIs as other clients. Automatic CI and Box conformance run only for pushes to release and pull requests targeting release; main does not start these workflows automatically. Delivery status is gate-driven, not percentage-driven. As of 2026-09-06, the README lists tenant-scoped Identity, PostgreSQL/A3S ORM, Operations/Flow, Outbox, public API and migrations as a Verified foundation. Installation scope and system-administrator RBAC are Verified core with a broader gate in progress. Workloads, Fleet, Runtime/Box, Gateway, supply, collaboration and enterprise controls are in progress, with an A0.4 real-provider gate verified. Agent and hosted MCP product lanes are in progress with A0.4 verified. Ontology Workflow and AI Applications/Files are in progress. Automations have a component foundation in progress. Data/S0 and Durable Cell are foundations in progress. Workload identity has verified trust and WI2-C1/C2/C3a/C3b foundations, with fleet hardware attestation and full issuance still open. FaaS, distributed inference, model supply, Static Web, Runtime CI/CD and full HA operations are planned or early foundation. Architecture targets are not availability claims; a capability is released only after real-provider, failure, recovery, cleanup, upgrade and release gates are marked Verified in ROADMAP.md.