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, so your team can focus on shipping.
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
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 workflow preview
Talk to your infrastructure.
Ask your agent to deploy a service. Follow it as it finds the environment, starts the deployment and watches the rollout.
Switch between Claude Code and Codex to see the workflow in each client.
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.
From the blog
How we think about running other people’s clouds.
BYOC is not self-hosting
The two get used interchangeably and they are opposites: one hands you the operational burden, the other hands you the account it runs in.
What a scoped role actually scopes
Every BYOC vendor says "least privilege". Here is the specific IAM shape Kapten asks for, why each permission is in it, and what it cannot reach.
The deploy should be boring
Health-gated rollouts, addressable images and rollback as a re-point rather than a re-run — the small decisions that make a deploy stop being an event.
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.