PostHog

Price each product separately

PostHog pricing lists 1 million analytics events monthly. PostHog replay pricing lists separate monthly allowances of 5,000 web and 2,500 mobile recordings. Events, recordings and flag requests have different meters; projects share an organization allowance.

PostHog’s product analytics pricing lists the first million events free each month and the next tier starting at $0.0000500 per event, with lower marginal rates at greater volumes. Other products have separate meters; confirm your actual configuration and charges.

A billing limit can prevent further ingestion for many products. PostHog says events dropped after a limit are permanently dropped. Decide whether a hard cap or unexpected cost is the greater operational risk.

Control collection and identity

PostHog’s product analytics guide says autocapture is on by default in its setup. Inventory captured events and properties before enabling it; free-text or sensitive properties may require exclusion.

PostHog documents identify and alias flows and merge restrictions. Use a stable identifier and test anonymous-to-known transitions, shared devices and logout. Check whether a mistaken merge can be corrected before production.

Set an archive and hosting plan

PostHog pricing says events and metadata are guaranteed for one year on Free and seven years on paid plans; replay retention is shorter and varies by plan. Confirm the current contract and export a representative event history before expiry.

PostHog batch exports describe scheduled exports of events. Check destination costs and point-in-time identity fields, then reconcile records against your own user mapping.

PostHog’s self-hosting guide describes an unsupported hobby deployment without paid support or operational guarantees. PostHog says paid-plan features are Cloud-only and new paid Kubernetes deployments are unsupported. Budget for your own infrastructure and operations.

Apply privacy controls for the actual platform

PostHog’s replay privacy guide says general web text is not masked by default and offers selective masking and blocking. Its mobile guidance describes different defaults.

Inventory inputs, page text, attributes, URLs, images, logs and network data. Configure the actual SDK and review a synthetic recording before rollout; a masked input alone does not prove the whole replay is safe.

How to compare the alternatives

Compare Mixpanel and Amplitude on the same event and identity cases. Their head-to-head comparison explains how contract meters can differ.

Common questions

Does PostHog charge only for events?

No. PostHog lists separate meters for products including analytics, replay and flags.

Is all replay text masked by default?

PostHog says general web text is not masked by default. Defaults vary by platform and configuration.

Sources and scope

We read the linked vendor pricing and documentation on November 5, 2026. This is documentation-only research; we have not used the products, installed SDKs, collected events or tested exports or replay.

Inclusion and corrections are free. Any future vendor placement will be clearly labeled and will not determine editorial judgment or order. Confirm current terms and test your own configuration.

Sponsorship never changes this page. How we research.