Skip to main content
usedby
Search tools, companies

How Pleo uses incident.io

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

What happened

Pleo replaced its in-house incident tooling with incident.io to manage incident response and on-call. It uses Workflows to automate response actions, Slack channels for communication, and the Insights dashboard for post-incident learning.

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

Before incident.io, Pleo’s in-house solution made even declaring incidents an exercise in frustration.

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

incident.io saves us hours per incident when considering the need for us to write up the incident, root cause and actions, communicate it to wider stakeholders and overall reporting.

Braedon Gough, Site Reliability Engineer, Pleo. 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 Pleo.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Pleo 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