Workflow · Ship

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.

When to use it

You built something that works on your machine and want it live, properly, without becoming an infrastructure engineer first.

Crew constellation: Kapten at the centre, linked to Navigator, Shipwright, Bosun, Purser, Warden, Helmsman.NavigatorStage 1ShipwrightStage 2BosunStages 2 · 5PurserStage 2WardenStage 3HelmsmanStage 6Kapten1 step · orchestrates
Kapten briefs each specialist in stage order and merges what they send back.
Specialists
7
Stages
6
Tier
Plan → Act
Duration
Typically one sitting

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 agent
prompt
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.
Simulated run
  1. You ask

    › 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.

  2. Stage 1

    • NavigatorArchitecture

      Map the application

      Detects the web app, API, worker and the Postgres and Redis they expect. Lists the environment variables the code reads.

  3. Stage 2 · 3 agents in parallel

    • ShipwrightBuild & containers

      Make it buildable

      Writes a Dockerfile per service, pins base images and opens a pull request with the changes.

    • BosunInfrastructure

      Plan the infrastructure

      Plans the cluster, network, managed Postgres, a bucket and the secrets, tagged and scoped to this environment.

    • PurserCost

      Estimate the bill

      Prices the plan line by line against your budget and flags anything that would push past it.

  4. Stage 3

    • WardenSecurity review

      Review exposure

      Checks which endpoints are public, that the database is private and that no secret is baked into an image.

  5. Gate 01 · stops for your approval

    Merge the Dockerfile pull request

  6. Stage 4

    • KaptenOrchestration

      One plan for your approval

      Merges everything into a single plan: resources, releases, cost, findings. Nothing has changed yet.

  7. Gate 02 · stops for your approval

    Approve the merged plan (resources, cost, findings)

  8. Stage 5

    • BosunInfrastructure

      Provision

      Applies the approved infrastructure plan through the scoped role in your account.

  9. Stage 6

    • HelmsmanReleases

      Release and verify

      Rolls out each service behind health checks, attaches the domain and TLS, and confirms it serves traffic.

  10. You get

    • A running production environment in your account
    • A pull request with build files
    • An architecture diagram on the canvas
    • A cost estimate and a security report
    • A one-step rollback

Related guide

You built it with an AI. Here is how to ship it.

Read the guide ↗

More workflows

Keep the crew busy.

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.