Skip to main content
usedby
Search tools, companies

How WorkOS uses incident.io

As published on incident.io, January 2024. Captured by usedby on Oct 7, 2026.

What happened

WorkOS replaced its manual, runbook-document-based incident response with incident.io, using automated workflows and follow-ups synced to Linear. This lowered the bar for declaring incidents and brought non-technical teams into the process.

Summary written by usedby from the source page, in English. The figures are those of incident.io and WorkOS, not ours.

Workflows are really impactful. Because we're declaring more incidents, being able to have rules around what happens during them is really useful. We've leaned into creating automation around what types of incidents need to have more of a focus on them.

From the page. incident.io, captured Oct 7, 2026

The biggest shift for the team has been the realization we can include anything reactive as an incident.

Alon Levi, VP of Engineering, WorkOS. Source, captured Oct 7, 2026

What the story claims, and what we checked

We compared the story with its live page on Oct 7, 2026.

  • The passage quoted aboveCheckedCopied word for word from the page, near the name of WorkOS.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • WorkOS uses incident.ioCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
  • The result itselfNot checkedWe quote it; we did not measure it.

Same company, same tool or same industry.

80%“Approximately 80% of our initial incident-response workflow is now automated.”Kaizen Gaming uses incident.io. Another customer of incident.ioUp to 10x“Up to 10x faster response time”Turbopuffer uses incident.io. Another customer of incident.io4+ hours“4+ hours saved on post-mortems”Built uses incident.io. Another customer of incident.io