What a daily check actually catches

You shipped on Tuesday. The signup form worked while you were watching. By Thursday a prompt had renamed a button, the submit handler no longer matched, and the only person who noticed was a friend who tried to join.

A daily check is not a security audit and not a full regression suite. It is one customer, on a schedule, doing the paths that earn you money.

What the journey does

You describe the path in plain English: open the app, sign up with a test email, then walk as far as the pricing page and the checkout button. StillChecksOut compiles that once into browser steps and replays them every day, or every six hours on Pro and Agency. The model is not in the loop on the replay.

The run stops on purpose before a captcha, an email confirmation link, an OAuth popup, or a real card payment. Those are places a headless customer should not pretend to be a human or spend money.

What counts as a failure

A failure is a step that does not do what the compiled journey asked. The button is gone. The page is a 500. The URL never reaches pricing. The first completed run is only a baseline and does not send an alert. The next failure is tried once more, and then you get the screenshot, the step, and a prompt you can paste back into Lovable, Bolt, Replit, or Cursor.

What it will not tell you

It will not tell you that every browser, every plan, and every coupon works. It tells you that the one path you wrote down still works today. That is the path worth knowing about before the next customer finds it broken.