Saneops correlates and deduplicates alerts from Grafana, Datadog and PagerDuty, then writes the first draft of the RCA. Your L1 stops clicking acknowledge at 3 AM and starts fixing things that matter.
If your team runs a 24/7 NOC or on-call rotation, you already know the pattern. Your L1 spends the night clicking acknowledge instead of fixing anything. Your seniors get paged for the same outage from four monitoring tools. By morning, nobody trusts the pager.
Point any alert source at Saneops via webhook. Grafana, Datadog, PagerDuty, Prometheus, custom JSON. No agents, no SDK, no data leaving your network.
Time-window grouping + content-hash dedup + CEL-based custom rules collapse 800 alerts into a handful of incidents. The first 50 lines of the runbook become unnecessary.
A first-draft RCA is generated for every incident — what changed, what's affected, what to check first. Then it's routed to the right channel via a visual workflow builder.
Every feature exists because a real on-call engineer wished it did at 3 AM.
Time-window + label-similarity grouping with tunable thresholds per tenant.
Same payload arriving from four monitoring tools? One alert, four sources attached.
Filter known-noise alerts with the same expression language Kubernetes uses.
First-draft RCA written for every incident. Bring your own Claude / OpenAI / Ollama key.
8-tab workflow editor — overview, builder, canvas, YAML, inputs, secrets, versions, runs.
Webhook tokens, API keys, SMTP passwords — encrypted at rest with your session key.
No agents to install, no SDK to import. Webhook in, webhook out.
Saneops runs as a Docker container on your own infrastructure. Alert payloads, incident history, runbook content — none of it leaves your network. Not even to us.
SESSION_SECRET.
# 1. Load the image (we send you a tarball) $ docker load -i saneops-beta-protected.tar.gz # 2. Edit two values in docker-compose.yml $ vim docker-compose.yml # 3. Bring it up $ docker compose up -d ✓ Saneops running on http://localhost:8000 Total time: ~10 minutes
I'm taking on ten design partners through the closed beta. You get the full product, free, self-hosted. In exchange: honest feedback, a 30-minute weekly sync, and a chance to shape what Saneops becomes.
Or email omkrjsr29@gmail.com directly.
Saneops is built by Omprakash Kumar from Jamshedpur, India. No VC, no marketing team — just one engineer who got tired of watching on-call rotations burn out good people.
The bet: most alert-fatigue isn't a tooling-volume problem. It's a correlation problem. Once a system can group, dedupe, and explain alerts the way a senior SRE does in their head, the L1 layer mostly disappears.
If that bet's wrong, the beta will tell us in 60 days. If it's right, Saneops becomes the layer between your monitoring and your humans.
Ten beta slots. First-come, first-served.
Apply for the beta