Fluidify Regen - Product Walkthrough
A complete guide to setting up and running oncall management with Regen
Regen is Fluidify AI's open-source, self-hosted oncall management platform. It handles alert ingestion, oncall scheduling, escalation paths, and incident handling end-to-end - with AI post-mortems, summaries, and handoff digests layered on top, using your own AI provider keys. Everything below is available in the free, open-source (AGPLv3) edition unless explicitly marked Pro.
Watch the complete walkthrough tutorial here
Under the hood, Regen runs on a Go backend, PostgreSQL for storage, Redis for queues and caching, and a React/TypeScript frontend - packaged as a single set of Docker images or a Kubernetes Helm chart. None of that is required reading to use the product, but it's part of why the platform behaves the way it does: predictable performance, a small operational footprint, and the ability to run entirely inside your own infrastructure with no calls out to a Fluidify-hosted backend.
This walkthrough follows the natural setup order: deploy the platform, connect your tools, configure AI, set up login, define alert routing, build your oncall schedule, set escalation policies, then move into the day-to-day incident lifecycle and AI features - closing with user management, migration tooling, and the underlying architectural guarantees that make the audit trail trustworthy.
1. Deployment
Before any configuration happens, Regen has to run somewhere - and because it's self-hosted, that "somewhere" is entirely yours.
- Docker Compose - the fastest path for a single-server deployment or evaluation. Brings up the Go backend, PostgreSQL, Redis, and the frontend together with one command.
- Kubernetes (Helm chart) - for production deployments that need to scale or run highly available. The Helm chart includes the Deployment, Service, Ingress, a Horizontal Pod Autoscaler, a migration Job that runs schema migrations automatically on upgrade, ConfigMap, and Secret resources.
- High availability - Regen is designed to run with multiple backend replicas behind a load balancer, PostgreSQL in an HA configuration (primary/replica), and Redis with Sentinel for failover, so the oncall platform itself doesn't become the single point of failure for your incident response.
- Zero-downtime upgrades - schema migrations are designed to run ahead of a rolling deploy, so upgrading Regen doesn't require taking oncall coverage offline.
- Data residency - because everything runs on infrastructure you control, alert payloads, incident content, Slack/Teams transcripts, and AI prompts/responses never leave your environment except to the AI provider you explicitly configure.
2. Initial Configuration
Regen is built to sit alongside the tools you already use - not replace them. The configuration screen is where every external connection lives.
2.1 Alert Source Integration
Connect whichever monitoring or alerting tool is emitting your alerts. Prometheus (via Alertmanager webhooks) is the example used most often - configured directly via webhook URL and a signing key, so Regen can verify incoming payloads are genuinely from your monitoring stack and not spoofed. Once connected, alerts from that source flow straight into Regen's ingestion pipeline.
Each incoming alert is stored with a full structured record, not just a notification string:
| Field | What it captures |
|---|---|
| External ID | The source system's own identifier (e.g., a Prometheus fingerprint), used for deduplication and re-firing/resolution matching |
| Source | Which tool the alert came from (Prometheus, Grafana, CloudWatch, generic webhook, etc.) |
| Status | firing or resolved |
| Severity | critical, warning, info |
| Title & description | Human-readable summary of what fired |
| Labels & annotations | Structured key/value metadata carried over from the source system |
| Raw payload | The complete original payload, preserved as-received for later debugging or audit |
| Started/ended timestamps | When the underlying condition began and (if applicable) cleared, as reported by the source |
| Received timestamp | Server-generated the moment Regen ingests the alert - this one is immutable and can never be backdated or edited |
Beyond Prometheus, Regen ships generic webhook support, plus dedicated handlers for Grafana and AWS CloudWatch (via SNS), so multi-source environments don't need a translation layer in between.
2.2 Chat Tool Integration (Bidirectional)
Connect your team communication platform so incidents live where your engineers already work:
- Slack - connect a Slack app directly (bot token + signing secret, with optional socket-mode app token). The integration is fully bidirectional: any status change, timeline note, or AI-generated update made in Regen posts to the linked Slack channel automatically, and relevant activity inside that Slack channel - replies, slash commands like
/incident new, status updates from the bot - reflects back into Regen's timeline in real time. A channel is auto-created per incident, so each incident gets its own dedicated thread of record. - Microsoft Teams - the same bidirectional behavior as Slack, included in the free, open-source tier, with a few Teams-specific mechanics worth knowing about:
- Channel creation and message posting run through two separate paths: standard Microsoft Graph API calls for channel management, and Bot Framework Proactive Messaging for posting - which gives Teams the same responsiveness as the Slack integration without requiring elevated delegated permissions.
- The Teams bot understands direct commands (
@Bot ack,@Bot resolve,@Bot status,@Bot new) and posts an Adaptive Card on incident creation and on every status change. - UI timeline notes sync to the Teams channel automatically, and non-command replies posted in Teams sync back into the Regen incident timeline - so a team using Teams gets full parity with a team using Slack, not a stripped-down version.
- Known platform limitation: Microsoft Graph API doesn't support true archiving of standard Teams channels, so a resolved incident's channel is renamed with a
[RESOLVED]prefix rather than archived outright. True archiving would require moving to Teams' private-channel model.
2.3 On-Call Notification Channels
For actually reaching the oncall engineer (calls, pages, push notifications) - separate from the team-wide visibility that Slack/Teams provides:
- Telegram - included free. Connect your Telegram account and oncall notifications and messages reach you there directly, independent of whether you're watching Slack.
- Fluidify Mobile App (Pro) - available on both the Play Store and the App Store, with native push notifications for incoming alerts, designed so the person actually being paged doesn't have to be staring at a desktop.
- Additional notification and voice-calling channels are available in the Pro tier beyond Slack/Teams/Telegram, for teams that want phone-call escalation as a fallback to chat-based notification.
2.4 AI Provider Configuration
Regen's AI features are bring-your-own-key - your incident data goes to the AI provider you choose, on your account, not to any Fluidify-operated AI backend. To configure:
- Go to the AI configuration section.
- Choose your model provider and paste in your API key. Supported providers include:
- OpenAI
- Anthropic (Claude)
- Google (Gemini)
- Self-hosted / local models
- Select the specific model you want to use for generation (summaries, post-mortems, and handoff digests can all use the same configured provider).
Once a key is added, every AI feature in Regen becomes active - at no additional licensing cost from Fluidify. You only pay your model provider directly for the tokens you use. If no key is configured, Regen continues to function as a complete oncall and incident platform - AI is additive, never a dependency for core functionality.
2.5 Login & SSO
Team members can log in two ways:
- Email + password, created at account setup, backed by Regen's own auth layer (session handling, login page, logout).
- Single Sign-On (SSO/SAML 2.0) - if your organization already runs Google Workspace, Microsoft Entra/Azure AD, or Okta as an identity provider, connect it directly. SSO supports just-in-time (JIT) provisioning, meaning a new team member's account is created automatically the first time they log in through SSO - no separate manual invite step required before they can authenticate.
SSO is completely free in the open-source tier - this is a deliberate, permanent decision, not a launch promo. The Pro tier adds support for a wider range of identity platforms, but Google, Microsoft, and Okta - the providers most teams actually run - are already covered for free. Regen does not charge a "security tax" for letting your team log in safely; gating SSO behind a paywall is treated internally as user-hostile, since SSO is a security hygiene requirement, not a premium feature.
3. Alerting Routes
Alerting routes are where raw alerts get filtered, deduplicated, and turned into something worth an engineer's attention. This is the layer that determines whether your team gets paged ten times for the same underlying problem, or once.
3.1 Creating a Route
To create a new alerting route:
- Define the resource the alert is coming from - i.e., which connected source (Prometheus, Grafana, CloudWatch, a generic webhook) this routing rule applies to.
- Configure regex patterns to filter alerts - match against title, labels, or annotations to decide which alerts this route should act on.
- Set rules to ignore alerts matching specific patterns entirely - useful for known-noisy checks, maintenance-window alerts, or low-value warnings you've decided aren't worth a page.
3.2 Deduplication
Deduplication is on by default. Alerts arriving from the same or multiple sources that match the same identifying pattern (typically the source system's fingerprint, combined with label matching) are automatically clustered into a single logical alert rather than creating duplicate noise. In practice, this means:
- A flapping check firing repeatedly doesn't create a new incident every time - it's recognized as the same underlying condition.
- The same underlying failure reported by two different monitoring tools watching the same service can be correlated rather than triggering two parallel response threads.
- Only alerts that clear the dedup and filtering logic go on to become incidents - this is what keeps the incident list meaningful rather than a flood of redundant tickets.
3.3 Routing → Incident Creation
Alert routing is directly paired with incident creation downstream: once an alert clears its route's filters and dedup logic, it can automatically generate an incident (subject to the severity thresholds you configure), fully populated with the alert's labels, annotations, and raw payload already attached - so the responding engineer starts with full context rather than a bare notification.