The Cheapest Way to Self-Host Uptime Kuma in 2026

Last updated: March 2026

Uptime Kuma is the best open source uptime monitoring tool you can self-host. It's a self-hosted alternative to UptimeRobot, Pingdom, and StatusCake - unlimited monitors, beautiful status pages, and notifications to 70+ services including Slack, Discord, Telegram, and email. Over 65,000 GitHub stars and actively maintained.

But "self-hosted" means you need somewhere to run it. And monitoring tools have a requirement most apps don't - they need to be running 24/7 with zero downtime. Your uptime monitor going down is the one outage nobody notices until everything else is also down.

I've tried multiple hosting setups for Uptime Kuma. Here's every option I found, ranked by actual monthly cost, with the trade-offs that matter for a monitoring tool specifically.

TLDR: The cheapest managed option is InstaPods at $3/mo or PikaPods at ~$2.50/mo - both handle everything. The cheapest self-managed option is a $3-5/mo Hetzner VPS with Docker. UptimeRobot's paid plan starts at $7/mo. The right answer depends on how many monitors you need and whether you want to own your data.

Every Way to Host Uptime Kuma, Ranked by Cost

Method	Monthly Cost	You Manage	Setup Time	Monitors
Oracle Cloud free tier	$0	Everything	~1 hr	Unlimited
PikaPods	~$2.50	Nothing	~1 min	Unlimited
InstaPods	$3	Nothing	~30 sec	Unlimited
Hetzner VPS + Docker	~$3.50-5	Everything	~30 min	Unlimited
Coolify on Hetzner VPS	~$5-8	VPS + OS	~10 min	Unlimited
CapRover on Hetzner VPS	~$5-6	Everything	~20 min	Unlimited
UptimeRobot (paid)	$7+	Nothing	~2 min	50+
Render	~$7	Nothing	~10 min	Unlimited
Elestio	~$17	Nothing	~3 min	Unlimited
Cloudron on Hetzner VPS	~$21	VPS + OS	~30 min	Unlimited

Let me walk through each one.

1. Hetzner VPS + Docker (~$3.50-5/mo)

The DIY approach. Rent a cheap VPS, install Docker, run Uptime Kuma.

version: "3"
services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    ports:
      - "3001:3001"
    volumes:
      - uptime-kuma-data:/app/data
    restart: always
volumes:
  uptime-kuma-data:

Cost breakdown:

• Hetzner CX11: EUR 3.29/mo (~$3.55) - 1 vCPU, 2 GB RAM, 20 GB storage
• Or Hetzner CAX11 (ARM): EUR 3.29/mo (~$3.55) - 2 Ampere vCPU, 4 GB RAM

Uptime Kuma is lightweight. It runs comfortably on the smallest VPS. Unlike n8n which needs at least 512 MB, Uptime Kuma runs fine with 256 MB of RAM even with 50+ monitors.

What you also need to set up:

