A headless Chromium browser opens your URL, finds the signup form, submits a fresh disposable email, waits for a verification email if one is sent, logs in, walks to checkout, and stops before any payment. It then opens a protected page as that non-paying account.
It never types a card number and never clicks Pay. It does create a real account on your app using a throwaway address, the same way a visitor would. Delete those test users on your side if your database keeps them.
No. The landing page runs one check without an account. Monitoring, deploy hooks, and the Stripe watchdog need a SignupCanary account.
Auto-detect is best-effort. On a saved app you can record the flow as a short step list with CSS selectors for the email field, password field, and submit button.
Every plan is checked once a day. Pro and Agency also run when a deploy hook fires, and the daily run includes them if the public page changed. Each check opens a real browser, walks signup through checkout, and stops before payment.
On paid plans you point a Stripe webhook at SignupCanary. We alert you if expected events stop arriving or if Stripe reports a failed payment event. It does not replace your own webhook handler.
Newsletter mail includes an unsubscribe link that takes effect immediately. The account welcome email is not a newsletter. Check alerts are separate and can be turned off in settings.
The free check includes a prompt you can paste into Lovable, Cursor, Claude Code, Replit, or Bolt. Saved prompts on monitored apps are part of Pro and Agency.