A whole SRE team for less than one SRE hire.
One flat monthly fee for 24/7 cover by in-house SREs, plus reliability work each quarter.
What you pay.
The fee stays flat however noisy your alerts get.
- Hours in a week
- 168
- Shifts to cover them
- 21
- SREs to hire, at least
- 4–5
Flat monthly fee, from
S$1,500
A month, for up to 5 production services.
A production service is something your users depend on that’s deployed and alerted on separately, such as an API, a web app or a database.
We quote for more than 5 services on the 20‑minute call. Prices are in Singapore dollars.
Billed monthly. Three-month minimum, then either side can end it with 30 days’ notice.
The 21 shifts are day, evening and night, seven days a week. Four to five SREs is the fewest who can fill them in-house, with no slack for leave or sickness; for a team in one location that covers nights, we’d want at least eight on the rota to keep on-call sustainable. What 24/7 on-call takes
What the fee covers, and what it doesn’t.
Included
- 24/7 cover by in-house SREs
- Every alert acknowledged within 15 minutes and assessed within 30, in your contract
- AI investigation of every alert
- Runbooks you’ve approved, with every run logged
- A likely cause for every alert and a written report on the contributing factors for every incident
- One or two reliability goals each quarter, each with a target and a date
- Monthly service report, walked through with your team, and a quarterly review
- Onboarding: a one-page service charter, a gap review of what your alerts can’t see, and a starter pack of runbooks for your approval
- No licence markups, no agent fees
Not included
- Fixes for new issues: they go to your team with the evidence
- Cover for on-premises production
- Changes to production you haven’t approved
- Projects, which are quoted separately at a fixed fee
How your options compare when an alert fires at 2am.
Whoever you choose, ask to see the response times in the contract.
| Option | Who makes the call | Response time | Work on why alerts happen | Cost | The catch |
|---|---|---|---|---|---|
| Tracefox | An in-house engineer, with AI doing the legwork | 15 min to acknowledge, 30 to assess, in your contract | Included: one or two goals each quarter, with targets and dates | From S$1,500 a month, flat | Cloud only. New issues go to your team with the evidence. |
| Hire SREs in-house | Your own SRE on the rota | Whatever your rota can sustain | If the rota leaves them time | 4–5 salaries to staff 21 shifts; at least eight to keep the rota sustainable | Slow to hire; leave and resignations open gaps in the rota. |
| Cloud MSP | A support desk, often across many services | Varies; check whether it’s in the contract | Ask whether it’s included or a separate project | Usually a custom quote | Broad service menus; production reliability is one line item among many. |
| AI-SRE tool | Software, escalating to your engineers | Software triage; no engineer on shift for you | Your team does it, with the tool’s data | Software fee, plus your team’s time | Your engineers still carry the pager when it escalates. |
| Do nothing | Whoever wakes up | None | When someone finds the time | No direct cost | Overnight incidents found late; a few engineers take most of the pages. |
Money and contract questions.
Access, AI and fit are answered on the questions page. All questions and answers
What counts as a production service?
Something your users depend on that is deployed and alerted on separately, such as an API, a web app, a background worker or a database. We agree the list with you in the service charter before cover starts. If you’re not sure how many you have, a rough number is fine for the call.
What if our alerts are very noisy?
At onboarding we agree a normal alert volume for your services. If it stays well above that, we run a joint clean-up with your team and the fee stays the same.
What happens if an incident runs for days?
We stay on it for as long as it’s open: watching, keeping your channel updated and keeping the timeline for the report. Engineering work to fix the underlying cause sits with your team, or with a project if you’d like us to do it, and we agree that in writing before any extra work is billed.
When does billing start?
When cover starts. The 20-minute call and the service charter come before that and cost nothing.
Is there a minimum term, and how do we leave?
Cover is billed monthly. After the first three months, either side can end it with 30 days’ notice. Leaving is deleting the identity you created, and the runbooks and documentation we wrote for you stay with you.