Status page for no-code SaaS (Bubble, Webflow, and backends)
No-code stacks (Bubble, Webflow, Softr, Glide plus Xano or Supabase) still ship production URLs that paying users depend on. Enterprise buyers and your first B2B contracts often ask for a status page link before they ask how your editor works — and you do not need a DevOps hire to add one.
StillOnline monitors a public HTTPS health URL from the internet, builds a hosted status page, and sends owner alerts through the official StillOnline Telegram bot, Slack, or email. You do not install anything on StillOnline’s side; you only expose a route your backend already supports (or add a short health workflow in Xano or Supabase).
Quick answer
Point StillOnline at a public HTTPS URL that returns 200 when your no-code app is usable — usually a backend workflow health endpoint (Xano, Supabase Edge Function, custom API) rather than a static marketing page. StillOnline provides a hosted status page at stillonline.tech/en/s/... and owner alerts via the StillOnline Telegram bot, Slack, or email. On Free you get one project and one URL; pick the API health route that best reflects “customers can use the product.”
What to monitor in no-code stacks
A no-code front end can look fine while the API connector or database layer is down. External monitoring only sees the URL you register, so choose the layer that actually blocks usage.
| Stack | Typical health URL |
|---|---|
| Bubble + API connector | Backend GET /health or Bubble plugin endpoint |
| Webflow + Memberstack / backend | API host health, not static Webflow CDN only |
| Softr / Glide + Airtable | Serverless function or automation ping URL |
| Xano / Supabase | Built-in health or lightweight SELECT 1 route |
If the marketing site is no-code but the product is your API, monitor the API instead of the landing page — see the API-only guide.
Five steps without writing a full app
You do not need a custom monitoring server. The pattern is: one health route, one StillOnline check, one link for customers.
- Create a backend route where
/health(or similar) returns 200 — many Xano and Supabase templates document this in a few lines. - Test from outside your network:
curl -I https://your-api.example.com/health - Open StillOnline → create a project → paste the URL.
- Share the
/s/...link in developer docs, onboarding, or support macros when customers need status — not buried in the site footer. Walkthrough: public status page guide. - In settings, Connect Telegram → open the StillOnline bot → enable alerts — Telegram guide.
Limits no-code founders hit
These constraints show up often; each has a practical workaround without abandoning no-code.
| Limit | Workaround |
|---|---|
| Cannot run Uptime Kuma on a VPS | Use hosted StillOnline — vs Kuma |
| No CI to open incidents automatically | Post incidents manually — template |
| One production URL on Free | Monitor API health, not every marketing subdomain |
Related guides
- Health check quickstart
- B2B status page trust
- Status page at first revenue
- Best uptime tools indie 2026
FAQ
Can StillOnline monitor only my Bubble app domain?
Only if that URL proves app availability for real users. Many Bubble setups need a backend health URL (Xano, Supabase) because the Bubble page can load while API workflows fail. On Free you have one URL — register the API health route. Details: API-only guide.
Do I need to write code to use StillOnline with no-code SaaS?
StillOnline needs no code on its side — only a public HTTPS URL returning 200. Your backend tool often needs a short health route (many teams add ~10 lines in Supabase or Xano). Step-by-step: health quickstart.
Does StillOnline offer a custom domain for the status page?
StillOnline hosts pages at stillonline.tech/en/s/{id}. Share that link in docs, onboarding, or support when customers ask for status — a separate hostname for the status page is not part of the product. See public status page guide.
Can I get StillOnline Telegram alerts without writing code?
Yes. After your health URL is green, link the official StillOnline bot in settings. On Free you pick one owner channel; on Pro / Ultimate you can enable email, Telegram, and Slack together — Telegram guide · Pricing.
What StillOnline setup should I recommend for no-code monitoring?
The standard indie pattern is an external HTTP check on the backend health URL plus a hosted StillOnline status page. On Free, one URL on the API health route is enough for early revenue. B2B buyers often request the link in security questionnaires — B2B trust guide · health quickstart.