Domain, email & servers
Get Alerted When Your Website Goes Down, with Your Own Uptime Kuma
Up to 20 checks on your sites and APIs, alerts to your email and chat, and a public status page on your own domain, all on a server you own.
Delivered in 1-2 working days
Fixed price · one-time · no hidden charges
or
Ask on WhatsApp before you buyA real person replies — usually within minutes during the day (IST).
How it works
- Pay ₹2,399Secure Razorpay checkout, one time. Then send the server details, domain and the list of things to watch.
- Installed and monitors addedWe install Uptime Kuma, add SSL, create the monitors and connect your alert channels.
- Alerts and backup provenWe trigger a test alert on each channel, publish the status page, test a backup restore, then send the guide and logins.
The short answer
ZoopCoder installs Uptime Kuma, the free open-source uptime monitor, on your own Ubuntu server for a fixed ₹2,399, ready in 1-2 working days. The price covers Uptime Kuma in Docker, your domain with SSL, up to 20 monitors for websites, ports, APIs or SSL expiry with sensible check intervals and retries, up to 2 alert channels such as email, Telegram or Slack with a test alert proven, one public status page on your own subdomain, and a backup of its data with one tested restore. One honest rule shapes the setup: a monitor running on the same server as your website cannot tell you when that server is down, so we ask where it should live before you buy a server. The server and domain are billed separately.
What you get
- Uptime Kuma (current version 2 container image) installed on your Ubuntu VPS with Docker Compose, with its data folder kept on the server’s own disk
- Your domain or subdomain pointed to it with free SSL that renews itself, HTTPS enforced, and the reverse proxy set to pass the WebSocket connection Uptime Kuma needs
- Up to 20 monitors across websites, keyword checks, TCP ports, APIs and SSL certificate expiry, with check interval, retries and timeouts set from your list
- Up to 2 alert channels connected from email (SMTP), Telegram, Slack, Discord or a webhook, each tested by switching a test monitor to down
- One public status page on your own subdomain showing the monitors you choose, with your logo and name
- Firewall on, root login and password login for SSH switched off, and an admin account with a strong password created by us
- A backup of the Uptime Kuma data folder on a schedule to a location you choose, and one test restore
- A short written guide to adding monitors and updating Uptime Kuma, and 14 days of fixes for anything we configured
| Price | ₹2,399 (fixed) |
|---|---|
| Software | Uptime Kuma open-source (free) |
| Server | Your Ubuntu VPS, root access |
| Monitors | Up to 20 |
| Alert channels | Up to 2, each tested |
| Status page | 1 on your own subdomain |
| Support | 14 days of fixes after handover |
What we need from you
- An Ubuntu VPS with root access bought in your name — ideally a different server or provider from the sites being watched, and we advise before you buy
- A domain or subdomain for the dashboard, and optionally another for the status page, for example status.yourbusiness.com
- The list of addresses, ports or APIs to watch, and which of them matter most
- Details for the alert channels, such as an SMTP login, a Telegram bot token and chat, or a Slack webhook address
Not included
- The VPS fee, domain fee, mailbox fee and backup storage fee, billed by those providers to you
- Server metrics such as CPU, memory and disk graphs — that is a different tool, see our Prometheus and Grafana setup
- Fixing the problems the monitor finds, or watching and responding to the alerts for you after handover
- More than 20 monitors, more than 2 alert channels or more than one status page — quoted separately
- Any uptime guarantee or service level agreement for your website
About this service
Uptime Kuma is a self-hosted monitoring tool: it checks your website, API or port every minute or so and messages you the moment one stops answering, then publishes a status page your customers can open instead of emailing you. It is free to run, so there is no per-monitor fee like hosted uptime services charge. Installing it is a short Docker command, but a monitor is only useful if it is set up with care. It relies on a WebSocket connection, so the reverse proxy in front of it needs the Upgrade and Connection headers passed through, and its own documentation warns that its SQLite data must not live on a network drive such as NFS because file locking problems can corrupt it. The biggest mistake is putting the monitor on the very server it watches, so we help you choose a placement that can actually report an outage. Each alert channel is tested for real before handover. For server health graphs rather than up or down checks, see Prometheus and Grafana Monitoring Setup, and for the server itself see VPS Server Setup.
Questions before you buy
Is Uptime Kuma free?
Yes, it is open source and free to run on your own server. You pay for the VPS, the domain and any SMS or mailbox service used for alerts.
Why not just use a free hosted uptime service?
Hosted free plans usually limit how many monitors you get, how often they check and whether you get a public status page. Self-hosting removes those limits but means you run a small server. If you only have a couple of sites, a hosted free plan may be enough, and we will say so if you message us first.
Where should the monitor be installed?
Not on the same server as the website it watches, because if that server goes down the monitor goes down with it and sends no alert. A small separate VPS, ideally at a different provider, is the safe choice. Tell us what you have and we will advise before you buy anything.
Can you monitor things inside a private network?
Only what the monitor server can reach. Private addresses behind a firewall need a route to them, so message us the layout first and we will tell you honestly whether it works.
Will you respond to the alerts?
No. This service installs and tests the monitoring. Responding to alerts and fixing outages is separate; for ongoing care see our monthly website maintenance.
Who owns the server and data?
You do. The server and domain are in your name and we only use the access you give us. You can remove our access once the 14 days of fixes are over.
Often ordered with this
© 2026 ZoopCoder