The route that returns 500 after a refactor
An agent-driven refactor touches thirty files. The tests that exist pass. The one route without a test breaks, and it is the one the checkout uses.
Monitoring for Windsurf apps
Your Windsurf app is live. Who tells you when it isn't?
Windsurf's Cascade will carry a feature from a sentence to a deploy. The deploy is where its involvement ends and yours begins, and that is the part nobody is watching.
Where it runs: you deploy what Windsurf wrote: Vercel, Netlify, Railway, Render, a VPS.
Paste your app's address. We propose the checks, you say yes:
We read the page once and propose the checks it needs. Nothing is created until you say so.
Or just check it once, no account:
What breaks after launch
None of these show up in the editor. All of them show up to your users first.
The certificate on a self-managed host
Renewal was set up once. It fails when the DNS challenge stops resolving or the cron stops running, and the browser warning is how you hear.
The domain
Registered fast, forgotten faster. Expiry reminders from registrars go to an inbox nobody reads.
The APIs the app calls
AI models, payments, maps, mail: outside services with outages and quotas of their own.
The background worker
The queue that stopped is invisible from the page; the emails and jobs it ran are the symptom.
The email problem
An app built with Windsurf sends transactional mail through a provider the agent connected. The send is a network call from a route or a job with a key and a from-domain; the ways it fails are the ways any outside call fails, plus the ways DNS fails: revoked key, spent quota, missing environment variable on the new host, SPF or DKIM records overwritten. The app reports success and the user waits for a mail that never comes. ServerInspector monitors the app, the API and the domain from outside on a schedule; on Pro an API test calls the sending endpoint and asserts on what came back, so a silent failure becomes an alert within fifteen minutes.
How to set it up
Nothing is installed in the app. Monitoring happens from outside, the way your users reach it.
- 1
Type your app's address into the free check above. It tells you in twenty seconds whether the site answers, how fast, whether the certificate and domain are in order, and which security headers are missing.
- 2
Create a free account and add the same address as a monitor. It is checked every five minutes (every minute on Pro), and you get an email when it stops answering and another when it is back.
- 3
Add your custom domain under Domains. Expiry is tracked and you are reminded 30, 14, 7 and 1 day before renewal.
- 4
Add the API's health endpoint as a monitor and, on Pro, an API test for the endpoint that sends mail.
- 5
Call the deploy marker endpoint from your pipeline so each Cascade-driven deploy is on the chart and alerts are held for the restart.
Free plan: 10 monitors or domains, 5-minute checks, commercial use welcome, no card.