Cross-posted from the Fluidify blog. Disclosure: I work on FluidifyAI Regen.
FluidifyAI Regen is an open-source (AGPLv3) on-call and incident management tool. You run it from a single Docker Compose file, point Alertmanager or Grafana at it, and get schedules, escalation, an immutable incident timeline, and AI-written post-mortems. There is no per-seat pricing on any tier, and no cap on users, incidents, or schedules.
This is a plain overview of what it does and how the three deployment models differ.
Run it three ways
Self-hosted, open source
The community edition is AGPLv3. Docker Compose or Kubernetes, up in under five minutes. Unlimited users, incidents, and schedules. SSO/SAML, Slack, Microsoft Teams, Telegram, mobile push, and BYO-LLM AI post-mortems are all included, not gated behind a paid tier.
Managed SaaS
Same feature surface as self-hosted, plus the dedicated iOS/Android on-call app with Twilio phone calls, RBAC, custom fields, and the multi-language interface. Free for 30 days, then $100/month (Pro) or $200/month (Business). Neither plan charges per user.
Enterprise on your own infrastructure
Forward Deployment Engineers stand up the stack on-prem, in a private VPC, or fully air-gapped, for teams that cannot send incident data to a hosted service.
What it does
Alert ingestion and routing
Ingests from Prometheus Alertmanager, Grafana, AWS CloudWatch, and a generic webhook, plus more. Pattern matching learns from historical incidents, so recurring alerts get recognized and routed without you rebuilding the rule each time.
On-call schedules
Rotations and overrides, with holidays, exceptions, and leave as first-class concepts rather than manual swaps. Global timezone support shows each person their own local hours on a follow-the-sun rotation. Interface available in multiple languages, including Chinese and Spanish.
Escalation policies
Multi-step escalation with per-step timeouts. No acknowledgement inside the window, it moves to the next person or team automatically.
Incident lifecycle with an immutable timeline
Every incident runs through a defined lifecycle with a commander assigned at creation. The timeline is immutable: every acknowledgement, status change, note, and Slack message is recorded in order and cannot be edited after the fact. That is what makes the post-mortem trustworthy and the audit trail real.
Slack and Microsoft Teams
Bidirectional sync with both. Slack gets channels, bot commands, and timeline sync. Microsoft Teams gets Adaptive Cards and bot commands. Actions taken in chat land on the incident timeline, and incident updates show up in chat.
AI post-mortems and digests
Generates incident summaries, post-mortems, and shift-handoff digests from the timeline, then posts them to Slack or Teams. It uses a model key you bring: OpenAI, Anthropic, or a local Ollama instance. Your incident data goes to the provider you choose, or stays on your own hardware with Ollama. Included on every tier, self-hosted build included.
Notifications
Telegram and mobile push for Android and iOS via Firebase Cloud Messaging on every tier. Managed SaaS and Enterprise add the dedicated on-call app and Twilio phone calls.
Identity
SSO/SAML 2.0 with Okta, Azure AD, Google Workspace, or any compliant IdP. On the free tier, not held back for a paid one.
What each deployment includes
| Capability | Self-hosted OSS | SaaS | Enterprise |
|---|---|---|---|
| No limits on users, incidents, schedules, AI | Yes | Yes | Yes |
| Incident lifecycle with immutable timeline | Yes | Yes | Yes |
| Escalation policies with multi-step timeouts | Yes | Yes | Yes |
| Alert ingestion: Prometheus, Grafana, CloudWatch, webhook | Yes | Yes | Yes |
| Pattern matching and learning from historical incidents | Yes | Yes | Yes |
| Schedules, rotations, overrides, holidays, leave | Yes | Yes | Yes |
| Global timezone support | Yes | Yes | Yes |
| SSO / SAML 2.0 | Yes | Yes | Yes |
| Slack integration | Yes | Yes | Yes |
| Microsoft Teams integration | Yes | Yes | Yes |
| AI summaries, post-mortems, handoff digests | Yes | Yes | Yes |
| BYO LLM key: OpenAI, Anthropic, Ollama | Yes | Yes | Yes |
| Telegram notifications | Yes | Yes | Yes |
| Mobile push, Android and iOS via FCM | Yes | Yes | Yes |
| Multi-language interface | No | Yes | Yes |
| Dedicated iOS/Android on-call app | No | Yes | Yes |
| Twilio call support | No | Yes | Yes |
| RBAC and custom fields | No | Yes | Yes |
| Full integration stack | Limited | Complete | Complete |
| On-prem, private VPC, or air-gapped deployment | Self-managed | No | Yes |
| Custom SSO / SCIM, redaction, MFA, audit logs and traces | No | No | Yes |
No per-seat pricing
Every SaaS competitor in this category charges per user or per responder: PagerDuty, incident.io, Opsgenie, xMatters, FireHydrant, Rootly, Splunk On-Call, Squadcast, HyperPing, and Grafana OnCall. At a 100-engineer team, that difference is worth an estimated $50k per year for Regen alone. Treat that as an estimate tied to a 50 to 60 member team size. The self-hosted edition has no seat limit and no billing attached to it at all.
Who it fits
- Teams whose on-call bill scales with headcount. Paying per responder for PagerDuty, Opsgenie, incident.io, or similar, and the gap grows with every hire.
- Slack-first or Teams-first incident response. The response happens in chat and the timeline stays accurate without anyone copying updates back and forth.
- Teams that stopped writing post-mortems because nobody has time. Regen drafts them from the immutable timeline.
- Enterprises with air-gap or compliance requirements: SOC 2, HIPAA, GDPR, the EU AI Act, DPDPA.
Poor fit: solo developers or hobby projects with no rotation, or teams that want their observability platform and their on-call tool to be the same product. Regen does on-call and incident management and integrates with the monitoring you already run.
Compliance
Built to SOC 2, GDPR, DPDPA, EU AI Act, and HIPAA guidelines. The Enterprise tier adds custom SSO and SCIM provisioning, redaction protocols, MFA, and audit logs with traces. The air-gapped deployment exists for teams that cannot send incident data to a hosted service under any circumstances.
FAQ
Is Regen open source? Yes. The self-hosted community edition is AGPLv3.
Is there a free version? Two. The self-hosted build is free permanently. The managed SaaS is free for the first 30 days.
Does the free tier include AI features? Yes. BYOK AI post-mortems and summaries are in the self-hosted build. Higher-volume managed AI features scale by paid tier via credits.
Can I self-host? Yes. Docker Compose or Kubernetes, under five minutes. Unlimited users, incidents, and schedules.
Does Regen do root cause analysis or auto-remediation? No. Regen owns on-call and incident coordination. Root cause analysis is Neuri, auto-remediation is Reflex. Both are part of the same suite.
What does Regen replace? PagerDuty, Grafana OnCall, Opsgenie, incident.io, FireHydrant, Better Stack, Splunk On-Call, Squadcast, xMatters, and Rootly.
How do I move existing schedules over? 1-click migration imports schedules and escalation policies from Grafana OnCall, Opsgenie, or PagerDuty.
Try it
Start the 30-day Pro trial for the hosted version, or clone the open-source repo and run the Docker Compose file against your own Alertmanager. The pricing page has the numbers at your team size, and contact us for on-prem, private VPC, or air-gapped deployment.
Top comments (0)