The use case: how Sublime Security deploys incident.io
Sublime Security's support, security, and engineering teams use incident.io for on-call paging, incident coordination in Slack, and structured incident workflows. Support triggers incidents from customer calls and Pylon, security runs private investigations with Linear follow-ups, and engineering uses it for escalation paths, replacing a homegrown automation setup.
More reported results
Figures published in incident.io’s case study. They are not independently measured by usedby.
A single report could take four hours or more.
In the customer’s words
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.Other AI tools used by Sublime Security
Other public relationships recorded on usedby.
Explore Sublime Security’s AI stackincident.io users in Cybersecurity
Companies in the same sector, with public evidence.
See all incident.io customersGo straight to the source
Based on incident.io’s published case study. We check the public evidence; the results are reported by the vendor.
incident.io- Source published
- Mar 26, 2026
- Last checked
- Nov 11, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 15 → 90Checked
The figure is on the page; its label is our wording.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Sublime Security.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Sublime Security uses incident.ioChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
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.




