Does deploying Uptime Kuma cost anything on top of the VPS?
No. One Click Apps is included with every OnetSolutions VPS from 2 vCPU, 2 GB of RAM and 30 GB of disk. There is no surcharge, no separate subscription and no usage-based billing.
Monitoring and status page
One-click Uptime Kuma hosting on a French VPS
Uptime Kuma watches your sites, your APIs and your servers, alerts you when they go down and publishes a status page for your users. Tick it at order time and it runs over HTTPS a few minutes later.
- HTTP, TCP, ping, DNS and TLS certificate checks
- Alerts to Slack, Telegram, email, webhooks and many more
- Public status page on your own domain
- No surcharge: it comes with the VPS
512 MB
of RAM required by the application
€0
surcharge on your VPS
7 days
of backups retained
France
hosting and data
Monitoring that belongs to you
Uptime Kuma is an open-source monitoring tool with a deliberately simple interface. You declare checks — a URL to hit, a port to test, a host to ping — and choose where the alert lands when something stops answering.
It doubles as a status page: a public address where your customers can see at a glance what is working, without having to write to you. It is often the first thing people set up once they run more than one service.
One rule holds for all monitoring: never watch a machine from itself. If the server goes down the check goes down with it and nobody gets told. Uptime Kuma belongs on a VPS separate from what it observes — which is easy when a small VPS is enough.
HTTP and TCP checksPing and DNSTLS expiryStatus pageOver 90 notification channels
From order to first alert
Three steps, no command line.
1
Order a VPS and tick Uptime Kuma
A Debian or Ubuntu image and a size of at least 2 vCPU, 2 GB of RAM and 30 GB of disk is more than enough for this application.
2
The deployment runs itself
The application is installed and published over HTTPS at an address you can use right away, with no certificate to request and no proxy to tune.
3
Declare your checks and alerts
Create your admin account, add the services to watch, wire up Slack or Telegram, and publish your status page on your own domain.
Manual install versus one click
What you would have done by hand on a bare server, and what is left for you here.
| By hand | One click | |
|---|---|---|
| Going live | SSH session, Docker to install and configure | One box ticked at order time |
| HTTPS | Reverse proxy and certificate to handle yourself | Issued and renewed automatically |
| Data persistence | Volume to create and mount correctly | Provisioned with the application |
| Updates | Image to pull again and container to recreate | Flagged in the console, applied in one click |
| Backups | Script and remote storage to set up | Daily, 7-day retention, one-click restore |
What size of VPS for Uptime Kuma
The application is very light: it asks for 512 MB of RAM. The platform minimum of 2 GB leaves room for other applications on the same server.
| Use case | Configuration | What it covers |
|---|---|---|
| Personal monitoring | 2 vCPU · 2 GB RAM · 30 GB NVMe | A few dozen checks, a status page, notifications. |
| Monitoring host | 2 vCPU · 4 GB RAM · 60 GB NVMe | Uptime Kuma alongside other tools on the same server: dashboard, log collector. |
| Large estate | 4 vCPU · 8 GB RAM · 120 GB NVMe | Several hundred checks on short intervals and a long history. |
Put this server somewhere other than the machine you are watching: a check hosted on the observed machine will never warn you about its outage.
What we do, what you do
Worth stating plainly: we deliver and run the server, the application stays yours.
On us
The VPS, the network, DDoS protection, the hypervisor, and the deployment platform that installs the application, issues the certificate and triggers the backups.
On you
Uptime Kuma itself: its checks, its alert channels, its updates, its data. Our support does not step into the application and provides neither maintenance nor monitoring for it.
Worth doing
Actually test an alert channel once you have configured it, and confirm the notification arrives when the watched service stops.
Frequently asked questions about hosting Uptime Kuma
What people ask us most before getting started.
Can I monitor a server that is not hosted with OnetSolutions?
Yes. Uptime Kuma queries any public address, whoever hosts it. That is in fact the point: useful monitoring sits outside what it observes.
Can I publish a status page on my own domain?
Yes. You declare the domain from the console and the TLS certificate is issued automatically for the address you choose.
How many applications can I install on the same server?
There is no cap. Available memory is the only limit, and Uptime Kuma is light enough to sit comfortably next to other applications.
Do I keep SSH access to the server?
Yes. The VPS remains a full VPS with root access. One-click deployment saves you from needing SSH, it does not take it away.
Your monitoring live in minutes
Order a Debian or Ubuntu VPS, tick Uptime Kuma, and declare your first check from an interface that is already on HTTPS.