The Netlify site and your domain
Netlify keeps the site up and the certificate renewed; the domain is yours to renew and its DNS yours to keep pointed at Netlify.
Monitoring for Bolt apps
Your Bolt app is live. Who tells you when it isn't?
Bolt builds the front end in minutes and connects Supabase, Stripe and a mail provider on request. Each connection is a thing that can break, on a site nobody is watching.
Where it runs: Bolt apps deploy to Netlify or a host you connect, often with Supabase behind them.
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.
Supabase
Auth, database, edge functions: a paused project or a spent quota leaves a page that loads and a product that does not.
The connected services
Stripe, Resend, an AI model: keys that rotate, quotas that run out, outages of their own.
Edge functions after a redeploy
A function that fails to deploy or throws on a missing secret answers 500 to the page that calls it.
The page that matters
The landing page loads while the checkout does not. Monitor the page that earns the money.
The email problem
A Bolt app sends mail from a Supabase edge function or a serverless function with a Resend or SendGrid key, from a domain whose records you added once. The failure is silent by design: the function returns success to the page whether or not the provider accepted the message, and the provider's own failures (revoked key, spent quota, a from-address on a domain whose DKIM changed) are reported nowhere the app looks. ServerInspector checks the site, the functions and the domain from outside; on Pro an API test calls the function that sends and tells you when it stops answering 2xx.
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 Supabase REST endpoint and any edge function URL your app depends on as monitors with an expected status.
- 5
On Pro, an API test for the function that sends mail, every fifteen minutes.
Free plan: 10 monitors or domains, 5-minute checks, commercial use welcome, no card.