What it sells
AI-native on-call and incident response carefully crafted to help…
Business model breakdown
Buyer: who owns the budget?
Director/Head of Platform or Engineering, and SRE leaders (quoted customers include Directors of Platform Engineering at Auror and Motive).
Trigger: what makes them buy now?
Replacing PagerDuty, Opsgenie or incident.io, scaling incident response as engineering teams grow, and cutting on-call tooling cost; migration team imports schedules and runs both tools side by side.
Workflow: what inputs become what output?
Alert pages the on-call engineer, incidents run in Slack, Teams or Google Chat with AI scribe, related-incident lookup and timelines, status pages are updated, and AI SRE finds probable root cause and drafts fixes; retrospectives are generated afterward.
Economics: what it saves and how it charges
Per-seat SaaS by product plus custom enterprise pricing and a startup program (up to 50% off, pay-what-you-can under 25 employees); customer claims include saving 200+ engineering hours a year (Caribou).
Distribution: how it reaches customers
Demo-led sales ("Book a demo", "Talk to an expert") with competitive switch campaigns against PagerDuty/Opsgenie/JSM, customer stories and a startup program.
Funding history and coverage
| Round date | Stage | Amount | Investors | Source |
|---|---|---|---|---|
| — | Y Combinator Summer 2021 | — | Y Combinator | ycombinator.com |
Profiles summarize public reporting and company websites. Business-model notes are MaxBC's reading of that material, not confirmed facts; unknowns are left blank rather than guessed. Updated 2026-10-12.