StillOnline?

Hosted status page without self-hosting Uptime Kuma

Uptime Kuma is excellent when you want full control on your VPS. Many indie founders never ship it — Docker, updates, backups, and another box to patch sit in the backlog next to the actual product.

StillOnline is the opposite wedge: hosted HTTP checks, a public status page in minutes, and Telegram owner alerts via the StillOnline bot (no BotFather). You trade VPS maintenance for a customer link you can share the same day you add a health route.

Honest comparison: StillOnline vs Uptime Kuma.

Quick answer

Uptime Kuma is free software on your VPS; StillOnline is hosted HTTP checks plus a public status page in about five minutes. StillOnline does not offer self-host — share stillonline.tech/.../s/... from docs or during incidents. Owner alerts use the official StillOnline bot on Telegram, not a DIY webhook.

When Kuma wins

Self-hosting pays off when you already operate the infrastructure and need protocols beyond HTTP.

  • You already run home lab Docker 24/7.
  • You need dozens of protocols (SNMP, game servers) beyond HTTP.
  • Data must stay on your metal.

When hosted StillOnline wins

Most indie SaaS teams deploy on PaaS and want a trust link before they want another server.

  • You ship on Vercel / Railway / Fly and do not want another server.
  • You need a customer-facing /s/... link today, not after a weekend install.
  • You want Google subscriber emails on the public page without building it.
  • You want MCP/API for agents on Pro — MCP post.

Time math (realistic)

Calendar time matters more than license cost at pre-revenue stage.

TaskSelf-host KumaStillOnline hosted
First status linkHours–days (VM, compose, TLS)~5 min (quickstart)
Mobile alertConfigure notification channelConnect Telegram → StillOnline bot (guide)
Public page for customersExtra config / reverse proxyDefault on project create

Migration path

You can run both temporarily; customers should see one canonical URL.

  1. List production URLs you care about.
  2. Create a StillOnline project per product (or one on Free).
  3. Add checks; share the new status URL with clients in docs or support.
  4. Keep Kuma internal if you want — or decommission when you are ready.

StillOnline does not fix your app — it gives accurate external check results plus customer communication. Deep diagnosis stays in logs. Need only a page? Public status page guide.

FAQ

How do I move monitors from Uptime Kuma to StillOnline?

Copy each production HTTPS URL into a StillOnline check manually — there is no automatic Kuma importer today. Create a project, add the health URL, and share the new /s/... link. Health check quickstart.

Can I self-host StillOnline like Uptime Kuma?

No. StillOnline is hosted SaaS on stillonline.tech; self-host is not part of the product. You trade VPS maintenance for a customer-facing status link the same day.

How does StillOnline pricing compare to free Kuma?

Kuma costs $0 plus your VPS time and patches. StillOnline Free is one project, one URL; Pro adds more checks, private visibility, and API — Pricing.

How do StillOnline Telegram alerts differ from Kuma notifications?

Kuma uses whatever notification channel you configure on your server. StillOnline links one official StillOnline bot from settings — Telegram guide. On Free, pick one owner channel.

Should I keep Kuma internally after adding StillOnline for customers?

Many teams keep Kuma for a home lab or internal hosts and StillOnline for the public customer link. Avoid two different “official” status URLs for the same product.

What StillOnline URL do I give B2B clients instead of my Kuma page?

Share stillonline.tech/s/demo in docs, onboarding, or contracts — hosted by StillOnline, not your VPS hostname — public status page guide.

Further reading