Fluidify · RegenAI-native incident management
Free forever
Replace PagerDuty or Grafana OnCall open-source, self-hosted, no per-seat taxAI triage agent investigates before your phone rings
Root cause found
before on-call was paged
Everything you need None of the lock-in
Grafana OnCall is archived · PagerDuty charges per seat
Regen is open-source, self-hosted, and built for the AI era
| Feature | Regen | PagerDuty | Grafana OnCall |
|---|---|---|---|
| Open source | |||
| Self-hosted | |||
| Per-seat pricing | |||
| AI triage agent | |||
| Actively maintained | |||
| Slack-native incidents | |||
| One-click Grafana OnCall import | |||
| MCP / AI agent integrations | |||
| Air-gap / offline mode |
Grafana OnCall marked archived March 2025. AI features in Regen ship Q3 2026.
From alert to resolution end to end
Regen handles the full incident lifecycle triage, escalation, response, and post-mortem.
Alert fires
Webhook arrives from Prometheus, Datadog, Grafana, PagerDuty, or any monitoring tool. Regen ingests it and opens an incident record instantly.
AI triage
Q3 2026The triage agent queries your observability stack through MCP — pod logs, recent deploys, error traces, dashboards. It surfaces a probable root cause before anyone is woken up.
Smart escalation
The right on-call engineer is paged via Slack, SMS, or voice. Escalation policies define who gets notified and when if there's no acknowledgement.
Runbook execution
Q3 2026Co-pilot mode: the agent proposes runbook steps, you approve each one. Every action is logged to the incident timeline with full audit trail.
Auto post-mortem
Once resolved, Regen drafts a post-mortem from the incident timeline — what happened, when, who acted, and what the AI found. Publish with one click.
On-call and incident management, without the per seat tax
Everything Grafana OnCall had plus an AI agent that investigates before you wake up
On-call schedules & rotations
Layer-based schedule model, shift types, override support. Import from Grafana OnCall in one step.
Escalation policies
Multi-step escalation paths with configurable timeouts. Pages the right person, every time.
Slack & Teams native
Incidents live in your existing channels. Dedicated incident channels, bot commands, status updates.
AI triage agent
Calls your observability stack through MCP: Datadog, Kubernetes, GitHub, before your phone rings.
Incident timeline
Immutable, agent-and-human timeline for every incident. Full audit trail from alert to resolution.
AI BYOK
Bring your own OpenAI or Anthropic key. AI features run under your credentials, zero incident data leaves your infrastructure.
Post mortem & handoff digest
Timeline auto-drafts the post-mortem the moment an incident closes. Handoff digest catches the incoming on-call up in seconds.
Slack pre-investigation
Before paging anyone, the agent scans channel history and past incident timelines for correlated failures, surfacing patterns humans miss.
Plugs into your existing stack
Connect your alerting, observability, and communication tools in minutes. No ripping out your stack.
Slack
Comms
Microsoft Teams
Comms
Prometheus
Alerting
Grafana
Alerting
Datadog
Observability
PagerDuty
Migration
GitHub
Engineering
GitLab
Engineering
Kubernetes
Infrastructure
Opsgenie
Migration
Alertmanager
Alerting
Webhook
Custom
Any tool that sends a webhook works out of the box. More native integrations shipping continuously.
Deploy anywhere in minutes
Fluidify Regen is fully open-source. Run it on your Kubernetes cluster, a Docker Compose stack, or spin it up locally in seconds. Your data stays on your infrastructure.
- Docker Compose quick start up in under 5 minutes
- Helm chart for Kubernetes with TLS + ingress
- Published image on ghcr.io/fluidifyai/regen
- No vendor lock-in your infra, your data
git clone https://github.com/FluidifyAI/Regencd Regencp .env.example .env# Edit .env with your values, then:docker compose up -d# Open http://localhost:8080
Start using Fluidify today
Deploy Regen in minutes. Let AI handle the noise so your team can focus on building.
Deploy in under 5 minutes. · AGPLv3 · Self-hosted on your infra