# Superflow vs Spur

> Spur is agentic QA testing for engineering teams. Superflow is a QA reviewer with a human in the loop: agents check, your team calls it, clients sign off.

This is the Markdown copy of https://usesuperflow.ai/comparisons/superflow-vs-spur, published for AI agents and scripts. The HTML page is canonical.

## Key facts

| Field | Value |
| --- | --- |
| Page type | Head-to-head comparison |
| URL | https://usesuperflow.ai/comparisons/superflow-vs-spur |
| Compares | Superflow vs Spur |
| Facts checked on | 2026-08-01 |
| Disclosure | Published by Superflow. Superflow is one of the tools compared. |
| Last updated | 2026-08-01 |

## Dimension by dimension

| Dimension | Superflow | Spur | Verdict |
| --- | --- | --- | --- |
| Who checks the site | Agents run your checklist. Every change, desktop and mobile. Broken links, brand colors and fonts against the brand guide, spelling, accessibility basics, and SEO. Findings land as pinned comments, rationale attached. Then a human. Agents are the first pass, never the last word: your team confirms or overrules every finding. | Autonomous agents plan, execute, and report tests. Five types: exploratory, localization, UI/UX, functional, and AI feature testing. The UI/UX agent explores the product like a real user and catches typos, content inconsistencies, layout overflows, and broken interactions. Written in plain English, no code. (verified August 2026) | On the agent half, even, and it says so. The difference is the other half: Spur's agents report and stop, Superflow's hand every finding to a person who confirms it or overrules it. |
| What it remembers | Brand guides, guidelines, and checklists go in once, per brand. Then your team's calls train it: every accept or reject on an agent's comment teaches that brand's Memory. The next review starts there. Agents check new work against that brand's rules and past decisions, and Memory flags a likely miss before review even opens. | Intent-based tests adapt when the site changes; when an edit is needed it's plain English, and their team helps. Learning from a human's accept or reject on a finding, carried into the next run: not yet verified. (verified August 2026 except where noted) | Two kinds of adaptation. Spur's tests keep passing when the site changes. Superflow's agents get sharper every time a human overrules one, so what your team rejected last month is what they check for next month. |
| What gets captured | Element and text pins, area comments: the finding sits on the thing it's about. A screenshot attaches to every comment automatically. Recordings: screen, video, voice, from the toolbar. | Every run produces full video playback and step-level evidence. Their public Bug Book shows the format: test, failure step, screenshot, and cost, rated Critical to Mild. No contextual comments. A finding lives in the run report, not pinned to the element on the page. (verified August 2026) | Spur's video of a failing run is the better proof for an engineer. But nothing is pinned to the page, so a person still has to carry each finding back to the element it belongs to. In Superflow the comment is already sitting on it. |
| How the client says yes | Multi-step review flows: agents check, your team gates, then whoever signs off. The approver opens a link and taps Approve. No account, no login, no app, from their phone. | Runs report to the team that owns the site, with full video playback and step-level evidence. An approval or sign-off step for anyone outside that team: none found on spurtest.com. (checked August 2026) | Spur reports to the team that owns the product. Superflow carries the finding to the person who has to approve the work. |
| Where you review | Superflow lives on the site itself: passwords, Okta, SSO, no extension needed, guests included. Findings tagged by device. Websites plus video, PDFs, images, and Lottie files, reviewed in the same place. | Tests from the outside, like a real user: you provide a URL, and a build file for native apps. Logins, MFA and OTP handled with test accounts and whitelisted IPs; strict bot protection is worked through with your security team. Web and native mobile apps only. No PDFs, images, or video review. (verified August 2026) | Spur goes deeper on one surface, including native iOS and Android. Superflow goes wider, across every format that has to be approved. |
| How it fits your stack | Connect GitHub or Vercel and a push or deploy starts the review flow on its own. Any change to the live site does too. Push-triggered runs, steps, conditions, and notifications, for review instead of deployment. No YAML. An MCP as well: create and run agents on your site from any LLM. Custom statuses, approval gates, kanban. Two-way Asana, Monday, ClickUp; Slack built in. | CI through GitHub Actions, for example on each pull request. Spur MCP wires Cursor, Claude, and Copilot to the agent, drafts tests from a pull request diff, and pairs with GitHub, Jira, Linear, or Slack. Hundreds of tests run in parallel across web and native mobile. (verified August 2026) | Both hang off the pipeline, and both have an MCP. The difference is what the trigger starts: Spur's run returns a pass or fail that gates the merge, Superflow's starts a review that routes to people and ends in a recorded sign-off. |
| What stays private | Internal-only notes your team sees and no one outside it does. The debate stays private; the approver sees one settled answer. | Every run is internal by construction: results go to your team, and there is no outside view or comment layer. (checked August 2026) | Not a defect, a consequence. Spur has no outward-facing side, so it has nothing to keep private from one; Superflow assumes from the start that someone outside the team will read this. |

