The domain
Vercel renews the certificate; nobody renews the domain but you. When it lapses, the certificate is the least of it.
Monitoring for v0 apps
Your v0 app is live. Who tells you when it isn't?
v0 designs the app and Vercel runs it. Vercel keeps the edge up; your domain, your database, your auth provider and the APIs your routes call are yours, and they break on their own schedule.
Where it runs: v0 apps deploy to Vercel, usually with a database and auth provider connected.
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.
Server routes and their dependencies
A route handler that calls the database, an AI model or a mail provider fails when they do; the static parts of the page keep rendering.
Environment variables
A variable changed in the Vercel dashboard, or set on preview and forgotten on production.
The auth provider
Clerk, Auth0, Supabase Auth: an outside service between your users and your app.
Cron routes
Vercel cron calls a route; if the route fails, the job it did stops, silently.
The email problem
v0 apps send mail from a route handler or a cron route through Resend or a similar provider, with a key in an environment variable and a domain verified once. The route returns whatever the agent wrote it to return; a rejected send is easy to swallow. The provider's key gets rotated, the domain's DNS changes, the cron route errors: the page still loads. ServerInspector checks the site and the routes from outside on a schedule, tracks the domain, and on Pro runs the sending route as an API test so a silent failure is an alert.
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 server routes that matter (the API your pages call, the cron route) as monitors with an expected status.
- 5
On Pro, an API test for the route that sends mail, with a test flag, every fifteen minutes.
Free plan: 10 monitors or domains, 5-minute checks, commercial use welcome, no card.