Holmes vs Functionize

Functionize checks what your coding agents build.Holmes also explores what nobody thought to check.

Both write tests from plain language and repair them when the UI changes. Functionize already runs on four browsers, and checks SMS and email. Holmes adds agents that explore past the script, native mobile testing, and context from specs, designs and analytics.

€250 in free credits · No credit card

What Holmes adds to Functionize

  1. Agents that explore past the script

    Functionize Studio tests what you describe; in its own words, you decide what matters. Holmes tests your goals too, and its agents also explore paths nobody wrote down.

  2. Native mobile apps as well as the web

    Functionize's pages describe web flows. Holmes tests native Android and iOS apps on emulators and simulators, with the same plain-language goals it uses for the web.

  3. Context from specs, designs and analytics

    Functionize lists MCP, CI/CD, Jira and Slack among its integrations. Holmes also reads the spec in Notion or Confluence, the design in Figma and your top pages in PostHog before it decides what to test.

  4. Accessibility audits in a real browser

    Holmes runs WCAG audits with keyboard navigation and walks your product as the personas you build for. Accessibility testing isn't described on Functionize's pages.

Holmes and Functionize, side by side

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

Holmes compared with Functionize
CapabilityHolmesFunctionize
Testing
How tests are writtenYes: Plain-language goals. No test code to writeYes: Describe it in a chat; Studio writes, runs and maintains the tests[1]
Finds bugs nobody scriptedYes: Agents explore and test paths nobody wrote downNot described: Not on its pages. Exploring beyond the tests you describe
Keeps tests working when the UI changesYes: Flows repair themselves when a label or layout changesYes: Self-healing on every run; elements found by how they look and what they mean[2]
Other browsersYes: Chromium, Firefox and WebKit, the engine behind SafariYes: Chrome, Firefox, Safari and Edge, single or in parallel[2]
Native Android appsYes: Native Android apps on an Android emulatorNot described: Not on its pages. Native Android apps
Native iOS appsYes: Native iOS apps on iPhone and iPad simulatorsNot described: Not on its pages. Native iOS apps
APIsYes: Every request behind a journey, checked in contextYes: APIs, databases, files, email and SMS in the same flow[2]
Visual testingPartly: Compares the Figma design with what shipped. No pixel-diff baselinesYes: Baseline, step comparison or page check[2]
AccessibilityYes: WCAG audits in a real browser, with keyboard navigationNot described: Not on its pages. Accessibility (WCAG) testing
Workflow
Pull requests and previewsYes: Check and comment on GitHub and Bitbucket pull requests. GitLab supportedPartly: Its developers page says every pull request is tested against the live app; git hosts and previews aren't named[3]
SchedulesYes: On every deploy, on a schedule, or by webhookYes: Orchestrations on demand or on a schedule, parallel or sequential[2]
Coding agents (MCP)Yes: Start runs and read findings from Claude and Cursor via MCPYes: MCP server for Claude Code, Cursor, Copilot and others[4]
Evidence with each bugYes: Recording, screenshots, console and network logs, steps to reproducePartly: Run records, a screenshot on every step and a diagnosis of each failure; video and console logs aren't described[2]
Where findings goYes: Findings on the pull request, the ticket, Slack, Microsoft Teams and emailPartly: Integrates with Jira, Slack, CI/CD and MCP; how findings reach Jira or Slack isn't described[5]
Pricing and security
What you pay forYes: Priced on how much Holmes tests, never on seatsNote: Credits, billed monthly or annually; Growth and Scale can buy more[6][7]
Entry priceYes: Free plan. Paid plans from €199 ($219) a monthNote: Free plan; Growth $20 a month, Scale $100 a month, Enterprise on request. Extra credits $10 per 200,000 on Growth and Scale[7]
Getting startedYes: €250 in free credits, no credit cardYes: Free plan with 800,000 credits a month, no credit card[7]
Where it runsNot covered: Not covered. Cloud onlyYes: Its cloud, or privately inside your own environment[5]
Data locationYes: EU company (Ghent, Belgium), GDPR compliantNote: Data kept in the region you operate in[5]

Holmes sells QA software, so we compete with Functionize. We've tried to be fair: every statement about Functionize 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. Functionize, Studio overview: Describe what your app should do. Studio writes the tests, runs them, and keeps them current as the app changes. Checked 17 November 2026.
  2. Functionize, Agent Tasks: Chrome, Firefox, Safari, and Edge, single or in parallel. Checked 17 November 2026.
  3. Functionize, For developers: Every PR is tested against your live app the moment it's ready. Checked 17 November 2026.
  4. Functionize, MCP: Build, run and diagnose tests against your real app from Claude Code, Cursor or Copilot Checked 17 November 2026.
  5. Functionize, Enterprise: Run on our cloud, or deploy privately inside your own environment. Checked 17 November 2026.
  6. Functionize, Usage limits: Credits are billed on your plan's payment cycle monthly or annually, in advance. Checked 17 November 2026.
  7. Functionize, Pricing: The Free plan includes all agent capabilities, 800,000 credits each month, and five parallel runs. You do not need a credit card. Checked 17 November 2026.

Questions about Holmes and Functionize

What is the main difference between Holmes and Functionize?

Both describe tests in plain language and keep them working as the UI changes. Functionize Studio tests the web flows you describe, across four browsers, and adds SMS, email and database checks. Holmes also explores paths nobody wrote down, tests native Android and iOS apps, and reads specs, designs and analytics before it tests.[1][2]

Do both test mobile apps?

Holmes tests native Android and iOS apps on emulators and simulators. Functionize's current pages describe web flows, and native mobile apps aren't described there.[2]

How does pricing compare?

Functionize charges credits. The Free plan includes 800,000 credits a month and five parallel runs, Growth is $20 a month, Scale is $100 a month, and Enterprise is priced on request. Holmes has a Free plan, Starter at €199 a month for up to 3 products, and Team from €499 a month, all with unlimited users.[7]

Do both work with coding agents?

Yes. Functionize has an MCP server for Claude Code, Cursor, Copilot and others. Holmes connects to Claude and Cursor via MCP to start runs and read findings, and it checks every pull request and preview deployment.[4]

When might Functionize be the better fit?

If you need runs on Safari and Edge, SMS, email or MFA checks (on paid plans), or a private deployment inside your own environment, Functionize covers those on its own pages, at a low entry price. If you want agents that explore beyond what you describe, native mobile testing and context from specs and designs, try Holmes.[2][5][7]

Further reading

Evaluating Functionize? 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.