Pricing 9 min read

Honeycomb pricing in 2026

What the free plan covers, what an event is, what changed on Pro this year, and three monthly bills worked out.

JeremyFunk By JeremyFunk Prices verified 2026-11-21

Honeycomb is an observability platform built around querying wide events: spans and structured logs with many attributes. It bills by the number of events and metrics data points you send each month, with unlimited seats and unlimited queries on every plan.

This guide covers the plans, what counts as an event, the Pro price change that takes effect for legacy plans after December 31, 2026, what happens when you send too much, and three worked monthly bills.

Maple publishes this guide and competes with Honeycomb. Section 06 compares the two; every Honeycomb figure comes from Honeycomb's own pages, linked at the end.

Key takeaways

  • Free includes 20 million events and 100 million metrics data points a month.
  • Pro starts at $150 a month for 50 million events and tops out at 750 million.
  • The 2026 Pro rate is $3.00 per million events, up from $1.30 on legacy plans.
  • Every span, span event, span link and log is one event, whatever its size.
  • Free and Pro never bill overage. Two months over the limit leads to throttling.

01 · Plans

How Honeycomb pricing works

Honeycomb meters two things: events (spans and logs) and metrics data points (time series measurements). Each plan sets a monthly limit for both, tracked separately.

FreeProEnterprise
Price$0From $150 a monthCustom
Events a monthUp to 20M50M to 750MFrom 10B a year
Metrics data pointsUp to 100M250M to 3.75BVariable
Seats and queriesUnlimitedUnlimitedUnlimited
Triggers2100From 300
SLOsNone2From 100
Event retention60 days60 days60 days, longer as an add-on
BillingMonthly or annualAnnual

Pro is sold in fixed tiers. The pricing page states the entry tier, $150 for 50 million events, and the top, 750 million. The docs put the 2026 Pro rate at $3.00 per million events across four tiers. You pick a tier and pay its price whether you use all of it or not; unused events do not roll over, and the counter resets on the 1st of each calendar month. Enterprise starts at 10 billion events a year with volume discounts that sales quotes.

What counts as an event

A span is one event. A trace with 150 spans is 150 events. In OpenTelemetry terms, each span event (an exception recorded on a span, for example) and each span link is also one event. A structured log line is one event. An event can be up to 1 MB with up to 2,000 attributes, and a 1 MB event costs the same as a 200-byte one.

Events dropped before they reach Honeycomb, by sampling or a Collector filter, do not count. Neither do events Honeycomb rejects for size or rate limits. Metrics sent as time series bill as data points; metrics sent as events bill as events.

The 2026 Pro change

As of July 1, 2026, Pro includes time series metrics and Honeycomb Intelligence features such as Canvas and the Honeycomb MCP server. The new generation of Pro plans moves from three tiers to four and raises the rate from $1.30 to $3.00 per million events. Teams already on Pro keep their legacy plan until a grace period ends on December 31, 2026.

During the grace period, a legacy team can commit to an annual term on its current tier and keep legacy pricing for that year at a 20% increase. There is no monthly option at legacy pricing. A team that does nothing moves to the 2026 tier closest to its current plan at the next billing boundary. Honeycomb notes that it picks that tier from your plan, not your actual usage.

Verified 2026-11-21 against honeycomb.io/pricing, 2026 Pro Plan Changes and How Honeycomb Calculates Usage.

02 · Limits

Limits instead of overage

On Free and Pro, sending more than your tier allows does not add a line to the invoice. Honeycomb divides the monthly limit by 30.4 to set a daily target and escalates in steps:

  1. Trending overEmail to team owners
  2. One month overEmail at the start of the next month
  3. Two months over10 days to upgrade or send less
  4. Throttled1 event in 10 accepted, the rest rejected

Throttling ends once your incoming rate stays under the daily target for 72 hours. Data points follow the same steps on their own limit, and either one can trigger throttling. Enterprise plans are exempt; their overage terms are in the order form.

Burst protection

Spikes above 2x the daily target are forgiven

On a day you send more than twice the daily target, the excess does not count toward the monthly limit. The data is still stored and queryable. It applies up to three times a calendar month, separately for events and data points.

