# How Sublime Security uses incident.io

**15 → 90** seats (6x growth)

As published on [incident.io](https://incident.io/customers/sublimesecurity), March 2026. Captured by usedby on 2026-10-07.

- Company: [Sublime Security](https://www.usedby.ai/companies/sublime-security.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Teams: Support, Security, Engineering

## What the story says

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.

> 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.

- **four hours**: “A single report could take four hours or more.”

> 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

## What usedby checked

We compared the story with its live page on 2026-10-07.

- Checked: the figure 15 → 90 is on the page; its label is our wording.
- Checked: the passage quoted above is copied word for word from the page, near the name of Sublime Security.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Sublime Security uses incident.io. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/sublime-security-incident-io · How we check: https://www.usedby.ai/methodology