Skip to main content
usedby

15 → 90

seats (6x growth)

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

What happened

Sublime Security's support, security, and engineering teams use incident.io for on-call paging and incident response, replacing separate tools and homegrown automations. It connects to Slack, Pylon, and Linear so incidents, channels, tickets, and follow-up actions are created and coordinated across the three teams.

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

  • four hours“A single report could take four hours or more.”

Fifteen licenses became 90. Nobody mandated it. Nobody ran a formal rollout. Three teams, each solving their own problem, converged on the same platform because it was the one that actually worked.

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

incident.io was adopted by more teams than we expected. We started with 15 seats and now we're at 90. Adoption was fast because everything integrated well.

Jonathon Klobucar, Security Engineering, Sublime Security. 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 figure: 15 → 90CheckedThe figure is on the page; its label is our wording.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Sublime Security.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Sublime Security 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