Calculate your price.
Set your environments, AWS accounts, workload, release cadence and support cover. You get a monthly estimate, the plan your answers point to, and a line by line breakdown you can carry into a scoping call.
Your setup
Every answer starts on a sensible default. Change only what you already know, the estimate updates as you go.
Anything you deploy to and expect to stay up. Dev, staging, production, per-region copies.
The three plans behind that number
Prices follow the environment count you set above. The highlighted plan is the one your answers point to.
Essential
Pipelines, monitoring, and access control, owned and maintained for teams running a few environments.
- CI/CD pipelines & ongoing maintenance
- Infrastructure as code (version-controlled)
- Business-hours support (weekdays)
- IAM and MFA setup
- Secrets management
- 99.5% monthly uptime target
Growth Platform
For engineering organisations shipping every week that can't afford surprises, in production or on the bill.
- Everything in Essential
- Advanced CI/CD with canary & instant rollback
- Monthly cost-optimisation PRs
- Full observability (metrics, logs, traces)
- Dedicated support lead
- Priority weekday support - 99.9% uptime
Enterprise
Governance, compliance, and high availability for platforms that can't go down.
- HA clusters and DR runbooks
- SOC 2 / ISO 27001 readiness pack
- Monthly game day & roadmap review
- Incident response & RCA - 24/7
- FinOps dashboard & reports
- 50–70 hrs engineering support / month
What this number is, and what it is not.
It is an estimate, not a quote
The figure moves once we see the real estate. We price it properly after a 20-minute scoping call and fix it in writing before any work starts.
Your AWS bill stays yours
Everything here is the Jet1 retainer. Cloud spend is billed to you by AWS, in your own accounts, and we never mark it up.
Enterprise is always scoped
24/7 on-call, SOC 2 or ISO 27001 readiness, HA and DR, or 40 extra hours put you in Enterprise, and those are priced per engagement.
