Regarding pricing, setup cost, and licensing, these are not much of a concern because as the volume of telemetry data increases, pricing will be a consideration. However, the initial setup is fairly straightforward.
I use the end product, and it operates on a usage-based pricing model, where costs mainly depend on volume and data retention requirements, while the initial setup was easy for me, and licensing is relatively straightforward, although managing data ingestion and costs can become challenging as the number of services grows.
My experience with pricing, setup cost, and licensing for Honeycomb Enterprise is that this is an area I evaluate carefully due to potentially complicated observability pricing as the amount of telemetry grows with application traffic.
Software Engineer at a non-tech company with 501-1,000 employees
Real User
Top 20
May 5, 2026
My experience with the pricing, setup cost, and licensing of Honeycomb Enterprise has been that the setup is a big ramp up to get the codebase connected to the system, but once that is set up, then it is pretty easy. There is a lack of Lambda functionality with Go that does not exist with Honeycomb Enterprise, which is a pain when a lot of our code has that. In terms of pricing, it was a little challenging to get the company to commit to the full pricing of Enterprise, but once we got there it was nice. Before that, we had to sample a lot of tracing, so we hit limits and got throttled a lot.
Honeycomb Enterprise delivers distributed tracing, real-time performance monitoring, and high-cardinality data analysis to enhance observability, scalability, and incident response.Honeycomb Enterprise provides organizations with the tools needed for debugging and performance optimization in complex environments. Utilizing features like BubbleUp and powerful querying, users gain end-to-end visibility and reduce troubleshooting time. Integrations with DevOps tools and customizable dashboards...
Regarding pricing, setup cost, and licensing, these are not much of a concern because as the volume of telemetry data increases, pricing will be a consideration. However, the initial setup is fairly straightforward.
I use the end product, and it operates on a usage-based pricing model, where costs mainly depend on volume and data retention requirements, while the initial setup was easy for me, and licensing is relatively straightforward, although managing data ingestion and costs can become challenging as the number of services grows.
My experience with pricing, setup cost, and licensing for Honeycomb Enterprise is that this is an area I evaluate carefully due to potentially complicated observability pricing as the amount of telemetry grows with application traffic.
My experience with the pricing, setup cost, and licensing of Honeycomb Enterprise has been that the setup is a big ramp up to get the codebase connected to the system, but once that is set up, then it is pretty easy. There is a lack of Lambda functionality with Go that does not exist with Honeycomb Enterprise, which is a pain when a lot of our code has that. In terms of pricing, it was a little challenging to get the company to commit to the full pricing of Enterprise, but once we got there it was nice. Before that, we had to sample a lot of tracing, so we hit limits and got throttled a lot.