• Reverse proxy (nginx or Caddy) for HTTPS
• SSL certificate (Let's Encrypt + certbot)
• Firewall rules (UFW)
• Automatic updates for Uptime Kuma and the OS
• Backups (cron job for the /app/data directory)
• Monitoring for your monitoring tool (yes, really - who watches the watchers?)

Pros: Cheapest paid option. Full control. Extremely lightweight. Can run other services on the same VPS.
Cons: You're the sysadmin. If the VPS has an outage, your monitoring goes down and you won't know your other services are down either.

Best for: Developers comfortable with Linux and Docker who want full control and don't mind maintaining the server.

2. Oracle Cloud Free Tier ($0/mo)

Oracle offers an always-free ARM instance (4 OCPU, 24 GB RAM) that can run Uptime Kuma. It's genuinely free - not a trial.

Cost: $0 if you can get an instance. Availability is limited and you'll hit "out of capacity" errors for days or weeks before getting one.

Catch: Oracle's free tier has been reliable for some people and randomly terminated for others. There are reports of instances being reclaimed without warning. Running your uptime monitoring on infrastructure that might disappear is... not ideal.

The deeper problem: Your monitoring tool needs to be more reliable than the things it monitors. Putting it on the least reliable infrastructure available defeats the purpose.

Best for: Testing Uptime Kuma or monitoring non-critical personal projects. Not recommended for anything you depend on.

3. Coolify on Hetzner VPS (~$5-8/mo)

Install Coolify (free, open source) on a VPS and deploy Uptime Kuma through its one-click catalog.

Cost breakdown:

• Hetzner CX22: ~$4.30/mo (minimum for Coolify + Uptime Kuma on same server)
• Hetzner CX32: ~$7.50/mo (recommended - Coolify itself uses 2 GB RAM)

Pros: Web UI for managing Uptime Kuma. Auto-updates. Can run other apps alongside it. Free.
Cons: Coolify's 2 GB RAM overhead is overkill when Uptime Kuma itself needs 256 MB. You're running a management platform heavier than the app it manages.

Best for: People already running Coolify for other apps who want to add monitoring.

4. CapRover on Hetzner VPS (~$5-6/mo)

Install CapRover (free) and deploy Uptime Kuma from its template catalog.

Cost: Same as DIY Docker - just the VPS cost. CapRover is free.

Pros: One-click Uptime Kuma install. Web UI.
Cons: CapRover development has stalled (last commit Dec 2025). Docker Swarm dependency is a long-term risk. You still manage the VPS.

Best for: Existing CapRover users. For new setups, pick Coolify instead.

5. InstaPods ($3/mo)

InstaPods has Uptime Kuma as a one-click app. Click deploy, get a running instance with SSL in about 30 seconds. $3/mo on the Launch plan.

Full disclosure: I built InstaPods. Including it because it's genuinely one of the cheapest managed options and the comparison wouldn't be complete without it. I'll be honest about the limitations.

Cost: $3/mo (Launch plan: 0.5 vCPU, 512 MB RAM, 5 GB storage). More than enough for Uptime Kuma - it barely uses 150 MB of RAM even with dozens of monitors.

Pros: Fastest setup of any option. No server management. SSL and URL included. Uptime Kuma runs on a real server (not a serverless function that sleeps). $10 free credit on signup.
Cons: New platform (launched 2026). Single region (EU - Nuremberg). Smaller community than established platforms.

Best for: People who want Uptime Kuma running in under a minute with zero maintenance.

6. PikaPods (~$2.50/mo)

PikaPods is managed hosting for open source apps. Pick Uptime Kuma, set your resource sliders, done.

Cost: ~$2.50/mo for Uptime Kuma with default resources. Uptime Kuma is lightweight enough that the minimum resources work fine.

Pros: Zero maintenance. Revenue sharing with open source projects (part of your payment goes directly to Uptime Kuma's developer). $5 welcome credit. Established platform with a good track record.
Cons: Limited configuration options. Can't customize Uptime Kuma's environment beyond what PikaPods exposes.

Best for: Non-technical users who want managed Uptime Kuma at the lowest price. Probably the easiest option overall.

7. UptimeRobot Paid Plan ($7+/mo)

Wait - this isn't self-hosting. True. But most people looking at Uptime Kuma are comparing it to UptimeRobot, so the pricing context matters.

UptimeRobot free tier: 50 monitors, 5-minute check intervals. No status page customization. Limited notification options.

UptimeRobot Pro: $7/mo for 50 monitors with 1-minute intervals. More notification methods. Custom status pages.

Why people switch to Uptime Kuma:

• UptimeRobot keeps reducing free tier value - check intervals have gotten slower over the years, and useful features keep moving behind the paywall
• UptimeRobot Pro at $7/mo adds up when self-hosted Uptime Kuma gives you unlimited everything for $2.50-3/mo
• Uptime Kuma has 70+ notification providers vs UptimeRobot's ~12
• Data privacy - your monitoring data stays on your server
• No vendor lock-in

The math: UptimeRobot Pro costs $7/mo for 50 monitors with 1-minute intervals. Self-hosted Uptime Kuma on PikaPods ($2.50/mo) or InstaPods ($3/mo) gives you unlimited monitors with 1-second check intervals - more features for less than half the price.

8. Render (~$7/mo)

Render can run Uptime Kuma as a Docker web service.

Cost: Free tier won't work - Render's free services sleep after 15 minutes of inactivity, and a monitoring tool that sleeps defeats the purpose. The paid Individual plan starts at $7/mo.

Important: You also need a Render Disk ($0.25/GB/mo) or your Uptime Kuma data resets on every deploy.

Pros: Managed. Good developer UX. Auto-deploys from Docker image.
Cons: $7/mo is expensive for a monitoring tool when managed alternatives exist at $2.50-3/mo. The sleeping free tier is useless for monitoring.

Best for: Developers already using Render for other services who want to add monitoring to their stack.

9. Elestio (~$17/mo)

Elestio is fully managed hosting. Pick Uptime Kuma, pick a cloud provider, they deploy it on a dedicated VM.

Cost: ~$17/mo minimum (Hetzner-backed VM). Higher for other cloud providers.

Pros: True zero-maintenance. Auto-updates, backups, security patches. Choose from 8 cloud providers.
Cons: $17/mo for a monitoring tool is hard to justify when the managed alternatives are $2.50-3/mo. One app = one VM is wasteful for something this lightweight.

Best for: Teams with budget who want fully managed hosting on a specific cloud provider. Otherwise overpriced for Uptime Kuma.

10. Cloudron on Hetzner VPS (~$21/mo)

Install Cloudron on a VPS and deploy Uptime Kuma from the app store.

Cost: VPS (~$5/mo) + Cloudron license (EUR 15/mo) = ~$21/mo.

Pros: Best admin dashboard. SSO, email, backups built in.
Cons: EUR 15/mo license for running a monitoring tool that needs 256 MB of RAM is absurd. Only makes sense if you're already running 5-10 other apps on Cloudron.

Best for: Existing Cloudron users only. Never worth the license just for Uptime Kuma.

The Real Comparison

Here's what it comes down to:

If you want the absolute cheapest managed option:
PikaPods at ~$2.50/mo or InstaPods at $3/mo. Both give you a running Uptime Kuma instance with SSL, zero maintenance, unlimited monitors. PikaPods has the slight price edge, InstaPods has faster deploy time.

If you want full control and have Linux skills:
Hetzner VPS + Docker at ~$3.50/mo. You manage everything, but you own every layer. Run other apps on the same server to share the cost.

If you're comparing to UptimeRobot:
Self-hosted Uptime Kuma on PikaPods or InstaPods costs less than half of UptimeRobot Pro, gives you unlimited monitors, 1-second check intervals, and 70+ notification integrations. The only thing UptimeRobot has that self-hosted doesn't is monitoring from multiple geographic locations (though you can work around this with multiple Uptime Kuma instances).

Special consideration for monitoring tools:
Your uptime monitor should be running on different infrastructure than the services it monitors. If your VPS hosts both your app AND Uptime Kuma, a server outage takes out both. You won't get notified. Consider running Uptime Kuma on a separate $3/mo managed platform even if you self-host everything else.

FAQ

How much RAM does Uptime Kuma need?
Very little. 150-200 MB for typical usage (50-100 monitors). Even with 200+ monitors, it rarely exceeds 300 MB. It's one of the lightest self-hosted apps you can run.

Can I monitor sites from multiple locations?
Not with a single instance. Uptime Kuma monitors from wherever it's running. For multi-location monitoring, you'd need multiple instances or use a service like UptimeRobot. For most people, single-location monitoring is fine.

How is Uptime Kuma different from UptimeRobot?
Uptime Kuma is self-hosted and free. UptimeRobot is a SaaS. Uptime Kuma gives you unlimited monitors, 1-second check intervals, and 70+ notification integrations. UptimeRobot's free tier gives you 50 monitors with 5-minute intervals. Uptime Kuma's status pages are more customizable.

Does Uptime Kuma support HTTPS monitoring?
Yes. It supports HTTP(S), TCP, Ping, DNS, Docker, Steam Game Server, MQTT, and more monitor types. It verifies SSL certificates and can alert you before they expire.

Can I set up a public status page?
Yes. Uptime Kuma has built-in status pages you can make public. Add your monitors, customize the look, and share the URL. No extra setup needed.

How do I back up Uptime Kuma?
Uptime Kuma stores everything in a SQLite database at /app/data/kuma.db. Back up that file. On Docker, back up the mounted volume. On managed platforms (PikaPods, InstaPods, Elestio), backups are handled for you.

Can I migrate from UptimeRobot to Uptime Kuma?
There's no official import tool, but Uptime Kuma's API lets you create monitors programmatically. Community scripts exist that export from UptimeRobot and import into Uptime Kuma. Notifications need to be set up manually since credentials don't transfer.

Should I run Uptime Kuma on the same server as my apps?
Ideally not. If that server goes down, your monitoring goes down with it and you won't get alerted. Running Uptime Kuma on a separate $3/mo managed platform is cheap insurance.

If you're looking at alternatives to traditional hosting platforms, I wrote a Heroku alternatives comparison on our blog. For more self-hosted platform comparisons, check out Coolify vs Cloudron vs CapRover and a 6-platform comparison. If you're also running n8n, check out the cheapest way to self-host n8n.

What's your monitoring setup? Running Uptime Kuma or something else? Drop it in the comments.