Uptime Kuma Instant App
Self-hosted Uptime Kuma VPS hosting
Uptime Kuma is an open-source uptime monitor with HTTP checks, alerts and public status pages. Compare live VPS prices, CPU, RAM, disk and regions, launch Uptime Kuma on the plan you choose, and keep root access so heartbeats stay on your server.
Uptime Kuma
Instant App on marketplace VPS
Live marketplace offers
Compare Uptime Kuma VPS plans
Choose billing and size, compare providers side by side, pick a location, then launch.
Inside Uptime Kuma
Uptime Kuma is a self-hosted uptime monitor. Use it instead of paying for Pingdom, StatusCake or Better Stack. It checks HTTP and other endpoints on a schedule, stores heartbeat history, sends alerts when something fails, and can publish a status page for customers. Sign in as admin with sample monitors already on the dashboard, then add your own URLs and notification channels. No Instant App form fields are required at create time.

Dashboard with live monitors after login
Open Uptime Kuma and see starter HTTP checks already listed. Green and red rows show uptime history instead of an empty first-run screen.

Add HTTP checks and intervals
Point monitors at your sites, APIs and landing pages. Pick intervals, keywords and certificate expiry notices that match how you run production.

Status pages for customers
Publish a public status page when you want outsiders to see incidents without signing into the admin UI.

