The use case: how Depot deploys Honeycomb
Depot, a build acceleration platform, replaced its homegrown logging and alerting setup with Honeycomb for distributed tracing, SLOs per product, and faster triage of issues. It also connects AI coding agents to Honeycomb via MCP to assemble root cause analyses for customer support tickets.
In the customer’s words
Honeycomb is the best tool I have seen for traces, and the best at the SLO concept, which is exactly what we wantedOther companies using Honeycomb
Customers across industries, with public evidence.
AmperityConfirmed
Booking.comConfirmed
DuolingoConfirmed
FenderConfirmed
FreshpaintConfirmed
GearsetConfirmedGo straight to the source
Based on Honeycomb’s published case study. We check the public evidence; the results are reported by the vendor.
honeycomb.io- Source published
- May 21, 2026
- Last checked
- Nov 13, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 40xChecked
Printed word for word on the page, near the name of Depot.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Depot.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Depot uses HoneycombChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Before Honeycomb, answering that question meant roughly an hour of manual log correlation. Engineers had to build up context for one error at a time to determine whether a pattern pointed somewhere actionable or to an intermittent external service issue.