Uptime Kuma Hosting on Its Own VPS

Uptime Kuma is an open-source (MIT) monitoring tool: it checks your sites and services on a schedule, alerts you when something goes down and publishes status pages for your users. Choose it with a plan, pay, and we build the VPS (KVM, NVMe, Ubuntu 24.04 LTS) and install Uptime Kuma, currently 2.5.8, in about three minutes after boot. You get:

• An HTTPS address like yourname-x7k2.devoster.app with a Let's Encrypt certificate.
• Your admin account already created. Log in as admin with a generated password shown in the Devoster dashboard, where you can also reset it. Uptime Kuma's setup screen, which creates the first admin, is never left open to the internet.
• Managed updates. We test new Uptime Kuma versions and apply them in a nightly window you choose, or when you press Update now, with a VPS snapshot first and an automatic rollback if it doesn't come back healthy. Auto-update can be switched off.
• Dashboard controls to open the app, restart, stop or start it, read its logs and connect your own domain.

The app is free; you pay only the VPS plan, with 10% off yearly. The server comes with full root, free nightly backups kept 3 days plus one snapshot, a dedicated IPv4 and DDoS protection. See the other apps that install this way on the One-Click Apps page.

A monitor that runs on the same machine as the site it watches goes down with it, and then nobody gets the alert. That is the main reason to give Uptime Kuma a small server of its own instead of adding it to an existing one.

Take the idea one step further and think about shared failure:

• Different server: the minimum. A crashed web server or a full disk no longer silences your alerts.
• Different provider or region: better. If your sites are hosted elsewhere, a monitor in Utah, USA sees them the way an outside visitor does. If your sites are also on Devoster, a problem that affects the whole datacenter would affect both, so add an external check from somewhere else for the alerts that matter most.
• One vantage point: every check runs from this one server in the US. Response times reflect that location, and a network problem between Utah and your host can look like an outage. Confirm before you wake someone up.

Uptime Kuma lets you require several failed checks in a row before alerting, which filters most of those blips.

Uptime Kuma checks HTTP and HTTPS endpoints (with keyword or JSON-query matching on the response), TCP ports, ping, DNS records, WebSocket endpoints and push monitors that your own cron jobs call, at intervals as short as 20 seconds. HTTPS monitors also report certificate details, so you can be warned before a certificate expires.

Alerts go to more than 90 notification services. The common ones need nothing extra on a Devoster VPS:

• Work out of the box: Telegram, Slack, Discord, Microsoft Teams, Pushover, ntfy, Gotify and plain webhooks, because they all talk HTTPS.
• Email needs a provider: outbound mail ports are blocked by default on Devoster VPS plans. To get alerts by email, use an external email provider; its SMTP submission port can be opened on request.

Set up at least two channels for important monitors, for example Telegram plus email, so one broken integration doesn't hide an outage.

Uptime Kuma can publish several status pages, each showing the monitors you choose, with incident notes and a history bar. To put one on status.example.com:

• In the Devoster dashboard, add status.example.com as the app's domain and create a CNAME record pointing at your devoster.app name. (A root domain uses an A record to the server IP instead.) The panel verifies DNS and issues the certificate automatically.
• In Uptime Kuma, open the status page's settings and add the same domain, so visitors to it land on that status page.

Keep the status page on a different provider from the sites it reports on when you can. A status page that goes down with your product can't tell anyone what is happening. Turn on Uptime Kuma's two-factor login too, since the admin login lives on the same address.

Very little. Uptime Kuma uses around 120 MB of RAM at idle, and each check is a small network request. What grows over time is its database of check results, which depends on how many monitors you run, how often they check and how long you keep history (adjustable in Uptime Kuma's settings).

You can upgrade from the panel later. If you are not sure, start on Nano.

We install Uptime Kuma and keep it updated. The VPS is still an unmanaged server: you have full root, and its security and what you add to it are your responsibility. We don't provide support for configuring monitors; Uptime Kuma's wiki covers that. Our VPS hardening checklist is a good first hour for any server with root access.

Nightly backups (3 days) and your snapshot slot cover the whole VPS, Uptime Kuma's database included. For a monitor you depend on, also keep a copy of its data directory off the server.