Developer Tools · head to head
Cortex vs Percy

Cortex
Developer Tools
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
- From
- On request
- Free plan
- No

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
- Percy is free; Cortex prices on request.
- Only Cortex lists service catalogue; only Percy lists screenshot diffing.
- 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 Cortex and Percy differ?
Cortex and Percy differ on starting price (On request against Free), pricing model and free tier (No against Yes). Only the attributes on which Cortex and Percy actually diverge.
Which features does each one have?
They share no listed features; 8 appear only for Cortex and 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 Cortex
- Service catalogue
- Scorecards
- Initiatives
- Self-service templates
- Query language
- Eng intelligence
- Integrations layer
- On-call and ownership mapping
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?
The jobs each tool is most often brought in to do.
Cortex
- A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Percy
- An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Percy
- Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Percy
- Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Percy
Percy
- A team already on BrowserStack for device testing that wants to add visual regression without a separate vendor relationshipnot Cortex
- A low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anythingnot Cortex
- A team wanting a lower cost per screenshot than Applitools and willing to tolerate more manual false-positive triagenot Cortex
- A Cypress or Playwright test suite adding visual checks without changing its existing test runnernot Cortex
Where do Cortex and Percy fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Cortex
- Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first
- The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything
- Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue
- It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves
- Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract
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 Cortex and Percy cost?
Cortex is priced on request; Percy is free to use. Plan by plan below, from each vendor's own pricing page.
Cortex
On request- CortexOn request
- Service catalogue and ownership mapping
- Scorecards and initiatives
- Self-service templates
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 Cortex if
- You need service catalogue.
- You work on Web, API.
- You also want scorecards.
Choose Percy if
- You need screenshot diffing.
- You want to start without paying.
- You also want framework integrations.
Questions people ask
- Is Cortex or Percy better?
- Neither clearly leads. Cortex 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, Cortex or Percy?
- Percy has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Percy.
- Does Cortex or Percy run on more platforms?
- Cortex runs on Web, API. Percy runs on Web.
- Can I use Percy for free?
- Yes. Percy has a free tier, so you can try it without paying. Cortex starts at On request.
- What is Cortex best used for?
- Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Percy is typically brought in for.
- What can Cortex do that Percy cannot?
- Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow.
Answered from the vendors’ own pages
Cortex: How is Cortex different from Backstage?
Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.
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.
Cortex: Is pricing published?
No. Cortex requires a sales conversation and prepares a custom proposal.
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.
Cortex: Can it self-host?
It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.
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.
Cortex: What is the main adoption risk?
Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.
Related pages
Other head to heads
- Cortex vs Backstage
- Cortex vs OpsLevel
- Cortex vs GitHub
- Cortex vs Spacelift
- Cortex vs Earthly
- Cortex vs Atlantis
- Cortex vs SonarQube
- Cortex vs Envoy
- Cortex vs Depot
- Cortex vs Istio
- Cortex vs Nix
- Cortex vs Buildkite
- Cortex vs Azure DevOps
- Cortex vs Bitbucket
- Cortex vs Daytona
- Cortex vs Helix
- Cortex vs Nx Cloud
- Cortex vs Pants Build
- Cortex vs Applitools
- Cortex vs Sauce Labs
- Cortex vs BrowserStack
- Cortex vs Playwright
- Cortex vs Cypress
- Cortex vs TestRail
- Cortex vs Katalon
- Cortex vs PractiTest
- Cortex vs Jest
- Cortex vs Xray Test Management
- Cortex vs JUnit
- Cortex vs Puppeteer
- Cortex vs Kameleoon
- Cortex vs Qase
- Cortex vs Robot Framework
- Cortex vs Zephyr Scale
- Cortex vs Ranorex
- Cortex vs Appium
- Percy vs Backstage
- Percy vs OpsLevel
- Percy vs GitHub
- Percy vs Spacelift
- Percy vs Earthly
- Percy vs Atlantis
- Percy vs SonarQube
- Percy vs Envoy
- Percy vs Depot
- Percy vs Istio
- Percy vs Nix
- Percy vs Buildkite
- Percy vs Azure DevOps
- Percy vs Bitbucket
- Percy vs Daytona
- Percy vs Helix
- Percy vs Nx Cloud
- Percy vs Pants Build
- Percy vs Applitools
- Percy vs Sauce Labs
- Percy vs BrowserStack
- Percy vs Playwright
- Percy vs Cypress
- Percy vs TestRail
- Percy vs Katalon
- Percy vs PractiTest
- Percy vs Jest
- Percy vs Xray Test Management
- Percy vs JUnit
- Percy vs Puppeteer
- Percy vs Kameleoon
- Percy vs Qase
- Percy vs Robot Framework
- Percy vs Zephyr Scale
- Percy vs Ranorex
- Percy vs Appium
