Workflow · Ship
Database migration rehearsal
Run a risky schema migration against a restored copy of production first, measure it, and only then schedule the real one.
When to use it
A migration touches a large table, changes a column type, or you are not sure the rollback still works afterwards.
- Specialists
- 4
- Stages
- 4
- Tier
- Plan → Act
- Duration
- Depends on data size
Start it with one prompt.
Paste it into Claude Code, Claude Desktop or Cursor once Kapten is connected. Replace the names with yours; Kapten asks for anything it cannot infer.
Connect your agentRehearse migration 0042_split_orders against a copy of production. Tell me how long it locks, and whether the previous release still works after it.You ask
› Rehearse migration 0042_split_orders against a copy of production. Tell me how long it locks, and whether the previous release still works after it.
Gate 01 · stops for your approval
Approve restoring the snapshot
Stage 1
BosunInfrastructure
Restore a copy
Restores the latest production snapshot into an isolated, short-lived environment.
Stage 2
HelmsmanReleases
Run the migration
Applies the migration and records its duration and the locks it takes.
Stage 3
LookoutObservability & incidents
Test both releases
Runs the current and the previous release against the migrated schema to check the rollback path.
Stage 4
KaptenOrchestration
Go / no-go report
Duration, locking, rollback safety and a recommended window. The rehearsal copy is then deleted.
You get
- Measured migration duration and locks
- Rollback compatibility verdict
- A recommended release window
Related guide
Rollbacks that survive a schema migration
More workflows
Keep the crew busy.
Ship your first app to production
From a repository that runs on localhost to a production environment in your own cloud account, with a domain, TLS and a rollback.
› Deploy this repo to production on my AWS account in eu-west-3. Use a managed Postgres, put the API behind api.example.com and keep it under 150 €/month.
- Navigator
- Shipwright
- Bosun
- Purser
- Warden
- Kapten
- Helmsman
A preview environment per pull request
Give each pull request a complete, isolated copy of the application with seeded data, and remove it when the branch closes.
› Set up preview environments for every pull request on github.com/acme/atlas. Seed Postgres from fixtures, cap each preview at 2 € a day and delete it on merge.
- Navigator
- Bosun
- Purser
- Kapten
- Helmsman
Install into a customer’s cloud
Deploy your product into an enterprise customer’s own account with a repeatable shape, a scoped role and a clear split of responsibilities.
› Prepare an install of our product in Globex’s AWS account, eu-central-1. They will create the role. Generate the access request and the plan.
- Navigator
- Warden
- Purser
- Bosun
- Helmsman
Build with Kapten
Start with one service.
Build from there.
Tell us what you want to deploy. We review each request and follow up about fit and onboarding on your preferred cloud.
Free during early access. No card required. Cloud usage billed separately.