Iterate is the monorepo behind a platform of Cloudflare Workers applications. Its main app is the product dashboard served at os.iterate.com; supporting apps cover a browser-based device installer, authentication, and internal services, and a published iterate command-line package delegates to local source when it runs inside the repository.
Projects expose their capability handles through an /api/itx surface with a public typed contract. A command-line client authenticates with an environment's admin secret and runs scripts against a project's itx surface, and the front end consumes the same surface as one capability tree over a single WebSocket, with thin hooks for sessions and queries and live state pushed from Durable Objects.
The domain layer is built from domain objects and stream processors. The documented processor model covers side-effect guarantees, an obligation and reconciler pattern, recovery after eviction, a staleness policy, and a Node test harness for writing and testing processors.
Deployment configuration is explicit rather than inferred: a typed environment map at the repository root lists every deployed environment with its hostnames, worker names, accounts, and resource IDs, and the secrets manager supplies only secrets, one configuration per environment. Production and numbered preview environments deploy; the shared and personal development configurations are fully local and never do. Each app deploys with its own scripts that build, deploy with atomic secrets, and smoke-test, and workers are never deleted.
A stated engineering principle for the project is that no system behaviour goes unexplained. An error is either an explicitly modelled and correctly classified expected outcome or a product defect, and the same rule applies to retry storms, stuck work, silent data loss, unexplained latency, state drift, and resource leaks. Recovery has to be bounded, observable, and to leave a durable explanation; for operational changes the acceptance proof includes a preview deployment whose traces, logs, metrics, and state transitions are coherent and free of new unexplained errors.
Features
- Cloudflare Workers platform: every app deploys as a worker, with per-app build, deploy, resource, and data-erasure scripts
- itx capability surface: typed project capability handles over /api/itx, scriptable from the CLI and consumed by the front end
- One WebSocket capability tree: a single connection carries the front-end programming model, with live state from Durable Objects
- Stream processors: documented side-effect guarantees, an obligation and reconciler pattern, eviction recovery, and a staleness policy
- Typed environment map: hostnames, worker names, accounts, and resource IDs in code, with the secrets manager holding only secrets
- Local-only dev configurations: shared and personal development configurations run entirely locally and are safe for parallel worktrees
- MCP access: a coding agent can be opened against the OS MCP server for production, preview, or local development
- Identity minting: a script mints a session as any user or admin in development and preview environments
- Browser testing: isolated headless sessions per concurrent agent, with an authorised real-browser mode when needed
- Preview-gated CI: a preview deploy plus end-to-end check with a performance budget guardrail, and test and CI telemetry in one analytics model
