PostHog

PostHog is a product analytics platform, built primarily for engineering and product teams, that tracks how people actually use a digital product and bundles a wide set of related tools into one stack. At its core it captures events — the actions users take inside a product, such as signing up, clicking a button, or completing a purchase — and turns them into trends, funnels, and retention analysis so teams can see where users engage, convert, or drop off. Around that core it adds session replay (watching recordings of real user sessions), feature flags (turning features on or off for chosen users), A/B experimentation, surveys, and error tracking. Founded in 2020, PostHog is notable for being open source: its core is available under a permissive license, so teams can self-host it on their own infrastructure or use its managed cloud.

PostHog's positioning is what sets it apart from a plain analytics dashboard. Rather than only reporting what happened, it aims to be an all-in-one platform for building better products — combining the measurement (analytics, replay) with the tools to act on it (feature flags, experiments) in one place, with a single way to instrument the product. Because it is open source and can be self-hosted, it appeals to teams that want to keep behavioral data on their own infrastructure rather than sending it to a third-party service, which matters for privacy-conscious or data-sensitive products. For a growth or product team, PostHog answers where users engage and drop off, and it lets the team run the experiments and rollouts that respond to those findings without stitching together several separate tools.

PostHog belongs to the product analytics category, whose job is to reveal how users behave inside a product — funnels, retention, feature usage — as distinct from web analytics tools focused on traffic and page views, or from business-intelligence tools focused on querying and visualizing warehoused data. Compared with other product analytics platforms, PostHog's differentiators are its open-source, self-hostable core and its all-in-one breadth: many competitors do analytics alone and require separate tools for session replay, feature flags, or experimentation, whereas PostHog folds them into one stack. That consolidation means fewer integrations to maintain and one consistent event model across measurement and action, which is a large part of its appeal to developer-led teams.

The self-hosting angle is the clearest line between PostHog and typical SaaS analytics. A closed, cloud-only analytics tool sends your users' behavioral data to a vendor's servers; PostHog's open-source core lets a team run the whole platform on infrastructure it controls, keeping that data in-house. That is a meaningful distinction for products with strict privacy or data-residency needs, and it is why PostHog is often chosen where sending behavioral data to an outside service is unacceptable. It also differs from a data warehouse like Redshift: a warehouse is a general store you query with SQL, while PostHog is a purpose-built product-analytics application with pre-built funnels, replay, and experiments. The distinction to hold is that PostHog is an all-in-one, self-hostable product analytics platform, not merely a dashboard and not a general-purpose warehouse.

Using PostHog well starts with a clear event plan — deciding which user actions matter and instrumenting them consistently — so that funnels and retention analysis reflect real behavior rather than noise. From there the value comes from using the whole stack together: watch session replays to understand why a funnel leaks, ship a fix behind a feature flag to a slice of users, run an experiment to measure whether it helps, and use surveys to hear directly from users. Teams also choose deliberately between self-hosting (for control over where behavioral data lives) and the managed cloud (for less operational overhead), based on their privacy needs and engineering capacity. The point is to close the loop from measurement to action inside one platform.

The failure modes are instrumenting events sloppily so the analytics are unreliable, treating PostHog as only a dashboard while ignoring the feature flags, experiments, and replay that make it more than reporting, and self-hosting without the engineering capacity to run and maintain it. Another trap is confusing product analytics with web analytics or with a data warehouse and expecting PostHog to do a job it is not built for. The discipline is to plan events carefully, use the combined analytics-plus-action stack to move from insight to change, and choose the hosting model to match privacy and resource realities — treating PostHog as an all-in-one product analytics platform, not a single-purpose chart.

PostHog — an open-source product analytics platform bundling event analytics, session replay, feature flags, and experimentation — measures product usage and provides the tools to act on it, self-hosted or in the cloud.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where posthog is a core concern: