Workflow · Operate
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.
When to use it
Before a launch, a big customer, a funding round’s due diligence, or simply before the first night you sleep without checking.
- Specialists
- 5
- Stages
- 2
- Tier
- Observe
- Duration
- Minutes
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 agentRun a production readiness review on the production environment of project “atlas”. Prioritise what could lose data or take us down.You ask
› Run a production readiness review on the production environment of project “atlas”. Prioritise what could lose data or take us down.
Stage 1 · 4 agents in parallel
NavigatorArchitecture
Check the architecture
Single points of failure, missing replicas, services without health checks, undocumented dependencies.
WardenSecurity review
Check the exposure
Public endpoints, TLS, secrets handling, IAM scope and database reachability.
LookoutObservability & incidents
Check the signals
Is there a health check, an error-rate signal and an alert that reaches a person for each service?
PurserCost
Check the guardrails
Budget caps, autoscaling limits and environments nobody owns.
Stage 2
KaptenOrchestration
One prioritised report
Merges and de-duplicates findings, ranks them by blast radius and attaches a proposed fix to each.
You get
- A ranked readiness report
- A proposed plan per fix, ready to review
- A backup and restore checklist
Related guide
Before your first production deployment
More workflows
Keep the crew busy.
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
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
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.