Cloud Development Environment Platform · View 01 of 21 · Context and scope
Decisions
- Two consumer classes are drawn as peers — a developer and a coding agent runtime — because the agent starts roughly two of every three workspaces and its goals contradict the developer's.
- CI/CD, production runtime and the editor product are drawn without a relationship on purpose. This platform runs developer code; it does not ship it, and the adjacent packages ci-cd-platform and internal-developer-platform own what it refuses.
- Package registries are reached only through the platform's own proxy, which is why they appear as a dependency of the platform and never of a workspace.
Assumptions
- 250,000 daily active workspaces across 1,800 tenants, 60,000 concurrent at peak, 65% of starts from agents.
- Identity is the tenant's, federated by OIDC with SCIM-driven seats; the platform issues no human accounts of its own.
Risks
- A git forge outage stops creation and push but must not stop a running workspace — the dependency is on the start path, not the work path.
- The platform is one hop from every tenant's source code, which makes it a high-value target whose blast radius is set by the egress and credential decisions (ADR-05, ADR-06).