Infrastructure provisioning

Start with the foundation. Then ship the product.

Kapten brings infrastructure setup and application delivery into one workflow. Build on Kubernetes in your own account, with a clear home for each service and environment.

Request early accessExplore the demo
Kapten MCPWith Bosun, Navigator, Warden and 1 more

Diagram: inside your cloud account, a network with a load balancer, a Kubernetes cluster with three nodes, and managed Postgres, Redis, object storage and secrets. Bosun’s plan applies 23 resources.

Illustrative · sample environment. Resources depend on your provider and are confirmed during onboarding.
Runs in
Your cloud account
Foundation
Kubernetes + managed data stores
Changes
Plan → approve → apply
Owned by
Bosun, with Purser and Warden

Inside the product

An environment your team can build on.

Interface previews
Illustrative · sample data · Early access

  • 01

    Start in your own account

    Make account ownership and deployment location part of the setup. Keep the foundation alongside the rest of your cloud infrastructure.

  • 02

    A foundation for the whole app

    Bring the services and dependencies your product needs into one environment. Start with a complete application shape.

  • 03

    See the setup progress

    Follow the stages of preparing an environment. Know which part is ready and where attention is needed before deploying the app.

  • 04

    Keep configuration deliberate

    Identify the ports, resources and values each service needs. Give every environment its own configuration before the first release.

  • 05

    Bring an existing cluster

    External cluster registration is part of the platform design. Review compatibility and the connection method with the team during onboarding.

  • 06

    Build on familiar foundations

    Kubernetes provides the workload foundation. Keep the shape of the infrastructure understandable to the people who will maintain it.

See it in context

An environment you can understand.

Choose where your infrastructure lives. Your team retains control of the account, the resources and the cloud relationship as the application grows.

kapten / infrastructureEnvironment preview

Commerce / staging

Your application has a home.

Example workspace
Project
Commerce

Your application

Environment
Staging

Isolated configuration

Cluster
Connected

Customer infrastructure

Environment components

4 components
  • ◇storefrontWeb service2 replicas
  • ◇payments-apiApplication3 replicas
  • ◇jobs-workerBackground worker1 replica
  • ◇postgresDatabasePersistent

Deployment context

Infrastructure owner
Your organisation
Connection
External cluster
Application source
GitHub repository
Configuration
Environment scoped
Illustrative · sample data. No live cloud connection.Open the interactive demo

Early accessInfrastructure provisioning is evolving during alpha. Early-access onboarding confirms the supported connection method, provider and cluster setup for your project.

Bosun’s plan

Read the diff.
Then approve it.

Every change to your account starts as a dry-run: the exact resources, their settings, what they cost and what the security review found. Nothing is created until you approve the plan.

  • 01

    Tagged and scoped

    Every resource carries its project and environment, so the inventory of what Kapten created is one filter away in your console.

  • 02

    Priced before it exists

    The Purser prices the plan line by line against the budget you gave, and says which line would push past it.

  • 03

    Reviewed before it is exposed

    The Warden checks that data stores stay private and that no secret is baked into an image, all before the first apply.

Meet BosunGuardrails for infrastructure agents
Bosun · plan #142Plan · dry-run
  1. plan_environment production --region eu-west-3
  2. +network.vpc10.0.0.0/16 · 3 zones
  3. +network.subnets3 private · 3 public
  4. +network.nat_gateway1 · shared egress
  5. +cluster.kubernetesv1.31 · 3 nodes
  6. +cluster.ingressload balancer · TLS
  7. +data.postgresmanaged · private · backups
  8. +data.redismanaged · private
  9. +storage.bucket["uploads"]versioned · private
  10. +secrets.app[4]values never echoed
  11. ~dns.record["api.example.com"]→ load balancer
  12. Plan: 9 to add, 1 to change, 0 to destroy.
  13. Purserest. 138 €/month · budget 150 €
  14. Warden0 public data stores · 0 secrets in images
  15. Waiting for your approval. Nothing has changed yet.
Illustrative · sample plan and prices. Supported providers and resources are confirmed during onboarding.

What lands in your account

  • Network

    • VPC across zones
    • Private and public subnets
    • Egress gateway
    • Load balancer

  • Compute

    • Kubernetes cluster
    • Node groups
    • Ingress and TLS
    • Autoscaling bounds

  • Data

    • Managed Postgres
    • Managed Redis
    • Object storage
    • Backup settings

  • Access

    • Secrets store
    • Scoped operator role
    • Resource tags
    • Plan history

With your crew · Kapten MCP

Describe the environment. Read the plan. Then approve it.

Kapten MCP puts a crew of specialists inside the coding agent you already use. On Infrastructure provisioning, these are the ones on watch. They read and plan freely; anything that changes your infrastructure waits for your approval.

Meet the whole crew

  • BosunInfrastructureLeads

    Plans the cluster, network, databases and secrets in your account, tagged and scoped.

  • NavigatorArchitecture

    Maps what the application expects before anything is planned.

  • WardenSecurity review

    Keeps databases private and checks the IAM scope of the plan.

  • PurserCost

    Prices the plan line by line before it is applied.

Your agentClaude Code · Claude Desktop · Cursor · VS Code

Try asking

Plan a staging environment for this repo on my AWS account in eu-west-3: managed Postgres, private networking, under 80 €/month. Show me the plan before you create anything.

  1. Kapten splits the request between Bosun, Navigator, Warden and Purser.
  2. Bosun plans the cluster, network, databases and secrets in your account, tagged and scoped.
  3. Navigator maps what the application expects before anything is planned.
  4. Warden keeps databases private and checks the IAM scope of the plan.
  5. Purser prices the plan line by line before it is applied.
  6. Plan ready. Nothing changes until you approve it.

Observe & Plan · no approvalAct · your approvalIllustrative run · early access

Workflows that use it

How it works

A foundation, built around your application.

Each station names the crew member that owns it. Diamonds are gates: the run stops there until a person decides.

  1. Bring the application shape
    Navigator
    Identify the services, data stores and external dependencies.
  2. Agree the connection
    Bosun
    Confirm the supported account or cluster setup during onboarding.
    Gate: Plan approved
  3. Prepare the first environment
    Bosun
    Set configuration and ownership before deploying a real workload.
Infrastructure provisioning, step by step. Early-access behaviour, confirmed during onboarding.
Want the long version?Postgres in production: the checklist

Deep dive

The ideas behind it.

  1. Keep the account yours

    Choose where your infrastructure lives. Your team retains control of the account, the resources and the cloud relationship as the application grows.

  2. Give services a common foundation

    Bring application workloads and their dependencies together on Kubernetes. Keep infrastructure decisions connected to the applications they support.

  3. Make ownership visible

    Organise work around projects and environments, so a developer can tell where a service belongs before making a change.

Good to know

A little more
before you start.

Have a particular application or setup in mind? Bring it to the early-access conversation.

Talk through your setup
Can I bring an existing cluster?

The platform specifications include external Kubernetes cluster registration. Share your current setup when requesting access so we can check compatibility.

Which clouds can I use?

AWS is the focus of the website’s alpha experience. Other providers appear in the roadmap; availability is confirmed during onboarding.

Will I see what gets created before it exists?

Yes. Bosun produces a dry-run plan first: the resources, their settings, an estimated cost from the Purser and the Warden’s exposure review. Nothing is created until you approve that plan.

How do I find what Kapten created in my account?

Resources are intended to carry project and environment tags, so you can list them from your own cloud console. Confirm the tagging scheme for your account during onboarding.

Keep exploring

One part of a bigger picture.

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.

Request early access Explore the demo

Free during early access. No card required. Cloud usage billed separately.