The signup died on Thursday
A prompt changed a label, the button no longer submits, and nobody noticed until a friend tried to join.
For apps built with Lovable, Bolt, Replit, and Cursor
Does your app still check out?
StillChecksOut acts like a customer. It walks signup, login, and the path up to checkout. It compares who paid in Stripe with who can actually get in. And it reads the public site the way a scanner would, looking for leaked keys.
They paid. They cannot get in.
Stripe has the customer. Your users table does not. Or the reverse: access is on, and the subscription is not.
The live key shipped in the bundle
sk_live, a Supabase service_role JWT, or an LLM key sitting in a public JavaScript file.
How a check actually runs
01
Prove the domain is yours
Add a DNS TXT record or a meta tag. Scheduled checks do not run against a site you have not claimed.
02
Describe the journey in English
“Sign up with the test user, then open pricing and click the checkout button.” We compile that once.
03
Replay it without the model
The saved steps run on a schedule in a headless browser. The LLM is not in the daily loop.
04
Get the failure, not a vibe
A screenshot, the step that broke, and a prompt you can paste back into Lovable, Bolt, Replit, or Cursor.
What it will not do
Journeys stop before captchas, email confirmation links, OAuth popups, and real payments. The public checker only reads what a browser already downloads: the page, its scripts, two well-known paths, checkout links, and response headers. It does not log in, fuzz, or attack.
- Free $0
- 1 app · 1 journeys · Daily
- Starter $19
- 1 app · 5 journeys · Daily
- Pro $49
- 3 app · 15 journeys · Every 6 hours
- Agency $99
- 15 app · 50 journeys · Every 6 hours