Skip to main content

Fully Managed
Uptime Kuma
as a Service

Deploy Uptime Kuma as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Uptime Kuma is an open-source monitoring tool that watches HTTP endpoints, ports, certificates, databases, and push heartbeats from your own services. It produces public status pages and routes alerts through Slack, Discord, Telegram, email, and 90-plus other channels — combining the convenience of a hosted uptime monitor with the privacy and cost control of self-hosted infrastructure.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

Uptime Kuma

Uptime Kuma

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Uptime Kuma Preview Image

ABOUT THE SOFTWARE

What is ​Uptime Kuma

Uptime Kuma is an open-source self-hosted monitoring tool — an alternative to UptimeRobot, Better Stack, and Pingdom that you run on your own infrastructure. It watches HTTP, TCP, DNS, ping, push, MQTT, Docker, Steam, and OracleDB endpoints and exposes a Vue 3 dashboard plus a public status page on a domain you own.

The project was created by Louis Lam in 2021 as a self-hostable replacement for the kind of monitor most teams used to pay for. It is MIT-licensed, written in Node.js (version 20.4 or newer since v2), and currently sits at roughly 87,000 stars on GitHub with more than 100 million Docker image pulls. The latest stable release, v2.3.2, was tagged on 3 May 2026.

v2.0 (20 October 2025) was the biggest change in the project's history. It switched to rootless Docker images, replaced the regex-based SMTP templating with LiquidJS, removed the legacy JSON Backup and Restore feature, and refreshed the UI. The 2.3 line continued that work with OracleDB monitor support, collapsible status-page groups, sub-millisecond TCP graph fixes, Prometheus metric deduplication, and explicit SQLite-locking patches in v2.3.1 and v2.3.2 (issues #7307 and #7312). Active maintainer is Louis Lam, working on top of a large community translator pool through Weblate.

FEATURES

What ​Uptime Kuma does

Uptime Kuma watches endpoints, ports, and services on a configurable interval, records heartbeat history, displays it on a Vue 3 dashboard, and broadcasts incidents through 90-plus notification channels. Public status pages render uptime percentages and incident timelines on your own domain.

HTTP, HTTP keyword, HTTP JSON query

Check that a URL returns 200, contains a specific string, or returns JSON matching a JSONPath expression. The third type catches broken-but-200 pages a vanilla check would miss.

Push monitor (heartbeat)

A monitor that expects YOUR service to ping IT on a schedule. Use it for cron jobs, queue workers, scheduled backups, and Stripe webhooks. Silent failures stop being silent.

Public status pages

Hosted on a subdomain you control, branded with your logo, grouped by service (e.g. API, Web, Background). Visitors see uptime history and active incidents without authenticating.

Maintenance windows and tags

Schedule planned-downtime windows so monitors don't page during deploys. Tag monitors by client, environment, or service for filtering in large instances.

TCP, DNS, ping

Port-level reachability, DNS record lookups with TTL tracking, and ICMP ping for hosts that don't speak HTTP. Useful for databases, mail servers, and legacy infrastructure.

Docker, Steam, MQTT, WebSocket, OracleDB

Container-status checks, game-server pings, MQTT broker heartbeats, raw WebSocket handshakes, and (since v2.3.0) OracleDB connectivity. Monitor types for less-conventional infrastructure.

90+ notification channels

Email (SMTP), Slack, Discord, Telegram, Pushover, Gotify, ntfy, Webhook, Microsoft Teams, Mattermost, PagerDuty, Opsgenie, Twilio SMS, plus 75 more. Per-monitor routing rules let alerts go to the right channel.

API and Prometheus export

Metrics exposed at /metrics for scraping into Prometheus and Grafana. Push-monitor endpoints at /api/push/<token> for integration with anything that can curl.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed ​Uptime Kuma

On 1 December 2024 UptimeRobot's updated Terms of Service banned commercial use of its free plan. Teams that had been monitoring production for years on the free tier got pushed onto $9, $38, or $69 monthly plans — or moved to self-hosted Uptime Kuma. Most quickly discovered the operational tax of running it themselves.

There is also a harder problem: Uptime Kuma probes from one host. If the host running Kuma goes down, you find out from a customer, not from a tool. The most-upvoted feature request is for distributed remote probes; it has not shipped. Self-hosters work around it by pointing a hosted heartbeat at the Kuma instance from a different provider — a side-channel that needs its own monitoring.

