Open-source AI root cause analysis. SerOps reads the logs, metrics, traces, deployments and code changes you already have, and tells you why an incident happened, even when no alert fired.
Or run it yourself, in about 10 minutes:
$ git clone https://github.com/getserops/serops$ cd serops/deploy/quick-start$ cp .env.example .env# then set the three secrets in .env$ docker compose up -d
No signup. No credit card. Logs and code stay on your infrastructure: SerOps reads only the diffs of recent commits, and only redacted context goes to the AI provider you choose.
Nothing to migrate and no agent to replace. Connect your existing tools from the UI.
Which setups have been validated end to end? See tested environments →
SerOps sits on top of your observability stack. It does not store your logs; it reads them when it needs them.
Point SerOps at your log, metric and trace backends, your repositories and your CI/CD. Credentials are encrypted in your own database.
On a schedule you set (every 15 minutes by default) and whenever an alert comes in, SerOps groups new signals per project and environment, collapses duplicate errors and lines them up with recent deployments.
When something changed, the AI model you chose gets the redacted context and returns a root cause, the evidence behind it and a recommended fix. Quiet windows skip the AI call entirely.
Every feature below ships in the open-source release. No paywall, no lite tier.
SerOps looks at the signals themselves, so it surfaces problems nobody wrote an alert for. Already have alerts? Send them in and they join the analysis.
Incidents are matched to when code reached each environment, not just when it was committed, so a slow rollout still points at the right change.
Understands pods, restarts and OOMKills, and aggregates metrics per service so pods moving between nodes don't break the picture. Works on plain VMs too.
Resolved issues become precedent: SerOps suggests similar past incidents and how they were fixed, and drafts a post-mortem you can edit.
Claude, Gemini, OpenAI, DeepSeek, or a local model through Ollama for fully on-premises analysis. Your provider bills you directly; set a monthly budget per organisation.
A sentinel skips the AI call when nothing changed, a thousand identical errors collapse into one line with a count, and the stable part of the prompt is cached by the provider.
Screenshots from the live demo. The same product you self-host.
The dashboard leads with the most severe open issue: why it is happening, what to do, and one click to the issue, the analysis or an investigation of that window.
Explore the live demo
SerOps runs where you deploy it. It queries your providers with credentials you supply, and AI calls go to the provider you choose, with your key. SerOps sends nothing back to us.
Passwords, API keys, tokens and email addresses are masked before any context is sent to an AI provider.
Switch providers per organisation to balance cost and reasoning. Use Ollama to keep everything on your own hardware.
Comparing tools? SerOps vs Datadog Bits AI SRE · SerOps vs Causely · SerOps vs K8sGPT · SerOps vs HolmesGPT · SerOps vs Coroot
Explore a fully populated demo organisation, or clone the repository and have SerOps running on your own machine.