Flow checks
Visit, assert text, click, fill, and fail the run if the page throws JavaScript errors. Built for the three screens that matter: signup, login, checkout.
Silent-break monitor
AI coding tools ship fast and break the flows that make you money. BreakAlarm re-walks signup, login, and checkout — then emails you a screenshot and a fix prompt before a customer has to.
One app. Daily checks. No card.
Free check · no account
We open the URL once, record the status, and keep a screenshot if the browser can launch. Your email is added to our onboarding list.
Breaks BreakAlarm catches — examples, not our status
01
Add the URL, then describe signup, login, or checkout as a short list of steps: open this page, expect this text, click this button, fill this field.
02
Free is daily. Starter is hourly, plus a deploy hook you can call from Vercel, Netlify, or GitHub Actions. Pro checks every 15 minutes.
03
When a check fails — and when it recovers — we email you. The message includes the evidence and a plain-English prompt you can paste into Cursor, Lovable, Bolt, or v0.
Built for founders who shipped with an AI tool and now live in fear of the next prompt. Not a 40-product observability suite.
Visit, assert text, click, fill, and fail the run if the page throws JavaScript errors. Built for the three screens that matter: signup, login, checkout.
A list of URLs that must answer. Marketing page, /login, /api/health. One 500 is enough to wake you up.
Hit an endpoint and expect a status code, plus an optional snippet in the body. Useful for the route your Stripe webhook actually lands on.
Starter and Pro get a secret URL. Call it at the end of a deploy so you find out in the same minute the AI tool shipped the bug.
Every failure writes a paste-ready prompt: what broke, the evidence, and what “done” looks like. If an AI Gateway key is set, we tighten the wording.
Pro reads a restricted Stripe key. We flag failed charges, events Stripe still hasn’t delivered to your webhook, and customers who paid but your access check says no.
Limits are enforced on the server. If you downgrade, extra apps stay in the dashboard but stop being walked.
$0/mo
One app, checked once a day. Enough to know yesterday’s deploy didn’t quietly kill signup.
$19/mo
Three apps, hourly walks, and a URL you can hit from Vercel or GitHub Actions the moment a deploy finishes.
$79/mo
Ten apps, every 15 minutes, plus a Stripe check for failed payments, undelivered webhooks, and paid-but-locked-out customers.
Subscriptions are billed through Stripe. Tax is not collected in this checkout until you turn on Stripe Tax and add a registration. If you sell to the US or EU, set that up before you go live.
No. Free runs once a day, Starter once an hour, Pro every 15 minutes. A deploy hook runs once per deploy, not in a loop. Flow checks are a handful of page loads, not a load test.
Only if you are on Pro and you paste one. We want a restricted key (rk_) with read access to charges and events. It is encrypted with AES-256-GCM before it hits the database. We never charge cards with it.
Start with uptime and an API health check. For flows, use a throwaway account and put those credentials in the fill steps. Don’t use your own production password.
Yes. BreakAlarm doesn’t care which tool wrote the app. It watches the live URL. The fix prompt is plain text, so it pastes into whichever editor you used to ship the bug.
You decide. A missing “Pay now” button, a 500 on /api/checkout, a console exception on the signup page, a webhook Stripe could not deliver. We alert when a check changes from passing to failing, and again when it recovers, so you don’t get the same email every 15 minutes.
Yes. The form on this page runs one check against a public URL you are allowed to test. For a schedule, screenshots of later failures, and alerts, create a free account.