There is no ops person
The agent that built the app is not running it. Nothing watches the server, the domain, the certificate or the queue, because nobody was ever assigned to.
Monitoring for vibe-coded apps
Your app is live. Who is watching it?
You built it by describing it. It works, it has users, and there is nobody on call. Vibe coding gets an app to launch in a day; this is what happens on day two, and how to be the first to know.
Where it runs: wherever the tool put it: an app builder's platform, Vercel, a VPS the agent configured.
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.
Everything outside the code
DNS, certificates, domain renewals, environment variables, provider keys and quotas: none of it is in the repository, none of it is in a pull request, all of it can fail.
Every service the agent connected
Auth, database, payments, mail, AI: each is an outside dependency with its own outages and its own key that rotates.
The deploy that did not come back
Shipping ten times a day is the point. Each deploy is a chance for the site to go down for as long as it takes someone to notice.
The quiet failures
Mail that stops going out, jobs that stop running, a webhook that stops answering. The page loads; the product does not.
The email problem
Whatever tool built the app, it sends mail through a provider with a key and a domain, and the failures are the same: the key revoked or rotated, the quota spent, the DNS records changed, the function or job that sends not running after a deploy. The app says 'sent'; the user's inbox says nothing. No monitoring tool reads inboxes. What ServerInspector does is watch every piece of that path that can be watched from outside, on a schedule, and tell you the moment one of them changes: the site, the API, the domain and its expiry, the certificate, and on Pro the sending endpoint itself as an API test. Then it tells you when it is back.
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 or the function endpoints your app depends on as monitors. Pick the page that earns money as its own monitor.
- 5
On Pro: an API test for the endpoint that sends mail, and a deploy marker call from wherever you deploy.
Free plan: 10 monitors or domains, 5-minute checks, commercial use welcome, no card.