← Back to software
AnalyticsSource checkedFree plan

PostHog

Product engineering platform combining analytics, replay, flags, experiments and data tools.

Budgeting for PostHog? Estimate your team's total software cost using prices you confirm with the vendor.
Editorial review
Official-source check: Aug 10, 2026

BUYER RESEARCH GUIDE

How to evaluate PostHog

Listed in Analytics under product analytics. For product teams reviewing user behavior, assess whether the product fits your product analytics needs using a realistic test workflow. The items below are research prompts, not confirmed product capabilities.

What to check

  • events and identities
  • funnels
  • retention
  • privacy controls

Other tools to compare

  • Amplitude
  • Countly
  • Heap
  • June

Comparison candidates, not tested rankings or endorsements.

Questions to ask before choosing PostHog
  1. How does PostHog handle events and identities for the intended use case?
  2. What are the constraints around funnels?
  3. Can the vendor document retention with a current official source?
  4. How does PostHog compare with a same-category alternative on privacy controls?

This is a research checklist based on directory classification, not a feature, pricing, security, or vendor verification report. Confirm purchase-critical details with current official documentation. The existing product record retains its own review status.

Pricing
Generous monthly free tiers; usage-based pricing above included limits
Free plan
Available
Free trial
Not confirmed
Quick verdict

PostHog is a Analytics option for Product analytics, Product engineering teams, Session replay and experiments. Analytics tools should be compared on the questions they answer, the data model they require and the effort needed to maintain trustworthy tracking.

PostHog overview

PostHog is a product engineering platform that combines product and web analytics with session replay, feature flags, experiments, surveys and data tooling. It can reduce the number of separate systems needed by product and engineering teams. Pricing is usage-based after monthly free allowances, so buyers should estimate events, recordings, flag requests and other product-specific units. A useful evaluation validates the event model, identity handling, privacy controls, retention and the team's ability to maintain accurate tracking.

Who PostHog is best for

  • ✓Product analytics
  • ✓Product engineering teams
  • ✓Session replay and experiments
  • ✓Teams combining analytics with feature delivery

When to consider another option

  • •Several billing units require forecasting
  • •Implementation quality determines insight quality
  • •Broad platform can be more than simple web analytics needs

Key features and capabilities

Product analytics

Build one decision-ready report in PostHog; check filters, export formats, refresh timing and who can see the result.

Web analytics

Build one decision-ready report in PostHog; check filters, export formats, refresh timing and who can see the result.

Session replay

Evaluate this PostHog capability with your own data, user roles and expected volume; record what works, what is limited and which plan is required.

Feature flags

Evaluate this PostHog capability with your own data, user roles and expected volume; record what works, what is limited and which plan is required.

Experiments

Evaluate this PostHog capability with your own data, user roles and expected volume; record what works, what is limited and which plan is required.

Surveys and data warehouse tools

Evaluate this PostHog capability with your own data, user roles and expected volume; record what works, what is limited and which plan is required.

PostHog pricing and value

Current pricing record: Generous monthly free tiers; usage-based pricing above included limits. Pricing should be modeled against users, contacts, executions, storage or other billing units that apply to the product.

  • Check the minimum plan containing every must-have feature.
  • Estimate cost at today's usage and at the next growth milestone.
  • Include migration, setup, training and administration time.
  • Verify renewal terms, overages, add-ons and cancellation rules.

Platforms

WebCloudSelf-hosted options

Integrations

JavaScriptReactNext.jsSegmentData warehousesCommon server SDKs
Shortlist comparison

PostHog alternatives and comparison table

Use the same decision factors for PostHog and these related options. The table reflects the directory record; confirm plan limits and current terms with each vendor.

Decision factorPostHogAdobe AnalyticsAirbyteAmplitude
CategoryAnalyticsAnalyticsAnalyticsAnalytics
PricingGenerous monthly free tiers; usage-based pricing above included limitsPricing requires confirmationPricing requires confirmationPricing requires confirmation on the official website.
Free accessFree planNot confirmedNot confirmedNot confirmed
Best forProduct analytics, Product engineering teams, Session replay and experiments, Teams combining analytics with feature deliveryAnalyticsAnalyticsProduct analytics teams, Growth teams, Digital product managers, Organizations with event data
Key featuresProduct analytics, Web analytics, Session replay, Feature flags, ExperimentsNot recordedNot recordedEvent analytics, Funnels, Retention analysis, Behavioral cohorts, User journeys
PlatformsWeb, Cloud, Self-hosted optionsWebWebWeb
IntegrationsJavaScript, React, Next.js, Segment, Data warehouses, Common server SDKsNot recordedNot recordedSegment, Snowflake, Braze, Slack
Trade-offsSeveral billing units require forecasting, Implementation quality determines insight quality, Broad platform can be more than simple web analytics needsNot recordedNot recordedRequires disciplined event instrumentation, Costs can grow with data volume, Advanced analysis has a learning curve

How to evaluate it before buying

Instrument one conversion journey, validate events against source data and recreate one decision-making dashboard.

  1. 1Event and identity model
  2. 2Implementation effort
  3. 3Retention and sampling
  4. 4Privacy controls
  5. 5Dashboards, exports and warehouse access

Pros

  • ✓Broad product-engineering toolkit
  • ✓Generous free usage allowances
  • ✓Usage controls and several deployment options

Cons and trade-offs

  • •Several billing units require forecasting
  • •Implementation quality determines insight quality
  • •Broad platform can be more than simple web analytics needs
Product-specific buying brief

Where PostHog fits—and where it does not

Strong fit

Product and engineering teams want analytics, session replay, feature flags and experiments close to one technical stack.

Consider another option

The team needs a simple marketing dashboard without engineering ownership of events, privacy and infrastructure choices.

A trial that can change the decision

Instrument one user journey, validate events against source behavior, replay a failure and run a controlled feature flag.

  • Event accuracy
  • Debugging value
  • Volume and retention cost

Cost people miss

Events, recordings, retention and engineering maintenance shape real cost more than the feature list.

Exit test

Export event definitions and key data, document flags and confirm that the product remains safe when the service is unavailable.

Frequently asked questions

What is PostHog best for?+

PostHog is most relevant for Product analytics, Product engineering teams, Session replay and experiments, Teams combining analytics with feature delivery. Fit still depends on the exact workflow, team size and required controls.

Does PostHog have a free plan?+

Yes. Our latest record shows a free plan for PostHog, although limits and included features can change.

How is PostHog priced?+

Generous monthly free tiers; usage-based pricing above included limits. Compare the billing unit, minimum tier and expected usage rather than relying only on the advertised starting price.

Which platforms does PostHog support?+

Our current record lists Web, Cloud, Self-hosted options. Confirm device, browser and regional requirements before rollout.

Which tools integrate with PostHog?+

Notable integrations in our record include JavaScript, React, Next.js, Segment, Data warehouses, Common server SDKs. Connector depth can differ, so test the fields and actions your workflow needs.

What should I test before choosing PostHog?+

Instrument one conversion journey, validate events against source data and recreate one decision-making dashboard. Also confirm export options so the team is not locked into a poor fit.

Compare PostHog with other options