For enterprise

Uptime you can put in a contract.

Your customers expect the platform to stay up. Your auditors expect evidence. Jet1 runs your infrastructure under a written SLA, with tested runbooks and a paper trail for every change.

Reliability & governance

Built to stay up, and to prove it.

High-availability clusters, disaster recovery runbooks, and governance aligned with SOC 2 and ISO 27001. Every deployment is health-checked and reversible, and infrastructure changes happen without downtime windows.

  • 99.95% monthly uptime target
  • 15-minute Sev 1 response, 24/7
  • 50–70 hours of engineering support a month
What each uptime target allows downtime per month
Essential, 99.5%
3 h 36 min
Growth Platform, 99.9%
43 min
Enterprise, 99.95%
Under 22 min
Based on a 30-day month. Targets from the SLA.
What you get

Ready for the next audit. And the next incident.

Response times in writing, evidence on demand, and costs somebody actually watches.

SOC 2 / ISO 27001 readiness

Controls, evidence collection, and audit-ready documentation. The audit becomes a review, not a scramble.

24/7 incident response

15-minute Sev 1 response from engineers with runbooks, not a ticket bot. Post-mortems within 5 business days.

FinOps dashboards

Monthly cost reviews, anomaly detection, and right-sizing. Cloud spend becomes a decision you make, not a number that happens to you.

HA clusters & DR

Multi-AZ active-active, with documented RTO and RPO targets. Game days prove the runbooks before you need them.

Dedicated support lead

A named engineer who knows your stack, not a ticket queue. Monthly roadmap reviews and architecture sign-off.

Compliance & auditability

Every change is version-controlled, peer-reviewed, and traceable. Audits stop being a quarterly fire drill.

Enterprise SLA

Commitments in writing.

Response times, uptime, and on-call coverage are in the contract, with service credits if we miss our own targets. If it isn't written down, it isn't a commitment.

Talk to sales
Enterprise SLA the short version
Monthly uptime target
99.95%
Sev 1 response
15 minutes, 24/7
Sev 2 response
1 hour, 24/7
Sev 3 response
4 business hours
Engineering support
50–70 hrs / month
Service credits
Up to 25%
From the Service Level Agreement. Read it in full
Proof, not promises

The tier FTL Transport runs on.

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 and zero-downtime releases, on a freight platform that never closes.

Read the case study
Take off with Jet1

A DevOps partner for the long haul.

Tell us about your environment. We'll send back an architecture plan and an SLA draft within a week.

Talk to sales