Applitools Eyes Pricing for a Small QA Team
Applitools Eyes Starter is listed at $667 per month, paid annually. See what the allowance means, what to confirm in a quote, and how to judge fit for a small QA team.
Applitools Eyes Starter is listed at $667 per month, paid annually. The public pricing page lists unlimited users and an allowance of 100,000 component checkpoints or 1,000 page checkpoints. Professional and Enterprise are shown as customizable tiers without public fixed prices. Treat $667 as the published rate label, not a confirmed all-in invoice for your team. Check Applitools’ current pricing page before budgeting.
1. What the Starter price includes
| Item | Published Starter detail | What to check |
|---|---|---|
| Price | $667 per month, paid annually | Ask for the Order Form and confirm total payable, payment schedule, taxes, subscription term, and renewal terms. |
| Users | Unlimited users | Confirm any user or role restrictions relevant to your team in the Order Form. |
| Usage | 100,000 component checkpoints or 1,000 page checkpoints | Model your workload against the relevant allowance. The page presents these as alternatives; do not add them together unless Applitools confirms that treatment. |
| Higher tiers | Professional and Enterprise are customizable | Request a quote if Starter capacity or capabilities do not fit. The public page does not establish their prices. |
The pricing page describes page testing as covering full application screens and multi-step flows, while component testing isolates interface elements. Those are different ways to scope coverage, so first decide what your team intends to validate. Applitools explains page and component testing.
2. Estimate whether the allowance fits
Count the visual checks your planned suite will run in a typical month. Use your existing test inventory or a representative run, and distinguish complete pages or flows from isolated components. Avoid converting page checks into component checks using an assumed ratio: the published pricing material does not define one.
- List the routes, screens, and important multi-step flows you want to cover.
- Separately list the components you want to test in isolation.
- Estimate how often each test runs per month, including scheduled and pull-request runs.
- Compare the resulting workload with the applicable published allowance, leaving room for retries and suite growth.
- Ask Applitools how checkpoints are counted for your specific test design and whether any usage beyond the allowance changes the price or plan.
Do not assume the allowance figures can be pooled or that a retry is treated in a particular way. Confirm counting rules directly for the intended workflow.
3. Check workflow fit before comparing price
Applitools positions Eyes for teams that already use coded automation. Its documentation includes a Java Selenium quickstart, and its product material references Cypress and Playwright integrations. Review the Eyes Selenium Java quickstart and verify support for the framework and test runner you use.
For a small QA team, the practical comparison is whether the existing automation suite can host the visual checks and whether the expected page or component coverage fits the purchased tier. A low checkpoint estimate is not useful if the team cannot integrate the checks into its current workflow; likewise, an integration alone does not establish that the annual commitment is worthwhile.
4. Budget for the annual commitment and contract terms
The displayed Starter label says “paid annually.” It does not, by itself, confirm your invoice total or the precise payment schedule. Applitools’ Terms of Service say applicable fees and payment timing are set in the Order Form. They also describe subscription terms and renewals, and state that cancelling before the subscription period ends does not entitle the customer to a refund. Read the Terms of Service and review the actual Order Form before purchase.
Ask the sales or billing contact to confirm these points in writing:
- Total fees, applicable taxes, currency, and when payments are due.
- Subscription start and end dates, renewal timing, and any notice deadline for non-renewal.
- How the checkpoint allowance is measured and what happens if usage exceeds it.
- Any terms specific to your order that affect cancellation or refunds.
- Whether the quoted tier includes the features and support your workflow needs.
The published monthly label is useful for an initial comparison, but it is not a verified quote for an individual buyer.
5. Use the trial to answer concrete questions
Applitools’ FAQ describes a fully featured 14-day free trial. Its Terms of Service specify a limit of up to 100 checkpoints per month per trial user. Those statements describe different aspects of the offer, so check the live signup terms and applicable limit before planning a large evaluation. See the Applitools FAQ and Terms of Service.
Make the evaluation representative: connect the framework you plan to use, run a small selection of page and component checks, and record the resulting checkpoint usage. Use the trial to verify integration and fit; do not assume its limits predict your final contract terms.
6. Decide whether Starter is a fit
| Starter may fit when… | Get clarification or a quote when… |
|---|---|
| Your expected workload fits one of the listed allowance alternatives. | You need to combine page and component allowances or cannot determine how usage is counted. |
| Your team already has a compatible coded automation workflow. | Your framework, integrations, support needs, or required capabilities are unclear. |
| Your budget can accommodate an annual subscription at the published rate, subject to confirmed order terms. | You need monthly flexibility, have procurement constraints, or need confirmed total cost before committing. |
| The trial gives enough room to validate the planned integration. | The stated trial limit is too small for your evaluation or signup terms differ from the FAQ. |
There is not enough information in the published pricing details to claim that Eyes is cheaper or more expensive than a particular alternative. Compare the annual commitment, the page-versus-component allowance that matches your work, automation fit, and any higher-tier requirements using actual quotes.
7. ScreenshotNeo as an alternative for screenshot capture
If your immediate need is to capture clean website screenshots for QA evidence, documentation, or review, try ScreenshotNeo first. It is a screenshot API and MCP server, not a visual regression testing suite, so it does not replace Eyes’ visual test workflow. One GET request can return PNG, JPEG, WebP, or PDF. The API also supports full-page or element capture, custom viewport and device settings, waits, cookies and headers, and other capture options; 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.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides screenshot, page-info, and PDF-capture tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.
Common pricing questions
Is Applitools Eyes expensive for a small team?
The public Starter rate is $667 per month, paid annually. Whether that fits depends on your expected coverage, annual budget, framework fit, and confirmed Order Form terms.
Can we use page and component checkpoints together?
The pricing page presents 100,000 component checkpoints or 1,000 page checkpoints. Confirm directly whether and how a mixed workload is supported; do not assume the two allowances combine.
Are Professional and Enterprise prices public?
The reviewed pricing page presents both as customizable tiers without fixed public prices. Request a quote for your requirements.
How long is the trial, and is it unlimited?
The FAQ describes a 14-day fully featured trial, while the Terms of Service specify up to 100 checkpoints per month per trial user. Verify the live offer and its usage rules when signing up.
Does the $667 label guarantee the final bill?
No. It is the published Starter rate label. The Order Form and applicable terms determine fees, payment timing, and contract details for a buyer.
