Delivered and gone
The task is closed, the session ended, the environment it used is torn down. The thing it deployed is still running, with nobody assigned to it.
Monitoring for Devin apps
Your Devin app is live. Who tells you when it isn't?
Devin takes a ticket and returns a pull request, sometimes a deploy. It works like a contractor: the work is delivered and the contractor leaves. Somebody still has to watch the building.
Where it runs: you deploy what Devin delivered: a cloud host, Kubernetes, a container platform, 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.
Configuration outside the repository
Certificates, DNS, environment variables, cron: Devin may have set them up in a session and left no record in the code.
Integrations with keys
Each service it connected has a key that rotates, a quota that runs out and an uptime that is not yours.
The domain
Expiry is a calendar problem, and the calendar was never created.
Scheduled work
Jobs and workers fail quietly; the page keeps loading.
The email problem
Mail from an app Devin built goes through whatever provider the task specified, wired in with a key and a domain. Once the session ends, nothing in the delivery watches that path: the key can be revoked, the quota spent, the DNS records changed by another task, the worker stopped. The route answers, the mail does not arrive. ServerInspector gives the delivered app an owner in the only way that scales: the site, its API and its domain checked on a schedule from outside, an API test that exercises the sending path, and a deploy marker call that Devin can add to the pipeline so every future delivery is on the chart.
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
Include 'add a health endpoint and monitor it in ServerInspector' in the ticket; the API takes a token and the agent can create the monitors itself.
- 5
Have the pipeline call the deploy marker endpoint so each delivery is visible and its restart window is silenced.
Free plan: 10 monitors or domains, 5-minute checks, commercial use welcome, no card.