Ship your app.
Keep your cloud.
Deploy apps, databases and jobs on the cloud provider of your choice. Kapten handles the platform work in your own account, from the dashboard or from Claude Code with a crew of agents doing the SRE work.
Free during early access. No card required. Cloud usage billed separately.
Watch a sample stack deploy. Example data and illustrative company logos.Open the interactive demo
- Northwind
- Lumen Health
- Vantage
- Cobalt
- Meridian
- Trellis
Kapten MCP
Built it with Claude?
Ship it with a crew.
Connect Kapten to the agent you already code with and get an SRE team behind it: eight specialised agents that provision, deploy, secure and watch your app in your own cloud account.
- 01
Ask in plain words
“Deploy this repo to production on my AWS account.” Kapten turns it into a plan.
- 02
Specialists do the work
Architecture, build, infrastructure, security, releases, monitoring and cost, all in parallel.
- 03
You approve one plan
Resources, cost and risks on one page. Nothing changes in your account until you say so.
One line in Claude Code
claude mcp add --transport http kapten https://mcp.kapten.io/mcpEndpoint illustrative during early access. Other clients
The convenience. The control.
A platform you’ll love.
On infrastructure you own.
Your agent connects through Kapten. Your applications, databases and network live in your cloud account, with the provider and region you choose.
Your agent
Kapten
Your cloud
- Apps
- Databases
- Network
- Secrets
- Your infrastructureyour cloud bill
- Your workload datain your cluster
- Your choice of regionclose to your users
- Built-in visibilitylogs + metrics
Your first release
Your whole stack.
One release.
A release is more than a container. Put databases, migration jobs and applications in an ordered pipeline. Choose whether a failed stage stops the release or lets it continue.
Know what happened. See where to look.Follow run history, deployment timelines and logs from the same workspace.
- 01
Prepare the data
postgresDatabase - 02
Run the migration
db-migrateJob - 03
Release the app
api + workerApplications
Apps and workers
Deploy container images with resource limits, health checks and persistent storage when you need it.
Databases, included
Run PostgreSQL, MySQL-compatible databases, MongoDB and Redis alongside your applications.
Jobs that fit the workflow
Run migrations before a release, trigger a task on demand or schedule recurring work.
Agent workflows
The jobs a platform team does. Started with a sentence.
Each workflow brings in the right specialists, runs them in parallel and stops where a human should decide. Copy the prompt, change the names, run it.
All 9 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
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
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
How it works
From your first container
to your first release.
Start with one service. Bring your cloud account and a container image; we help you work through setup during early access.
Bring your cloud account
Choose the account and region for your first environment. Review the cloud access needed before connecting it to Kapten.
Set up your first environment
Kapten provisions the platform, networking, logs and metrics. Add your container image, environment variables and a database.
Run your first release
Put the database, migration job and app in order. Run the pipeline, follow each stage and inspect the logs from the same workspace.
Room to grow
Let your app grow.
Keep control of how.
Set the resources your app needs and the replica range it can use. Kapten adjusts stateless app capacity to CPU demand, within the limits you choose.
Minimum replicas for your baseline. Maximum replicas for your ceiling.
Steady at api ×2. Nobody was paged.
Scaling simulation · example data
Before you start
A few practical answers.
Have a question about your stack or cloud access?
Talk to the teamCan I use my own cloud provider?
Yes. Bring the cloud provider of your choice and deploy in your own account. Tell us which provider you use when you request early access so we can help with setup.
What do I need to get started?
A cloud account you control and a container image for your first application. Bring its environment variables and any database or migration requirements. You do not need to connect a cloud account to request early access.
What does early access cost?
The Kapten control plane is free during early access, with no credit card required. Your cloud provider bills you directly for the infrastructure you provision. Cloud usage is billed separately.
Can I bring an existing application?
Yes, start with a container image of your application. Configure its variables, database and jobs in Kapten. Moving existing data and switching traffic require a migration plan; deploying a container does not automatically move your database or cut over your domain.
What access does Kapten need?
Kapten needs cloud access to provision and operate the resources it manages. Review the requested permissions with us before connecting your account. Your apps and databases run in your account; never include cloud credentials in your early-access request.
What happens if I leave?
Your cloud account and its bill remain yours. Leaving also means handing over operation of the resources Kapten manages and removing its access. Contact us to plan that handover before disconnecting; any resources left running continue to incur cloud charges.
What happens after I request access?
We review your request and follow up by email about fit and next steps. Access opens in small batches. During early access, you work directly with the engineers building Kapten on setup and your first workload.
Resources
Learn the part after localhost.
Whitepapers for the argument, guides for the steps, and reference shelves for the words, the trade-offs and the tools.
Whitepapers
The long argument, in 3 papers.
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.