Mirrors
agc up starts the app on localhost with its own masked branch of production: names, emails, phones, addresses and free text replaced; numbers, dates and ids kept. Ready in seconds, one per task.
$ agc up --detachEverything your agent needs to shipand you need to trust it
agent.cloud runs the apps coding agents build: a masked mirror of production to work on, rehearsals for releases with checks or data changes, your OK on the first release and every database change, and production explained to you and your agent.
Build
Your agent works on real-shaped data,never on real people.
Point-in-time mirrors
Reproduce production as it was at a moment in the last day, masked the same way, to see what a customer saw a few hours ago.
$ agc up --at 6hProduction view for agents
Agents query a masked, read-only view of production, answered from a recent branch and never older than the latest release.
$ agc db query --env prod "…"Any agent, one CLI
Codex, Claude Code, Cursor or anything with a terminal. Every agc response is JSON with a next step, and new apps need no account.
{ "ok": true, "next": [ … ] }Ship
Every release with checks or data changesis rehearsed before it touches production.
Rehearsed releases
Releases with checks, database changes or workers run first on a fresh branch of production with the new build. Data rules and flows must pass, or production keeps serving what was live.
21/21 checks passed · liveMigrations proven
Each migration is proven on a branch of production first: old and new shapes agree, and no existing row is lost unless the migration declares the drop.
migrations/…_cents.sql ✓Held checks
A check that stopped a bad release, or came with a fix, is held. Weakening, renaming or removing it needs a person.
held · stopped v4Agents unblock themselves
When an app won’t start, the agent gets a plain cause and a fix (a missing module, the wrong port, file modes), never the raw log.
cause: read_deniedDecide
Agents move fast.You decide what changes your data.
Approvals
The first release and every database change wait for a person. You get a link that says what changes and what was checked.
Needs your OK · v6Release policy
Choose what agents may release on their own: code-only changes, or nothing at all. You also set the app’s monthly budget.
routine | watchYour code on GitHub
A private repo per app, one commit per live release with who approved it. Join it, or take it to your own GitHub.
agentcloud-apps/<app>Read-only database logins
One-hour logins for psql or any client: on a masked branch, safe to share, or on production, just you, each session recorded. Revoke any time.
agc_ro_… · ends in 60 minRun
Production, explainedto you and to your agent.
Observability and incidents
Requests, server errors, p95 response time and logs, per release. A sentinel watches errors, response time, crashes and new error kinds every minute.
0.0% server errors · p95 121 msReplay
What happened to each booking, order or user, step by step, as the app recorded it: in production and in rehearsals.
booking:123 · 6 stepsCapsules
agc capsule shows an agent what production did for one entity or incident: workflow steps, failed requests, error classes and the releases around it, masked.
$ agc capsule booking:123Send with one HTTP call. A retry with the same key never sends twice, and mirrors and test addresses capture mail instead of sending it.
POST $AGC_EMAIL_URLWorkers and scale
Background workers get SIGTERM and a minute to finish their job on every release. Run one to four web instances.
web × 2 · worker × 1Well Architected Review
Findings across reliability, security, performance, cost and operations, each with its evidence and a fix: a prompt for your agent, or a setting for you.
1 open · medium