OpsAct vs ilert AI SRE
ilert is a German incident management platform: paging, on-call schedules, call routing and status pages. Its AI SRE investigates alerts inside that platform. OpsAct does no paging. It maps your estate, investigates and runs approved fixes, so the two can work side by side.
At a glance
| OpsAct | ilert AI SRE | |
|---|---|---|
| Where it runs | A control plane hosted in the EU, plus small agents on your sites that only dial out | ilert’s cloud, built and hosted in Germany |
| Where your data is processed | EU only. Credentials and raw data stay on your sites | For EU customers, AI runs on dedicated servers in Frankfurt and Stockholm |
| What it covers | Hybrid estates: VMware, Windows and Linux servers, databases, network switches, Kubernetes and cloud | Investigates from any alert using logs, metrics, recent changes and past incidents; 150+ integrations |
| Discovery and dependency map | Built in. Finds what you run and maps what depends on what, before any incident | Not stated on the pages we checked |
| Fixes | Runs fixes from reviewed runbooks, shown as flowcharts with every step’s risk labelled | Proposes a next action backed by evidence. Approved actions (its L2) and bounded autonomy (L3) are not yet enabled |
| Approval before changes | Every change to production waits for a person. More autonomy is earned per runbook | Nothing changes in production without explicit approval; every step is logged |
| Learning from past incidents | Remembers past incidents and turns approved fixes into runbooks | Uses past incidents in its investigations |
| DORA and NIS2 reports | Drafts DORA and NIS2 incident reports for a person to check and send | Not stated on the pages we checked |
| Pricing | A platform fee by estate size, from €1,500 a month for up to 250 systems, investigations included | Free plan to start; see ilert’s pricing page |
Where OpsAct differs
A map before the incident
OpsAct discovers what you run and how it connects before anything breaks, so an investigation starts from the checkout path, not from a single alert.
Fixes that run, not only suggestions
OpsAct runs the fix from a reviewed runbook once a person approves it, checks each step and records the change. ilert’s product page lists approved actions as not yet enabled.
Estates that aren’t all cloud
VMware, Windows servers, databases and switches are first-class in OpsAct, with runbooks for each.
The regulator report
OpsAct drafts DORA and NIS2 reports from the incident record.
Which one fits
Choose ilert when
- You want paging, on-call schedules, call routing and status pages in one product.
- You want AI investigation inside the tool your on-call team already uses.
- Suggestions are enough and you don’t need fixes run for you yet.
Choose OpsAct when
- Your estate includes VMware, Windows, databases or switches.
- You want fixes run from reviewed runbooks, with a person’s approval.
- You need DORA or NIS2 report drafts.
- You want OpsAct to discover and map what you run.
Using them together
Use both: ilert wakes the right person, and OpsAct has the investigation and the plan ready when they open it. ilert can forward alerts to OpsAct by webhook.
Sources
Facts about ilert AI SRE come from these pages, checked on 13 October 2026. Products change; if something here is out of date, tell us at hello@opsact.eu and we’ll fix it.
See what it would have found last month
We replay a month of your alerts through OpsAct and walk you through what it finds.