No rollover

Unused events expire monthly

The counter resets on the 1st of each calendar month, whatever your billing date. A quiet month does not bank headroom for a busy one.

03 · Surprises

What surprises teams on Honeycomb

  • Span count, not request count, sets the bill. One request through a gateway, three services and a database can be 20 spans. Auto-instrumentation adds a span for every client call it wraps.
  • Span events and links are events too. An exception recorded on a span adds a second event. Instrumentation that records many span events can double the count without adding a single span.
  • The price is per event, not per byte. This favors wide events: a span with 300 attributes costs the same as one with 3. It penalizes many small spans and short log lines.
  • The limit is enforced with throttling. There is no surprise invoice, but a team that stays over the limit loses nine events in ten until it upgrades or sends less.
  • Legacy plans reprice after 2026. At $3.00 instead of $1.30 per million, the same event volume costs about 2.3 times as much on the 2026 rate, or about 1.9 times a legacy plan locked in for a year at the 20% increase ($1.56 per million).
  • Pro includes 2 SLOs. Teams that run SLOs per service reach the limit on Pro quickly; Enterprise starts at 100.

04 · Examples

What a month of Honeycomb costs

Three workloads at the prices checked 2026-11-21, in millions per month. The Pro price is the tier you need, at the 2026 rate.

WorkloadSpansSpan eventsLogsEventsData pointsPlanPer month
Small team15M0M3M18M60MFree$0.00
Mid-sized team38M2M8M48M200MPro, 50M tier$150.00
Larger team500M50M100M650M1,000MPro, 750M tier (estimated)$2,250.00

Small team: $0.00 a month

A service handling 100,000 requests a day at 5 spans each sends 15 million spans a month. With 3 million log lines that is 18 million events, under Free's 20 million, and 60 million data points, under its 100 million. The team pays nothing. The limits that bite first are 2 triggers and no SLOs, and a 12% traffic increase takes it past 20 million events.

Mid-sized team: $150.00 a month

38 million spans, 2 million span events and 8 million logs make 48 million events, which fits the 50 million entry tier. The 200 million data points fit its 250 million. The bill is $150.00, which works out to $3.00 per million events at full use of the tier. At the legacy rate of $1.30 per million, the same events price at $62.40, though legacy plans were also sold in tiers.

Larger team: about $2,250.00 a month

500 million spans, 50 million span events and 100 million logs make 650 million events. At $3.00 per million that is $1,950.00, but Pro is sold in tiers, so the team buys the smallest one that covers it. The page text names only the 50 million and 750 million tiers. If no tier sits between 650 and 750 million, the team buys the top one, about $2,250.00 at the published rate. At the legacy rate the same events price at $845.00. Growth past 750 million moves the team to Enterprise, which has no published price.

Seats are not in any of these bills. A 5-person team and a 50-person team pay the same for the same events.

05 · Cutting the bill

How to cut a Honeycomb bill

  1. 01

    Find the events nobody queries

    The Usage page under Team Settings breaks event volume down by environment and dataset. Health checks, readiness probes and debug logs are usually the first to go.

  2. 02

    Filter in the Collector

    Events dropped before they leave your network do not count. The config below drops health-check spans and logs below INFO, keeping logs that set no severity.

  3. 03

    Sample with Refinery

    Refinery is Honeycomb's tail-based sampling proxy. It decides once a trace is complete, so its rules can keep every error and slow trace and sample the rest. Honeycomb weights query results by each event's sample rate, so counts stay correct.

  4. 04

    Move metrics off events

    Metrics sent as events count against the event limit. Honeycomb's own migration notes suggest sending them as time series instead, which bill against the separate data point allowance.

  5. 05

    Choose your 2026 tier yourself

    On a legacy plan, look at the last few months of usage before December 31, 2026. Either lock in legacy pricing with an annual term at a 20% increase, or pick the 2026 tier that fits. The automatic move uses your plan, not your usage.

collector.yaml

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  filter/noise:
    error_mode: ignore
    traces:
      span:
        - attributes["url.path"] == "/healthz"
    logs:
      log_record:
        - severity_number > SEVERITY_NUMBER_UNSPECIFIED and severity_number < SEVERITY_NUMBER_INFO

