Part of the FluidifyAI open-source suite

---

Unlimited alert noise reduction and incidents, unlimited on-call schedules, and unlimited AI postmortems and handoff digests with 1-click Import from Grafana Oncall/Pagerduty

---

Features

- Incident lifecycle with immutable timeline

- Escalation policies with multi-step timeouts

- Alert ingestion — Prometheus, Grafana, CloudWatch, generic webhook

- Slack integration — channels, bot commands, timeline sync

- Microsoft Teams integration — Adaptive Cards, bot commands

- 1-click migration from Grafana OnCall/PagerDuty

- AI incident summaries, Post-mortem, Handoffs Summaries with Slack/Teams synch (BYO key — OpenAI/Anthropic/Ollama)

- SSO / SAML — Okta, Azure AD, Google Workspace

- Docker Compose + Kubernetes Helm chart

- PostgreSQL HA + Redis Sentinel support

- No limits on incidents/AI features

---

Integrations

---

Fluidify Regen Vs Pagerduty/incident.io/Grafana Oncall

---

Migrate in 1 click from

• PagerDuty — schedules, escalation policies, EU region supported
• Grafana OnCall — drop-in replacement for the archived OSS project

---

Installation

Quickest start — Docker Compose:

git clone https://github.com/FluidifyAI/Regen.git
cd Regen
cp .env.example .env   # add your Slack token, AI key, etc.
make start

Open http://localhost:8080 — create your admin account on first load.

For detailed guides, see:

• Full installation guide — prerequisites, env vars, health checks
• Docker Compose self-hosting — production setup
• Kubernetes / Helm — HA deploy with Helm chart
• Environment variables — all config options

Don't wanna host and manage yourself? Get in touch and we'd do it for you.

---

Built for production

Benchmark results (HA stack · Apple M2 / Colima · 2026-03-31)

Production numbers will be higher — these were captured on a single-machine local HA stack. Reproduce yourself: make load-test and make chaos-db. Full methodology in docs/RELIABILITY.md.

How it stays up

• Zero-downtime deploys — rolling restarts drain in-flight requests before pod shutdown (SIGTERM → 30 s drain → exit)
• PostgreSQL HA — Patroni manages automatic primary election; HAProxy re-routes to the new primary within one health-check interval (3 s). No app restart, no config change.
• Redis Sentinel — 3-node quorum detects primary loss; workers reconnect to new master automatically
• Kubernetes-native — HPA, health-gated rolling deploys, resource limits out of the box
• Webhook flood protection — rate limiter returns 429 before the DB sees load spikes; validated at 3,917 RPS with zero OOM events
• Full observability — /metrics (Prometheus) + pre-built Grafana dashboard in deploy/grafana/

Send a test alert

curl -X POST http://localhost:8080/api/v1/webhooks/prometheus \
  -H "Content-Type: application/json" \
  -d '{
    "receiver": "fluidify-regen",
    "status": "firing",
    "alerts": [{
      "status": "firing",
      "labels": {"alertname": "TestAlert", "severity": "critical"},
      "annotations": {"summary": "Test alert from curl"},
      "startsAt": "2024-01-01T00:00:00Z"
    }]
  }'

An incident is created automatically. If Slack is configured, a dedicated channel appears within seconds.

Connecting Slack: Regen uses Slack's HTTP Events API (signed POST to /api/v1/slack/{events,interactions,commands}) — not Socket Mode. Local dev needs a public tunnel (ngrok). Full setup, including the three Request URLs and troubleshooting, is in docs/getting-started/connecting-slack.md.

---

Security

• Authentication: bcrypt (cost 12), timing-safe comparison, 5-attempt account lockout, HTTP-only SameSite=Strict session cookies
• No SQL injection surface: All database access uses GORM parameterized queries — no raw string interpolation
• Webhook verification: Slack (HMAC-SHA256 + replay protection), Teams (RSA/OIDC), CloudWatch (RSA + SSRF-safe cert validation)
• Rate limiting: Redis Lua script enforcing three tiers — 10/min on auth endpoints, 120/min unauthenticated, 600/min authenticated
• Security headers: CSP, HSTS (2 years), X-Frame-Options, X-Content-Type-Options, Permissions-Policy on every response
• Container hardening: non-root UID 1001, read-only filesystem, all Linux capabilities dropped
• CORS: explicit allowlist via CORS_ALLOWED_ORIGINS; dev-only fallback to localhost
• Frontend: no dangerouslySetInnerHTML, no secrets in bundle, session token never accessible to JavaScript

Review the Production Security Checklist — TLS, PostgreSQL password, Redis auth, and CORS origins for prerequisiste checklist.

Full security architecture: SECURITY.md

Don't wanna manage uptime and security? Get in touch and we'd do it for you.

---

Contributing

We love contributions big and small. This is how you join us:

# Start backend + dependencies
docker-compose up -d db redis

# Run backend with hot reload
cd backend && go run ./cmd/regen/... serve

# Run frontend with hot reload
cd frontend && npm install && npm run dev

Read for raising a PR:

• Read the setup & workflow in CONTRIBUTING.md
• Discover all developer commands with make help
• Have a big idea? Let’s discuss it first

---

Support us

If you find Regen useful, consider supporting us by:

• Star this repo - It helps others discover Regen
• Guide us - Every issue you raise goes into building

---

License

AGPLv3 — free forever, including SSO.

---

Built by FluidifyAI · your incident data belongs to you