Softwr

Testing · head to head

GrowthBook vs Percy

GrowthBook logo

GrowthBook

Testing

Open source feature flags and A/B testing that run experiment analysis inside your own data warehouse

From
Free
Rated
-
Full reviewWebsite
Percy logo

Percy

Testing

Visual regression testing owned by BrowserStack, with a permanent free tier for low screenshot volume

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: GrowthBook warehouse-native analysis is only an advantage if you have a warehouse with clean event data in it; without one, GrowthBook has nothing to compute against and you are back to buying an event-collecting platform.; 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: GrowthBook covers Feature flags, Percy covers Screenshot diffing.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which GrowthBook and Percy actually diverge.

Attributes where GrowthBook and Percy differ
AttributeGrowthBookPercy
Pricing modelPer user per monthFreemium, paid tiers by screenshot volume
PlatformsWeb, Self-hosted, DockerWeb

Identical on both: starting price (Free), free tier (Yes), 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 GrowthBook

  • Feature flags
  • Warehouse-native analysis
  • Reusable metric definitions
  • Bayesian and frequentist engines
  • CUPED variance reduction
  • Visual editor
  • Self-hosting
  • Guardrail metrics

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.

GrowthBook

  • An engineering team that wants feature flags without a per-monthly-active-user bill that grows with product successnot Percy
  • A data team that needs experiment results to reconcile exactly with the metrics reported in its BI toolnot Percy
  • A company with data residency or privacy constraints that cannot send user-level event data to a third-party vendornot Percy
  • Running long-tail experiments where sequential testing and CUPED shorten the time to a decision on low-traffic surfacesnot Percy

Percy

  • A team already on BrowserStack for device testing that wants to add visual regression without a separate vendor relationshipnot GrowthBook
  • A low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anythingnot GrowthBook
  • A team wanting a lower cost per screenshot than Applitools and willing to tolerate more manual false-positive triagenot GrowthBook
  • A Cypress or Playwright test suite adding visual checks without changing its existing test runnernot GrowthBook

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

GrowthBook

  • Warehouse-native analysis is only an advantage if you have a warehouse with clean event data in it; without one, GrowthBook has nothing to compute against and you are back to buying an event-collecting platform.
  • Metrics are SQL, so a marketing or product team without data engineering support cannot define or fix them, and a badly written metric silently produces a confident wrong answer.
  • Cloud Pro bills per seat and then adds CDN request and bandwidth overages, so a high-traffic site can find the variable component exceeds the seat cost it budgeted for.
  • Self-hosting means you own the Mongo database, the SDK endpoint availability and the upgrade path, and a flag service that is down is a production incident, not an analytics inconvenience.
  • The statistics engine exposes real choices, Bayesian versus frequentist, sequential testing, variance reduction, and the tool will not stop a team that configures them wrongly, so it rewards statistical literacy and punishes its absence.

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

GrowthBook

Free
  • Open source (self-hosted)Free
    • Unlimited users, feature flags and experiments
    • One project
    • MIT licensed, you run the infrastructure
  • Starter (cloud)Free
    • Up to 3 users
    • 1 project
    • Unlimited flags, experiments and traffic
  • Pro (cloud)$40/month
    • Per seat, up to 50 users
    • 3 projects
    • CDN overage at $10 per million requests beyond the included allowance
  • Enterprise$undefined/year
    • Unlimited users and projects
    • SSO, audit logs and advanced permissions
    • Available on cloud or self-hosted

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 GrowthBook if

  • You need feature flags.
  • You want to start without paying.
  • You work on Web, Self-hosted, Docker.
  • You also want warehouse-native analysis.
GrowthBook review

Choose Percy if

  • You need screenshot diffing.
  • You want to start without paying.
  • You also want framework integrations.
Percy review

Questions people ask

Is GrowthBook or Percy better?
Neither clearly leads. GrowthBook starts at Free and Percy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, GrowthBook or Percy?
GrowthBook starts at Free and Percy at Free.
Does GrowthBook or Percy run on more platforms?
GrowthBook runs on Web, Self-hosted, Docker. Percy runs on Web.
Can I use GrowthBook for free?
Both have a free tier, so you can try either at no cost before committing.
What is GrowthBook best used for?
GrowthBook is most often used for an engineering team that wants feature flags without a per-monthly-active-user bill that grows with product success, a data team that needs experiment results to reconcile exactly with the metrics reported in its bi tool, a company with data residency or privacy constraints that cannot send user-level event data to a third-party vendor, running long-tail experiments where sequential testing and cuped shorten the time to a decision on low-traffic surfaces. Of those, an engineering team that wants feature flags without a per-monthly-active-user bill that grows with product success and a data team that needs experiment results to reconcile exactly with the metrics reported in its bi tool are not what Percy is typically brought in for.
What can GrowthBook do that Percy cannot?
GrowthBook covers Feature flags, Warehouse-native analysis, Reusable metric definitions, Bayesian and frequentist engines. Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow.

Answered from the vendors’ own pages

GrowthBook: Is the self-hosted version actually usable, or crippled?

It is genuinely usable: unlimited users, flags and experiments on one project under an MIT licence. The paid tiers add multiple projects, SSO, audit logs and support.

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.

GrowthBook: Do I need a data warehouse?

For experiment analysis, effectively yes. Feature flagging works without one, but the reason to choose GrowthBook over a flag-only tool is the warehouse-native statistics.

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.

GrowthBook: How does the cost compare with LaunchDarkly or Optimizely?

GrowthBook charges per seat rather than per monthly active user or per tracked event, so cost stops scaling with traffic. At high volume that difference is large.

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.

GrowthBook: Does it support mobile and server-side flags?

Yes, there are SDKs across JavaScript, React, Python, Go, Ruby, PHP, Java, Kotlin, Swift and more, covering client, server and mobile evaluation.

Share

Related pages

More on GrowthBook

More on Percy

Keep looking

Other head to heads