Workflow · Optimise
Monthly cost review
Find idle environments, oversized nodes and orphaned resources, and get the expected saving for each change before you make it.
When to use it
The cloud bill went up and nobody can say why, or you want a monthly habit that keeps it from happening.
- Specialists
- 4
- Stages
- 4
- Tier
- Plan → Act
- Duration
- Minutes
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 agentReview last month’s spend for every environment. Find what is idle or oversized and tell me what I would save by fixing it.You ask
› Review last month’s spend for every environment. Find what is idle or oversized and tell me what I would save by fixing it.
Stage 1 · 2 agents in parallel
PurserCost
Break down the bill
Spend by environment and service, with the month-on-month change and its cause.
LookoutObservability & incidents
Measure actual usage
CPU, memory and traffic over the period, to separate busy from merely big.
Stage 2
PurserCost
Find the waste
Idle previews, oversized node pools, unattached volumes, old snapshots and chatty egress.
Stage 3
KaptenOrchestration
Savings plan
Each change with its expected saving and its risk. You pick which ones to apply.
Gate 01 · stops for your approval
Choose which savings to apply
Stage 4
BosunInfrastructure
Apply what you chose
Rightsizes and cleans up the resources you approved, nothing else.
You get
- A cost breakdown with explanations
- A savings plan with expected impact
- Updated budget caps
Related guide
What a small SaaS really costs on AWS
More workflows
Keep the crew busy.
Get ready for a launch
Before a launch or a press day: find the first thing that will break under load, set sensible autoscaling and caps, and rehearse the rollback.
› We launch on Tuesday and expect 20× our usual traffic. Find what breaks first, set autoscaling and make sure we can roll back fast.
- Navigator
- Lookout
- Bosun
- Purser
- Helmsman
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.
› 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
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.