Uptime Kuma hosting Watch your sites from a server that stays on.
Uptime Kuma hosting on Selfhost.dev runs Uptime Kuma on a dedicated server we provision, secure and run, with HTTPS and its data on a persistent volume. Open it as soon as it is up and create the admin account: the first person to do so owns it.
The database type is preset, so the first page anyone sees is the account setup, and it is yours if you open it first.
- Uptime Kuma2.5.6, pinned
- databaseSQLite, preset
- dataa persistent volume
- HTTPSon from the start
- adminthe first visitor; open it first
What is Uptime Kuma hosting?
What it is
Uptime Kuma is an open source monitoring tool. It checks websites, APIs and servers over HTTP, TCP, ping, DNS and more, sends an alert when one goes down and publishes status pages. Uptime Kuma hosting runs it on a server that stays on, apart from the laptop you would otherwise run it on.
Who it is for
Developers and small teams who want to know the moment a site, an API or a server stops answering, and a status page to show for it.
When to use it
When you want monitoring that keeps running when your own machine sleeps, without setting up Docker, HTTPS and a volume by hand.
Uptime Kuma Docker, set up for you
The one click runs one container, the official image pinned to 2.5.6, with its database type preset to SQLite on a persistent volume. These are the settings that matter.
The stack, end to end
You and your status page visitors
TLS and routing
Uptime Kuma 2.5.6
SQLite
Monitors and history
| What the template sets | Why |
|---|---|
louislam/uptime-kuma:2.5.6, an exact tag | The image changes only when we re-pin it, never on a restart |
The full image, not -slim | The slim image leaves out the Chromium that real-browser monitors use |
UPTIME_KUMA_DB_TYPE=sqlite | Without it, Uptime Kuma 2 opens on a database picker that would let the first visitor point it at any database host |
A persistent volume for /app/data | The database and everything else Uptime Kuma keeps survive a restart |
| HTTPS through our proxy, no host port | Port 3001 stays inside the container |
Uptime Kuma hosting requirements
Uptime Kuma hosting requirements are light. The platform weighs Uptime Kuma as a light app with no memory floor, so it starts on the default 4 GB server, x86 or ARM, with room for other apps beside it.
What it needs
- Uptime Kuma
- 2.5.6, pinned
- Database
- SQLite, on the server volume
- Memory and CPU
- 4 GB, the platform default; x86 or ARM
- Login
- None set at deploy; the first visitor creates the admin
- Ports
- 443 over HTTPS; 3001 stays inside the container
How to deploy Uptime Kuma in 3 steps
One click, then claim it before anyone else does.
-
Choose Uptime Kuma and a 4 GB server
Launch opens the Uptime Kuma template in the console. It asks for a name and a server, nothing else: there is no login to set.
-
Open it the moment it runs do it now
The first person to open the address creates the only admin account, and the setup screen closes after that. Open it from the console as soon as it reads Running, before you share the link.
-
Add monitors, then two settings
Add your first monitor and a notification channel. In Settings, set Primary Base URL so links in notifications point here, and turn on Trust Proxy under Reverse Proxy so visitor addresses are logged correctly.
What Uptime Kuma hosting costs
Uptime Kuma hosting here is one server line. Uptime Kuma is free under the MIT licence, the template adds no fee and monitors cost nothing extra. A European 4 GB server is $0.02/hr, about $15 to $16 a month, paid by the hour from prepaid credits.
| Item | Cost |
|---|---|
| Uptime Kuma | $0 |
| Monitors and status pages | $0, limited only by the server size |
| Bandwidth | $0, traffic is included in the server price |
| Optional daily backups | +20% of the server price |
| Server | RAM, cores, disk | Where | Rate | About a month |
|---|---|---|---|---|
cx23 (recommended) | 4 GB, 2 cores, 40 GB | Europe | $0.02/hr | $15.18 |
cax11 (ARM) | 4 GB, 2 cores, 40 GB | Europe | $0.02/hr | $16.35 |
cpx21 | 4 GB, 3 cores, 80 GB | US | $0.12/hr | $87.75 |
cpx22 | 4 GB, 2 cores, 80 GB | Singapore | $0.10/hr | $72.56 |
Monthly figures assume 730 hours.
If your balance reaches zero
With a card on file or a past top-up, Uptime Kuma keeps running for 5 days after your balance reaches zero. Then it is stopped and kept for 24 hours before it is deleted; a top-up in that time restarts it. We email you when the balance reaches zero and again when it stops. Welcome-credit-only servers are deleted at zero.
Price another size or region in the calculator, no signup.
What we run and what you set up
Uptime Kuma, its volume and HTTPS are ours to run. The admin account, the monitors and two settings are yours.
On the server (we set it up)
- Uptime Kuma, HTTPS and the data volume
- The health check
- Your HTTPS address, and a custom domain if you add one
What you set up
- The admin account, the moment it is up
- Monitors and notification channels
- Primary Base URL and Trust Proxy in Settings
Four checks on every Uptime Kuma server
- No database picker left open. The database type is preset, so the first page anyone sees is the account setup, not a form that could point it elsewhere.
- A deploy is never reported done until Uptime Kuma is healthy. Its own health check has to pass first.
- Your Uptime Kuma version stays put. The image is an exact tag; a restart or redeploy brings back the same build.
- A warning in the console. It tells you to open Uptime Kuma before you share the link, and what to do if someone got there first.
The console allows up to ten minutes for the Uptime Kuma template after the server is ready; first-time server provisioning adds time.
Uptime Kuma hosting limitations
- The first visitor owns it. The setup screen goes to whoever opens the address first, and two people setting it up at the same moment can both succeed. Open it as soon as it runs; if someone else got there first, delete the app and create it again.
- One admin, no team accounts. Uptime Kuma has a single admin and no user management.
- No in-app backup. Uptime Kuma 2 has no backup or export, so the server volume is the only copy. Turn on daily backups if your history matters.
- It watches from one place. Every check runs from this one server, so an outage of the server itself is one Uptime Kuma cannot report.
Nothing here in your way? Open it the moment it runs and it is yours.
Launch Uptime KumaUptime Kuma backup and restore
Uptime Kuma 2 has no backup or export of its own, so its data volume, with the SQLite database inside, is the only copy of your monitors, history and settings. The server can take an optional daily image of it; to copy the volume out, ask us for container access over SSH.
| Method | What it covers | Where it lives |
|---|---|---|
| Daily server backup (optional, +20%) | Uptime Kuma and its whole data volume; the last 7 kept | With the server; deleted with it |
A copy of uptime-kuma-data | Monitors, history, status pages and settings | Your storage, via container access over SSH, granted on request |
Monitoring a lot of sites?
Tell us roughly how many monitors you plan and how often they check. We send back the size we would pick and what it costs a month.
Frequently asked questions
Is Uptime Kuma free?
Yes. Uptime Kuma is open source under the MIT licence. Here you pay only for the server it runs on, by the hour from prepaid credits; the template adds no fee and monitors cost nothing extra. See pricing.
Who becomes the Uptime Kuma admin?
Whoever opens the address first. Uptime Kuma has no way to set an admin before it starts, so its setup screen creates one for the first visitor and then closes. It has one admin and no other users. Open it as soon as the console says it is running. If someone else got there first, delete the app and create it again, because a password reset would not undo what they changed.
Can I use my own domain for Uptime Kuma?
Yes. Every deployment gets its own HTTPS address first. To use a domain you own, point its DNS at the server, then add it from the project in the console; Uptime Kuma and its status pages answer there at once. Then update Primary Base URL in Settings, which does not follow the domain on its own.
How do I back up Uptime Kuma?
With the server. Uptime Kuma 2 has no backup or export of its own, so the volume on the server is the only copy of your monitors and history. Turn on the optional daily server backups, or ask us for container access over SSH to copy the volume out.
Related guides.
Uptime monitoring on a server that stays on. Yours from the first visit.
- Uptime Kuma 2.5.6 with SQLite preset
- Monitors, alerts and status pages over HTTPS
- A European 4 GB server, about $15 to $16 a month
About Selfhost.dev
Selfhost.dev is a managed self hosting platform for developers and small teams. Open source apps and databases on dedicated servers you control, billed by the hour, in six locations across three continents.
Best for: Uptime Kuma, Grafana, Keycloak and managed PostgreSQL, MySQL, Redis, ClickHouse, OpenSearch and Kafka.