0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Datadog, Inc. · www.geteppo.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.
Eppo at a glance
- Vendor
- Datadog, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Eppo 2/5, the mean of 6 judges. Eppo — acquired by Datadog and now branded Datadog Experiments — is a warehouse-native experimentation and feature-flagging platform. how scores are made
- As of
- Vendor pages captured 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
Eppo — acquired by Datadog and now branded Datadog Experiments — is a warehouse-native experimentation and feature-flagging platform. The bench scored it strongest on data and integrations, where scores cluster at 7-8, and on experimentation scope, also 7-8: experiments run on the customer's own warehouse — Snowflake, Databricks, BigQuery and Redshift are named — with no data duplication, and SDKs are documented for twelve languages. Statistical rigour clusters at 6-7 on named methods — sequential, fixed-sample and Bayesian frameworks with CUPED variance reduction — though we found no public information on sample-ratio-mismatch detection or correction for multiple metrics. The weakest areas are consent and tracking, scored 0-2, with no public information on how the script behaves relative to consent; sovereignty, scored 0-3, where the published terms point to Eppo Data, Inc. of San Francisco under Datadog's master agreement; and performance impact, clustering at 2. The genuine split is fit: one judge scored experimentation scope 8 for the server-side SDK programme while the e-commerce judge returned 0, and several judges found no public information on a visual editor or multi-page tests. We found no published prices.
Speaks for it
- Experiments run natively on your own warehouse — Snowflake, Databricks, BigQuery and Redshift are named — with no data duplication
- Statistical methods are named outright: sequential, fixed-sample and Bayesian frameworks, CUPED variance reduction, and non-inferiority testing with guardrail cutoffs
- SDKs are documented for twelve languages, from JavaScript to Android, spanning client and server
- Flag configurations are published to a CDN with local caching and no real-time reliance on the vendor's API
- The vendor states that PII never leaves your system, with results described as leaving a paper trail easy to audit and reconcile
Held against it
- We found no public information on when the assignment script runs relative to consent, what it stores on a visitor's device, or whether a cookieless mode exists
- We found no published figures on script weight, flicker handling or impact on Core Web Vitals
- Contracting points to Eppo Data, Inc. of San Francisco under Datadog's Master Subscription Agreement, and only subprocessor categories — without locations — are published
- We found no public information on a visual editor or on split-URL and multi-page tests, so building a test takes a developer
- We found no public information on a documented API for managing experiments and reading results, on webhooks, or on export formats and limits
Best for
- You run server-side or app experiments and want results computed in your own warehouse — Snowflake, Databricks, BigQuery or Redshift — where they stay in your data and can be audited
- Your engineers ship in the twelve documented SDK languages and want feature gates, controlled rollouts, mutual-exclusion layers and global holdouts on one metric model
- You need named statistics — sequential, fixed-sample and Bayesian with CUPED variance reduction — that you can defend to finance
Avoid if
- Your marketing team needs point-and-click page testing without developers; the captured pages describe an SDK-and-flag programme, and we found no public information on a visual editor
- Your procurement requires an EU contracting entity, published EU residency or a named subprocessor list; the published terms point to Eppo Data, Inc. of San Francisco under Datadog's master agreement, with subprocessor categories only
- You must satisfy a data protection officer on how the test script treats consent before deploying it on your site; consent and tracking scored 0-2, with no public answer on script behaviour, storage or a cookieless mode
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 3.5 of 5 |
| Statistical method & guardrails | 3.5 of 5 |
| Consent & visitor tracking | 1 of 5 |
| Snippet performance & flicker | 1 of 5 |
| Analytics, data export & integrations | 3.5 of 5 |
| European sovereignty | 1 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
Server-side experiments, feature gates, controlled rollouts, mutual-exclusion layers and global holdouts are documented across twelve SDK languages, with personalisation through contextual bandits and flags sharing one governed metric model — but there is no visual editor on any captured page, so my team could not build a test without a developer. We found no public information on split-URL or multi-page testing. Strong engineering scope, weak marketer self-service. 4 1 3
The E-Commerce Manager
This is a full experimentation programme, not a page-tweaker: experiments randomising users across variants, feature flags and gates, controlled rollouts and kill switches, mutual exclusion layers, and global holdouts are all documented, with SDKs spanning twelve languages from JavaScript to Android. Personalisation via contextual bandits sits on the same metric model as the web tests, which is what I need when I want a personalised product page judged against a control. What I did not find on the captured pages is a visual editor for client-side tweaks or multi-page funnels spelled out. 1 4
The Product Engineer
This is server-side experimentation done the way I want it: SDKs in twelve named languages from JavaScript to Rust to Go, mutual exclusion layers, global holdouts, and feature flags living on one platform with the same metric model as the experiments. Contextual bandits cover personalisation, and clustered experiments and non-inferiority testing are documented in product updates. We found no public information on a visual editor or multi-page tests in the captured pages, which keeps this off the top band rather than changing the verdict. 1 4 6
The CRO Consultant
Eppo runs an SDK-and-flag programme rather than an editor product: experiments, feature gates, kill switches, controlled rollouts, mutual-exclusion layers and global holdouts are documented across twelve named SDK languages from JavaScript through Go to Android, with contextual bandits for personalisation. I found no public information on a visual editor, split-URL or multivariate tests, which keeps it just below the top of this range. For server-side and app programmes this coverage is what I'd recommend, but a marketing team wanting point-and-click page tests is not served by these pages. 1 4 6
The Data Protection Officer
Experiments randomize users between variants through SDKs listed for twelve languages including JavaScript, Python and Go, with mutual exclusion layers, global holdouts and controlled rollouts documented, and personalisation offered through contextual bandits. We found no public information on multi-page tests or on personalisation being tested against a control group. The terms point to a documentation site where the SDKs are described. 4 1 3
The Skeptic
Experiments run through documented SDKs across twelve named languages spanning client and server, with mutual exclusion layers, global holdouts, controlled rollouts, and contextual-bandit personalisation sharing one platform, audience and metric model. We found no public information on multi-page tests or on personalisation being tested against a control, which keeps this short of the top rung. 4 1
Statistical method & guardrails
panel disagrees
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
Sequential, fixed-sample and Bayesian frameworks are named alongside CUPED variance reduction, guardrail cutoffs for non-inferiority testing and clustered experiments — exactly the kind of numbers I can defend when finance asks. We found no public information on sample ratio mismatch detection or correction for multiple metrics or variants, so the guardrail stack is not complete on the evidence shown. 1 6 7
The E-Commerce Manager
Sequential, fixed-sample and Bayesian frameworks are named outright, with CUPED++ variance reduction to shorten runtimes and non-inferiority testing with guardrail cutoffs — that covers peeking protection, variance reduction and guardrails that can call a test harmful. The pages also promise a clear paper trail so results can be audited, but I found no public information on sample ratio mismatch detection or handling of multiple metrics and variants, which is what keeps me from scoring higher. 1 6 7
The Product Engineer
Sequential, fixed sample and Bayesian frameworks are named outright, CUPED variance reduction is claimed as the most robust implementation, and non-inferiority testing with guardrail cutoffs plus experiment forecasts give me lifecycle guardrails. What the captured pages do not show is sample ratio mismatch detection or an explicit correction for multiple metrics or variants, so I stop short of the top band. 1 6 7
The CRO Consultant
The methods are named and modern — sequential, fixed-sample and Bayesian frameworks, CUPED and CUPED++ variance reduction, non-inferiority testing with guardrail cutoffs, and results the vendor says leave a clear paper trail to audit and reconcile. I found no public information on correction for multiple metrics or variants, sample-ratio-mismatch detection, or methodology detailed enough to reproduce a figure. Credible statistics, but the documented guardrails against misreading a result stop short of the full set. 1 6 7
The Data Protection Officer
Sequential, fixed sample and Bayesian frameworks are named and implemented, alongside CUPED variance reduction and non-inferiority testing with guardrail cutoffs, and experiment forecasts for planning. We found no public information on sample ratio mismatch detection, correction for multiple metrics or variants, or confidence intervals shown per variant, so the guardrails around these named methods remain undocumented. 1 6 7
The Skeptic
The frameworks are named — sequential, fixed sample, and Bayesian — alongside CUPED++ variance reduction, non-inferiority testing with guardrail cutoffs, and version-controlled metric and guardrail definitions, so protection against peeking is documented rather than implied. We found no public information on a correction for multiple metrics or variants, on sample ratio mismatch detection, or on methodology published in enough detail to reproduce a result. 1 6 7
Consent & visitor tracking
n/r
n/r
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 captured pages show a cookie notice for the vendor's own site, a general claim of easy GDPR compliance tied to keeping data in the customer's warehouse, and a statement that PII never leaves your system — but we found no public information on when the test script runs relative to consent, what it stores on a visitor's device, whether a cookieless mode exists, or how this maps to §25 TDDDG. This is the first question our data protection officer will ask, and the pages do not answer it. 2 7 4
The E-Commerce Manager not rated — no public information
We found no public information on how the experimentation script behaves relative to visitor consent, whether a cookieless or consent-pending mode exists, or what it stores on a visitor's device under §25 TDDDG. The privacy notice's statements on cookies, beacons and pixels, and its note that do-not-track signals go unanswered, concern the vendor's own website rather than the product running on my shop. 1 2
The Product Engineer
The privacy notice covers the vendor's own website — cookies and beacons with a cookie notice available, and a statement that they do not currently respond to do-not-track signals — but says nothing about consent handling for the experimentation script itself. One line claims easy GDPR compliance, and the warehouse architecture keeps personal data in the customer's system, yet we found no public information on a consent-pending mode, a cookieless mode, or the storage keys the SDKs set. For a tool that runs on every visitor, that silence is a real gap. 2 4 7
The CRO Consultant
Beyond a generic "Easy compliance with GDPR" line and the warehouse-native claim that PII never leaves your system, I found no public information on when the assignment script runs relative to consent, what it stores on a visitor's device, or a consent-pending or cookieless mode. The privacy notice covers the vendor's own website — including that it does not respond to Do-Not-Track signals — not the script my clients would deploy on theirs. No DPO I work with could sign this off from public pages alone. 2 4 7
The Data Protection Officer
A cookie notice exists and the vendor names beacons, pixels and tags as its tracking technologies and states it does not respond to Do Not Track signals. Nothing we captured says when the assignment script runs relative to the consent banner, lists the cookies or storage keys it sets, or describes a consent-pending mode; the one relevant statement is that personally identifiable data never leaves the customer's own system. 2 4
The Skeptic not rated — no public information
We found no public information on how the experiment SDK behaves relative to consent under §25 TDDDG or the ePrivacy rules — nothing on when it runs relative to consent, what it stores on the device, or whether a cookieless mode exists. The privacy notice we read covers cookies on the vendor's own marketing website, not the testing product's behaviour on a customer's site. 2 4
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 pages describe flag configuration delivered from a CDN with local caching and no real-time reliance on the vendor's API, which speaks to resilience of delivery, but we found no public information on script weight, flicker handling, or any measured impact on Core Web Vitals. Marketing speed claims about the fastest feature flags are not measurements I can put in front of our web team. 4 1
The E-Commerce Manager
The feature-flagging pages describe a smart-client architecture with configs published to a CDN, local caching and no real-time reliance on the vendor API, which speaks to speed and resilience, and server-side SDKs give an escape route for flicker-sensitive pages. But the captured pages say nothing about flicker handling, asynchronous loading with a timeout, script weight, or any measured impact on Core Web Vitals — for a shop where a tenth of a second shows up in the conversion rate, that silence matters, and no published figures appear. 1 4
The Product Engineer
The architecture pages are the right kind of engineering: configs published to a CDN, local cache redundancy, and no real-time reliance on the vendor API, with billions of daily assignments claimed. But the criterion asks what the snippet costs the page, and we found no public information on script weight, flicker handling, or impact on Core Web Vitals in the captured pages. 1 4
The CRO Consultant
What is documented is delivery resilience rather than page cost: configurations are published to a CDN with local caching and no real-time reliance on the vendor's API, and the flags are claimed to power billions of daily assignments. I found no public information on script weight, loading behaviour, anti-flicker handling, or a measured impact on Core Web Vitals. The published cost claims are about warehouse pipeline spend, not the visitor's page. 1 4
The Data Protection Officer
The architecture page describes configuration delivery from a CDN with a local cache and no real-time reliance on the vendor's API, with redundancy across the application, CDN and cache. We found no public information on script weight, flicker handling, impact on Core Web Vitals, or a self-hosting option for the delivery script. 4 1
The Skeptic
The feature-flag pages describe configs published to a CDN with local caching and no real-time reliance on the vendor's API, which documents delivery design rather than measured cost. We found no published figures on script weight, load impact, Core Web Vitals, or flicker handling on the captured pages. 4 1
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
This is the strongest part for me: metrics live in our own warehouse (Snowflake, Databricks, BigQuery and Redshift are named), experiments run on our own tables with version-controlled metric definitions, results are described as easy to audit and reconcile, and PII never leaves our system. We found no public information on an API for managing experiments and reading results, or on CDP audience integrations. 7 1 4
The E-Commerce Manager
The warehouse is treated as the source of truth: experiments run natively on Snowflake, Databricks, BigQuery or Redshift in my own cloud, metric definitions are governed once with version control and a semantic layer, and an audit trail is promised with no data duplication or egress. That is exactly the 'check it in my own data' property I want in a finding. What the captured pages do not show is a documented API for managing experiments or stated export formats and limits. 1 7
The Product Engineer
This is the model I'd ship: metrics defined once and computed in the customer's own cloud, integrating with Snowflake, Databricks, BigQuery and Redshift, with control of tables, queries and update schedules, no data duplication, and an audit trail for results. Raw experiment data lives where the team already trusts it. What keeps this from the top band is that we found no public information on a documented API for managing experiments and reading results, or on named analytics and tag-manager integrations, in the captured pages. 1 7 8
The CRO Consultant
This is the strongest story in the file: experiments run natively on the customer's own warehouse — Snowflake, Databricks, BigQuery and Redshift are all named — with metrics defined once under version control, no data duplication, and results the vendor says are easy to audit and reconcile entirely in your own cloud. Outside the warehouse the picture thins: the integrations headline is generic, and I found no public information on a documented API with stated limits, visitor-level export mechanics, or CDP integrations. For checking a result against a client's own data, though, the architecture is exactly what I want. 1 7 8
The Data Protection Officer
Experiments run on the customer's own warehouse, with Snowflake, Databricks, BigQuery and Redshift named, from a single source of truth with no data duplication, which leaves the raw data in the customer's cloud and makes results easy to audit and reconcile. We found no public information on a documented API for managing experiments and reading results with stated limits, on webhooks, or on named analytics and tag manager integrations. 7 1 3
The Skeptic
This is the product's strongest suit: experiments run on the customer's own metrics in their own cloud across Snowflake, Databricks, BigQuery and Redshift, with no data duplication and a single source of truth — the result lives in the customer's data, where it can be checked. We found no public information on a documented API for managing experiments or reading results, on webhooks, or on export formats and their limits. 7 1 4
European sovereignty
panel opinion
panel disagrees
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 entities are named — Eppo Data, Inc. at a San Francisco address, with billing and the governing Master Subscription Agreement now under Datadog — and a privacy notice and subprocessor categories are published, but we found no public information on EU data residency, a data processing agreement, or where the hosted service processes data. Experiment data sitting in our own cloud helps, though the vendor itself is shown in California. 2 3 7
The E-Commerce Manager
The contracting entity is Eppo Data, Inc. of San Francisco with use governed by Datadog's master subscription agreement, and a privacy notice is published; the hosting location of the service is not stated, though experiment computation is described as running in the customer's own cloud. No EU residency option, data processing agreement or subprocessor locations appear on the captured pages — only subprocessor categories without locations — so a European shop is contracting with a US entity on the evidence shown. 2 3 7
The Product Engineer
The contracting picture is American end to end: Eppo Data, Inc. in San Francisco, purchases governed by Datadog's master subscription agreement with billing through Datadog, and a subprocessor list that names categories but no locations. The warehouse-native claim that metrics stay completely in your own cloud is the one architectural mitigation, but we found no public information on EU data residency for the service or a data processing agreement in the captured pages. For a European buyer, nothing here documents a safeguard. 2 3 7
The CRO Consultant
The contracting side is demonstrably American — Eppo Data, Inc. of San Francisco, with the service now governed by Datadog's master subscription agreement — and I found no public information on transfer safeguards, a data processing agreement, subprocessor locations, or where the application itself is hosted. The one European-friendly fact is that metric computation runs completely in the customer's own cloud, which an EU client would host wherever it chooses. Corporate entity and governing law remain non-EU with nothing published to bridge that gap. 2 3 7
The Data Protection Officer
The contracting documents point to the United States: the privacy notice names Eppo Data, Inc. at a San Francisco address, and the hosted service is governed by Datadog's Master Subscription Agreement with billing through Datadog. We found no public information on EU residency for the service or the snippet delivery, on a data processing agreement covering visitor data, or on a named subprocessor list with locations — only subprocessor categories are published. The one mitigation visible in the evidence is that metrics and experiment data stay in the customer's own cloud. 2 3 7
The Skeptic
The contracting entities are named — Eppo Data, Inc. of San Francisco, with Datadog's Master Subscription Agreement governing the service — and a privacy notice is published, while the warehouse pages state that data stays in the customer's own cloud. We found no public information on an EU contracting entity, an EU residency commitment for visitor data, a data processing agreement, or a subprocessor list naming providers and their locations. 2 3 7
Pricing transparency
not rated — the vendor publishes no price
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
No price appears anywhere on the captured pages; the terms describe the service as negotiated per Order with billing through Datadog, and the only commercial term stated publicly is that support during business hours is included at no additional charge. I cannot derive even a rough annual cost from public information, which makes board sign-off on budget impossible. 3
The E-Commerce Manager
We found no public prices at all on the captured pages, and the evidence records no public pricing page; contracting happens through Orders under the master subscription agreement, with support included and no automatic renewal. Nothing published lets me compute what a December traffic spike would cost, how traffic is metered, or what any module adds to the invoice. 1 3
The Product Engineer
There are no public prices at all: no pricing page appears in the captures, purchasing runs through orders under Datadog's master subscription agreement, and even the technical white paper sits behind a lead-capture form. A buyer cannot compute any part of the annual cost from public pages alone; support is the only priced item stated, and it is included at no additional charge. 3 8
The CRO Consultant
I found no public prices, tiers or traffic metric on any page I read — commercial terms live in Orders under the master agreement, and even the technical white paper sits behind a lead-capture form. The only public commercial facts are that support is included at no additional charge and that orders do not automatically renew. I could not estimate a client's annual cost from public pages at all. 3 8
The Data Protection Officer
We found no public prices on any captured page; the service is contracted through orders under Datadog's Master Subscription Agreement, with no tier figures, traffic metric, limits or overage rates stated. The terms confirm orders do not automatically renew, but nothing on these pages lets a buyer compute an annual cost. 3 1
The Skeptic
The published terms describe Orders that do not automatically renew and support included at no additional charge, but name no figures of any kind. We found no public prices for any tier, no traffic metric behind the price, and no module or overage pricing on the captured pages, so a buyer cannot compute even an approximate annual cost. 3 1
European sovereignty — proven facts
0 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 |
Not determined
unverified
Why unverified?The vendor's pages name a local subsidiary and do not state the parent's seat. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Eppo
Is Eppo European?
No. whats-best.ai classifies Eppo as Rest of world.
Where does Eppo store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Eppo have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Eppo?
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: Eppo alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The vendor's pages name a local subsidiary and do not state the parent's seat.
- 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.
- 2 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
- 1 compliance 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
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.geteppo.com Checked 16 Nov 2026 Details →
- 2 Privacy policy www.geteppo.com Checked 16 Nov 2026 Details →
- 3 Terms of service www.geteppo.com Checked 16 Nov 2026 Details →
- 4 Experiment types & delivery — found from sitemap www.geteppo.com Checked 16 Nov 2026 Details →
- 5 Experiment types & delivery — found from sitemap www.geteppo.com Checked 16 Nov 2026 Details →
- 6 Snippet performance & flicker — found from sitemap www.geteppo.com Checked 16 Nov 2026 Details →
- 7 Analytics, data export & integrations — found from sitemap www.geteppo.com Checked 16 Nov 2026 Details →
- 8 Analytics, data export & integrations — found from sitemap www.geteppo.com Checked 16 Nov 2026 Details →