The use case: how Scribe deploys Honeycomb
Scribe, an AI documentation and process automation company, replaced New Relic with Honeycomb for observability. Its engineers use Honeycomb with OpenTelemetry for end-to-end tracing and to investigate incidents.
More reported results
Figures published in Honeycomb’s case study. They are not independently measured by usedby.
This approach supports scale while contributing to a 75% reduction in observability costs compared to their previous solution.
In the customer’s words
Whenever a user clicks on a trace, they can see that whole workflow. With Honeycomb, we know exactly what part of the trace or where in our system is slowing that user down. If there are errors, we know exactly where they are.Other AI tools used by Scribe
Other public relationships recorded on usedby.
Explore Scribe’s AI stack
Honeycomb users in Artificial Intelligence
Companies in the same sector, with public evidence.
See all Honeycomb customers
Go 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
- Mar 19, 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: 5 minutesChecked
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 Scribe.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Scribe uses HoneycombChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Engineers report that isolating the root cause now takes about five minutes, with high confidence in the results.