Softwr

Automation Integration · head to head

Cyclr vs Percy

Cyclr logo

Cyclr

Automation Integration

Embedded integration platform that SaaS vendors ship inside their own product

From
$1595/month
Free plan
No
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

  • Percy is free; Cyclr starts at $1595/mo.
  • Only Cyclr lists connector library; 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 Cyclr and Percy differ?

Cyclr and Percy differ on starting price ($1595/month against Free), pricing model and free tier (No against Yes). Only the attributes on which Cyclr and Percy actually diverge.

Attributes where Cyclr and Percy differ
AttributeCyclrPercy
Starting price$1595/monthFree
Pricing modelPer month by API call volumeFreemium, paid tiers by screenshot volume
Free tierNoYes
PlatformsWeb, APIWeb
CategoryAutomation IntegrationTesting

Not yet recorded: founded for Percy.

Which features does each one have?

They share no listed features; 8 appear only for Cyclr 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 Cyclr

  • White-label integration UI
  • Connector library
  • Workflow builder
  • Custom connectors
  • Regional hosting
  • MCP server offering
  • Usage metering
  • Templates

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.

Cyclr

  • A mid-market SaaS vendor losing deals because prospects ask for a CRM integration it has not builtnot Percy
  • A product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectorsnot Percy
  • A European software company that needs its customers' integration data processed inside the EU for procurement reasonsnot Percy
  • A vendor whose customers each want a slightly different variation of the same integration and cannot be served by one hard-coded connectornot Percy

Percy

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

Where do Cyclr and Percy fall short?

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

Cyclr

  • Entry pricing of 1,595 US dollars a month for one connector and 100,000 API calls means small vendors will find building two or three integrations in-house genuinely cheaper, and Cyclr only pays off past a certain integration count
  • Connectors and API calls are metered separately, so a successful integration marketplace pushes you up tiers as your customers adopt it, meaning the cost rises with usage rather than with the revenue that usage generates
  • Custom connectors to APIs outside the library are your work to build and maintain, so the promise of not building integrations only holds for applications Cyclr already covers
  • Debugging is harder when the integration runs in a third-party runtime, because your support team sees a failed workflow rather than an HTTP response and has to escalate to Cyclr for anything non-obvious
  • Deep embedding creates real switching cost: your customers' live integrations run on Cyclr, so migrating later means recreating every customer workflow, which in practice means you rarely leave

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 Cyclr and Percy cost?

Cyclr starts at $1595/mo; Percy is free to use. Plan by plan below, from each vendor's own pricing page.

Cyclr

$1595/month
  • PAYG$1,595/mo
    • 100,000 API calls included
    • 1 connector included
    • Unlimited integrations and users
  • Growth$2,595/mo
    • 1,000,000 API calls included
    • 10 connectors included
    • Everything in PAYG
  • Scale$7,195/mo
    • 5,000,000 API calls included
    • Unlimited connectors
    • Everything in Growth
  • Private CloudOn request
    • Dedicated hosting in US, UK or EU
    • Configurable processing and runtime
    • Quoted pricing

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

  • You need white-label integration ui.
  • You work on Web, API.
  • You also want connector library.

Choose Percy if

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

Questions people ask

Is Cyclr or Percy better?
Neither clearly leads. Cyclr starts at $1595/month and Percy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cyclr or Percy?
Percy has a free tier; the other does not. Paid plans start at $1595/month for Cyclr and Free for Percy.
Does Cyclr or Percy run on more platforms?
Cyclr 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. Cyclr starts at $1595/month.
What is Cyclr best used for?
Cyclr is most often used for a mid-market saas vendor losing deals because prospects ask for a crm integration it has not built, a product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectors, a european software company that needs its customers' integration data processed inside the eu for procurement reasons, a vendor whose customers each want a slightly different variation of the same integration and cannot be served by one hard-coded connector. Of those, a mid-market saas vendor losing deals because prospects ask for a crm integration it has not built and a product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectors are not what Percy is typically brought in for.
What can Cyclr do that Percy cannot?
Cyclr covers White-label integration UI, Connector library, Workflow builder, Custom connectors. Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow.

Answered from the vendors’ own pages

Cyclr: What does Cyclr actually cost?

Published tiers start at 1,595 US dollars per month for 100,000 API calls and one connector, rising to 7,195 for unlimited connectors and five million calls.

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.

Cyclr: Do my customers know they are using Cyclr?

No. The interface is white-labelled to appear as part of your product.

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.

Cyclr: Can I host it in the EU or UK?

Yes, on the private cloud tiers, which matters for European procurement requirements.

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.

Cyclr: What if the connector I need does not exist?

You build a custom connector using Cyclr tooling, which is work you own rather than work the platform removes.

Share

Related pages

Other head to heads