Why Regle exists
Datadog and PagerDuty weren't built for a team of 12
Between us we've been on-call at companies of every size, from 10-person startups to 10,000-person platforms. The tools we relied on were either free-tier toys or six-figure enterprise suites.
There was nothing in the middle. Nothing that answered the one question we always had at 2 AM: what just shipped?
So we built it. For ourselves first, and now for the next couple thousand teams in the same gap.
What we believe
Boring, useful, fast
- The on-call engineer is the customer. Not the VP, not procurement, not the dashboard committee. Every feature gets weighed against "does this help someone at 2 AM?"
- Five minutes to value or it doesn't ship. If you can't point your alerting tool at a Regle webhook and see something useful inside five minutes, the product has failed.
- AI is invisible. We use LLMs to draft post-mortems and rank likely causes. You won't see a chat window unless it makes the timeline faster.
- Bootstrapped, on purpose. No board pressure to bolt on features for a Fortune-500 RFP. We'd rather stay small and serve our band well.
The team
Two engineers, no middle managers
When you email support, one of us answers. Usually within an hour, sometimes within a minute, never with a ticket number.
Jason Wu
CEO & Co-founder
Former engineer at large-scale platforms. Spent enough nights paging himself awake to develop strong opinions about on-call ergonomics. Handles product, sales, and most of the writing.
Paul Mou
CTO & Co-founder
Distributed-systems engineer who's rolled back his share of bad deploys. Builds the correlation engine, the integrations, and the parts of the product that have to work at 2 AM.
Background: previously at
