Holmes vs Bug0

Bug0 runs your QA for you as a managed service.Holmes is QA your own team runs, starting free.

Both write tests in plain language, heal them when the UI changes and run on every pull request. Bug0 assigns a dedicated QA engineer who builds tests, checks every failure and gates releases, across Chrome, Firefox, Safari and Edge. Holmes is self-serve from a free plan, and adds agents that explore on their own, native mobile and API testing, and context from your specs and designs.

€250 in free credits · No credit card

What Holmes adds to Bug0

  1. Start on your own, today

    Holmes is self-serve, sets up in under ten minutes and has a Free plan with €250 in free credits, no credit card. Bug0's pricing page lists Managed at $2,500 a month, with a discounted 60-day pilot.

  2. Agents that explore on their own

    On Bug0's pages, the forward-deployed engineer explores your app and maps the critical flows. Holmes agents also explore by themselves and test paths nobody wrote down, on every change.

  3. Native mobile and API testing

    Bug0's pages describe web testing. Holmes also tests native Android and iOS apps on emulators and simulators and checks every request behind a journey, so web, mobile and API sit in one place.

  4. Context from specs, designs and analytics

    Holmes reads the code change, the ticket, the spec in Notion or Confluence, the design in Figma and your analytics in PostHog before it tests. Jira, Linear, Figma and Notion aren't on Bug0's integrations page.

Holmes and Bug0, side by side

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

Holmes compared with Bug0
CapabilityHolmesBug0
Testing
Managed serviceNot covered: Not covered. Self-serve, with guided onboarding on Team and upYes: Managed: a dedicated forward-deployed engineer plans, builds and maintains your tests and gates releases[1][2]
How tests are writtenYes: Plain-language goals. No test code to writeYes: Plain-English steps run as Playwright actions. Studio: you create them from a screen recording, a text description or by hand[3][4]
Finds bugs nobody scriptedYes: Agents explore and test paths nobody wrote downPartly: Managed: the engineer explores the app to map critical flows. An agent that explores on its own isn't on its pages[5]
Keeps tests working when the UI changesYes: Flows repair themselves when a label or layout changesYes: Steps run from intent and heal when the UI changes. Managed: the engineer confirms each heal[6][7]
BrowsersYes: Chromium, Firefox and WebKit, the engine behind SafariYes: Cloud-hosted Chromium. Managed: Chrome, Firefox, Safari and Edge, plus common viewports[8][9]
Real devicesNot covered: Not covered. Android emulators and iOS simulatorsYes: Managed: mobile web on real devices, including iOS Safari and Android Chrome[10]
Native Android appsYes: Native Android apps on an Android emulatorNot described: Not on its pages. Native iOS or Android apps
APIsYes: Every request behind a journey, checked in contextNot described: Not on its pages. API testing as a feature
AccessibilityYes: WCAG audits in a real browser, with keyboard navigationNot described: Not on its pages. WCAG audits
Workflow
Pull requests and previewsYes: Check and comment on GitHub and Bitbucket pull requests. GitLab supportedYes: Managed: runs on every pull request or commit through GitHub Actions, GitLab or any CI. Studio: validates preview deployments[11][12]
SchedulesYes: On every deploy, on a schedule, or by webhookYes: Managed: on a schedule. Studio: every 15 minutes, hourly, daily or weekly, or from any CI through its API[11][13][12]
Context it reads before testingYes: Reads the code change, ticket, spec (Notion, Confluence), design (Figma) and analytics (PostHog)Not described: Not on its pages. Jira, Linear, Figma, Notion or analytics
Coding agents (MCP)Yes: Start runs and read findings from Claude and Cursor via MCPNot described: Not on its pages. MCP server or coding-agent integration
Evidence with each bugYes: Recording, screenshots, console and network logs, steps to reproduceYes: Managed: video, network and console logs, repro steps. Studio: per-step status and screenshots[14][15]
Where findings goYes: Findings on the pull request, the ticket, Slack, Microsoft Teams and emailYes: GitHub and Slack. Studio also lists email, Vercel and Netlify[16][17]
Test code you ownYes: Plain-language goals. No test code to writePartly: Tests run on its source-available engine, and its pricing page says tests live in your repos and stay portable. A February 2026 post says it won't export standalone Playwright scripts[29][18][19]
Pricing and security
What you pay forYes: Priced on how much Holmes tests, never on seatsNote: Managed: a flat monthly fee for one engineer and up to 500 user flows, pro rata beyond[20][21]
Entry priceYes: Free plan. Paid plans from €199 ($219) a monthNote: Managed $2,500 a month, month-to-month. Studio isn't on the pricing page; Bug0's general terms (last updated June 2025) say pricing starts at $250 a month[20][22]
Getting startedYes: €250 in free credits, no credit cardYes: Managed: discounted 60-day pilot. Studio: sign in with Google[23][24]

