Workflow · Ship
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.
When to use it
A customer will only buy if the software runs in their account, and you need the second install to look like the first.
- Specialists
- 5
- Stages
- 4
- Tier
- Plan → Act
- Duration
- Days, mostly waiting on the customer
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 agentPrepare 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.You ask
› 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.
Stage 1
NavigatorArchitecture
Package the application shape
The services, data stores and configuration every customer install needs.
Gate 01 · stops for your approval
Customer creates the scoped role
Stage 2 · 2 agents in parallel
WardenSecurity review
Prepare the access request
The exact role and permissions to send to the customer’s security team, with the reason for each.
PurserCost
Size and estimate
A cost estimate the customer can review against their own cloud commitments.
Gate 02 · stops for your approval
Approve the plan in the customer’s account
Stage 3
BosunInfrastructure
Provision in their account
Once the role exists, applies the approved plan in the customer’s account and region.
Stage 4
HelmsmanReleases
Release and hand over
Deploys, verifies health and produces the runbook and responsibility matrix for the customer.
You get
- An access request for security review
- A repeatable install plan
- A runbook and a shared-responsibility matrix
Related guide
Plan your first customer-cloud deployment
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
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
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.