An Octomind alternative: where to take your generated Playwright tests
Octomind generated Playwright tests from a URL and ran them on pull requests; the service went offline at the end of May 2026 and the company wound down in June. If that was your workflow, FlowQA gives you the same shape: point it at a URL, get a suite, run it on every deploy, with two changes that address why generated tests often did not earn trust: a plan you review before tests are written, and a proof step that breaks the page to check each test can fail.
What Octomind offered
Auto-generated end-to-end tests from a URL, a pull-request integration, a free tier, and published plans (Basic at $89 a month for 80 tests and 240 runs, Pro at $589 a month for 300 tests and 1,800 runs). It was a well-made hosted Playwright with generation on top. Its founders said it closed for lack of market validation after more than three years, which is a lesson about the category: a better hosted Playwright on its own did not sell.
What is the same in FlowQA
- Point the agent at a URL and it maps the site and generates tests.
- Run on every deploy from your pipeline, with the result as a status and a message when it fails.
- Cloud browsers included, local runs free.
- Tests are exportable; your suite is yours.
What is different
You review the plan first. After mapping, the agent proposes journeys with their outcomes. Ten minutes crossing off the irrelevant and correcting the outcomes is where generated suites go from plausible to useful.
Every test is proven. A generated test that passes proves nothing until it has failed on a broken page. FlowQA breaks the page and runs the test; tests that still pass are rewritten or dropped. Each is also replayed on a fresh session.
Repairs wait for a person. When a page changes, one small repair is proposed, proven twice, shown with its reason, and approved or rejected.
The agent asks when it cannot know. A code from an inbox, which of two buttons, whether to follow a link to another host. Answers are kept.
Bugs and tests in one workspace. Snag captures what slipped through, with the screenshot, steps, console and network; a snag becomes a test; a failing test files a snag; your coding agent works both over MCP.
Prices, side by side
Octomind's last published prices against FlowQA's as published on 2026-10-07.
| Octomind (last published) | FlowQA | |
|---|---|---|
| Free | Yes | 1 project, 100 tests, 1,000 cloud runs a month, 10 AI-generated tests |
| Entry | $89 a month, 80 tests, 240 runs | $49 a month, unlimited tests, 3,000 cloud runs, 3 explorations |
| Growth | $589 a month, 300 tests, 1,800 runs | $149 a month, 15,000 cloud runs, 10 explorations, 15 members |
| Generated tests | Included | 10 cents per accepted test beyond the allowance, 2 with your own model key |
| Trial | Free tier | 14-day trial of Team, no card |
Moving over
Export what you can from your old suite as a list of journeys: start page, steps, outcome. That list is the plan. Give it to the agent with your staging URL and a test account, review what it proposes, and let it generate and prove. Most teams are back to a running suite on their deploy pipeline within a day.
FlowQA explores your site, writes the tests, proves them against a broken page, and keeps proving them after every change.
See FlowQA