# Observability pricing for Series A and Series B companies

Use $2,000 to $7,000 per month as a working budget for a managed observability setup at a Series A company, and $5,000 to $15,000 per month at Series B. A broad platform deployment can cost more because infrastructure monitoring, APM, logs, databases, frontend monitoring, security, and incident response may be billed separately.

These ranges are planning assumptions, not vendor quotes or market benchmarks. Model a specific deployment from telemetry volume, retention, infrastructure size, and enabled products before selecting a vendor.

Published prices in this document were checked on August 18, 2026. “Darkly” means LaunchDarkly, and “Datahog” means Datadog.

## Choose by primary use case

The products are not direct substitutes. OpenTelemetry is an instrumentation standard, Honeycomb and Datadog are observability backends, and PostHog and LaunchDarkly cover adjacent product and release workflows.

| Product | Primary role | Main billing dimensions | When to evaluate it |
|---|---|---|---|
| Honeycomb | Application observability | Events and metric data points | You want a focused backend with few billing dimensions |
| Datadog | Full-stack operations | Hosts, ingestion, indexed data, sessions, and product-specific units | You want to consolidate operations, security, and service-management tools |
| PostHog | Product analytics and developer tooling | Usage for each enabled product | You also need analytics, feature flags, replay, or experiments |
| LaunchDarkly | Feature delivery and release control | Service connections, client-side users, AI runs, and observability usage | You need telemetry tied to releases, experiments, or automated controls |
| OpenTelemetry | Instrumentation and telemetry transport | No license fee; backend and operating costs remain | You want portable instrumentation and control before ingestion |

For backend observability alone, compare Honeycomb and Datadog first. Add PostHog or LaunchDarkly when their adjacent workflows are part of the purchase. Use OpenTelemetry with any of these backends when portability matters.

## Set a working budget

“Managed observability” means a focused hosted backend. “Broad platform deployment” also includes functions such as security, incident response, databases, frontend monitoring, or CI.

| Company stage | Managed observability | Broad platform deployment |
|---|---:|---:|
| Early Series A, 15 to 30 engineers | $500 to $3,000/month | $2,000 to $6,000/month |
| Larger Series A or early Series B, 30 to 70 engineers | $2,000 to $7,000/month | $5,000 to $15,000/month |
| Series B, 70 to 150 engineers | $5,000 to $15,000/month | $10,000 to $30,000/month |
| High-volume Series B | $10,000 to $30,000/month | $20,000 to $50,000+/month |

These estimates do not follow from company stage or engineer count alone. Treat the stage labels as scenario names. Telemetry volume and the products included in the contract determine the bill.

## Collect usage before requesting quotes

Record the following inputs for the current month and a 12-month growth case:

- spans per month;
- log records and ingested log GB per month;
- metric data points and cardinality;
- hosts, nodes, containers, and database instances;
- required retention;
- the share of telemetry that must remain indexed and immediately searchable;
- real-user monitoring and session-replay volume;
- product-analytics events;
- feature-flag evaluations;
- error volume;
- LLM or agent telemetry;
- SLOs, on-call users, and incident-management users; and
- security and compliance requirements.

Filtering, aggregation, and sampling before ingestion are the main technical controls on usage-based cost. Ask each vendor to price the same current and growth scenarios.

## Compare vendor pricing

### Honeycomb bills primarily by telemetry volume

Honeycomb meters events and metric data points. Its Pro plan starts at $150 per month for 50 million events and 250 million metric data points. The public plan permits up to 750 million events and 3.75 billion metric data points per month. Honeycomb lists unlimited seats and queries.

OpenTelemetry users can filter and sample data before sending it to Honeycomb. This can reduce cost without changing application instrumentation.

Working estimate:

- Series A: $750 to $2,000/month
- Series B: $3,000 to $10,000/month

The upper end depends on event volume, metric volume, and enterprise terms. These ranges are planning assumptions, not published Honeycomb prices.

### Datadog bills each product separately

Datadog has the broadest product surface in this comparison and the most billing dimensions. Representative list prices for annual billing include:

