A written SLA
Response and restoration targets by severity, agreed in advance, with the hours we actually staff rather than an aspirational number.
Managed Support
The team that built it also keeps it up.
Software does not stop needing attention at launch. We take the pager for systems we built and, after a review, for systems we did not.
What you get
A named engineer
Someone who knows your system by name, with a documented second so a holiday is not an outage.
Runbooks before incidents
The failures we can predict get written up and rehearsed while nothing is on fire.
Monitoring that pages a human
Alerts tuned to symptoms your users feel, routed to on-call. Noisy alerts get fixed or deleted, never muted.
Patching and upgrades
Dependency and platform updates on a schedule, in staging first, with a rollback path. Not a rushed sprint after a CVE lands.
A monthly written report
What broke, what we changed, what the cloud cost, and what we recommend next. Two pages, sent whether or not anything went wrong.
Stack we use
PagerDuty · Grafana · Prometheus · Sentry · Datadog · Docker · Kubernetes · Terraform · AWS · GCP · Cloudflare · Rockit Desk
Engagement shapes
How this work is usually bought
Support retainer
Agreed hours each month against a written SLA.
On-call cover
Out-of-hours response for named severities.
Takeover review
Paid assessment before we agree to own anything.
Tell us what is on fire, or what might be
Send the architecture, the alerting you have today, and who currently gets woken up. We will come back with what a realistic SLA looks like.
or email hello@siyon.co.nz