Admin account ready after boot
The first admin user is created for you. Sign in with the username and password from your server notes, then wire Telegram, Discord, email or webhooks.
Why use the NodeRings marketplace?
Compare live Uptime Kuma VPS plans from independent providers, then self-host uptime monitoring and status pages on the offer you pick. Use it instead of paying for Pingdom, StatusCake or Better Stack.
Compare Uptime Kuma VPS offers in one place
See live prices, regions and plan sizes before you buy. Shop monitoring hosts across independent providers, including 1 GB boxes that fit a small check set.
Self-host Uptime Kuma without a manual install
Pick a plan and Uptime Kuma is prepared on that VPS for you, including the admin account and starter monitors. You still get root access.
Watch from a region you choose
Compatible offers list cities and countries. Put the monitor away from the apps it checks so a dead app server does not silence the alert.
Own the monitor and the history
Heartbeats, incidents and status pages live on your VPS volume. You control SSH, DNS and who can sign in to Uptime Kuma.
Uptime Kuma hosting as a marketplace, not a single hoster
Most Uptime Kuma VPS pages sell one company's servers. NodeRings lists Compute Instance plans from independent providers so you can compare self-hosted monitoring offers by price, size and region, then launch on the one that fits.
Uptime Kuma Instant App prepares Uptime Kuma on the provider VPS you selected. NodeRings does not operate that hardware or sell its own VPS fleet.
Single-provider Uptime Kuma hosting
- One company catalogue and renewal pricing
- One set of regions and support paths
- One vendor panel for that host only
NodeRings marketplace
- Uptime Kuma VPS offers from independent providers
- Compare resources, prices and regions side by side
- Deploy Uptime Kuma on the plan you pick
How it works
Compare plans, pick a provider offer, and launch Uptime Kuma on that server.
01
Compare Uptime Kuma VPS plans
Browse live offers below. A 1 GB plan is a solid start for a small monitor set. Sort by provider, size, price and region.
02
Pick the offer that fits
Choose the provider plan and region. There are no Instant App form fields to fill for Uptime Kuma.
03
Deploy and sign in
Confirm checkout and wait for the server. Then open the site URL and sign in with the admin username and password from your server notes. You keep root SSH.
On the VPS after Uptime Kuma deploys
NodeRings Instant App brings Uptime Kuma up with Docker Compose and prepares first-boot access for you. Use the sections below to reach the UI, find passwords, and operate the stack.
Open the web UI
- In a browser, go to http://YOUR_SERVER_IP/ using the IPv4 from your order.
- Sign in with uptime_kuma_admin_user and uptime_kuma_admin_pass from the credentials file.
- Add monitors from the dashboard after login.
Where the password is
Credentials are written on first boot to:
/root/.noderings_passwordRead them over SSH:
cat /root/.noderings_password- Keys in that file include uptime_kuma_admin_user, uptime_kuma_admin_pass and site_url.
- SSH in as root with the create-flow password or key, then run the command above.
- Change the Uptime Kuma admin password after you first sign in.
Where files live
Compose project directory
/opt/noderings/uptime-kuma
/opt/noderings/uptime-kuma/docker-compose.yml
/opt/noderings/uptime-kuma/.envWorking directory for compose, the stack file, and generated secrets.
Credentials file
/root/.noderings_passwordWritten once on first boot.
Boot unit
/etc/systemd/system/noderings-uptime-kuma.serviceBrings compose up after Docker is ready.
What runs in Docker
A single Compose service runs Uptime Kuma on HTTP port 80.
uptime-kumaUptime Kuma monitoring UI on HTTP port 80.
Container status
cd /opt/noderings/uptime-kuma && docker compose psLive logs
cd /opt/noderings/uptime-kuma && docker compose logs -fRestart containers
cd /opt/noderings/uptime-kuma && docker compose restartsystemd unit status
systemctl status noderings-uptime-kumaAdd HTTPS with Cloudflare
Your Uptime Kuma app starts on http://. Cloudflare can give visitors a padlock without installing anything on the VPS.
Add your domain
Sign up at Cloudflare and add the domain you want to use.
Point it at your VPS
Create an A record to your server IP and leave the orange cloud on.
Open the https site
Visit https://your-domain and sign in with the admin credentials from your server notes.
Only allow Cloudflare
Optional. With SSH (port 22) already allowed and everything else blocked by default, open only Cloudflare to ports 80 and 443:
curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; done
That is enough for a first secure visit. You can tighten SSL in Cloudflare later if you need it. Keep port 22 allowed for SSH; leave other ports denied except this Cloudflare allow for 80 and 443.
More detail
- NodeRings does not sell Uptime Kuma as a product and is not the Uptime Kuma project.
Uptime Kuma VPS requirements and sizing
Uptime Kuma is light when quiet. Public measurements and NodeRings lab notes show roughly 130–250 MiB for a small set of HTTP checks. More monitors, browser checks and long retention raise RAM and disk. These are starting points, not guarantees.
| Workload | Illustrative starting point | Note |
|---|---|---|
| Personal or small fleet | 1 vCPU / 1 GB RAM / 20+ GB disk | Suggested Instant App floor for a handful of HTTP checks. |
| Dozens of monitors | 1–2 vCPU / 2 GB RAM | Headroom for shorter intervals and longer heartbeat history. |
| Browser checks or heavy retention | 2 vCPU / 4 GB RAM and watch disk | Real browser monitors and years of history cost more memory and storage. |
| Placement | Separate VPS from the apps you watch | If the monitor shares a host with the outage, the alert may never leave the box. |
These are starting points, not guarantees. Needs depend on monitor count, check type, interval and how long you keep history.
Root access and who does what
This is self-hosted Uptime Kuma on a provider VPS, not a managed monitoring SaaS. You pick the plan. Uptime Kuma is prepared on that server. Day-to-day care stays with you.
What you get ready
Uptime Kuma is prepared on the VPS with no Instant App form variables. The admin account and starter HTTP monitors are created for you.
What you keep
Root SSH on the VPS. You own monitors, alerts, status pages, DNS, TLS, OS updates and backups unless a provider product says otherwise.
What is not included
Managed notification routing, automatic TLS and hands-off OS patching are not bundled in. Wire alerts and finish TLS after the server is up if you need them.
Support boundaries
NodeRings helps with marketplace, billing and console. Provider hardware issues go to that provider. Looking after Uptime Kuma on the server is yours.
Uptime Kuma VPS FAQs
What is Uptime Kuma?
Uptime Kuma is a free, open-source uptime monitor. It checks websites and services on a schedule, stores history, sends alerts and can publish a status page on hardware you control.
Do I need to fill Instant App variables for Uptime Kuma?
No. Uptime Kuma Instant App asks for no form variables at create time. After the VPS is ready, sign in with the admin username and password from your server notes.
Does NodeRings run the Uptime Kuma server?
No. NodeRings is a marketplace. Independent providers list VPS plans. You pick a plan, Uptime Kuma is prepared on that provider server, and you manage monitors from there.
Is this managed Uptime Kuma hosting?
No. You get a virtual machine with Uptime Kuma prepared for you, plus root access. That is different from a managed product that owns updates and support for you.
What is Uptime Kuma Instant App?
It prepares Uptime Kuma on the VPS you choose so you skip hunting through install guides by hand. It is still your self-hosted server, not a separate managed hosting brand.
How do I sign in after deploy?
Open the site URL from your server notes and sign in with uptime_kuma_admin_user and uptime_kuma_admin_pass from /root/.noderings_password. Nothing was collected from you at checkout for Uptime Kuma.
What size Uptime Kuma VPS do I need?
A common starting point for a small monitor set is about 1 vCPU, 1 GB RAM and 20 GB disk. More monitors and longer history usually need more RAM and disk. Use the sizing guide above and compare plans in the list.
Should Uptime Kuma run on the same server as my apps?
Prefer a separate VPS. If the monitor shares hardware with the outage, the alert path can die with the app. Many operators also add one outside check that watches Uptime Kuma itself.
Can I publish a public status page?
Yes after you sign in. Create a status page in Uptime Kuma and point DNS at your VPS when you want customers to see incidents without admin access.
What happens after I click Deploy Uptime Kuma?
You confirm the plan and finish checkout. When the server is ready, open the site URL and sign in with the admin credentials from your server notes.
Can I choose the server region?
Yes. Each compatible plan lists available regions. Pick the city or country that matches latency and where you want checks to originate.
