Workflows
Recipes for your crew. Start one with a sentence.
Each workflow brings in the right specialists, runs them in parallel where it can, and stops where a human should decide. Copy the prompt into your agent, or adapt it to your stack.
- Workflows
- 9 ready to use
- Specialists
- 7 specialists, led by Kapten
- Read-only
- 2 never change anything
- Changes
- Always behind your approval
The library at a glance
9 recipes. One crew.
Every workflow against every specialist. Read a row to see who a run brings in; read a column to see where an agent earns its keep.
- Steps
- 47
- Parallel stages
- 9
- Approval gates
- 9
| Workflow | Kapten | Navigator | Shipwright | Bosun | Helmsman | Warden | Lookout | Purser | Gates |
|---|---|---|---|---|---|---|---|---|---|
| Ship your first app to production | 1 step | 1 step | 1 step | 2 steps | 1 step | 1 step | none | 1 step | 2 |
| Production readiness review | 1 step | 1 step | none | none | none | 1 step | 1 step | 1 step | read-only |
| Incident triage | 2 steps | none | none | none | 2 steps | none | 2 steps | none | 1 |
| A preview environment per pull request | 1 step | 1 step | none | 1 step | 1 step | none | none | 1 step | 1 |
| Security posture audit | 1 step | 1 step | none | none | none | 2 steps | none | none | read-only |
| Monthly cost review | 1 step | none | none | 1 step | none | none | 1 step | 2 steps | 1 |
| Database migration rehearsal | 1 step | none | none | 1 step | 1 step | none | 1 step | none | 1 |
| Install into a customer’s cloud | none | 1 step | none | 1 step | 1 step | 1 step | none | 1 step | 2 |
| Get ready for a launch | none | 1 step | none | 1 step | 1 step | none | 1 step | 1 step | 1 |
Ship
Get code from a repository to a running environment, the first time and every time after.
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
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
Operate
Know what is running, find out why it broke and decide what to do about it.
Production readiness review
Four specialists review an environment in parallel and hand back one prioritised list of what to fix before you rely on it.
› Run a production readiness review on the production environment of project “atlas”. Prioritise what could lose data or take us down.
- Navigator
- Warden
- Lookout
- Purser
- Kapten
Incident triage
When something breaks, start from what changed. The crew correlates the symptom with deployments, config and dependencies, and proposes a mitigation.
› Checkout is returning 502s in production since about 14:10. What changed, and what is the safest way to stop the bleeding?
- Lookout
- Helmsman
- Kapten
Secure
See what is exposed and who can reach it, with a fix proposed for each finding.
Optimise
Spend less, and be ready for more traffic than you have today.
Monthly cost review
Find idle environments, oversized nodes and orphaned resources, and get the expected saving for each change before you make it.
› Review last month’s spend for every environment. Find what is idle or oversized and tell me what I would save by fixing it.
- Purser
- Lookout
- Kapten
- Bosun
Get ready for a launch
Before a launch or a press day: find the first thing that will break under load, set sensible autoscaling and caps, and rehearse the rollback.
› We launch on Tuesday and expect 20× our usual traffic. Find what breaks first, set autoscaling and make sure we can roll back fast.
- Navigator
- Lookout
- Bosun
- Purser
- Helmsman
Who does the work
The crew behind every workflow.
Kapten
Turns your request into a plan, hands each part to the right specialist and brings back one decision for you.
Shipwright
Makes the application buildable and reproducible: a container image per service, built the same way every time.
Bosun
Prepares the ground in your cloud account: cluster, network, managed databases, storage and secrets.
Helmsman
Ships the change: health-gated rollouts, configuration, domains, and a rollback that re-points instead of rebuilding.
Warden
Reviews what will be exposed and who can reach it before it ships, and keeps reviewing after.
Lookout
Watches the running system and, when something breaks, starts from what changed.
Purser
Keeps the bill honest: estimates before you provision, and finds idle or oversized resources after.
Need a workflow that is not here?
Describe the job in your own words and Kapten composes a run from the same specialists. If it is something your team does every week, tell us during onboarding and we will help you turn it into a recipe.
How multi-agent workflows runBuild 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.