Skip to main content
usedby
incident.iousedbyTurbopuffer

How Turbopuffer uses incident.io

ConfirmedVendor case study · Checked Oct 7, 2026
View captured proof

The use case: how Turbopuffer deploys incident.io

turbopuffer, a small team that runs a search engine and carries its own pager, uses incident.io's Investigations agent inside its existing on-call and incident response workflow. It helps responders find root causes faster and points them to how similar past incidents were resolved.

In the customer’s words

Investigations lets us get more out of the on-call team we have. It's stress relief. It allows us to support more customers with a smaller team.
Nikhil Benesch, CTO, Turbopuffer — Source

Other AI tools used by Turbopuffer

Other public relationships recorded on usedby.

BasetenDeclaredDatadogDeclaredFireworks AIDeclaredPylonDeclaredResendDeclaredTypeSafe AIDeclared
Explore Turbopuffer’s AI stack

incident.io users in DevTools & Infrastructure

Companies in the same sector, with public evidence.

ContentfulConfirmedGiant SwarmConfirmedWorkOSConfirmedHashiCorpObservedHoneycombObservedLinearObserved
See all incident.io customers

More stories

Go 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
Aug 3, 2026
Last checked
Oct 7, 2026
incident.ioCaptured incident.io case study about TurbopufferOpen source capture
What the story claims, and what we checked

What we compared with the page.

  • The figure: Up to 10xChecked

    Printed word for word on the page, near the name of Turbopuffer.

  • The passage quoted aboveChecked

    Copied word for word from the page, near the name of Turbopuffer.

  • The publication dateChecked

    Read from the page’s own metadata, never guessed.

  • Turbopuffer uses incident.ioChecked

    Confirmed line.

  • The result itselfNot checked

    We quote it; we did not measure it.

When turbopuffer's billing service broke one morning, Investigations pinned down the cause within minutes, before any of the responders knew what had changed.
From the page. incident.io