PostHog
By PostHog
PostHog is an open-source product analytics platform that combines event tracking, session replay, feature flags, and A/B experimentation in a single self-hostable or cloud-hosted product. It is designed to give engineering-led teams a…
Definition
PostHog is an open-source product analytics platform that combines event tracking, session replay, feature flags, and A/B experimentation in a single self-hostable or cloud-hosted product. It is designed to give engineering-led teams a single tool covering the full product analytics workflow — from capturing user behavior to running experiments and rolling out features gradually — without needing to license separate specialist tools for each function.
Overview
PostHog was built for teams, often smaller or engineering-driven ones, that wanted the core capabilities of tools like Amplitude, LaunchDarkly, and FullStory without paying for and integrating four separate vendor products, and without necessarily sending user data to an external SaaS company at all. Its open-source core lets teams self-host the entire platform on their own infrastructure, addressing both cost and data-residency concerns that come up in regulated industries or privacy-conscious organizations. Mechanically, PostHog's SDKs capture events from web and mobile applications similarly to other analytics tools, but the platform is architected as a set of connected modules on shared event data: the same underlying event stream feeds funnel and retention analysis, session replay recordings that let a team watch an actual user's screen interactions, feature flags that can be toggled per user segment for gradual rollouts, and experimentation tooling that measures the impact of those flag-gated changes, all cross-referenced against each other in one interface. An engineer investigating a spike in errors, for instance, can jump from a funnel drop-off directly into the session replays of the affected users without leaving the product or reconciling data across separate tools. Within the product analytics landscape, PostHog's differentiation is breadth-in-one-platform combined with an open-source, self-hostable model, contrasting with Amplitude or Mixpanel's cloud-only, analytics-focused products and with the separate point solutions many teams previously stitched together for flags, replay, and experimentation individually. This makes PostHog attractive to smaller teams wanting to consolidate tooling, though larger organizations may still find best-of-breed specialist tools more capable in any single discipline. In practice, teams use PostHog to track feature usage and funnels the same way they would with Amplitude, to watch session replays when investigating a confusing user complaint or a suspected bug, to gate new features behind flags for a subset of users before a full release, and to measure the impact of those changes with built-in experimentation, all from data already flowing through the same pipeline. The trade-off of an all-in-one, self-hostable platform is that each individual module — analytics, replay, flags, experimentation — is generally less deep than a dedicated specialist product in that category, and self-hosting shifts operational responsibility for scaling and maintaining the platform onto the team that runs it, an overhead the fully managed cloud offering is designed to remove for teams that would rather not take it on. Teams choosing between the two deployment modes typically weigh engineering bandwidth for running infrastructure against the cost of a managed subscription, rather than any difference in the underlying feature set.
Key Features
- Combined event analytics, session replay, and feature flags in one platform
- Open-source core with both self-hosted and managed cloud options
- Built-in A/B experimentation tied to the same feature flag system
- Session replay for watching real user interactions and bugs
- Funnel, retention, and path analysis on shared event data
- Self-hosting option for data residency and cost-sensitive teams
- Single data pipeline feeding all product modules rather than separate tools