PostHog
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by PostHog Inc. · posthog.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
PostHog at a glance
- Vendor
- PostHog Inc.
- Headquarters
- Incorporated in the United States source, captured 16 Nov 2026
- Data hosting
- Default not stated; pages mention the US and Germany source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 22 Sep 2026
- Panel verdict
- The AI panel rates PostHog 2.5/5, the mean of 6 judges. PostHog scores highest on pricing transparency at 7–8 and data and integrations at 5–8, lowest on sovereignty at 3–4 and experimentation scope at 2–5. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
PostHog scores highest on pricing transparency at 7–8 and data and integrations at 5–8, lowest on sovereignty at 3–4 and experimentation scope at 2–5. Pricing is public per-product: anonymous events $0.00005 and identified events $0.000198 each after the first 1M monthly, flag requests $0.0001, with a hard billing cap and no credit card required on the free plan; Boost, Scale and Enterprise go through sales. Experimentation scope is the sharpest split: 5 from the product engineer for a documented server-side model that runs on a third-party flag library, 2 from the growth lead because a marketing team would work through flags and code rather than a point-and-click editor. Data and integrations splits 5–8 over whether the managed warehouse and its 120+ external sources outweigh our finding of no public information on visitor-level export. Statistical rigour is flat at 4: Bayesian and frequentist engines are named, but we found no public guidance on sample size or peeking. Sovereignty sits low because contracting is with PostHog Inc. of San Francisco and Frankfurt EU hosting is an option the customer selects.
Speaks for it
- Public per-product unit prices with monthly free allowances, a hard billing cap and no minimum spend
- Both a Bayesian engine and a frequentist engine using t-tests and confidence intervals are documented across five metric types
- Cookieless tracking mode with 'always' and 'on reject' settings, with a single first-party cookie and no cross-site tracking
- A documented warehouse API with webhooks, a Segment destination and 120+ external sources such as Stripe and Postgres
- Asynchronous snippet with a stated 100-500ms flag load and a documented bootstrapping fix for flicker
Held against it
- Contracting is with PostHog Inc. of San Francisco and EU hosting in Frankfurt is an option the customer selects rather than the default
- We found no public information on a visual editor, split-URL or multivariate tests, holdouts, mutually exclusive groups or personalisation
- We found no public information on sample-size guidance, peeking protection, multiple-comparison correction or sample ratio mismatch detection
- We found no public information on visitor-level export of experiment results or an API for reading them
- The captured pages give different figures for pay-as-you-go event retention, two years on one and seven years on another
Best for
- Your engineering team can ship experiments in code through feature flags, even against a third-party flag library with results computed in PostHog
- You want to estimate your bill from event and flag-request volume before signing, with public unit prices and a hard billing cap
- You want a managed warehouse combining product data with 120+ external sources such as Stripe and Postgres, with SQL and BI on top
- You need measurement to continue without cookies after a consent rejection, via the cookieless mode's 'on reject' setting
Avoid if
- Your marketing team needs a point-and-click visual editor and audience targeting rather than code-level flags
- You must defend a winner with sample-size planning, peeking protection or sample ratio mismatch checks
- You need visitor-level experiment results exported to your own warehouse for independent re-analysis
- Your procurement requires an EU contracting entity and EU processing as the default rather than a selectable option
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 2 of 5 |
| Statistical method & guardrails | 2 of 5 |
| Consent & visitor tracking | 2 of 5 |
| Snippet performance & flicker | 2.5 of 5 |
| Analytics, data export & integrations | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3.5 of 5 |
Experiment types & delivery
panel disagrees
Show reasoningHide reasoning
How this is scored
What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
0 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, and personalisation that can itself be tested against a control.
10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.
The Growth Lead
The captured pages show experiments delivered through feature flags, with variants compared against a fixed control baseline, a choice of Bayesian or frequentist evaluation, and five metric types including funnels and retention; experiments can even run with an external flag library. We found no public information on a visual editor, split-URL or multivariate tests, or audience targeting conditions, so the marketing team would be working through flags and code rather than a point-and-click editor. 6 6 7 8
The E-Commerce Manager
Experiments run through code and feature flags rather than a visual editor: variants with a fixed control name, experiments that can run against a third-party flag library, and flag flicker addressed via bootstrapping and local evaluation. We found no public information on multivariate tests, holdouts, mutually exclusive experiment groups, or personalisation that can itself be tested against a control — the last of those is exactly what I want for the shop. 5 6 12 6
The Product Engineer
Experiments hang off feature flags with bootstrapping and local evaluation documented, and you can run an experiment on a third-party flag library while the results are still computed here — that's the server-side model I'd actually ship. The docs sweat real details, like the fixed control variant used as the results baseline. I found no public information on SDK coverage per language, mutually exclusive groups, holdouts or personalisation. 6 6 12 2
The CRO Consultant
Experiments are documented as flag-driven: results are computed against a fixed 'control' baseline, they can be tracked even when another feature flag library serves the variants through a named flag key, and experiments are billed together with feature flags. I found no public information on a visual editor, multivariate or split-URL tests, audience targeting or personalisation, so I am scoring the code-level A/B capability that is actually documented. 6 6 12 2
The Data Protection Officer
Experiments are documented as feature-flag variants that can also run on a customer's own flag library with results calculated in PostHog, evaluated across five metric types including funnel, mean, percentile, ratio and retention. We found no public information on a visual editor, split-URL tests, audience targeting by behaviour or attributes, personalisation, multi-page tests or holdouts. 6 8 7 6
The Skeptic
Experiments run through feature flags with a fixed control variant and five documented metric types (funnel, mean, percentile, ratio, retention), and the documentation shows running experiments while tracking results against an external flag library. We found no public information in the captured pages on a visual editor, split-URL tests, multi-page tests, holdouts, mutually exclusive groups or personalisation. 6 6 2 8
Statistical method & guardrails
Show reasoningHide reasoning
How this is scored
Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
0 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.
3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.
5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.
8 — Sequential testing or another documented protection against peeking, plus correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.
10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.
The Growth Lead
Both a Bayesian engine that reports the probability one variant beats another and a frequentist engine using t-tests and confidence intervals are documented by name, with percentile metrics handling multiple events per user. We found no public information on sample-size guidance, test-duration rules, peeking protection, or sample ratio mismatch detection, which is what I would need before defending a number to the board. 7 6 7 8
The E-Commerce Manager
Both engines are documented by name — a Bayesian engine reporting the probability one variant beats another, and a frequentist engine using t-tests and confidence intervals — across five metric types, including percentiles that account for multiple events per user. We found no public information on sample-size guidance, protections against peeking, sample ratio mismatch detection, CUPED-style variance reduction, or guardrail metrics that could stop a harmful test. 7 8 8
The Product Engineer
Both engines are documented by name — a Bayesian engine reporting probability-to-beat instead of p-values, and a frequentist engine using t-tests with confidence intervals across five metric types, including percentile metrics that account for multiple events per user. I found no public information on sample-size or duration guidance, protection against peeking, multiple-comparison correction or sample ratio mismatch detection. 7 8
The CRO Consultant
Two engines are documented by name: a Bayesian engine that reports the probability one variant beats another instead of p-values, and a frequentist engine using t-tests and confidence intervals, across five metric types including funnel, percentile and retention. I found no public information on sample-size guidance, protection against peeking, multiple-comparison correction or sample ratio mismatch detection, so this stops short of the guardrail level my clients need to defend a winner. 7 8
The Data Protection Officer
Both engines are documented by name: a Bayesian engine reporting the probability that one variant beats another, and a frequentist engine using t-tests and confidence intervals. We found no public information on sample-size or test-duration guidance, protection against peeking, correction for multiple comparisons, sample ratio mismatch detection or guardrail metrics. 7 8 8
The Skeptic
Both engines are named — a Bayesian engine reporting the probability that one variant is better than another instead of p-values, and a frequentist engine using t-tests and confidence intervals — with the five metric types documented. What I read for and did not find: sample ratio mismatch checks, any stated handling of peeking or of multiple metrics or variants, or a sample-size calculator; a probability-to-beat figure with no documented stopping rule is exactly how winners regress to zero. 7 8 8
Consent & visitor tracking
Show reasoningHide reasoning
How this is scored
Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
0 — No consent handling of any kind: the vendor states that the script runs and stores identifiers regardless of the visitor's consent.
3 — A documented integration with a consent tool or a setting that holds the script until consent, and the cookies or storage keys the script sets listed.
5 — Documented behaviour before and after consent, integration with common consent management platforms, and a published list of cookies and storage keys with their lifetime.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, IP anonymisation and retention of visitor data stated, and guidance on the legal basis for testing in the EU under §25 TDDDG.
10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.
The Growth Lead
The JavaScript SDK documents a cookieless mode with an 'on reject' setting that switches to cookieless audience measurement when consent is refused, and the SDK's cookie behaviour is documented as a single first-party cookie that does not track across sites. We found no public information on integration with consent management platforms, storage lifetimes, or guidance on the legal basis for testing under German consent rules, so my privacy officer would have to fill those gaps herself. 9 9
The E-Commerce Manager
The JavaScript SDK documents a cookieless mode with an on reject setting, so measurement continues without cookies after a consent rejection, and product cookies are first-party only with no cross-site tracking; a GDPR page recommends the EU cloud. We found no public information on integration with named consent management platforms, a published list of storage keys with their lifetimes, or written guidance on the legal basis for testing under §25 TDDDG. 9 10 9
The Product Engineer
The JavaScript SDK has a documented cookieless mode with "always" and "on reject" options plus a server hash mode enabled in project settings — a genuinely consent-reactive path — and cookies are first-party only with no cross-site tracking, while event retention is stated per plan from one year up to seven. I found no public information on consent management platform integrations, a published list of cookies and storage keys with lifetimes, or guidance on the legal basis for testing under the German telemedia rules. 9 9 2
The CRO Consultant
The JavaScript SDK documents a cookieless tracking mode, enabled in project settings, that runs always or in response to a consent rejection, and states it stores a first-party cookie with no cross-site tracking — a starting point a DPO will engage with. I found no public information on consent management platform integrations, a published list of cookies with lifetimes for the customer's snippet, IP anonymisation, or guidance on the legal basis for testing under §25 TDDDG. 9 9
The Data Protection Officer
A cookieless tracking mode with "always" and "on reject" settings, a single first-party in-house cookie, and a GDPR page steering European customers to the Frankfurt cloud are documented. The captured pages do not say whether the test script may run before the consent banner is answered, we found no list of storage keys with their lifetimes, no consent management platform named, no consent-pending mode and no guidance on the legal basis for testing under §25 TDDDG. 9 9 12 10
The Skeptic
The JavaScript SDK documents a cookieless mode with 'always' and 'on reject' settings, storage is a first-party cookie that does not track across sites, and the GDPR page points compliance-minded customers at the Frankfurt cloud. We found no public information on integration with named consent management platforms, a published list of storage keys with their lifetimes, or guidance on the legal basis for testing under §25 TDDDG. 9 10 9
Snippet performance & flicker
Show reasoningHide reasoning
How this is scored
The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
0 — A synchronous, render-blocking snippet stated as the only way to install the product, with no flicker handling.
3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.
5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.
8 — Published performance figures including the impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.
10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.
The Growth Lead
The snippet is documented as asynchronous and non-blocking, with the trade-off honestly stated that some events can be missed before the library loads, and feature flag flicker is addressed with a stated 100-500ms default load time plus a bootstrapping and local evaluation guide. We found no published figures on Core Web Vitals impact, script size, or a first-party hosting option for the script. 12 11
The E-Commerce Manager
The snippet loads asynchronously with the trade-off stated honestly (events can be missed before the library loads), and flag latency of roughly 100-500ms with flicker fixed through bootstrapping is published plainly — on a product page I would have to bootstrap to avoid the flash. We found no public information on script size, CDN delivery, per-project bundles, or measured Core Web Vitals impact; a self-hosted MIT-licensed edition exists as the heavier alternative. 12 11
The Product Engineer
The snippet loads async with the trade-off stated in plain words — some events can be missed before the library loads — and flag fetch latency is published at about 100–500ms, with bootstrapping and local evaluation as the documented fix for flicker; the MIT-licensed open-source edition gives a self-hosted path for first-party delivery. Publishing a latency number instead of claiming zero cost is the honest version. I found no public information on measured Core Web Vitals impact or per-project script bundles. 11 12 2
The CRO Consultant
The snippet is documented as asynchronous so it does not block page load, with the trade-off stated that events can be missed before the library loads, and flicker is addressed head-on: flags load in about 100-500ms by default, during which they are disabled, with bootstrapping documented as the fix. I found no published figures for Core Web Vitals impact or script size. 11 12
The Data Protection Officer
The snippet is documented to load the full library asynchronously so it does not block page load, with the stated trade-off that events before the library loads can be missed, and flag flicker during a stated 100-500ms flag load is addressed through bootstrapping. We found no published figures on script size or Core Web Vitals impact, and no self-hosting option for the script. 11 12
The Skeptic
The snippet is documented as asynchronous and non-blocking, with the trade-off stated plainly that events before the library loads can be missed, and flag flicker is explained with a 100-500ms load figure and a bootstrapping fix. We found no published snippet size, CDN delivery detail, Core Web Vitals impact or first-party script-hosting option in the captured pages. 12 11
Analytics, data export & integrations
panel disagrees
Show reasoningHide reasoning
How this is scored
Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
0 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.
3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.
5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.
8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API for managing experiments and reading results with stated limits.
10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.
The Growth Lead
There is a documented API with personal-key bearer authentication over the data warehouse, plus webhooks, a SQL editor and BI layer, 120-plus inbound warehouse sources from Stripe to Postgres, and a Segment destination for pageviews and custom events. The API evidence we captured covers warehouse operations and monitoring rather than reading experiment results, and we found no public information on exporting visitor-level experiment data for independent re-analysis in our own stack. 13 14 1 13
The E-Commerce Manager
A documented API with key scopes and webhooks, a Segment destination, and a managed data warehouse ingesting from 900+ sources with its own API endpoints give me several ways to pull results out and check them. The warehouse is PostHog's managed one, though, and we found no public information on Google Analytics or tag-manager integrations, visitor-level export into our own warehouse, or stated API rate limits. 13 14 1
The Product Engineer
The data warehouse API is buildable-on: personal-key auth with granular scopes, provisioning and deprovisioning endpoints, monitoring timeseries, batch export scopes, and a warehouse fed by 120+ external sources like Stripe and Postgres with a SQL editor and webhooks. The Segment destination page even lists which features it cannot carry, which is the kind of documentation I trust. The model is PostHog as the warehouse rather than metrics computed in the customer's own, and I found no public information on stated API rate limits or open-format export of full historical experiment data. 13 13 1 14
The CRO Consultant
There is a documented API with personal API key bearer authentication and scoped endpoints, webhooks, a Segment destination, and a managed data warehouse ingesting from 120+ external sources such as Stripe, Postgres and HubSpot with SQL and BI on top. That warehouse is the vendor's own, however, and I found no public information on exporting visitor-level experiment results, streaming to the customer's own warehouse, or Google Analytics and tag manager integrations. 13 1 14 13
The Data Protection Officer
A documented API with personal API key authentication covers the managed data warehouse, PostHog is a named Segment destination for pageviews, custom events and user identification, and 900-plus sources feed a SQL editor with webhooks. We found no public information on export of visitor-level raw data to a customer's own warehouse, or an API for managing experiments and reading results. 14 1 13 13
The Skeptic
A documented, scope-limited API with bearer-token authentication covers the data warehouse, Segment is offered as a destination, webhooks are listed, and 900+ sources feed a warehouse with 120+ external syncs. A batch-export scope appears among the API key scopes, but we found no public information on visitor-level export or an API for reading experiment results — an experiment result I cannot check in my own data is a claim, not a finding. 13 14 1 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
The contracting entity is PostHog Inc. of San Francisco, with EU hosting offered as an optional Frankfurt cloud region the vendor recommends for GDPR compliance, a self-serve DPA generator with a path to a signed DPA, Standard Contractual Clauses, and Data Privacy Framework certification. Subprocessors Amazon Web Services and Google Cloud Platform are named without locations, EU hosting is a selectable option rather than the standard configuration, and the website itself is hosted in the United States. 3 9 10
The E-Commerce Manager
The contracting entity is PostHog Inc. of San Francisco, with AWS and Google Cloud named as subprocessors, and EU processing is offered as an option through PostHog Cloud EU hosted in Frankfurt — workable for a German shop, but it is a choice, not the default. A self-serve data processing agreement is offered and subsidiaries in the UK and Germany are named, but the captured pages show no EU-entity processing arrangement and no subprocessor locations beyond the names. 3 10 2
The Product Engineer
PostHog Inc. is the contracting entity in San Francisco with UK and German subsidiaries named, and EU hosting is an option the customer selects: PostHog Cloud EU on servers in Frankfurt, recommended for GDPR, with SCCs and Data Privacy Framework certification as transfer safeguards plus a self-serve DPA generator and a subprocessor list naming AWS and Google Cloud. EU hosting is an option rather than the stated default. I found no public information on where the snippet itself is delivered from. 3 10 2
The CRO Consultant
Contracting is with PostHog Inc., a San Francisco entity, and EU residency is opt-in: PostHog Cloud EU on Frankfurt servers is offered free and recommended for GDPR, while the websites default to US hosting; SCCs and Data Privacy Framework certification are stated, AWS and GCP are named as subprocessors, and a self-serve DPA generator is offered. I found no public information on subprocessor locations or on the German and UK subsidiaries acting as contracting entities. 3 10 2
The Data Protection Officer
PostHog Cloud EU hosted in Frankfurt is documented as an option the customer selects, and a subprocessor list names Amazon Web Services and Google Cloud Platform, though without locations and with no delivery CDN named. The contracting entity is the US-based PostHog Inc., backed by Standard Contractual Clauses and Data Privacy Framework certification plus a self-serve DPA generator, so EU processing is offered as a choice rather than the standard configuration for visitor data. 3 10 2
The Skeptic
The contracting entity is PostHog Inc. of San Francisco, websites are hosted in the United States unless the customer selects EU hosting, and EU cloud in Frankfurt is offered as an option, with Data Privacy Framework and SCC safeguards, a self-serve DPA generator and named subprocessors AWS and GCP. EU residency is an option rather than the standard, which is what sets the level. 3 9 10 2
Pricing transparency
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead
Per-unit prices are public for every usage metric — anonymous events at $0.00005 each and identified events at $0.000198 each after the first million, flag requests, replays and warehouse rows — with monthly free allowances, monthly billing, a hard billing limit that stops charges rather than invoicing overage, taxes stated as excluded, and no setup fees or minimum spend. What is not computable from the pages is the annual-commitment discount threshold and the Boost, Scale and Enterprise platform packages, for which we found no public prices. 1 2 2
The E-Commerce Manager
Every usage dimension carries a public unit price — $0.00005/event anonymous, $0.000198 identified, $0.0001/request for flags, $0.005/recording for replays, $0.000015/row for warehouse — with monthly free allowances, a hard billing cap, month-to-month default terms, no minimums, taxes stated as excluded, and experiments billed with feature flags. Usage-based billing with caps means no December tier cliff, which is what I want to see; what stays off the public pages is the price of the Boost, Scale and Enterprise platform packages and the spend level where annual discounts begin. 4 1 2 2
The Product Engineer
Every product carries a public per-unit price on its documented metric — events at $0.00005 (identified events $0.000198 each after the first 1M), flag requests at $0.0001, recordings at $0.005, warehouse rows at $0.000015 — with monthly free tiers, a hard billing cap that drops events instead of charging overage, no minimum spend, a month-to-month default, and prices in USD excluding taxes. An annual cost is computable for a given volume without a sales call. The gaps are real though: annual and volume discounts apply "above a certain spend" with no published threshold, and enterprise platform features go through sales. 2 2 1 2
The CRO Consultant
Unit prices are public per product — anonymous events $0.00005 each after the first 1M free monthly, identified events $0.000198, feature flag and experiment requests $0.0001 after 1M free, replays $0.005 after 5K free — with hard billing caps, free-plan overage dropped rather than billed, monthly billing, no minimum spend, unlimited team members, six projects on the paid plan, and prices in USD excluding taxes, so I can estimate a client's bill from event and flag-request volume before signing. The platform packages with SSO and audit logs sit behind sales and volume discount schedules are unpublished, and the captured pages give different figures for pay-as-you-go data retention — two years on one, seven years on another. 2 1 2 2
The Data Protection Officer
Per-product unit prices with monthly free allowances are published — anonymous events at $0.00005 each and identified events at $0.000198 each after the first 1 million, feature flags at $0.0001 per request after 1 million, session replay at $0.005 per recording — with a hard billing limit cap, monthly billing, no minimum spend, unlimited team members and USD prices excluding taxes; experiments are billed with feature flags. Annual discounts apply only "above a certain spend" and we found no public prices for the Boost, Scale and Enterprise packages, so a full annual invoice is not derivable from the public pages alone. 1 2 2 2
The Skeptic
Per-product unit prices are public — anonymous events at $0.00005 each after the first 1M, identified events at $0.000198, feature flags at $0.0001 per request — with monthly free allowances, a hard billing cap, a month-to-month default term and tax treatment stated. The platform packages Boost, Scale and Enterprise and the annual-commitment discount schedule are not priced in the captured pages, so a buyer cannot compute every add-on from public pages alone. 4 1 2 2
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in US
unverified
Why unverified?The privacy policy states headquarters rather than a company register, gives no state of incorporation for PostHog Inc., and the site also names a UK subsidiary (Hiberly Ltd) and a German one (PostHog GmbH). |
0/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The excerpt shows only the navigation item 'DPA generator' plus a 'See how to get a signed DPA' link, not the generator tool itself, so how the agreement is concluded online is not shown. |
1/1 pts | 3 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about PostHog
Is PostHog European?
No. whats-best.ai classifies PostHog as Rest of world. Its vendor, PostHog Inc., is incorporated in the United States, per the vendor’s page captured 16 Nov 2026.
Where does PostHog store data?
The default storage location for customer data is not stated on the vendor’s pages as of 16 Nov 2026. The vendor’s pages mention the US and Germany as hosting locations, per the vendor’s page captured 16 Nov 2026.
Does PostHog have a free plan?
Yes. PostHog has a free plan, per the vendor’s page captured 22 Sep 2026.
What are the best alternatives to PostHog?
As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Varify.io (3/5) and Webtrends Optimize (3/5) highest among the other 45 Conversion Optimization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Varify.io (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: PostHog alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The excerpt shows only the navigation item 'DPA generator' plus a 'See how to get a signed DPA' link, not the generator tool itself, so how the agreement is concluded online is not shown.
- Weak sourcing — Legal entity. The privacy policy states headquarters rather than a company register, gives no state of incorporation for PostHog Inc., and the site also names a UK subsidiary (Hiberly Ltd) and a German one (PostHog GmbH).
- Weak sourcing — Hosting location, Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 163 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 14 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage posthog.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 22 Sep 2026 Details →
- 2 Pricing page posthog.com Checked 16 Nov 2026 +4 earlier captures: 2 Nov 2026, 26 Oct 2026, 19 Oct 2026, 22 Sep 2026 Details →
- 3 Privacy policy posthog.com Checked 16 Nov 2026 Details →
- 4 Terms of service posthog.com Checked 16 Nov 2026 Details →
- 5 Experiment types & delivery — found from sitemap posthog.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 6 Experiment types & delivery — found from sitemap posthog.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 7 Statistical method & guardrails — found from sitemap posthog.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 1 Oct 2026 Details →
- 8 Statistical method & guardrails — found from sitemap posthog.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 1 Oct 2026 Details →
- 9 Consent & visitor tracking — found from sitemap posthog.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 10 Consent & visitor tracking — found from sitemap posthog.com Checked 16 Nov 2026 Details →
- 11 Snippet performance & flicker — found from sitemap posthog.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 12 Snippet performance & flicker — found from sitemap posthog.com Checked 16 Nov 2026 Details →
- 13 Analytics, data export & integrations — found from sitemap posthog.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 14 Analytics, data export & integrations — found from sitemap posthog.com Checked 16 Nov 2026 Details →