How to Deploy Uptime Kuma from Oikos OpenHub: Self-Hosted Uptime Monitoring

Uptime Kuma is an elegant, open-source status page and monitoring tool designed to check the health and performance of your websites, APIs, and services. It provides a beautiful dashboard, instant notifications upon downtime, and is an excellent self-hosted alternative to expensive monitoring services.

Deploying Uptime Kuma through the Oikos OpenHub Platform-as-a-Service (PaaS) is the fastest way to launch this critical DevOps utility, ensuring it runs reliably with minimal configuration overhead.

1. Accessing the Oikos OpenHub Catalog#

Access the Oikos Console#

Navigate to OpenHub#

  • Locate: Find the OpenHub option in the left-hand navigation sidebar (standardizing the terminology from Marketplace).
  • Selection: Click OpenHub to view the comprehensive catalog of deployable open-source applications.

Search for Uptime Kuma#

  • Identify: You can navigate directly to the application link or use the search bar to find Uptime Kuma.

2. Configuring and Initiating Deployment#

Uptime Kuma requires a stable, persistent volume to save its monitoring history, configuration, and user accounts.

Start Deployment and Configuration Review#

  • Action: Once you locate the Uptime Kuma tile, click Deploy to initiate the deployment wizard.

Review Deployment Settings#

  • App Name: Assign a unique name to your monitoring instance (e.g., production-health-check).
  • Cloud Region: Select a Cloud Region that offers stable connectivity to the services you need to monitor.
  • Resource Allocation: Review the default CPU and RAM. Uptime Kuma is generally lightweight, but consider resource needs based on the number of services you plan to monitor.

Crucial Persistence: Oikos must ensure a persistent volume is mapped to the container directory where Uptime Kuma stores its SQLite database file (data/kuma.db). This is absolutely necessary to retain all monitoring history and configuration across restarts.

  • Finalization: Review all settings, confirm persistence is configured, and click Deploy to commence the container launch process.

Monitor Deployment Status#

  • Process: The container image is pulled, resources are allocated, and the service is started.
  • Completion: Wait for the status indicator to change to Running.

3. Accessing and Initial Setup#

Wait for Completion and Launch#

  • Action: Once the status is Running, click the Open App button.
  • Result: This redirects you to the unique, secure URL of your deployed Uptime Kuma instance.

First-Time Admin Setup#

  • Credentials: On first launch, Uptime Kuma will prompt you to create the initial Admin Account. Define a strong Username and Password.
  • Language: Select your preferred language.
  • Finalize: Click Create to complete the setup and log into the main dashboard.

4. Key Monitoring Features#

Once logged in, you can begin adding monitoring checks:

Adding Monitors#

  1. Select Monitor Type: Click Add New Monitor. Choose the appropriate type:
    • HTTP(s): For checking website and API endpoints.
    • TCP Port: For checking services like SSH, databases (MySQL, PostgreSQL), or custom ports.
    • Ping: For basic network reachability.
    • Steam Game Server: For specialized monitoring.
  2. Configuration: Enter the necessary URL, IP, or port details, and set the Heartbeat Interval (how often the check runs).

Setting Up Notifications#

Uptime Kuma supports integration with dozens of services:

  • Navigate to Settings → Notifications.
  • Configure channels like Email, Telegram, Slack, Discord, Webhooks, or even custom scripts to ensure your team receives instant alerts when a service goes down.

Status Page Creation#

  • Navigate to the Status Page settings.
  • You can create a beautiful, public-facing status page instantly, displaying the current health of your monitored services for your users.

Core Benefits of Deploying Uptime Kuma on Oikos#

1. Real-time Monitoring and Alerts#

Uptime Kuma actively pings your services, and Oikos provides the stable, dedicated environment needed for reliable, real-time health checks, ensuring you get instant alerts upon downtime.

2. Full Control Over Data and Status#

By self-hosting, you maintain full data sovereignty over your monitoring history and status page configurations, avoiding the vendor lock-in and pricing tiers of commercial services.

3. Simplified Deployment and Persistence#

The Oikos PaaS handles the complex container and volume setup. The managed persistent storage ensures your monitoring history is safe and retained indefinitely.

4. Customizable Status Page#

You can quickly deploy a professional, brandable status page to enhance customer trust and transparency regarding service availability.

Official Documentation#

To learn more about advanced features, notification integrations, and custom monitoring types:

Uptime Kuma Wiki: https://github.com/louislam/uptime-kuma/wiki