Alerts nobody sees
The pager fires at 3 a.m. in your timezone. Customers notice before anyone on the team does.
Night-shift on-call for startups and SaaS without an SRE
When an alert fires at 3 a.m., we pick it up. We triage it, fix it if it is safe and approved, or wake the right person with the facts already written down. Every morning you get a short report of what happened overnight.
5xx rate above 4% on /checkout for 5 min.
First assessment posted in your channel.
Runbook step 3: roll back last deploy. Approved in advance.
Timeline, cause, and follow-ups for your team.
The problem
Small teams without an SRE usually end up with the same three nights on repeat.
The pager fires at 3 a.m. in your timezone. Customers notice before anyone on the team does.
One or two people carry every night. Sleep gets worse, and so does the daytime work.
Flaky alerts train people to ignore the pager, until the one alert that mattered.
Services
Scope is capped on purpose, so it stays predictable for both sides.
Anything outside the scope is quoted hourly up front, and only done if you say yes.
How it works
No calls needed. Email, Slack, and written reports.
Tell us your stack, your timezone, and what currently wakes people up.
We sign your NDA (or send ours) before we ask for any access.
Dashboards, logs, alerting. Nothing that can change production unless you decide otherwise.
What counts as urgent, who to escalate to, what we may fix on our own.
Alerts route to us. You get a written report each morning.
If we miss it, that month is free. Response means a human has looked at the alert and posted a first assessment in your channel.
No calls needed. Email, Slack, and written reports.
Changes only with your explicit approval.
Signed before we see a single log line.
No lock-in. The first month is free.
Sample audit
Before a trial we can run a free external check: only what anyone on the internet can see. No access needed. Here is an anonymized example of what comes back.
| Severity | Finding | Suggested fix |
|---|---|---|
| High | API origin host reachable directly, bypassing the CDN, and returns server version banners. | Allow origin traffic only from the CDN; hide version headers. |
| Medium | DMARC set to monitor-only (p=none) with no reporting address, so spoofing goes unseen. | Add a report mailbox, check alignment, then move to quarantine. |
| Medium | Missing security headers: no Content-Security-Policy, no frame protection. | Add CSP and frame-ancestors / X-Frame-Options. |
| Medium | SLA advertised on the pricing page, but no public status page. | Publish a status page fed by real uptime checks. |
| OK | TLS configuration is sound: modern protocols and a valid certificate. | Nothing to do. |
Pricing
The trial is the same service as a paid month. No card needed to start.
Trial
Free for 1 month
After the trial
Written quote
Read-only access to monitoring, logs, and alerting, granted after an NDA is signed. Use separate accounts or scoped tokens so you can see and revoke our access at any time. We do not ask for production write credentials by default.
With read-only access, we can't. Any change happens only with your approval, following steps written down in advance in the runbook. If something is unclear at night, we escalate rather than guess.
Yours. We agree the night-shift hours for your timezone in writing before the trial starts. The 15-minute response promise applies inside those hours.
One month, free, same service as a paid month. No card needed to start. At the end you decide to continue or not; if not, we hand back access and delete what we hold.
No. Everything works over email, Slack, and written reports. A call is fine if you want one, but it is never required.
Email us with your stack and timezone. We reply in writing.