We run Uptime Kuma on the platform ourselves. Every managed instance defaults with a 90-day heartbeat retention policy, nightly off-host snapshots of the /app/data volume, and a pre-warmed SMTP relay so alert email works from minute one. We also run a second-region meta-monitor on every customer instance, so if the Kuma host goes down we get the alert and follow up the immediate fix.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run ​Uptime Kuma on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

12-PERSON MANAGED-SERVICE PROVIDER

80 client endpoints, one dashboard, one chat channel

Runs Uptime Kuma in Germany with 180-day retention, and 80 monitors tagged by client. Each tag drives a private status page on a customer-domain reverse-proxy host rule. Slack routing splits tier-1 clients to #noc-critical and tier-3 to #noc-watch. Monthly client uptime reports email out via the platform SMTP relay.

5-PERSON B2B SAAS STARTUP

Production, staging, payment webhooks, all in one dashboard

Runs in Brazil on the base €9 instance. 28 monitors covering production API (HTTP keyword on /health), staging, marketing site, Stripe webhook receiver (push monitor every minute), and Postgres TCP on the app subnet. Public status page at status dot example dot com on a Cloudflare front. PagerDuty for P1, Discord for everything else.

FEDERATION COMMUNITY ADMIN

PeerTube, Mastodon, Matrix, and the .well-known endpoints they break on

Runs in Finland, 365-day retention for transparency reports. 22 monitors covering each Fediverse service's main port plus the /.well-known/host-meta and /.well-known/webfinger endpoints that federate independently. ntfy push notification to the admin's phone, public status page open to the community at status dot community dot tld.

COMPARISON

Four ways to run ​Uptime Kuma

Four common paths to running Uptime Kuma: pay UptimeRobot or another hosted monitor instead, rent a VPS and run it yourself, run it on a home or office server, or have DANIAN manage it for €9 per month. Costs and the trade-offs each path makes are below.

 PATH10 MONITORS100 MONITORS200 MONITORS YOUR OPS TIMENOTES
UptimeRobot (the hosted SaaS being replaced)
$9/mo Solo$38/mo Team$69/mo Enterprise0 hr/mo1-minute checks; 3 seats on Team; commercial use blocked on Free since 1 Dec 2024
Self-host on a $24/mo production-class VPS
$44/mo infra$44/mo infra$44+/mo infra1–4 hr/moOS patching, TLS renewal, /app/data backup;
Home server (HP ProLiant ML30 Gen10, ~€800–1,500)
€85–187/mo€85–187/mo€85–187/mo2–4 hr/moHardware amortised over 36 months, electricity, business internet with static IP, off-site backup target; no native multi-region probing
DANIAN Managed ​Uptime Kuma€9/mo€9/mo€9/mo0 hr/mo90-day retention, nightly snapshots, SMTP relay, second-region meta-monitor, 24/7 chat, region of your choice across 21 datacenters

BY INDUSTRY

​Uptime Kuma for specific industries

Uptime monitoring lives in different operational contexts depending on industry. A managed-service provider's instance looks nothing like an e-commerce site's, and an agency monitoring 30 client WordPress sites needs different tagging than a SaaS startup monitoring its own three apps. Five industries with the configurations that fit them below.

Managed-service providers contract on uptime — typically 99.5% to 99.9% endpoint availability per client, with service-credit triggers tied to monthly downtime totals. One Uptime Kuma instance per MSP, with 180-day heartbeat retention is the typical shape.

Monitors get tagged by client, each tag drives a private status page exposed on a customer-domain reverse-proxy host rule, and Slack alert routing splits tier-1 clients (60-second probes, instant notification) from tier-3 (5-minute probes, daily digest). Monthly client uptime reports template through LiquidJS with the heartbeatJSON variable, then email out via the platform SMTP relay. One instance comfortably holds 8 to 15 SMB clients at 5 to 10 endpoints each, with headroom to about 150 monitors before we move you to a larger plan.
E-commerce sites pay for downtime in cart abandonment. The cross-industry figure Gartner cited in 2014 was $5,600 per minute; Ponemon's 2016 update placed small and medium businesses in a more realistic $137 to $427 per minute range. The configuration on DANIAN that matches: a 20-second probe interval on /cart, /checkout, and the payment-gateway webhook.

An HTTP keyword check on /checkout looks for the "Place Order" button text — that catches the broken-but-200 case where a PHP error pushes the checkout form off the page but Apache still returns success. SMS plus Slack alert on first failed check, status-page incident auto-published after the second consecutive failure, marketing-page monitor downgraded to 5-minute polling. A typical storefront runs 12 to 20 monitors per domain.
Public SLA pages have settled on 99.9% monthly availability as the B2B SaaS norm — 43 minutes 49 seconds of allowed downtime per month, the figure you commit to in MSA boilerplate. Uptime Kuma's status page is the public-facing artifact.

