Softwr

Developer Tools · head to head

GitLab CI/CD vs Percy

GitLab CI/CD logo

GitLab CI/CD

Developer Tools

Automatically build, test, deploy, and monitor your applications with GitLab CI/CD

From
Free
Free plan
Yes
Percy logo

Percy

Testing

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

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Where GitLab CI/CD falls short: compute minute quotas for Premium and Ultimate tiers not disclosed in documentation.
  • Where Percy falls short: paid tier pricing above the free tier is not transparently published as a fixed number, requiring a quote to know actual cost at scale.
  • Prices and features on this page were last checked on 20 November 2026.

How do GitLab CI/CD and Percy differ?

GitLab CI/CD and Percy differ on pricing model and category (Developer Tools against Testing). Only the attributes on which GitLab CI/CD and Percy actually diverge.

Attributes where GitLab CI/CD and Percy differ
AttributeGitLab CI/CDPercy
Pricing modelFreemiumFreemium, paid tiers by screenshot volume
CategoryDeveloper ToolsTesting

Identical on both: starting price (Free), free tier (Yes), platforms (Web).

Not yet recorded: founded for Percy.

Which features does each one have?

They share no listed features; 6 only for Percy. 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 GitLab CI/CD

Nothing recorded that Percy does not also cover.

Only in Percy

  • Screenshot diffing
  • Framework integrations
  • Responsive and cross-browser snapshots
  • Review workflow
  • Build history
  • BrowserStack platform integration

What is each one used for?

GitLab CI/CD is most often brought in for reducing open source project infrastructure costs with public project discounts. The jobs each tool is most often brought in to do.

GitLab CI/CD

  • Reducing open source project infrastructure costs with public project discountsnot Percy
  • Enforcing monthly CI/CD spending limits and quota notificationsnot Percy
  • Allocating compute minutes to open source contributors affordablynot Percy
  • Forecasting CI/CD spending patterns across multiple projectsnot Percy
  • Providing private runners for cost control without owning infrastructurenot Percy

Percy

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

Where do GitLab CI/CD and Percy fall short?

GitLab CI/CD's most cited limit: compute minute quotas for Premium and Ultimate tiers not disclosed in documentation. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

GitLab CI/CD

  • Compute minute quotas for Premium and Ultimate tiers not disclosed in documentation
  • Additional compute minutes beyond quota incur charges; exact pricing not specified
  • Free tier namespaces on GitLab.com receive 400 compute minutes a month, and extra minutes must be bought separately
  • Compute minutes are multiplied by a cost factor, up to 12 for the largest Linux runners, so big runners use the quota much faster
  • macOS and Windows GitLab-hosted runners are listed as Beta, with macOS runners carrying cost factors of 6 and 12

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

How much do GitLab CI/CD and Percy cost?

GitLab CI/CD is free to use; Percy is free to use. Plan by plan below, from each vendor's own pricing page.

GitLab CI/CD

Free
  • FreeFree
    • 400 compute minutes per month for free tier namespaces
    • Linux x86-64 runners at 1x cost factor
  • PremiumOn request
    • Higher monthly compute minute quotas than free tier
    • Additional compute minutes available for purchase
  • UltimateOn request
    • Highest monthly compute minute allocations
    • Additional compute minutes available for purchase

Percy

Free
  • FreeFree
    • 5,000 screenshots a month
    • Unlimited users and projects
    • 30-day build history
  • PercyOn request
    • 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 GitLab CI/CD if

  • You want to start without paying.

Choose Percy if

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

Questions people ask

Is GitLab CI/CD or Percy better?
Neither clearly leads. GitLab CI/CD 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, GitLab CI/CD or Percy?
GitLab CI/CD starts at Free and Percy at Free.
Does GitLab CI/CD or Percy run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use GitLab CI/CD for free?
Both have a free tier, so you can try either at no cost before committing.
What is GitLab CI/CD best used for?
GitLab CI/CD is most often used for reducing open source project infrastructure costs with public project discounts, enforcing monthly ci/cd spending limits and quota notifications, allocating compute minutes to open source contributors affordably, forecasting ci/cd spending patterns across multiple projects. Of those, reducing open source project infrastructure costs with public project discounts and enforcing monthly ci/cd spending limits and quota notifications are not what Percy is typically brought in for.
What can GitLab CI/CD do that Percy cannot?
Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow.

Answered from the vendors’ own pages

GitLab CI/CD: How many GitLab CI compute minutes does the free tier include?

The free tier of GitLab CI includes 400 compute minutes per month for free tier namespaces on GitLab.com.

Source
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.

GitLab CI/CD: What is the cost factor for different GitLab CI runner types?

Linux x86-64 small runners cost 1x; medium runners cost 2x; large runners cost 3x. macOS and Windows runners have cost factors of 6-12x and are in beta status.

Source
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.

GitLab CI/CD: Do public open-source projects get discounts on GitLab CI compute minutes?

Public open-source projects receive a 0.5x discount on compute minutes. Public forks of GitLab open-source projects receive a 0.008x discount.

Source
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.

Share

Related pages

Other head to heads