We said MAYBE on August 8, 2026. Not settled — due August 8, 2027.
Read this with the caveat. We tested the engine that produced this verdict against 292 launches whose outcomes we already knew, and could not show it predicted which survived. Some of its data sources were also dead at the time of scoring. The verdict stays up, dated and unedited, because a record you can quietly revise is not a record — but it is worth less than it looked when it was written.
Demand is real but modest—proven by four paying competitors and growing search, though social pull is quiet. Winnability is middling: a legitimate open-source/observability wedge exists against funded incumbents, but the engineering burden and free-alternative saturation make durable revenue hard for a solo builder.
Four established competitors are actively charging for browser automation, which is strong proven demand for a B2B/utility tool, and search demand is growing; social chatter exists but is thin and low-engagement.
A genuine wedge exists (open-source, self-hosted, lightweight local agent dev with built-in observability), but the incumbents are well-funded infra giants (Vercel, Cloudflare) and the underlying browser-orchestration engineering is heavy for a solo founder.
The strongest case against building: the wedge (open-source local browser automation) is exactly where a solo founder burns out—maintaining a reliable multi-browser orchestration layer against constantly-shifting anti-bot defenses and browser updates is a treadmill of infra work, not a shippable weekend product. Vercel and Cloudflare can bundle this into ecosystems for near-zero marginal cost, and open-source browser agents (Playwright-based, browser-use, etc.) already flood GitHub, meaning monetization is fragile even if adoption comes.
What is worth more than this page. The register records what became of 6,266 real launches. No engine has to be right for that to be true.