How should PostHog compete with Datadog and Sentry as it expands into observability with Error Tracking, Logs and tracing?

Introduction

PostHog started in product analytics, but it now sells a growing set of products that overlap with observability: Error Tracking (first 100,000 exceptions free each month), Logs, and distributed tracing, which entered beta in July 2026, alongside LLM analytics for AI applications. That puts PostHog in front of two strong incumbents: Sentry, the default error-monitoring tool for developers, and Datadog, the dominant infrastructure observability platform with deep enterprise relationships. The question is how PostHog should compete. This is a hard strategy question because the obvious answer, "build a cheaper Datadog", ignores what PostHog is good at and where it would lose.

Key business objectives:

1. Grow observability revenue as a meaningful new line
2. Increase the number of PostHog products each customer uses
3. Strengthen PostHog's position with product engineers, its core persona
4. Avoid a costly feature war with better-funded incumbents

I'll clarify goals, analyse the market, set a vision and roadmap, prioritise initiatives, plan execution, define metrics, and manage risk.

Step 1

Clarify the Strategic Goals (3-4 minutes)

• Is the goal to replace Datadog and Sentry, or to win the observability needs of PostHog's existing customers?

Why it matters: Full replacement means competing on infrastructure monitoring, alerting and on-call, which is a very different product. Expected answer: Win observability for product engineering teams, starting with existing customers. Impact on approach: Focus on application-level observability linked to users, not host-level infrastructure metrics.

• Which customers matter most?

Why it matters: Startups and enterprises buy observability differently. Expected answer: Startups and scale-ups up to roughly 500 engineers, where product engineers choose tools. Impact on approach: Self-serve adoption and pricing transparency matter more than sales-led features.

• What is the time horizon and investment?

Why it matters: Observability needs heavy infrastructure for ingestion and storage. Expected answer: A three-year horizon, with a few small teams (Error Tracking, Logs, tracing) and shared ClickHouse infrastructure. Impact on approach: Choose areas where shared infrastructure gives an advantage.

Strategic assumptions:

1. PostHog competes for the product engineer's attention, not the SRE's budget.
2. The advantage is connecting errors, logs and traces to users, sessions, flags and revenue.
3. Pricing stays usage-based with a generous free tier.