Uptime Kuma hosting: your monitors and status page, in one click
Pick Uptime Kuma from the app catalog, name it, deploy. It runs from the project's official image with its data kept safe, answers at https://name.fadehost.app, and pings your servers, sites and bots from a machine that is not yours, which is the point of a monitor.
What you get
- The official Uptime Kuma image, updated with a click on Redeploy.
- An https address the moment it starts; set your admin account on the first visit.
- Monitors for HTTP, TCP ports, ping, DNS, Docker, game servers and keywords; a public status page per project.
- Notifications to Discord, Telegram, Slack, email, ntfy and ninety more.
- Its database and uploads live under /data, so a redeploy or a restart keeps everything.
Sizing
Uptime Kuma is a small Node.js app. The free tier's 256 MB runs a few dozen monitors; a hundred monitors polling every minute is more comfortable on Starter with 1 GB. On the free tier the web address sleeps when nobody looks at it and wakes on the next visit; the monitors keep running, because the process itself never sleeps.
Monitoring your own servers
A game server's port, a bot's web address or a database's public endpoint are all monitors like any other. Servers, bots and databases on your private network are reachable by their private names when the monitor runs in the same region and the network is on.
Frequently asked questions
Is it the real Uptime Kuma?
Yes, the official image from the project, unmodified. Updates come from the project; press Redeploy to pull the latest version.
Does the free tier sleep?
The address does, when nobody has opened it for a while; the app and its monitors keep running around the clock on every tier. A paid tier keeps the address awake at no extra cost.
Where is my data?
Under /data in the app's container, on a volume that survives redeploys and restarts, with daily backups on paid tiers and a one-click restore.
Can I use my own domain?
Yes. Point a CNAME at the app from its page and the status page answers on your domain with a certificate.
What happens on a deploy?
The repository is cloned at your branch, dependencies install, the build runs when there is one, the app starts. With auto-deploy on, every push does the same. The live console shows each step; a failed one is explained in plain words.