The use case: how Amperity deploys Honeycomb
Amperity, a customer data platform company, moved from a suite of separate tools for logs, metrics, and dashboards to Honeycomb for observability. The goal was to reduce reliance on tribal knowledge and avoid logging halts caused by an ingest-based pricing limit.
In the customer’s words
It required constant vigilance about what we were sending to ensure our logging wouldn’t stop whenever we hit the ingest tariff limit. We had this persistent feeling that we wouldn’t be able to scale that constant oversight as our company grew.Other companies using Honeycomb
Customers across industries, with public evidence.
Booking.comConfirmed
DepotConfirmed
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
- Nov 1, 2024
- Last checked
- Nov 13, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Amperity.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Amperity uses HoneycombChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Its ingest-based pricing model meant that Amperity’s logging would halt—full stop—whenever they exceeded the daily limit.