App Store template

Uptime Kuma

Uptime Kuma is an easy-to-use self-hosted monitoring tool for websites, APIs, networks, and infrastructure.

Launch in your Sealos workspace.

Source Deploy guide Website

Uptime Kuma template preview — Template previewFull screenshot

Template deployments: 12 on Sealos
Deployment: Your own instance
Category: Monitoring

About this template

Overview

Uptime Kuma is a self-hosted monitoring dashboard for websites, APIs, network services, and infrastructure. This template deploys Uptime Kuma 2.4.0 with persistent storage and an optional dedicated MySQL-compatible database on Sealos Cloud.

From the documentation

Uptime Kuma provides configurable HTTP, TCP, DNS, ping, database, WebSocket, and certificate monitors through a browser-based dashboard. It records heartbeat history, measures response times, sends notifications, and publishes public status pages.

How to deploy Uptime Kuma

Choose Deploy now to start Uptime Kuma in your Sealos workspace.
Review enable_external_database in the deployment form.
Launch the template, then inspect the application status and resource cards in Canvas.

Resources to plan for

Start with the resources defined by the Uptime Kuma template. Review CPU, memory, persistent storage, and network allocations for every service in Canvas. Capacity needs depend on your data and workload; monitor usage as they grow.

Template configuration and setup

Access after deployment

Use the application URL or connection details shown in Canvas. Follow the deployment guide for first-time account setup or client configuration, and keep generated credentials available for that step.

Hosting and billing

Sealos monthly plans include compute, memory, storage, and traffic. Size your plan for all deployed services. Software licenses and external AI or API services may have separate terms and charges. Confirm the applicable plan and optional charges in Cost Center.

Compare Sealos resource plans

Read full documentationCollapse documentation

For current cloud charges, refer to Sealos plan pricing. Upstream documentation may reference earlier billing models.

Deploy and Host Uptime Kuma on Sealos

Uptime Kuma Screenshot

About Hosting Uptime Kuma

The Sealos template provisions a single Uptime Kuma StatefulSet, a 1 GiB persistent data volume, a public HTTPS endpoint with WebSocket support, and health probes. SQLite is the lightweight default. A deployment option can provision a dedicated KubeBlocks MySQL-compatible database for installations that prefer an independent database service.

Common Use Cases

Website and API Monitoring: Check availability, latency, status codes, certificates, and response content.
Network Service Monitoring: Track TCP ports, DNS records, ping targets, and WebSocket endpoints.
Incident Notifications: Send alerts through email, chat, webhook, and other supported providers.
Public Status Pages: Publish service health and incident updates for customers or internal teams.

Dependencies for Uptime Kuma Hosting

The template includes the Uptime Kuma container, persistent storage, Service, WebSocket-enabled Ingress, health probes, and Sealos application entry. The optional database mode also provisions KubeBlocks MySQL and an initialization Job.

Deployment Dependencies

Uptime Kuma Documentation - Installation, configuration, and feature documentation
Uptime Kuma Source - Source code, releases, and issue tracker
Environment Variables - Database and server configuration reference

Implementation Details

Architecture Components:

Uptime Kuma: A single StatefulSet serving the dashboard and running monitor checks on port 3001.
Persistent Storage: A 1 GiB volume mounted at /app/data for configuration, users, monitor history, and SQLite data.
Public Endpoint: A Sealos-managed HTTPS Ingress configured for Socket.IO and WebSocket traffic.
Optional Database: A KubeBlocks MySQL-compatible Cluster and initialization Job, enabled through enable_external_database.

The application uses SQLite when enable_external_database is disabled. When enabled, the template injects Sealos-managed database credentials and creates the uptime_kuma database before Uptime Kuma starts.

Uptime Kuma is licensed under the MIT License.

Why Deploy Uptime Kuma on Sealos?

One-Click Deployment: Provision the application, storage, network, and optional database from one template.
Persistent Monitoring Data: Preserve users, monitors, settings, and heartbeat history across restarts.
Instant HTTPS Access: Receive a public domain with TLS and WebSocket routing automatically configured.
Kubernetes Operations: Inspect and adjust the deployment through Sealos Canvas, AI dialog, and resource cards.
Efficient Resources: Start with validated personal low-load CPU and memory settings and scale when your monitor count grows.

Deployment Guide

Open the Uptime Kuma template and click Deploy Now.
Keep Enable a dedicated MySQL-compatible database disabled for SQLite, or enable it to provision an independent database service.
Wait for deployment to complete, typically 2-3 minutes. Sealos then opens the Canvas, where the AI dialog and resource cards can apply later changes.
Open the Uptime Kuma application URL shown in Sealos.

Register and Sign In

On the first visit, Uptime Kuma opens the account setup page:

Select the dashboard language.
Enter an administrator username and a strong password.
Confirm the password and click Create.

Uptime Kuma signs the new administrator in and opens the Dashboard. On later visits, enter the same username and password on the login page. You create and manage these credentials, so store them securely.

Configuration

After signing in, click Add New Monitor, choose a monitor type, enter the target, and save it. Configure notification providers under Settings > Notifications, and create public service pages from Status Pages.

For deployment changes, use the Sealos Canvas AI dialog or open the StatefulSet, storage, network, and database resource cards directly.

Scaling

Increase CPU and memory through the Uptime Kuma StatefulSet card as the number or frequency of monitors grows. Keep one application replica because the persistent SQLite and scheduler topology is single-instance; the optional external database separates database storage while the Uptime Kuma scheduler remains a single replica.

Troubleshooting

The setup or login page does not load

Wait until the StatefulSet reports Ready and refresh the application URL. Check the Uptime Kuma Pod logs and confirm that the Service has a ready endpoint.

A monitor stays down

Verify that the target is reachable from the Uptime Kuma Pod, then review its URL, port, DNS, TLS, authentication, and accepted status-code settings.

Getting Help

License

This Sealos template follows the licensing terms of the templates repository. Uptime Kuma is distributed under the MIT License.

From launch to everyday operations

Why deploy
on Sealos

A shorter path from an app you want to an app you can run. Sealos brings deployment and ongoing operations into one place.

One-click deployment
Start with a ready-made template. Review its configuration and launch from the Sealos console.
Managed Kubernetes
Run on managed infrastructure with built-in workload scheduling and recovery.
Automatic HTTPS
Give your application a public HTTPS endpoint with certificates managed for you.
Persistent storage
Keep application data on persistent volumes across container restarts.
Room to grow
Adjust CPU, memory, and replicas from the console as your workload changes.

One template. Connected resources.

You Get the Whole Stack

Sealos provisions the resources defined by your template and brings them together in your workspace.

App Service
Container workloads with configurable CPU, memory, and replicas.
Public HTTPS URL
An address for your app, with managed TLS certificates.
Database
A database provisioned alongside your app when the template calls for one.
Persistent Volume
Storage for the files and data your application needs to keep.
Environment Variables
Application settings and secrets configured in one place.
Logs & Metrics
Inspect container logs and resource usage from the console.