The edit was somewhere else
You asked the model to restyle the settings page. Signup, checkout, or the save button three files away is what actually broke.
Canary in the coal mine
ShipCanary checks signup, checkout, and the other flows your last AI edit did not touch, then warns you within minutes of a deploy — before your users do.
You asked the model to restyle the settings page. Signup, checkout, or the save button three files away is what actually broke.
You are logged in, the data is already there, and the happy path you remember is fine. A new user is the one who finds the hole.
The deploy was Friday. The first email from a customer is days later, with no trace of which prompt did it.
Paste a URL. No account. You get a public report of load, console errors, broken links, headers, and leaked-looking keys.
Three to five sentences. Optional test credentials, stored encrypted, used only when that flow runs.
Vercel, GitHub, or a one-line POST. A failure email includes the step, the error, and a fix prompt.
Example failure email
Signup failed on Northwind
Step 4 expected the dashboard to show “Welcome”. The page said “Something went wrong”, and the console logged signup failed: welcome panel missing. The fix prompt below is ready to paste back into the editor that shipped the change.
Limits are enforced on the server. A webhook from a Free account does not run, and a Starter account cannot quietly grow a second app.
The public check, plus one watched flow.
$0/mo
For one product you ship several times a week.
$19/mo
A few apps, and the flows that actually make money.
$49/mo
Paid plans use Stripe Checkout and the customer portal. Create an account to watch flows continuously.
The public site only. It loads the homepage, follows a handful of same-site links, reads security headers, and scans shipped JavaScript for strings that look like live secrets. It does not log in and it does not crawl the whole internet.
A sentence a user would recognize. “Sign up with a new email, then confirm the dashboard shows Welcome.” ShipCanary turns that into browser steps, stops if the sentence is not true, and keeps the screenshot.
No. If a flow needs a test account, you can store that email and password. They are encrypted at rest and never shown back in full. Leave them blank and the checker will invent a throwaway email when the page asks for one.
As soon as your host POSTs the deploy hook. Vercel deployment-succeeded, GitHub deployment_status or push, or any script that can curl a URL. There is also a daily run, and a Run now button when you do not want to wait.
An email with the flow, the step that died, the console or network error, and a fix prompt you can paste into Cursor, Lovable, Bolt, or v0. The screenshot stays on the run page.
Yes. Starter and Pro are monthly Stripe subscriptions. The customer portal is where you change card, switch plan, or cancel. Free never asks for a card.