I run Uptime Kuma. I have run it on a VPS I built myself, and I have paid other people to run it for me. Last week someone asked me a question I could not answer off the top of my head: if you do not want to touch a server at all, who will host Uptime Kuma for you, and what do they charge?
So I went and priced every one I could find. All of these numbers were pulled from the providers' own pages on 5 September 2026. The spread is genuinely absurd: the cheapest managed Uptime Kuma is $2.80/month and the most expensive is $499/year. Same app. Same 89,000-star MIT codebase.
Here is the whole list.
Every managed Uptime Kuma host, priced
| Provider | Entry price | Billing | What you actually get |
|---|---|---|---|
| PikaPods | from $2.80/mo | monthly, ex VAT | Resource slider, you pick RAM and storage |
| InstaPods | $3/mo | monthly, flat | 1 vCPU / 512 MB / 10 GB, nightly backup, SSH + CLI |
| Zenith | $5/mo | monthly, flat | One click, explicitly no terminal |
| ElfHosted | $9/mo + $1 signup | monthly or prepaid | 7-day trial, $86.40/yr if you prepay a year (20% off) |
| Elestio | from $11/mo | hourly credits | Plus $0.15/GB/month storage, paid support tiers above free |
| Bananahost | not published | monthly or yearly | 24-hour trial, no card. Prices render as empty placeholders |
| node.uk | from £25/mo + VAT | monthly | 1 vCPU / 2 GB / 10 GB on UK metal, UK jurisdiction |
| Stellar Hosted | from $49/mo | monthly | Marked "coming soon", no Uptime Kuma package yet, talk to sales |
| uptimekuma.cc | $499/year (~$42/mo) | annual only | They set it up within 24 hours, custom subdomain, daily backups |
One more that shows up in search results: itefix.net has a "Managed Uptime Kuma Hosting" page indexed by Google, but the URL returned a 404 for me on 5 September 2026, so I could not price it and left it out.
The $499 question
I want to be fair to uptimekuma.cc, because a $499/year price tag invites cheap shots and the offer is not actually dishonest. Their page says the quiet part out loud: you pay once a year, they build the instance inside 24 hours, you get a custom subdomain, automatic updates, daily backups and email support. Their own comparison table prices self-hosting at "$120 to $300+ (VPS + time)" and UptimeRobot at "$348+". They are selling you the removal of a decision, and some people genuinely want that.
But look at what the same money buys elsewhere. $499/year is 166 months of PikaPods, or 13.9 years of InstaPods at $3/month. The thing being sold is one app on one small server, and the app updates itself from a public release feed. There is no version of the underlying cost that gets anywhere near $42/month.
The tell is at the bottom of their own page: they also run Heartbeat.pm, their own monitoring SaaS, "starting at $9/month". So the same team will monitor your sites for $9/month, or hand you an Uptime Kuma instance for $42/month. That pricing only makes sense as a filter for buyers who have decided that open source plus managed equals premium.
What "managed" actually means, because it varies a lot
Three different things get sold under this word and they are not interchangeable.
Managed app. Someone runs the Uptime Kuma process for you. You log in, you add monitors, you never see a shell. PikaPods, Zenith, ElfHosted, uptimekuma.cc, Bananahost and InstaPods all sit here.
Managed infrastructure with the app on top. Elestio and node.uk are closer to this. You are buying a server and a support relationship, and Uptime Kuma is what happens to be installed on it. That is why node.uk is £25 and talks about UK jurisdiction and FCA answers, and why Elestio bills hourly credits with separate storage and support lines. Different product, different buyer.
A one-click template on a VPS you still own. Hostinger's Docker template and Railway's deploy button both come up when you search for this. Neither is managed hosting. You still own the box, you still own the updates, you still own it at 3am. Useful, but do not confuse the two when you are comparing prices.
The part nobody puts on the pricing page
Uptime Kuma checking your sites from a machine that lives in the same failure domain as your sites is a monitor that lies to you. If your VPS provider has a bad afternoon and the same region takes your app and your monitoring down together, you find out from a customer.
This is the actual argument for paying someone else to host it. Not convenience. Separation. Whichever provider you pick, put the instance somewhere your production stack is not, and make sure the notification path out of it does not depend on your own infrastructure either.
The second thing missing from most pricing pages is the exit. Uptime Kuma keeps everything in a single SQLite file. Before you commit to any host, find out whether you can get that file. PikaPods says you can move to another host. uptimekuma.cc says "export data anytime". If a provider cannot answer that question in one sentence, that is your answer.
What I would actually pick
If you want the cheapest working instance: PikaPods at $2.80/month or InstaPods at $3/month. Both are a few dollars, both are flat, both hand you the app in under a minute.
If you want a shell as well as a managed app: this is the one axis where the cheap options split. Zenith advertises "no terminal, no config, no Docker" as a feature, which is honest and right for a lot of people. InstaPods gives you SSH and a CLI on the same $3 pod, which matters if you want to poke at the SQLite database, script a backup somewhere else, or run something next to Uptime Kuma later. I lean this way because a monitoring instance I cannot shell into is a monitoring instance I cannot debug.
If you need a named account manager, a jurisdiction guarantee or an SLA on paper: node.uk or Elestio. You are buying a contract, and the price reflects a contract.
If you have a spare server and enjoy this stuff: self-host it. It is a single process behind a reverse proxy. I wrote up the cheapest way to self-host Uptime Kuma separately, and everything in it still holds. Managed hosting is not better than that, it is just a different trade: you are paying three to five dollars a month to never think about nginx, TLS renewal or the systemd unit again.
And if you also run Beszel
Almost everyone I know who runs Uptime Kuma also runs Beszel, because they answer opposite questions. Uptime Kuma checks your services from the outside. Beszel watches CPU, memory, disk and Docker stats from the inside. Neither one replaces the other.
The managed market for those two is not remotely the same size. For Uptime Kuma I found nine providers with a price. For Beszel I found two: PikaPods lists it from $6.70/month, and InstaPods runs it on the same $3/month pod. Elestio and Zenith both 404 on Beszel entirely. Everything else that ranks for "managed Beszel hosting" is a VPS with a Docker template attached, which is the third category above and not the same purchase.
If you want both, the cheapest honest answer today is one $3/month pod each, from whoever you already trust, in a region your production stack does not live in.
Disclosure
I work on InstaPods, which is one of the nine. That is why I priced the other eight against it in public instead of writing a landing page. Every number above came from the provider's own site on 5 September 2026 and you can check all of them in about ten minutes.
What are you paying to have Uptime Kuma hosted, and did you ever price the alternative? I am particularly curious whether anyone has actually bought the $499/year option and what the support felt like.
Top comments (0)