Automatically resolve incidents before they wake your team.
Early-stage prototype. Partnering with 2–3 SRE teams to co-build v1.
Wake up only when it actually matters.
Built by an engineer who's been on-call at 3AM. Targeting PagerDuty, Datadog, Splunk, and Slack for first pilots.
Example: how OnCallLess handles an incident
▸ Simulated demo — not a real system interface
The Problem
Your engineers are waking up at 3AM to fix the same issues repeatedly. The answers are already in your runbooks — no one is executing them fast enough.
Groggy engineers context-switch, dig through dashboards, and re-read runbooks they wrote six months ago. All while the customer is down.
The fix is often already documented in your postmortems and runbooks. But at 3AM, that knowledge is useless if no one can execute it fast.
Painful on-call rotations are a common reason SREs leave. Every unnecessary 3AM page costs you morale, productivity, and the team you spent years building.
How It Works
OnCallLess is designed to plug into what you already have. No rip-and-replace. It learns from your history and acts with your tools.
Connect your runbooks, postmortems, Confluence pages, and internal docs. OnCallLess builds a semantic index of everything your team knows about your systems.
Designed to integrate with your alerting (PagerDuty, Splunk, Datadog), communication (Slack), and the internal tools and scripts your team already uses to resolve issues. Integrations are built per-pilot.
When an incident fires, OnCallLess searches your historical data, matches it to known patterns, and executes the right remediation — or escalates to a human with full context if confidence is low.
Every action is logged. Low-confidence issues get escalated with a ticket and all context attached. Your team reviews in the morning — rested, not reactive.
Integrations
Pilot integrations are built per-customer during onboarding. These are the tools we're targeting first.
Who's building this
I'm Eric Nwagwu — a software engineer with 4 years building backend systems. I built OnCallLess after too many prod-support rotations where the same incidents kept pulling me off real work. The fixes were already known — just manual, repetitive, and annoying. I'm looking for 2–3 SRE teams to pilot with so we can shape v1 together. If that's you, let's talk.
Limited design-partner slots available. We'll reach out within a few business days.