Testing · head to head
Eppo vs Percy
Eppo
Testing
Warehouse-native experimentation and feature flagging, now sold as Datadog Experiments
- From
- On request
- Rated
- -
Percy
Testing
Visual regression testing owned by BrowserStack, with a permanent free tier for low screenshot volume
- From
- Free
- Rated
- -
The short version
- Only Percy has a free tier, so it costs nothing to try first.
- Each has a real cost: Eppo datadog acquired Eppo in May 2025 and is folding it into Datadog Experiments, so you are now buying a component of an observability suite rather than an independent product, and roadmap priorities will follow Datadog’s bundle strategy.; Percy pixel-based diffing generates more false positives from font rendering and anti-aliasing noise than Applitools' AI-based comparison, which trains some teams to start ignoring diff alerts over time.
- They diverge on capability: Eppo covers Warehouse-native analysis, Percy covers Screenshot diffing.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Eppo and Percy actually diverge.
Identical on both: user rating (Not yet rated), category (Testing).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Eppo
- Warehouse-native analysis
- Sequential testing
- CUPED variance reduction
- Feature flagging
- Metric governance
- Contextual bandits
- Experiment scorecards
- Heterogeneous effect analysis
Only in Percy
- Screenshot diffing
- Framework integrations
- Responsive and cross-browser snapshots
- Review workflow
- Build history
- BrowserStack platform integration
What people use each for
The jobs each tool is most often brought in to do.
Eppo
- A company whose experiment results have repeatedly disagreed with the analytics team’s own numbers because the two systems define revenue differentlynot Percy
- A product organisation with low traffic on a key surface that needs variance reduction to reach a decision in weeks instead of monthsnot Percy
- A team that must keep user-level event data inside its own warehouse for regulatory reasons and cannot ship it to a third-party analytics vendornot Percy
- An existing Datadog customer consolidating product analytics, feature flags and experimentation onto one vendor agreementnot Percy
Percy
- A team already on BrowserStack for device testing that wants to add visual regression without a separate vendor relationshipnot Eppo
- A low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anythingnot Eppo
- A team wanting a lower cost per screenshot than Applitools and willing to tolerate more manual false-positive triagenot Eppo
- A Cypress or Playwright test suite adding visual checks without changing its existing test runnernot Eppo
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Eppo
- Datadog acquired Eppo in May 2025 and is folding it into Datadog Experiments, so you are now buying a component of an observability suite rather than an independent product, and roadmap priorities will follow Datadog’s bundle strategy.
- No pricing is published anywhere, before or after the acquisition; the site offers only a demo request, so cost cannot be estimated without a sales process and is likely to be quoted alongside a wider Datadog contract.
- Because analysis runs in your warehouse, Eppo shifts compute cost onto your Snowflake or BigQuery bill; a large experiment programme with frequent recomputation raises a line item that does not appear in the Eppo quote at all.
- Results are only as fresh as the pipeline feeding the warehouse, so teams used to near-real-time dashboards from an event-based tool will wait hours for updated numbers, which slows down the fast iteration loops some product teams rely on.
- It assumes a mature data stack with a warehouse, defined metrics and analysts who can maintain them; an organisation without that has to build the data foundation first, which makes the real adoption cost far larger than the licence.
Percy
- Pixel-based diffing generates more false positives from font rendering and anti-aliasing noise than Applitools' AI-based comparison, which trains some teams to start ignoring diff alerts over time.
- It is billed separately from core BrowserStack device testing, and stacking Percy with other BrowserStack modules such as Accessibility Testing materially increases total contract value beyond the headline device testing price.
- Paid tier pricing above the free tier is not transparently published as a fixed number, requiring a quote to know actual cost at scale.
- The free tier's 5,000-screenshot cap is easy to exceed for any team running visual tests across multiple browsers and viewports on every commit, pushing many active projects into a paid tier faster than the free number suggests.
- As part of a larger acquired portfolio, Percy's roadmap priority within BrowserStack's broader product strategy is less certain than it would be as a standalone company's sole focus.
Pricing, plan by plan
Eppo
On request- Eppo, now Datadog Experiments$undefined/year
- Warehouse-native experiment analysis
- Feature flagging and assignment
- Sequential testing and CUPED variance reduction
Percy
Free- FreeFree
- 5,000 screenshots a month
- Unlimited users and projects
- 30-day build history
- Percy$undefined/month
- Priced by screenshot volume above the free tier
- Sold separately from core BrowserStack device testing plans
- Get a current quote before assuming bundled pricing with other BrowserStack products
Which should you pick?
Choose Eppo if
- You need warehouse-native analysis.
- You work on Web, Cloud.
- You also want sequential testing.
Choose Percy if
- You need screenshot diffing.
- You want to start without paying.
- You also want framework integrations.
Questions people ask
- Is Eppo or Percy better?
- Neither clearly leads. Eppo starts at On request and Percy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Eppo or Percy?
- Percy has a free tier; the other does not. Paid plans start at On request for Eppo and Free for Percy.
- Does Eppo or Percy run on more platforms?
- Eppo runs on Web, Cloud. Percy runs on Web.
- Can I use Percy for free?
- Yes. Percy has a free tier, so you can try it without paying. Eppo starts at On request.
- What is Eppo best used for?
- Eppo is most often used for a company whose experiment results have repeatedly disagreed with the analytics team’s own numbers because the two systems define revenue differently, a product organisation with low traffic on a key surface that needs variance reduction to reach a decision in weeks instead of months, a team that must keep user-level event data inside its own warehouse for regulatory reasons and cannot ship it to a third-party analytics vendor, an existing datadog customer consolidating product analytics, feature flags and experimentation onto one vendor agreement. Of those, a company whose experiment results have repeatedly disagreed with the analytics team’s own numbers because the two systems define revenue differently and a product organisation with low traffic on a key surface that needs variance reduction to reach a decision in weeks instead of months are not what Percy is typically brought in for.
- What can Eppo do that Percy cannot?
- Eppo covers Warehouse-native analysis, Sequential testing, CUPED variance reduction, Feature flagging. Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow.
Answered from the vendors’ own pages
Eppo: Is Eppo still a separate product?
It is still sold and supported, but Datadog acquired it in May 2025 and it is branded as Datadog Experiments. Buy it expecting a Datadog product roadmap.
Percy: Is Percy free?
Yes for up to 5,000 screenshots a month with unlimited users and projects; beyond that it is a paid, quote-priced module.
Eppo: What does it cost?
Nothing is published. There is no pricing page, only a demo request, and pricing is now likely bundled into a Datadog agreement.
Percy: Is Percy included if I already pay for BrowserStack device testing?
No, it is billed separately by screenshot volume, not bundled into core device testing plans.
Eppo: Does it need a data warehouse?
Yes. Warehouse-native analysis is the whole architecture. Without Snowflake, BigQuery, Redshift or Databricks there is no product.
Percy: How does it compare to Applitools?
Percy uses pixel-based diffing, which is generally cheaper per screenshot but produces more false positives than Applitools' AI-based perceptual comparison.
Eppo: Does it include feature flags?
Yes. Assignment and measurement come from the same system, which is the main reason teams pick it over pairing a flag tool with a separate analysis tool.
Related pages
Other head to heads
- Eppo vs GrowthBook
- Eppo vs Split
- Eppo vs Kameleoon
- Eppo vs Xray Test Management
- Eppo vs Qase
- Eppo vs Tricentis Tosca
- Eppo vs Appium
- Eppo vs TestRail
- Eppo vs Katalon
- Eppo vs Zephyr Scale
- Eppo vs TestNG
- Eppo vs Applitools
- Eppo vs pytest
- Eppo vs Testsigma
- Eppo vs Vitest
- Eppo vs Jest
- Eppo vs BrowserStack
- Eppo vs Cypress
- Eppo vs Sauce Labs
- Eppo vs PractiTest
- Eppo vs JUnit
- Eppo vs Cucumber
- Eppo vs QA Wolf
- Eppo vs Ranorex
- Eppo vs WebdriverIO
- Percy vs GrowthBook
- Percy vs Split
- Percy vs Kameleoon
- Percy vs Xray Test Management
- Percy vs Qase
- Percy vs Tricentis Tosca
- Percy vs Appium
- Percy vs TestRail
- Percy vs Katalon
- Percy vs Zephyr Scale
- Percy vs TestNG
- Percy vs Applitools
- Percy vs pytest
- Percy vs Testsigma
- Percy vs Vitest
- Percy vs Jest
- Percy vs BrowserStack
- Percy vs Cypress
- Percy vs Sauce Labs
- Percy vs PractiTest
- Percy vs JUnit
- Percy vs Cucumber
- Percy vs QA Wolf
- Percy vs Ranorex
- Percy vs WebdriverIO