Percy Enterprise Features for Visual Testing

Percy is a visual testing and review platform that is now part of BrowserStack. Its documented workflow is to integrate Percy with a project, run visual tests, and review the results. Percy’s public materials describe integrations with test frameworks, CI/CD services, pull and merge requests, Slack notifications, and custom webhooks. A Percy changelog entry dated March 13, 2023 says Percy Enterprise Plan customers gained access to BrowserStack’s standard audit logs. That historical announcement does not establish the complete current enterprise feature set.

If you are evaluating Percy for an enterprise team, use the public evidence to understand the workflow, then verify current plan documentation and contract terms for identity, governance, scale, security, support, and pricing requirements. The sources reviewed do not confirm a complete current feature matrix.

What Percy documents for enterprise visual testing

Visual test workflow

Percy describes itself as an all-in-one visual review platform. Its stated workflow is to integrate the service, run visual tests, and review the results. It can add visual coverage to existing continuous integration suites, including complex suites running in different processes or on different machines. Percy’s homepage describes its relationship to BrowserStack with the statement “Percy is now part of BrowserStack.” Percy’s official homepage

Integrations and review flow

Percy’s integrations page describes connections to test frameworks and CI/CD services, as well as pull and merge requests, Slack notifications, and Percy webhooks. It also describes use with web applications, native apps, static sites, style guides, and component libraries. Confirm that the specific frameworks, code-review system, CI provider, and notification routes your team needs are supported in the current documentation. Percy integrations

Audit logs: the documented date matters

Percy’s changelog entry dated March 13, 2023 says: “Percy Enterprise Plan customers now have access to the standard audit logs supported by BrowserStack”. This supports the claim that Percy announced access to those standard BrowserStack audit logs for Percy Enterprise Plan customers at that time. It does not establish today’s full audit-log contents, event coverage, retention period, export behavior, or the complete set of enterprise governance controls. Percy audit logs changelog entry

What the public evidence does not confirm

The reviewed official pages do not provide a complete, current Percy Enterprise feature matrix. Do not assume any of the following are included without current official confirmation:

SSO, SCIM, or particular identity-provider support.
Role granularity, permissions, or administrative controls.
Audit-log event coverage, retention, access controls, or export options.
Data residency or particular compliance certifications.
Dedicated support, response times, or an SLA.
Custom pricing, contractual guarantees, snapshot limits, or usage allowances.
Specific browser, device, viewport, or parallelism coverage.

These are procurement questions, not confirmed Percy features based on the sources cited here. Ask Percy or BrowserStack for current plan documentation that answers each requirement explicitly.

Enterprise evaluation checklist

Map your workflow. List test frameworks, CI services, pull or merge request systems, notification destinations, and webhook consumers. Check each against Percy’s current integration documentation.
Define visual coverage. Identify the web or native applications, static sites, component libraries, browsers, devices, and viewports the team needs to cover. Verify the supported scope rather than inferring it from a general integration statement.
Specify governance needs. Write down the audit events you need, who should access them, how long they must be retained, and whether export is required. Ask for confirmation that the current plan supplies those controls.
Model operating scale. Estimate build and snapshot volume, concurrent work, baseline ownership, review responsibilities, and expected usage. Confirm current limits and plan terms.
Complete security and procurement review. Request current security documentation, identity details, support commitments, contract terms, and pricing from the vendor. Treat each as unverified until documented.
Validate the actual plan. Match the written requirements to the current plan or contract, including any audit-log scope. The 2023 changelog entry alone is not a current feature matrix.

How Percy fits into CI and code review

The public workflow supports a practical integration shape: run visual tests as part of an existing test suite, then review results through the available pull or merge request integrations and notification mechanisms. Percy also documents webhooks for custom workflow connections. The exact setup depends on your framework and CI provider; use Percy’s current integration instructions for the commands and configuration specific to your stack.

Choose the test framework and CI pipeline where visual coverage belongs.
Confirm whether the suite runs in one process or across multiple processes or machines, and check Percy’s integration guidance for that arrangement.
Connect the review path your team uses, such as pull or merge requests.
Configure Slack notifications or webhooks only where they fit the team’s review process.
Define who reviews visual changes and how baselines are managed before expanding coverage.

The reviewed source pages do not provide a universal, copy-and-run Percy configuration or command applicable to every framework. Avoid copying a generic snippet into a production pipeline without selecting the matching official integration guide.

Choosing a screenshot API alternative

If your need is to capture a URL as an image or PDF through a simple API, ScreenshotNeo is the first alternative to try: it removes consent banners, popups, and chat widgets before capture, bills only clean shots, and its lowest paid plan is $5 for 3,000 screenshots. Percy’s documented focus here is visual testing and review integrated with test and code-review workflows; confirm which approach matches your use case.

Or skip the browser setup

ScreenshotNeo takes a URL in one API request and returns a screenshot or PDF. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month.

Reliability, performance, and cost questions

The cited Percy pages do not establish performance benchmarks, uptime, pricing, usage limits, or specific reliability commitments. For Percy, request current plan and contract details covering snapshot volume, parallelism, service commitments, and support. For ScreenshotNeo, the supplied product facts state that only clean shots are billed and that cache hits cost nothing; responses include X-Page-Verdict and X-Billed headers identifying the result and billing status. Avoid projecting either vendor’s limits or costs without checking the applicable current terms.

Troubleshooting the evaluation

Symptom	Likely cause	What to do
Audit logs are required, but the available details are unclear.	The historical changelog confirms access to standard BrowserStack audit logs for Percy Enterprise Plan customers as of March 13, 2023, but does not specify current event coverage or retention.	Ask for current documentation covering events, retention, access, and export, then confirm the answers apply to the proposed plan.
A required framework or CI setup is not obvious in the integration list.	The high-level integrations page is not a complete configuration guide for every stack.	Find the official integration instructions for the exact framework and CI arrangement, including multi-process or multi-machine execution where relevant.
Stakeholders assume SSO, SCIM, an SLA, or a certification is included.	The reviewed pages do not establish those features or commitments.	Record them as open procurement requirements and request current written confirmation.
Usage or pricing estimates cannot be validated.	The reviewed sources do not establish current Percy pricing or limits.	Ask for current plan terms, expected-volume limits, and a quote if needed; do not infer them from the historical audit-log announcement.
Visual review notifications do not reach the expected workflow.	The integration may not be configured for the team’s chosen pull/merge request, Slack, or webhook path.	Check the current integration guide for the target service and validate the notification route with the owning team.

FAQ

Does Percy Enterprise include audit logs?

Percy’s March 13, 2023 changelog says Enterprise Plan customers gained access to BrowserStack’s standard audit logs. Confirm current scope and plan applicability with official documentation.

Does Percy connect to CI/CD and code review?

Percy’s integrations page describes CI and test-framework connections, pull and merge request integrations, Slack notifications, and webhooks. Check current documentation for your specific providers.

Is the 2023 audit-log announcement proof of Percy’s current enterprise controls?

No. It is evidence of a dated announcement with a specific scope. It does not document the full current feature set or the details of audit-log operation.

Where can I verify current enterprise requirements?

Use Percy and BrowserStack’s current official plan, integration, security, and contract documentation, and ask the vendor to confirm any requirement that is not explicitly documented.