I've seen other YC companies do this exact thing and pivot. What's your differentiation?

Completely agree with some of the comments, actually the hardest part is to execute these tests in a fast an reliable manner paralelizing the most of it, for your regression tests.

As we all know, in large orgs the form issue has been solved by using trusted components with unit tests. What worries me is how somebody were actually to provide valuable bugs, those that keep you up at night trying to fix them.

I worked with exploratory testing companies that would report hundreds of bug that nobody ever cared about. Does YC really care about the bug that they found, or have a business impact?

(Actually coming from building a company in this area now https://desplega.ai, you can try it out for free too)

UI tests, and any automated tests in general, must be reproducible and deterministic to be useful. Do you position this product as an automated test tool, or useful “chaos monkey”?

Also a nitpick, but there are profanities on your landing page and it kinda puts me off.

This is actually a great idea but my advice to you is to package it in some bigger kind of offering because this is a small niche.

And likely this type of thing is not suitable for CI use. CI systems are already too slow and flaky. You want to run this type of thing nightly.

For example look at supabase. They basically sell a DX CLI + UI as their core offering. But that’s not a real business. So they sell off the shelf AWS RDS + postgrest + gotrue and now it is a cohesive platform that you can charge real money for. But those pieces are just the easy to assemble legos around their core thing. Not to belittle how impressive they are at shipping, but a lot of what makes supabase great is the brilliant assembly of these preexisting components, wrapped in a delicious package

This is awesome and an idea i've thought a lot about. In my experience, people either have flaky e2e tests or no e2e tests. How do you solve cost / margin? Is this an order of magnitude more expensive than my existing CI running playwright tests?

We use Gitlab. Is that planned?

Typo on your landing page: "GitHub PR Intergration" -> "GitHub PR Integration"

Man this is a tough crowd.

The product looks interesting. My only question would be what does a common successful description of a user journey look like?

Is it pages and pages of prompting to get the agents to understand or do you see success with less verbose descriptions?

Price?

You know “Ghostship” was the name of an incredible East Bay artists’ community that was destroyed in a fire which killed multiple people. Is this really the name you’re going with? It’s not ancient history, either - less than 10 years.