exporters:
  otlp/honeycomb:
    endpoint: api.honeycomb.io:443
    headers:
      x-honeycomb-team: ${env:HONEYCOMB_API_KEY}

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [filter/noise]
      exporters: [otlp/honeycomb]
    logs:
      receivers: [otlp]
      processors: [filter/noise]
      exporters: [otlp/honeycomb]

Set HONEYCOMB_API_KEY in the Collector's environment. The same filter processor can drop span events by name if one library records more of them than you need.

06 · Maple

Maple pricing for the same workloads

Maple is an OpenTelemetry observability platform. Like Honeycomb it charges nothing per seat. It meters bytes instead of events: one plan at $39/month with 100 GB each of logs, traces and metrics included, then $0.30 per GB for each signal. Logs and traces are kept 30 days and metrics 90.

To compare, this table assumes 1 KB per span or log record and 0.1 KB per metric data point. Span events and links travel inside their span, so this table adds 1 KB for each span event instead of counting it as a separate event. Maple meters uncompressed OTLP bytes.

WorkloadTracesLogsMetricsMapleHoneycomb
Small team15 GB3 GB6 GB$39.00$0.00
Mid-sized team40 GB8 GB20 GB$39.00$150.00
Larger team550 GB100 GB100 GB$174.00$2,250.00

The larger team's Maple bill is $39 plus 450 GB of traces over the included 100 at $0.30. Its logs and metrics stay inside their allowances.

The size of an event decides which model is cheaper. At $3.00 per million events and $0.30 per GB, the two rates meet at an average of 10 KB per event. Teams that send fewer, wider events of more than 10 KB pay less per event on Honeycomb; teams with many small spans and log lines pay less on Maple. The included allowances shift that line at low volume.

Honeycomb is the better fit in several cases. The small team pays nothing on Honeycomb's Free plan and $39 on Maple, which has no free cloud plan. Honeycomb keeps events for 60 days against Maple's 30, and BubbleUp is built for finding what sets a slow slice of requests apart. Maple adds session replay and an error inbox on the same plan, and its source is available to self-host.

Maple

Send the same OpenTelemetry data to both

Add a second exporter to the Collector above and compare a few days of usage on each.

Sources and further reading

FAQ

자주 묻는 질문

Is Honeycomb free?
Yes. The Free plan costs nothing with no time limit and includes up to 20 million events and 100 million metrics data points a month, unlimited seats and 2 triggers. It has no SLOs. Events are kept for 60 days.
How much does Honeycomb Pro cost?
Pro starts at $150 a month for 50 million events and 250 million metrics data points, and goes up to 750 million events. Honeycomb's docs give the 2026 Pro rate as $3.00 per million events, up from $1.30 on legacy plans. Above 750 million events a month you need Enterprise, which is priced by sales (verified 2026-11-21).
What counts as an event in Honeycomb?
Each span in a trace is one event, so a trace with 150 spans is 150 events. Each OpenTelemetry span event and each span link is also one event, and so is each structured log. Events can be up to 1 MB with up to 2,000 attributes, and a large event costs the same as a small one.
What happens if I go over my Honeycomb event limit?
Free and Pro plans are not billed for overage. After a first month over the limit, Honeycomb emails a warning. After a second consecutive month it gives 10 days' notice, then throttles: the API accepts one event in ten and rejects the rest until your daily rate stays under target for 72 hours. Enterprise plans are exempt from throttling.
Can I keep Honeycomb's legacy Pro pricing?
Until December 31, 2026, a team on a legacy Pro plan can commit to an annual term on its current tier and keep legacy pricing for that year at a 20% increase. There is no monthly option at legacy pricing. Teams that do nothing move to the closest 2026 tier at their next billing boundary after the grace period.

오늘 첫 트레이스를 확인하세요.

SDK를 추가하고 OTLP 익스포터를 Maple로 향하게 하면 트레이스가 도착합니다.

maple.dev: OpenTelemetry 위의 옵저버빌리티