PostHog

Visit Website

Introduction

PostHog is a product platform that brings many tools developers usually buy separately into one place. It includes product analytics, web analytics, session replay, feature flags, experiments, surveys, error tracking, a data warehouse and LLM observability, all sharing the same user and event data.

For quality work, the combination is the point. A feature flag can roll out a change to ten per cent of users; the experiment attached to it measures conversion and guardrail metrics; session replays show what users actually did on the new screen; error tracking shows whether exceptions rose; and a survey can ask users what they thought. Because these live on the same events, you can move from a metric dip to the replays and errors behind it without exporting data.

Feature flags support boolean and multivariate flags, percentage rollouts, targeting by person or group properties, local evaluation in server SDKs, and early-access feature management. Experiments use Bayesian statistics and can target funnels, trends or secondary metrics. Session replay records web and mobile sessions with privacy controls for masking inputs and text.

SDKs and integrations cover JavaScript, React, Next.js, Node.js, Python, Go, Ruby, PHP, Java, iOS, Android, React Native and Flutter, among others. PostHog Cloud runs in US or EU regions. The open-source repository is MIT licensed outside its ee/ directory, and a hobby self-hosted deployment is available, though the company recommends Cloud for production scale.

Pricing is usage-based with a free allowance every month for each product, and the site says usage stops at the free limits unless you add billing, so you cannot be charged by surprise. In the quality loop PostHog sits at production and UX validation, giving teams evidence about how releases behave for real users.

The source code is at PostHog/posthog on GitHub under the MIT (outside its ee/ directory) licence, with about 40,700 stars; the most recent commit was on 11 November 2026.

Define the events and properties experiments depend on before launch, so results are not skewed by missing or renamed events.

Features

1. Product analytics: Trends, funnels, retention, paths and SQL insights.
2. Session replay: Web and mobile recordings with masking.
3. Feature flags: Rollouts, targeting and local evaluation.
4. Experiments: A/B tests with Bayesian analysis.
5. Surveys: In-app surveys tied to user data.
6. Error tracking: Exceptions linked to sessions and users.
7. Heatmaps: Clicks and scroll depth.
8. Data warehouse: Join external data with events.
9. LLM observability: Trace and analyse AI features.
10. EU and US hosting: Regional cloud options.

Pros

1. All-in-one: Flags, experiments, replay and errors share one data model.
2. Transparent pricing: Monthly free tier per product and published usage rates.
3. Free to use: Open source under the MIT (outside its ee/ directory) licence, so the core tool costs nothing to use.
4. Actively maintained: The repository had commits as recent as 11 November 2026.
5. Community: About 40,700 GitHub stars.

Cons

1. Breadth over depth: Specialist tools may go deeper in a single area.
2. Self-hosting limits: Hobby deployment is not intended for large scale.
3. Event volume costs: High-traffic sites need to manage sampling and limits.
4. Privacy configuration: Replay masking needs careful setup for sensitive apps.

Usage and Links (Example)

Install the web snippet or SDK:

import posthog from "posthog-js";
posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY, { api_host: "https://eu.i.posthog.com" });

if (posthog.isFeatureEnabled("new-pricing-page")) {
  renderNewPricing();
}
posthog.capture("plan_selected", { plan: "pro" });

Server-side flag check in Python:

from posthog import Posthog
ph = Posthog(project_api_key="phc_...", host="https://eu.i.posthog.com", personal_api_key="phx_...")
enabled = ph.feature_enabled("new-pricing-page", "user-42")

Practical tips:

1. Attach an experiment to a flag and define guardrail metrics before launch.
2. Configure replay masking for forms and personal data.
3. Set billing limits per product to control spend.

Resources:

• PostHog website
• GitHub repository

Pricing

PostHog has a monthly free tier for every product with no credit card required; usage stops at free limits unless billing is added. Beyond that, pricing is usage-based per product, as listed on posthog.com/pricing. The open-source code is MIT licensed outside the ee/ directory.

Recommended for?

1. Product engineering teams that want analytics, flags and replay in one tool.
2. Startups relying on the monthly free tier.
3. Teams investigating UX issues with replay and surveys.
4. Not ideal if you only need one capability and already have best-of-breed tools.

Conclusion

PostHog gives developers a single place to release, measure and understand changes: flags and experiments, replays and errors, all on the same events.

Its free tier makes it easy to start; set masking and billing limits early, and use it to connect release decisions with real user behaviour.

On CheckOps, PostHog is filed under the Production monitoring & observability, Prototype & UX testing and Release & CI gates stages. Related tools listed here include GrowthBook, Statsig, Optimizely, Wingify (VWO and AB Tasty), LaunchDarkly and Microsoft Clarity. When comparing them, weigh the licence, the languages and platforms each supports, whether it is self-hosted or managed, and how cleanly it slots into your existing CI pipeline. Details on this page were checked against the official website, documentation and repository on 11 November 2026.