Managed operations

You keep the cluster. We keep it running.

Managed means we own the pager for the infrastructure we built. Not "we'll look at it during business hours" — actual on-call, actual drills, actual written reports with measured numbers. If an SLA is going to be missed, you hear it from us first.

Tiers

Three levels of coverage

The difference between tiers is how fast we answer, how often we rehearse failure, and whether the response target is contractual. Nothing in a lower tier is a broken promise — it is simply a narrower one.

Essential

99.9% uptime target

from $1,900 /cluster/month

  • Monitoring stack deployed and tuned
  • Business-hours incident response (PT)
  • Monthly patch cycle
  • Quarterly capacity report
Not included
  • Out-of-hours response
  • Failover drills

Mission-Critical

99.99% uptime target

from $7,900 /cluster/month

  • Everything in Business
  • 24×7 follow-the-sun response
  • Contractual 15-min response target
  • Monthly chaos drill
  • Dedicated runbook ownership
  • Capacity headroom guarantee

GPU / HPC node management

from $220 /GPU node/month

Priced per node, not per GPU card. Includes driver/fabric health, scheduler tuning, and utilisation reporting.

Retainer / emergency support

from $4,000 /month

A prepaid hour pool you can drain anytime. For teams who build themselves but want a senior engineer one message away.

Definitions

What the words in an SLA actually mean

SLAs are usually written in language that means less than it appears to. These are our definitions, stated before you sign rather than after something goes wrong.

What counts as a cluster
A set of devices or nodes that share a fate and are operated as one unit: a Kubernetes cluster, a database cluster, a Ceph cluster, a firewall HA pair, a switch stack or MLAG pair, a router pair, or a SAN fabric. We price per cluster per month, so a dual-fabric SAN with two firewalls in front is three line items — not one, and not zero.
Uptime target
Measured on the cluster control plane and the services we are contracted to keep available — not on your application. Measured monthly, published to you whether or not it was met.
Response target
Time from your alert or call reaching our on-call queue to a named engineer acknowledging and starting work. Not time to resolution — that depends on the fault.
Maintenance window
Planned work is done in a window you approve. Planned maintenance does not count against the uptime target; unplanned does.
Excluded from SLA
Customer-initiated changes, upstream carrier failures, hardware faults awaiting vendor RMA, and anything caused by systems outside the contracted scope. We list them because every SLA has them.
Quarterly drill
A rehearsed failure: real failover, real restore, or real node loss, executed in a window, with a written report including measured timings — including when the result was worse than expected.
Recurring work

What actually happens every month

Managed work is not reactive only. Here is the recurring schedule by tier — the drills are the part that separates a real operations practice from a monitoring subscription.

Essential

  • Monthly patch cycle
  • Quarterly capacity report

Business

  • Quarterly failover drill + report
  • Quarterly restore-from-backup drill
  • Monthly patch cycle
  • Quarterly capacity report

Mission-Critical

  • Monthly chaos drill
  • Quarterly failover and restore drills
  • Monthly patch cycle with rollback rehearsal
  • Capacity headroom guarantee

Measured, not promised Median first response and quarterly drill outcomes are published on our status page. If we miss, you see the miss — that is the point of publishing.

Hand over the pager

If you already have a cluster that needs looking after, start with an audit. We'll tell you what condition it is in and what it would take to run it properly.