Cost control
Know what you are running. Know who is billing it.
Keep infrastructure usage on your cloud provider’s invoice and the platform relationship separate. Understand the resources behind the bill before deciding what to optimise.
- Infrastructure bill
- Your cloud provider
- Platform terms
- Separate Kapten agreement
- Resource owner
- Your organisation
- Cloud discounts
- Subject to provider terms
Inside the product
A clearer view of the operating cost.
Start with account ownership, resource context and environment lifecycles. Then make capacity decisions with the team that owns them.
Interface previews
Illustrative data · Early access
Keep the cloud invoice direct
Your provider bills the infrastructure in your account. Kapten’s platform fee is a separate part of the operating cost.
Keep your provider relationship
Review cloud credits and committed-use discounts against your deployment. Eligibility and rates remain governed by your provider’s terms.
Know what the spend belongs to
Organise the conversation around services and environments. Resource ownership helps you investigate the bill with the team responsible for it.
Review what is still running
Give temporary environments an owner and an end date. Include storage and resources outside the cluster in the cleanup plan.
Keep the infrastructure you own
Leaving the platform does not change who owns the cloud account. Plan the handover of releases, monitoring and maintenance before disconnecting.
Make capacity a conscious choice
Compare the baseline the application needs with the limits you set. Review capacity and provider costs together as the product grows.
See it in context
The account stays on your side.
The illustrated cloud connection shows the ownership model: Kapten coordinates the work, while infrastructure resources belong to the customer’s account.
git push
Commit 4f2a9c1 lands on main. Kapten's webhook receiver queues a build and resolves the target environment. Nothing has touched your AWS account yet.
Early accessThe connection flow is illustrative. Access methods and supported cost-management controls are confirmed during onboarding; cloud charges follow your provider’s terms.
The workflow
Understand the bill before optimising it.
- 01
Map the resources
Know which services and environments own the infrastructure.
- 02
Review the baseline
Look at provider charges alongside actual application needs.
- 03
Adjust deliberately
Change capacity and environment lifecycles with a named owner.
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 ↗Who charges for the infrastructure?
Your cloud provider bills usage in your account. Kapten’s platform terms are separate; see the pricing page for the early-access offer.
Do cloud credits and discounts still apply?
They follow your provider agreement and resource eligibility. Check the deployment against the terms attached to your account.
Is there a guaranteed cost reduction?
No fixed saving is promised. The result depends on the application, resource sizing, usage patterns and provider pricing.
Connected capabilities
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.
Free during early access. No card required. Cloud usage billed separately.