Workflow · Ship
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.
When to use it
Reviewers keep saying “works on my machine”, or two features are fighting over one staging environment.
- Specialists
- 5
- Stages
- 4
- Tier
- Plan → Act
- Duration
- One setup, then automatic
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 agentSet 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.You ask
› 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.
Stage 1
NavigatorArchitecture
Define the preview shape
Which services a review actually needs, and which can be shared or stubbed.
Stage 2 · 2 agents in parallel
BosunInfrastructure
Plan an isolated namespace
A namespace per branch, a throwaway database seeded from fixtures, preview-only secrets.
PurserCost
Set the cost boundary
A daily cap per preview, sleep after inactivity and deletion on merge or close.
Stage 3
KaptenOrchestration
Approve the template
You approve the preview template once. Each pull request then follows it without asking again.
Gate 01 · stops for your approval
Approve the preview template once
Stage 4
HelmsmanReleases
Deploy on every push
Builds the branch, deploys the preview and posts the URL on the pull request.
You get
- A preview URL on every pull request
- Seeded, disposable data
- Automatic cleanup and a daily cost cap
Related guide
Preview environment lifecycle
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
Database migration rehearsal
Run a risky schema migration against a restored copy of production first, measure it, and only then schedule the real one.
› 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.
- Bosun
- Helmsman
- Lookout
- Kapten
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.