Holmes vs Applitools

Applitools catches visual changes with Visual AI.Holmes tests whether each journey still works.

Both run on pull requests, repair tests when the UI changes and work with coding agents through MCP. Applitools is the specialist in visual regression. Holmes adds agents that explore functional journeys, WCAG audits with keyboard navigation, and context from tickets, specs and analytics.

€250 in free credits · No credit card

What Holmes adds to Applitools

  1. Agents that explore functional journeys

    Applitools runs the tests you write, record or crawl, deterministically. Holmes agents also explore your product, test paths nobody wrote down, and re-test borderline issues before they report them.

  2. Accessibility audits beyond contrast

    Applitools' pages describe visual WCAG checks: contrast, font sizes and layout overlap. Holmes runs WCAG audits in a real browser, keyboard navigation included, and walks your product as the personas you build for.

  3. Context from tickets, specs and analytics

    Both can use Figma designs. Holmes also reads the code change, the ticket, the spec in Notion or Confluence and your top pages in PostHog before it decides what to test.

  4. Start free, then from €199 a month

    Applitools Starter is $667 a month, paid annually, and its plain-English Autonomous tests sit in Professional, priced on request. Holmes has a Free plan and publishes its Starter and Team prices.

Holmes and Applitools, side by side

Based on each product's public pages on 17 November 2026. A red cross means Applitools's pages don't describe it, not that it can't be done.

Holmes compared with Applitools
CapabilityHolmesApplitools
Testing
How tests are writtenYes: Plain-language goals. No test code to writeYes: Visual checkpoints in your own test code, or plain English in Autonomous[1][2]
Finds bugs nobody scriptedYes: Agents explore and test paths nobody wrote downNot described: Not on its pages. An agent that explores for bugs beyond scripted or crawled tests
Keeps tests working when the UI changesYes: Flows repair themselves when a label or layout changesYes: Self-healing locators; accept a visual change once and it applies across the suite[3][4]
Visual testingPartly: Compares the Figma design with what shipped. No pixel-diff baselinesYes: Visual AI against baselines, with the DOM and CSS change behind each difference[4]
Other browsersYes: Chromium, Firefox and WebKit, the engine behind SafariYes: Chrome, Safari, Firefox and Edge, rendered at once on the Ultrafast Grid[5]
Native Android appsYes: Native Android apps on an Android emulatorYes: Visual checkpoints in Appium or Espresso scripts[6]
Native iOS appsYes: Native iOS apps on iPhone and iPad simulatorsYes: Visual checkpoints in Appium or XCUITest scripts[6]
Real devicesNot covered: Not covered. Android emulators and iOS simulatorsPartly: Real and emulated iOS and Android devices on its Native Mobile Grid; its pricing page lists real-device access as an Enterprise add-on[6][7]
APIsYes: Every request behind a journey, checked in contextYes: API steps in Autonomous flows; codeless API testing on Professional[2][7]
AccessibilityYes: WCAG audits in a real browser, with keyboard navigationPartly: WCAG contrast checks with Contrast Advisor, plus font-size and layout-overlap checks in Eyes, on web, native mobile and PDF[8][5]
Workflow
Pull requests and previewsYes: Check and comment on GitHub and Bitbucket pull requests. GitLab supportedYes: Autonomous runs on every pull request; baselines follow GitHub and GitLab branches[2][5]
SchedulesYes: On every deploy, on a schedule, or by webhookYes: On a schedule, or from CI/CD through the API[2][3]
Context it reads before testingYes: Reads the code change, ticket, spec (Notion, Confluence), design (Figma) and analytics (PostHog)Partly: Figma designs as baselines. Notion or Linear aren't on its integrations pages[9]
Coding agents (MCP)Yes: Start runs and read findings from Claude and Cursor via MCPYes: MCP server for Claude Code, Cursor, Copilot and Cline[1]
Evidence with each bugYes: Recording, screenshots, console and network logs, steps to reproduceYes: Visual diffs with the DOM and CSS cause, browser recordings and console logs[4][9]
Where findings goYes: Findings on the pull request, the ticket, Slack, Microsoft Teams and emailYes: Jira, Slack, Microsoft Teams and email, among 60+ integrations[5][10]
Pricing and security
What you pay forYes: Priced on how much Holmes tests, never on seatsNote: Checkpoints on Starter; active pages and components on higher plans[7]
Entry priceYes: Free plan. Paid plans from €199 ($219) a monthNote: Starter $667 a month, paid annually, after a 14-day free trial; Professional and Enterprise on request[7][11]
Where it runsNot covered: Not covered. Cloud onlyYes: SaaS, dedicated cloud, or on-premises inside your firewall; on-premises is an Enterprise add-on[12][7]