The default configuration on DANIAN: HTTP JSON Query monitor on /health checking for an expected JSON response, push monitors on every cron job and background worker (the queue worker, the nightly database snapshot, the Stripe webhook receiver), and an HTTP keyword check on the marketing site. Status page at status dot your-domain, grouped into API, Web, and Background sections so a partial outage does not read as full downtime. PagerDuty webhook for P1, Discord for everything else. A typical seed-stage SaaS runs 25 to 40 monitors across production and staging.
Marketing-agency retainers increasingly itemise uptime monitoring as a $10 to $50 per-site monthly deliverable. The agency configuration on DANIAN: one Uptime Kuma instance per agency, one tag per client, white-label status pages per client on reverse-proxy host rules (status.clientname.com pointing at the same Kuma instance).

Each client gets three monitors: SSL certificate expiry, DNS A-record check, and an HTTP keyword check that looks for the footer copyright text. The footer-text check is the one that catches the WordPress white-screen-of-death failure mode where PHP errors but Apache still returns HTTP 200. Tag-based Slack routing sends client name plus monitor name into the agency's #client-alerts channel. A 6-person agency monitoring 30 WordPress sites typically runs about 90 monitors across one Kuma instance.
Higher-education and edtech procurement increasingly references EN 301 549 accessibility-availability language, and most LMS suppliers contract for 99.5% uptime during academic-term hours. The DANIAN configuration for education customers: maintenance windows pre-scheduled around exam-period freezes (no patches during finals week), HTTP monitors on the LMS login flow, the video-streaming origin, the LTI tool-launch endpoint, and per-region CDN edges.

Slack alerts route to a faculty-ops channel during business hours and to an on-call rotation at night. The status page is kept private day-to-day and goes public during incidents for student communication, with incident messages templated to avoid acronyms students might not recognise. A typical multi-tenant LMS runs 30 to 60 monitors covering web tier, video origin, OAuth endpoint, and CDN edges across regions.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

Comfortable headroom up to roughly 200 monitors per €9 instance. Above that we can upgrade you to a larger plan with more vCPU and RAM.
We run a meta-monitor from a different region, so the failure mode of the monitor that monitors everything being the thing that died does not apply on managed DANIAN. Our chat opens on the alert, we restart or restore from the previous snapshot, and it's back online.
No. Uptime Kuma covers HTTP keyword, HTTP JSON query, TCP, DNS, ping, push, Steam, Docker, MQTT, WebSocket, and (since v2.3.0) OracleDB. It does not run headless-browser scripts. If you need login-flow synthetics, pair Uptime Kuma with a separate hosted tool — they coexist fine on the same status-page architecture.
Not yet. Issue #128 has tracked this since 2021 and has not shipped. On a managed DANIAN instance, anyone with the dashboard password has full edit and delete access to every monitor. If you need separate read-only viewers, the standard pattern is a public or password-protected status page per audience.
You cannot bring history — Uptime Kuma has no UptimeRobot or Better Stack importer. The standard pattern is to export your monitor URLs from the existing tool as CSV, then bulk-create them on the new instance using the AutoKuma kuma CLI. Past uptime history starts fresh.
90-plus providers: email (SMTP), Slack, Discord, Telegram, Pushover, Gotify, ntfy, generic webhook, Microsoft Teams, Mattermost, PagerDuty, Opsgenie, Twilio SMS, and dozens more. Each monitor can route to one or more notification configurations, so production goes to PagerDuty while marketing-site checks go to a daily Discord digest.
We snapshot the /app/data volume nightly to off-host storage on a different location. The legacy in-app JSON Backup feature was removed in v2.0; the file-level snapshot is the only supported method, and it is the only method we use.
v2 requires Node.js 20.4 or newer, switches Docker images to rootless, replaces regex-based SMTP templating with LiquidJS, removes JSON Backup and Restore, and rewrites heartbeat-data aggregation (the upgrade to v2 can take minutes to hours on first launch depending on history size). We run v2.x on every managed instance.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Yes. Every managed instance ships with a pre-warmed SMTP relay so alert email works out of the box. If you would rather use your own provider, give us the credentials and we wire it in. SMTP body templating since v2.0 uses LiquidJS variables — we can write the templates with you on chat.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed ​Uptime Kuma for 7 days

No card. Cancel from the dashboard.