PostHog

Key features

• Event tracking, funnels, user paths Event tracking, funnels, user paths: captured actions feed funnel reports and user-path visualisation, connecting product changes and campaigns to completed sign-ups and purchases.[1]

• Session replay tied to events Session replay tied to events: individual session recordings show clicks, navigation, and points of friction, analysable against the same event stream as the dashboards.[1][2]

• Feature flags with targeted rollouts Feature flags with targeted rollouts: releases gate behind flags with targeting rules, so teams ship gradually and limit the blast radius of new code.[1][2]

• Built-in experiments Built-in experiments: variants compare against conversion goals inside the suite, without exporting data to a separate testing tool.[1][2]

• Capture and private API Capture and private API: public POST-only endpoints capture events and evaluate flags, while authenticated private endpoints manage nearly all data; available to all users and instances including self-hosted ones. Private endpoints authenticate with personal, project-secret, or OAuth keys and carry documented per-resource rate limits.[1]

• Hobby Docker self-host under MIT Hobby Docker self-host under MIT: a free Docker Compose deploy and trial TUI installer run the same product as Cloud on operator infrastructure, with no tagged releases and officially unsupported status. The vendor recommends Cloud for most users and asks self-hosters to track the latest image, since every change ships continuously from master.[1][2]

• Managed Cloud free tier, EU/US regions Managed Cloud free tier, EU/US regions: Cloud starts with 1 million events, 5,000 recordings, and 1,500 survey responses free every month, with EU and US hosting regions. Usage beyond the free tier follows metered pricing on the official pricing page.[1][2]

• SAML SSO and SCIM on paid tiers SAML SSO and SCIM on paid tiers: organisation authentication supports verified domains, SAML, just-in-time provisioning, and SCIM, with some SSO features reserved for paid platform packages. Domain setup centres on a verified authentication domain, with DNS TXT verification on Cloud.[1]

Who will love it

• Consolidating product teams Consolidating product teams: one implementation and one event stream cover measurement, release control, and experimentation, removing integration work and conflicting numbers.[1][2]

• Data-must-stay-home operators Data-must-stay-home operators: the MIT-licensed hobby deploy runs the full product on operator infrastructure for privacy requirements or policies that exclude third-party clouds.[1]

• Startups scaling on metering Startups scaling on metering: the monthly free tier covers early volume, and costs then track event, recording, and survey usage instead of an upfront platform fee.[1][2]

Who should avoid it

• Needing supported self-hosting Needing supported self-hosting: the vendor manages no self-hosted instances and offers no paid support plans or guarantees for them; without in-house operations capacity, Cloud is the only honest option.[1]

• Wanting a flat fee Wanting a flat fee: costs scale with event, recording, and survey volume rather than a fixed per-month figure, so spiky traffic makes bills harder to forecast.[1][2]

• Pageview-stats-only need Pageview-stats-only need: where the requirement is visits, referrers, and conversions on one screen, the suite's flags, experiments, and replays are overhead; the published Matomo comparison is the better starting point.[1][2]

Alternatives and compatibility