Regle correlates every deploy, config change, and feature flag flip with your incidents — so you find the bad change in seconds, not hours. Built for small teams who don't have a war room.
The 2 AM problem
Alert fires. You stumble to your laptop. Stack of dashboards open. None of them tell you what just shipped.
GitHub tab. Slack #deploys. CI logs. LaunchDarkly. Whose change touched this service? Was it the deploy or the flag flip?
27 minutes in. Still guessing. Eventually roll back the wrong thing. Post-mortem next week says: "add better tooling."
Datadog Incident Management and PagerDuty solve this for 200-person orgs with a procurement budget. Below that, it's tabs and guesswork. Regle is the tool you actually open at 2 AM.
How Regle works
GitHub for deploys. PagerDuty / Opsgenie / Slack for alerts. LaunchDarkly or your config repo for flags. No agents to install.
Every merge, deploy, flag flip, and infra apply gets stitched into one timeline — tagged with service, owner, and blast radius.
Regle ranks the changes most likely to have caused it — by service overlap, timing, and historical correlation. Owner, diff, and rollback link in one click.
Who Regle is for
Honest about who we serve. If you don't see yourself below, we're probably the wrong tool — and we'll happily tell you so.
Also included
URL and heartbeat checks for the services your big observability tool doesn't watch.
SEV levels, owner, status, and updates — the parts of incident.io you actually use, none of the ones you don't.
One subdomain, one toggle. For when you need to tell customers something broke.
After resolution, Regle drafts a timeline + likely cause writeup from the events it captured. You edit, not author.
Pricing
Free for solo developers and OSS projects. 14-day free trial on Team. Cancel anytime.
Solo developer or OSS maintainer? Get a free Team account →