Your custom domain
Bubble serves the app; the domain is yours. It expires, its DNS gets edited during some other change, and the certificate Bubble issues for it depends on the records pointing where Bubble expects.
Monitoring for Bubble apps
Your Bubble app is live. Who tells you when it isn't?
Bubble runs your app, your database and your workflows. It does not run your domain, your email provider or the APIs you call from workflows, and those are what break.
Where it runs: Bubble hosts the app on *.bubbleapps.io or your custom domain, with its own database and workflows.
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.
API Connector calls
Every workflow that calls an outside API (a payment provider, a maps service, an AI model) trusts that API to be up and the key to be valid. When it is not, the workflow fails and the user sees a spinner.
Scheduled workflows and capacity
A backend workflow that runs on a schedule fails quietly when the app hits its capacity or the workflow errors; nothing on the page changes.
The one page that matters
The home page can load while the page users actually pay for, the one with the heavy workflow, times out. Monitor the page that earns the money, not only the front door.
Email from workflows
Bubble's built-in mail is for development; production apps wire SendGrid, Postmark or similar. When that stops, your app keeps saying 'sent'.
The email problem
A Bubble app sends mail from workflows: the welcome message, the receipt, the reminder a user set. That mail leaves through a provider you connected with an API key, from a domain whose SPF and DKIM records you added by hand. Any of those can change without the app noticing: the key is rotated in the provider's dashboard, the monthly quota is spent, a DNS record is overwritten during a redesign. The workflow reports success because the request was accepted; the message never lands. ServerInspector watches the pieces that can be watched from outside: the page, the domain, the certificate, and any endpoint your workflows call. On Pro, an API test can call a backend workflow endpoint on a schedule and tell you when it stops answering the way it did.
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 page that matters most (checkout, dashboard, the form that generates leads) as its own monitor, with a keyword check for a word that only appears when the page really rendered.
- 5
For each outside API your workflows depend on, add its endpoint as a monitor or, on Pro, an API test with the same call your workflow makes.
Free plan: 10 monitors or domains, 5-minute checks, commercial use welcome, no card.