Solutions · For AI-built apps
You built it with an agent. Ship it with a crew.
Claude, Cursor and their peers made writing software fast. Kapten makes the next part fast too: the build, the infrastructure, the release, the alerts and the bill, handled by a crew of agents from the same conversation, in your own cloud account.
- Starts from
- Claude Code, Cursor, Claude Desktop, VS Code
- Crew on the job
- 7 of 8 specialists
- You approve
- One plan, before anything changes
- Runs in
- Your own cloud account
The problem
Localhost was hiding the hard part.
An agent can write the app in an afternoon. Production asks for a build, infrastructure, secrets, releases, alerts and a bill to watch. Here is what changes when a crew takes that on.
Without: “It works on my machine”, and nowhere else.
With Kapten: A container image per service, built the same way every time.
ShipwrightBuild & containersWithout: API keys committed next to the code that reads them.
With Kapten: Secrets scoped per environment, never baked into an image.
WardenSecurity reviewWithout: A database you have never configured, open to the internet.
With Kapten: A managed, private database planned and tagged in your account.
BosunInfrastructureWithout: You learn it is down from a user.
With Kapten: Health checks, an error-rate signal and an alert that reaches you.
LookoutObservability & incidentsWithout: A deploy that half-succeeds and no way back.
With Kapten: Health-gated releases and a one-step rollback.
HelmsmanReleases
How it works
Everything localhost was hiding, handled.
From repository to production in one conversation
Point your agent at the repository. Navigator maps the services, Shipwright makes them buildable, Bosun plans the infrastructure and Helmsman ships it, and you approve one plan before anything changes.
Safe by default, not by expertise
Warden checks exposure and secrets before the first release. Databases stay private, keys stay out of images, and production needs your approval. You do not need to know which questions to ask.
An app you actually own
Everything runs in your cloud account on standard infrastructure. When you hire your first infrastructure engineer, they inherit a clean setup instead of a mystery, and nothing has to be migrated.
Workflows
Start from a recipe built for this.
Each workflow names the specialists it brings in and where it stops to ask you. Copy the prompt into your agent, or read the run step by step.
All workflowsShip 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
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
The crew on this job
Who does what, for you.
Every specialist has a narrow job and a boundary. Nothing reaches your account without a plan you approved.
Meet all eight specialists- KaptenOrchestrationTurns “deploy this” into one plan you can read.
- NavigatorArchitectureMaps the services and data stores your code expects.
- ShipwrightBuild & containersWrites the Dockerfiles and opens a pull request.
- BosunInfrastructurePlans the cluster, database and secrets in your account.
- WardenSecurity reviewChecks exposure and secrets before the first release.
- HelmsmanReleasesShips behind health checks, with a rollback ready.
- LookoutObservability & incidentsWatches the running app and starts incidents from what changed.
Read before you start
Guides and papers for this path.
- The deploy gapWhy software written with AI stalls before production, and what closes the gap.Read the whitepaper
- You built it with an AI. Here is how to ship it.A working localhost is most of an application and very little of a deployment. What is missing, in order, and how the Kapten crew handles each step.
- Secrets and configuration for AI-built appsKeep keys out of code, out of images and out of prompts. Separate configuration by environment, rotate on schedule, and know what to do the day a key leaks.
- Connect Kapten to Claude Code, Claude Desktop and CursorAdd the Kapten MCP server to your coding assistant, sign in, choose a scope and run your first five prompts.
FAQ
A few practical questions.
I have never deployed anything. Is this for me?
Yes. The crew explains each plan in plain terms and asks before acting. Start with the workflow “Ship your first app to production” and read the plan it produces before approving it.
Why not a one-click hosting platform?
For a prototype, that can be the right choice. Kapten is for when the app matters: you want it in your own account, with your data, your region and a setup that grows with the product. See the comparison with a traditional PaaS.
Which stacks work?
Anything that runs in a container: Node, Python, Go, Ruby, Java and others, with Postgres, Redis, object storage and background workers. Tell us your stack when you request access.
Will the crew rewrite my code?
No. Navigator only reads the repository. When something has to change to make the app buildable (a Dockerfile, a health endpoint), Shipwright opens a pull request for you to review.
Keep exploring
See how it fits together.
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.