We run your deploys, AWS, and on-call. You ship.

Jet1 is a senior DevOps team that owns your delivery platform under a written SLA. Everything lives in your repos and your cloud accounts, so you stay in control and never get locked in.

Month to month. No long-term contract, no lock-in.

  • 15+ engineering teams
  • Uptime SLA up to 99.95%
  • SOC 2 and ISO 27001 readiness
Proof, not promises

Measured on a freight platform that never closes.

Deploy downtime
0s

Was 45–120 s on every release

Rollback
<90s

Was 15–30 min, by hand

API latency
121ms

Was 310 ms on average

Errors under load
0.1%

Was 3.8%

99.97% uptime over 90 days. FTL Transport now ships several times a week, with no maintenance windows and nobody on standby.

Read the case study
What changes

Three problems. One team that owns them.

What engineering leaders tell us on the first call, and what it looks like a month later.

“We deploy at night, just in case.”

Ship on a Tuesday afternoon.

Push to main. Tests run, traffic shifts only when health checks pass, and a bad release rolls itself back in under 90 seconds.

  • No maintenance windows, nobody on standby
  • Every environment built from the same code
Release pipeline on every merge to main

Commit

A pull request opens. Linting, unit tests, and a security scan run before a human spends time reviewing it.

Trigger: pushGate: tests and scan pass

Build

One immutable image is built and signed, then reused unchanged in every environment. What you tested is what ships.

Artefact: signed OCI imageRebuilt per environment: no

Stage

The image is deployed to an environment built from the same code as production, so differences are configuration, not surprises.

Environment: from codeDrift: none

Canary

Traffic shifts in steps, 5%, 25%, 100%, and only moves on when latency and error rates hold. Nobody watches a dashboard to decide.

Steps: 5 / 25 / 100%Gate: health checks

Rollback

If a step fails its health checks, traffic goes back to the previous version automatically in under 90 seconds, then you get told what happened.

Rollback: under 90sHuman needed: no

“The bill doubled and nobody can say why.”

A bill you can defend, line by line.

Your setup moves into code, where waste has nowhere to hide. Every month a cost-review pull request lands in your repo. You approve it, and you see exactly what changed.

  • Right-sizing, cleanup, and reservations
  • Every change reviewable and revertible
cost: right-size staging workers +2 −2
resource "aws_instance" "worker" { - instance_type = "m5.2xlarge" + instance_type = "m5.large" count = 4 - # 30d avg CPU: 8%, peak 21% + # right-sized against 30d utilisation }
Illustrative example of a monthly cost-review PR. Your repo. Your approval.

“Only one person understands our setup.”

Nothing lives in one person's head.

Infrastructure as code in your repos, a runbook for every failure mode, and a whole team that knows your stack. If anyone leaves, including us, everything keeps working.

  • A rota, not a single phone number
  • Handover is a walkthrough, not a migration
Runbook: primary database failover runbooks/db-failover.md
  1. Confirm the symptom. Which alert fired, and what the dashboard shows.
  2. Check replica lag before promoting anything.
  3. Promote the standby using the documented command.
  4. Verify writes and watch error rate for 10 minutes.
  5. Tell the channel, then open the RCA.
One runbook per failure mode. In your repo, owned by you.
How it starts

Live in weeks, not quarters.

No rip-and-replace. We learn your setup before we touch production, and nothing ships without your sign-off.

  1. Day one

    A 20-minute review

    You walk an engineer through how you deploy today, and where it hurts.

  2. Within 48 hours

    Your risk list

    The top delivery risks we'd fix first, in writing. Yours to keep either way.

  3. Week one to two

    First pipeline live

    Built in your repos and your accounts, under your change control.

  4. Every month after

    We run it

    Monitoring, cost reviews, and incident response, backed by the SLA.

Your options

Hire, contract, or hand it to a team?

Sometimes an in-house platform team is the right call. Here is the honest comparison.

Jet1
In-house hire
Contractor
Someone accountable in
Jet1Days
In-house hire3–6 months to recruit
ContractorWeeks, until the project ends
When something breaks
Jet1A team on call, under an SLA
In-house hireOne person, if they're awake
ContractorGone after handover
Documentation
Jet1Runbooks and code in your repos
In-house hireDepends on the person
ContractorRarely happens in practice
If they leave
Jet1Nothing breaks. You own all of it
In-house hireKnowledge walks out the door
ContractorYou start from scratch
Pricing

Flat monthly. Priced up front.

One price per plan, set by how many environments you run. Your AWS bill stays yours.

3 deployable environments
135710+

Essential

Pipelines, monitoring, and access control, owned and maintained.

$ 999 / mo
  • CI/CD pipelines & ongoing maintenance
  • Infrastructure as code (version-controlled)
  • IAM, MFA, and secrets management
  • Business-hours support (weekdays)
  • 99.5% monthly uptime target
Start with a technical review

Enterprise

Governance, compliance, and high availability for platforms that can't go down.

Let's talk
  • Incident response & RCA, 24/7
  • HA clusters and DR runbooks
  • SOC 2 / ISO 27001 readiness pack
  • FinOps dashboard & reports
  • Monthly game day & roadmap review
  • 50–70 hrs engineering support / month
Contact sales
PAY FOR RESULTS

Outcome-based

A lower base, plus a bonus we only earn when the savings show up on your bill.

You save, we earn.

Lower base fee + a share of verified savings

  • Measured against a baseline we agree before work starts
  • Bonus capped and time-limited, so you always know the ceiling
Talk through the numbers
FOR EARLY-STAGE STARTUPS

Tech for equity

Production-grade infrastructure now, before the cash is in the bank.

$ 0 upfront

Fees deferred to your next round + a small equity stake

  • Pay nothing until your next funding round closes
  • Rolls into a normal monthly plan once you've raised
Apply for a fit review

Response times and service credits for every plan are in the Service Level Agreement.

FAQ

What engineering leaders ask before signing.

Alongside them. They keep architectural control and sign-off on everything. We take the pipelines, monitoring, cost reviews, and incident response, so your senior engineers get their real job back.

More than you have now. Everything is set up in your accounts, every change is a pull request your team can read, and nothing reaches production without your sign-off.

NDA before we see anything. Then least-privilege, role-based access: the permissions the work needs and nothing more. Every action is auditable, and secrets live in a secrets manager, not in chat threads.

You keep everything, because it was already yours: the code, the pipelines, the docs, the cloud accounts. We hand over the runbooks and walk your team through them. There is nothing to migrate.

Yes, on the Enterprise plan. We set up the controls, evidence collection, and audit-ready documentation. Because every change is version-controlled and reviewed, audits stop being a quarterly fire drill.
Take off with Jet1

20 minutes. Your top delivery risks, in writing.

Walk an engineer through how you deploy today. Within 48 hours you get the risks we'd fix first. Keep the list whether or not you hire us.

Book a 20-minute review

Not ready for a call? Audit your AWS account yourself.

Preflight is our free, open-source, read-only CLI. It finds what you pay for and don't use, and shows the arithmetic. See our open-source tools

$ curl -fsSL https://jetonecloud.com/preflight | sh