Holmes sells QA software, so we compete with Applitools. We've tried to be fair: every statement about Applitools comes from its own public pages, linked below with the date we checked them. Products change. If something here is out of date, email support@useholmes.com and we'll fix it.

Sources

  1. Applitools, Create: Add Applitools to Selenium, Cypress, Playwright, Appium, and dozens of other frameworks and languages with one line of code. Checked 17 November 2026.
  2. Applitools, Autonomous: Autonomous lets QA and manual testers describe tests in plain English, then executes them with a Deterministic Language Model that produces the same result every time. Checked 17 November 2026.
  3. Applitools, Execute: When a class, ID, or attribute changes, Applitools uses visual and semantic clues to find the same element instead of failing outright. Checked 17 November 2026.
  4. Applitools, Analyze: Click a visual difference and see the exact DOM and CSS rule change that caused it, instead of comparing screenshots side by side. Checked 17 November 2026.
  5. Applitools, Eyes: Validate responsive layouts across Chrome, Safari, Firefox, Edge, iOS, and Android simultaneously. Checked 17 November 2026.
  6. Applitools, Mobile testing: Add a visual checkpoint to an existing Appium, Espresso, or XCUITest script without rebuilding your test suite. Checked 17 November 2026.
  7. Applitools, Pricing: Access to real iOS & Android devices Checked 17 November 2026.
  8. Applitools, Accessibility testing: Set the WCAG version (2.0 or 2.1) and level (AA or AAA) per test, and Contrast Advisor measures against that exact threshold. Checked 17 November 2026.
  9. Applitools, What's new: Play back browser recordings or download console logs for more context Checked 17 November 2026.
  10. Applitools, Integrations: Applitools works with 60+ major testing frameworks and languages, source code tools, CI/CD tools, and collaboration tools. Checked 17 November 2026.
  11. Applitools, FAQ: Yes, Applitools a 14-day free trial that is fully featured, allowing users to explore the platform. Checked 17 November 2026.
  12. Applitools, Home: Deploy Applitools on your own infrastructure, inside your firewall for maximum security. Checked 17 November 2026.

Questions about Holmes and Applitools

What is the main difference between Holmes and Applitools?

Applitools is built around Visual AI: it compares screens against baselines and shows the DOM and CSS change behind each difference, and its Autonomous product runs plain-English tests deterministically. Holmes is an AI agent that tests functional journeys on web, mobile and APIs, and explores paths nobody wrote down.[4][2]

How do they handle visual testing?

Applitools does visual regression testing against baselines and renders one run across Chrome, Safari, Firefox, Edge, iOS and Android. Holmes compares the Figma design with what shipped; it does not keep pixel-diff baselines. If pixel-level visual regression is your main need, Applitools is the specialist.[4][5]

Do both test mobile apps?

Applitools adds visual checkpoints to Appium, Espresso or XCUITest scripts, and real iOS and Android devices are an Enterprise add-on. Holmes tests native Android and iOS apps on emulators and simulators, without test scripts.[6][7]

How does pricing compare?

Applitools Starter is $667 a month, paid annually, priced on checkpoints. Professional and Enterprise are priced on request by active pages and components, and AI-driven functional testing sits in Professional. There is a 14-day free trial. Holmes has a Free plan, Starter at €199 a month for up to 3 products, and Team from €499 a month, with unlimited users on every plan.[7][11]

When might Applitools be the better fit?

If visual regression is your main concern, you want visual checks inside existing Selenium, Cypress, Playwright or Appium suites, or you need Storybook or PDF testing, real devices or on-premises deployment, Applitools covers those on its own pages. If you want agents that explore functional journeys from plain-language goals, with WCAG audits and checks on preview deployments, try Holmes.[1][6][7][2][12]

Further reading

Evaluating Applitools? See what Holmes finds first.

Your bugs in your inbox, 30 minutes from now.

Free, no scripts, no SDK, and no test account needed to start.