Consider it for
Product teams investigating activation, retention and releases with event-level data.
Analytics · Written evaluation
PostHog
Product analytics connected to session replay, feature flags and experimentation in one platform.
Plan at a glance
Plans & sources ↓- Starting plan
- Free
- Includes
- See the plan limits below.
Limits & source scope
Collection, consent, sampling and product-specific meters need deliberate configuration; a spending cap can interrupt collection.
Selected source read 2026-10-20Official sources read 9 October 2026. The evaluation below is editorial judgement based on documentation; no hands-on product test was performed.
Research scope & testing evidence
Price and billing scope
Official pricing ↗Source read · Selected free access
Selected published free allowances and project/retention scope only.
- FreeFree
1M analytics events, 5,000 session recordings and 1M feature-flag requests/month; one project, unlimited team members, one-year retention.
- Pay as you goUsage-dependent
Each product has its own rates, allowance and billing limits. No new numeric paid rate verified.
Free does not mean unlimited use; no new traffic, cost-saving or adoption claim. Source receipt.
Our evaluation
PostHog makes the strongest case when a product team needs to move from a conversion question to the sessions behind it, then measure a change. That connection can reduce the work of reconciling separate analytics and replay tools. It does not remove the need for an event taxonomy: autocapturing everything can create a noisy dataset and an unnecessary privacy burden. Start with one activation funnel and decide which events actually answer it. The free allowances are useful for a pilot, but each product has its own meter and retention policy. A billing limit protects the budget by limiting collection, which can also distort the picture during a traffic spike. A simple informational website may need much less machinery.
Fit and limits
Fit and limits
Check before committing
Collection, consent, sampling and product-specific meters need deliberate configuration; a spending cap can interrupt collection.
What the documentation confirms
What the documentation confirms
- Build funnels, retention reports and paths from captured product events.
- Open session recordings behind product analytics to investigate behavior.
- Set separate usage limits for metered products.
- posthog.com · Official documentation ↗
- posthog.com · Official documentation ↗
- posthog.com · Official documentation ↗
Selected official documents read 9 October 2026. Access can depend on plan, region and account.
Recorded editorial criteria
Recorded editorial criteria
These are the previously recorded editorial opinions used in the directory. They have no individually recorded assessment date and were not rescored during this documentation refresh. They are not product-test results.
| Functionality | 9/10 |
|---|---|
| Pricing value | 9/10 |
| Ease of use | 7/10 |
| Reliability | 8/10 |
| Founder fit | 9/10 |
Try one complete task
Instrument signup and first successful project creation in a staging app, generate three known user paths, build the funnel and inspect the matching replay with sensitive fields masked.
Create a trial worksheet →Compare requirements
Edited by Clinton Feyisitan · Evidence policy · Suggest a correction