Holmes sells QA software, so we compete with Bug0. We've tried to be fair: every statement about Bug0 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. Bug0, Homepage: Bug0 is a managed QA testing company built on its own AI platform, not a DIY tool. Checked 17 November 2026.
  2. Bug0, Managed QA: A forward-deployed QA engineer plans coverage, builds your tests on Bug0's agentic AI engine, verifies results, files bugs, and gates releases. Checked 17 November 2026.
  3. Bug0, QA agent: Tests are written as plain-English steps and executed as Playwright actions by AI. Checked 17 November 2026.
  4. Bug0 Studio docs, Creating tests: Record your screen performing the flow, and AI extracts test steps automatically. Checked 17 November 2026.
  5. Bug0, Homepage (how it works): Your FDE explores the app, maps your critical flows (signups, checkouts, dashboards) and drafts the coverage plan. Checked 17 November 2026.
  6. Bug0, Homepage (test maintenance): Tests auto-heal. 0% flake rate. Bug0 AI, our open-source engine, executes each step from intent. Checked 17 November 2026.
  7. Bug0, Managed QA (self-healing): The engineer confirms each heal, which is what stops a healed test from passing while it checks nothing. Checked 17 November 2026.
  8. Bug0, AI platform: Cloud-hosted Chromium tests with realistic data and fixtures. Checked 17 November 2026.
  9. Bug0, Managed QA (cross-browser): Validate your app across major browsers (Chrome, Firefox, Safari, Edge) and common viewports. Checked 17 November 2026.
  10. Bug0, Managed QA (real devices): Running suites on macOS Safari, Windows Edge, iOS Safari, and Android Chrome. Checked 17 November 2026.
  11. Bug0, Homepage (CI/CD): GitHub Actions and the Bug0 app. Tests run on every PR, every commit, or on a schedule. Checked 17 November 2026.
  12. Bug0 Studio docs, CI/CD: Call the /api/run-tests endpoint directly from any CI/CD system. Checked 17 November 2026.
  13. Bug0 Studio docs, Scheduling: Every 15 minutes Critical path monitoring Checked 17 November 2026.
  14. Bug0, Homepage (bug reports): files a report with video recording, network logs, console logs, and repro steps. Checked 17 November 2026.
  15. Bug0 Studio docs, Running tests: Screenshots - Visual state at key points Checked 17 November 2026.
  16. Bug0, Homepage (reports): Reports go to GitHub, Slack, or wherever you need them. Checked 17 November 2026.
  17. Bug0 Studio docs, Integrations: Connect your GitHub repository for: Checked 17 November 2026.
  18. Bug0, Why we don't export Playwright scripts (February 2026): Can I export my Bug0 tests as Playwright scripts? Checked 17 November 2026.
  19. Bug0, QA agent (licence): Bug0 AI is licensed under FSL-1.1-Apache-2.0. Checked 17 November 2026.
  20. Bug0, Pricing: $2,500/mo flat. Month-to-month. No annual contracts. Checked 17 November 2026.
  21. Bug0, Pricing (coverage): Up to 500 user flows. Pro rata beyond. Checked 17 November 2026.
  22. Bug0, Terms of Service (June 2025): Pricing starts at $250/month and scales based on usage. Checked 17 November 2026.
  23. Bug0, Homepage (FAQ): We offer a discounted 60-day pilot. Month-to-month, no annual commitment. Cancel anytime. Checked 17 November 2026.
  24. Bug0 Studio docs, Quickstart: Click Sign in with Google (use your work email) Checked 17 November 2026.
  25. Bug0, Introducing Bug0 Studio: We are opening up Bug0 Studio v0.1 in research preview. This is the internal tool our FDE team uses to turn natural language and video into clean, reliable Playwright tests. Checked 17 November 2026.
  26. Bug0, Homepage (enterprise): BAAs available for healthcare customers. Checked 17 November 2026.
  27. Bug0, Voice AI testing: Bug0's AI agents and forward-deployed engineers catch what breaks before your customers hear it. Checked 17 November 2026.
  28. Bug0, Managed QA (FAQ): We're not a fit for mobile-native apps. Checked 17 November 2026.
  29. Bug0, Pricing: You own the artifacts. Tests live in your repos and CI. Checked 17 November 2026.

Questions about Holmes and Bug0

What is the main difference between Holmes and Bug0?

Bug0 is first a managed service. A dedicated forward-deployed engineer plans coverage, builds tests on Bug0's AI engine, checks every failure and gates your releases. Holmes is a self-serve product: its agents test your web app, mobile app and APIs, explore on their own, and read your specs and designs, with results on the pull request.[1][2]

Does Bug0 have a self-serve product?

Yes. Bug0 Studio is the tool its own engineers use, opened as a v0.1 research preview. Its docs cover tests from a screen recording or a text description, pull request runs, schedules, and Slack and email results. Bug0's pricing page lists only Managed. Its general terms of service, last updated in June 2025, say pricing starts at $250 a month and scales with usage; they don't name Studio.[25][4][20][22]

How does pricing compare?

Bug0 Managed is $2,500 a month flat, month-to-month, for one engineer and up to 500 user flows, with pro rata pricing beyond that and a discounted 60-day pilot. 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. Holmes is priced on how much it tests, never on seats.[20][21][23]

Can I take my tests with me?

Bug0 says your tests stay portable: its pricing page says tests live in your repos and CI, and its engine, Bug0 AI, is source-available under FSL-1.1-Apache-2.0 and runs in any Playwright project. A February 2026 post says it won't build a button that exports standalone Playwright scripts. Ask Bug0 what you keep if you leave. Holmes tests are plain-language goals, with no test code to maintain.[29][18][19]

When might Bug0 be the better fit?

If you want a dedicated QA engineer to plan, write, maintain and triage your tests for you, Bug0 is built for that. Its managed service also covers Chrome, Firefox, Safari and Edge, mobile web on real devices including iOS Safari, BAAs for healthcare customers, and testing for voice and chat AI agents. Its managed page says it isn't a fit for mobile-native apps. If you want to run QA yourself, starting free, with native mobile apps, API testing and context from your specs and designs, try Holmes.[2][9][10][26][27][28]

Further reading

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