- Infrastructure Pro: $15 per infrastructure host per month;
- Infrastructure Enterprise: $23 per infrastructure host per month;
- APM: $31 per APM host per month, plus ingestion and indexed spans;
- Database Monitoring: $70 per database host per month;
- log ingestion: $0.10 per GB, plus charges for indexed log events; and
- profiling, RUM, session replay, incident response, security, synthetics, and other products: separate charges.

The total depends on host and database counts, ingested and indexed data, custom metrics, user sessions, seats, and enabled products. Consolidation can still reduce total cost if Datadog replaces several tools.

Working estimate:

- Series A: $3,000 to $6,000/month
- Series B: $12,000 to $25,000/month
- Broad Series B deployment: $20,000 to $40,000+/month

These ranges are planning assumptions, not published Datadog prices.

### PostHog bills usage for each enabled product

PostHog combines product analytics with session replay, feature flags, experiments, error tracking, AI observability, logs, and other developer tooling. Each product has its own free allowance and usage rate.

For example, the public plan includes monthly allowances of 1 million analytics events, 5,000 session recordings, 1 million feature-flag requests, 100,000 exceptions, 100,000 AI-observability events, and 10 GB of ingested logs. Usage above each allowance is metered separately.

Working estimate for a company using several PostHog products:

- Series A: $1,500 to $3,000/month
- Series B: $5,000 to $12,000/month

These ranges are planning assumptions. Calculate product analytics, feature flags, replay, errors, logs, and AI telemetry separately. PostHog is most relevant when one purchase can replace several product and developer tools.

### LaunchDarkly bills release-platform and observability usage

LaunchDarkly is primarily a feature-delivery, experimentation, and release-control platform. It is not a direct replacement for Honeycomb or Datadog.

The free Developer plan includes 10 million logs, 10 million traces, 5,000 session replays, and 5,000 errors per month. The Foundation plan is billed annually at $10 per service connection per month and $8.33 per 1,000 client-side monthly active users per month. It includes five service connections; usage beyond the observability allowances is billed separately. Enterprise pricing is custom.

Working estimate for a broader LaunchDarkly deployment:

- Series A: $15,000 to $50,000/year
- Series B: $40,000 to $150,000+/year

These estimates cover the broader release platform, not observability alone. Use the published Foundation units for a self-service deployment and obtain a quote for Enterprise capabilities.

### OpenTelemetry has no license fee but requires a backend

OpenTelemetry provides vendor-neutral APIs, SDKs, instrumentation, and a Collector for generating, processing, and exporting traces, metrics, and logs. It does not store, query, or visualize telemetry.

A company can send OpenTelemetry data to Honeycomb, Datadog, another managed backend, or a self-hosted stack. Standardizing at this layer reduces dependency on a backend and lets the company filter, aggregate, and sample data before ingestion.

Self-hosting still requires compute, storage, upgrades, reliability work, and engineering time. The following total-cost estimates include engineering time:

- Series A: $3,000 to $9,000/month
- Series B: $8,000 to $30,000/month

These ranges are planning assumptions. Infrastructure-only cost can be lower. For most Series A companies, OpenTelemetry with a managed backend is simpler than operating the storage and query stack.

## Recommended default architecture

Use OpenTelemetry instrumentation and Collectors with a managed observability backend. This keeps instrumentation portable and provides one place to filter, aggregate, and sample telemetry before paid ingestion.

Choose the backend from the required scope:

- Choose Honeycomb for focused application observability and simpler volume-based pricing.
- Choose Datadog when platform consolidation justifies more billing dimensions.
- Add PostHog when product analytics and developer tooling are part of the same decision.
- Add LaunchDarkly when feature delivery and release control are part of the same decision.

Do not compare vendor totals until every quote uses the same telemetry, retention, growth, and product assumptions.

## Sources

- [Honeycomb pricing](https://www.honeycomb.io/pricing)
- [Datadog pricing](https://www.datadoghq.com/pricing/list/)
- [PostHog pricing](https://posthog.com/pricing)
- [LaunchDarkly pricing](https://launchdarkly.com/pricing/)
- [OpenTelemetry overview](https://opentelemetry.io/docs/what-is-opentelemetry/)