## Scorecard

| Measure | Spur | Superflow |
| --- | --- | --- |
| Who checks the site | agents, five types, plain English | agents, from your checklist |
| How the client says yes | reports to your team; no sign-off step | a recorded approval: team gate, then final sign-off |
| Where you review | live web and native mobile, from a URL or build file; logins, MFA, OTP | live site, behind logins and SSO, no extension; plus video, PDF, images, Lottie |
| What stays private | no outside view, so nothing to keep from one | internal-only comments |
| What gets captured | full video playback, step-level evidence, screenshots; no comments pinned to the page | contextual pins on the element; automatic screenshots; screen, video, voice |
| What it remembers | intent-based tests adapt to the site; learning from review decisions - | Memory, per brand; every accept or reject teaches the next review |
| How it fits your stack | GitHub Actions CI; MCP for Cursor, Claude, Copilot; pairs with GitHub, Jira, Linear, Slack | GitHub and Vercel push triggers; MCP from any LLM; statuses, approval gates, kanban; two-way Asana, Monday, ClickUp; Slack |
| What it costs | annual plans on test-run volume, not seats; demo for a quote (August 2026) | Free plan; Growth $29 per seat/mo ($24 annual); Scale $34; Enterprise custom |

## Where Superflow fits

Spur earned its logo wall. Its agents drive real journeys, sign in, checkout with a card, a return, chained together and run hundreds at a time across web, iOS, and Android. Every run comes back with video playback and step-level evidence, and customers report about 80% fewer false positives than scripted suites. Alo spent seven months failing to stabilise Selenium; Spur got tests live in days. Living Spaces went from zero to 80% coverage in a month. Their public Bug Book shows the actual production bugs they caught, with the failing step attached.

## Pricing

Verified August 2026: annual plans based on test-run volume, not per seat. No public price list, no free plan, and no free trial stated; you book a demo for a quote tailored to your release cadence. Most teams start with a one to two week POC, and there is a three-phase pilot program with limited slots. Overages are never auto-billed, they're flagged and agreed together.

From the Growth plan. See /pricing.

## Sources

- https://www.spurtest.com
- https://www.spurtest.com/agents/ui-ux-feedback
- https://www.spurtest.com/agents/functional-testing
- https://www.spurtest.com/agents/localization-agent
- https://www.spurtest.com/bug-book-collection
- https://www.spurtest.com/case-studies
- https://www.spurtest.com/spur-mcp
- https://www.spurtest.com/book-a-demo

## Questions and answers

### Is Superflow a replacement for Spur?

No, and for a QA team running regression it shouldn't be. Spur automates functional testing for a product team; Superflow runs the review and approval loop for the people shipping the work.

### Can Superflow test a checkout flow?

Not today. Superflow's agents check pages, they don't simulate multi-step journeys, so a checkout that errors on step three is Spur's catch, not ours.

### Do the agents replace my reviewers?

No. Agents run the first pass. Your team decides, then whoever owns the sign-off approves.

### Spur's agents adapt too. How is Superflow's memory different?

Spur's tests adapt to the site, which keeps them passing through a redesign. Superflow's Memory adapts to the brand: every agent comment your team accepts or rejects becomes a rule the next review already checks for.

### Can we run both?

Yes, and many teams should. Spur gates the release in CI; Superflow gets the campaign page reviewed and signed off.

### Will reviewers have to learn a new tool?

No. They get a link and an Approve button. No account, no login, no app, from their phone.

### What does it cost?

From the Growth plan. See /pricing.

## Related pages

Each of these also publishes a Markdown copy at its own path plus `.md`.

- [Superflow vs BugHerd](https://usesuperflow.ai/comparisons/superflow-vs-bugherd)
- [Superflow vs Marker.io](https://usesuperflow.ai/comparisons/superflow-vs-marker-io)
- [AI review agents](https://usesuperflow.ai/ai-review-agents)

## About Superflow

Superflow is a website and creative-asset review tool. Its agents watch every page of a site, report what changed, and route findings to the people who approve them. Teams leave contextual feedback on live sites, staging environments, PDFs, images, videos, and Lottie animations, and comments sync two-way with Asana, ClickUp, Monday, Slack, Webflow, and Google Tag Manager.

Machine-readable entry points:

- Site index: https://usesuperflow.ai/llms.txt
- Full site content in one fetch: https://usesuperflow.ai/llms-full.txt
- Free tools, with a Markdown copy of each: https://usesuperflow.ai/tools.md
- MCP server (Streamable HTTP, no account and no API key): https://usesuperflow.ai/api/mcp
- Agent card: https://usesuperflow.ai/.well-known/agent-card.json