Hey there, I'm Jeff (one of the founders). To be honest I don't know if there is or will be any kind of moat in SaaS. But today:

1/ General purpose models are still not good at this task. I would personally love it if I could trust my agent when it says its done after a 24h build. But whether it's because of sycophancy, context degradation over time, or something else coding agents still struggle to verify their own work. Maybe with 1B context windows this will change.

2/ Infra is still annoying to setup. We wanted to provide a unified interface across web, mobile and soon desktop as well. So users don't have to worry about provisioning, concurrency, security, etc.

3/ As with any SaaS, even beyond the initial build, maintenance is a headache. I think most companies would rather not consider agentic QA as one of their core competencies and investments. It takes a ton of eng effort to keep the lights on, continually update the models used, train new ones, groom ground truth, onboard infra providers, etc.

When people say "just point Opus/Codex at localhost using Playwright MCP," they've obviously never attempted to do exploratory testing by leveraging parallel browser workers against stateful applications. A coding agent running in a loop spends almost all of its context window struggling with DOM selectors and doesn't even detect state persistence problems like the 2.5h->25h decimal inflation upon refreshing the page as demonstrated in the demo. Managing read/write resource leases for parallel sub-agents not to step on each other's test fixtures is already a non-trivial orchestration challenge by itself.