Uptime Kuma

TAS Score: S3/3 – D5/5 – A3 / T2

Brief Description

Self-hosted monitoring tool that tracks the availability of websites, services, and network endpoints. Provides a clean dashboard, notifications, and status pages without cloud dependencies.

Architectural Role

Observability layer: monitors your services and alerts you when something goes wrong.

Technical Autonomy

Works without internet (monitors local services)
Stores data locally (SQLite database)
Does not require external accounts
Allows data export (SQLite file, config export)
Provides offline updates (manual via Docker)

Philosophical Assessment (whose.world criteria)

Criterion Status Comments ————————– ——————- ———————— Pause Yes Monitoring can be paused; alerts are user-controlled.

Exit Yes Data can be exported; you can stop using it at any time.

Recoverability Yes SQLite database can be backed up and restored.

Visibility Yes Open source, fully transparent.

External Dependencies Yes None; runs entirely offline. ———————————————————————–

Configuration (Minimal)

Example docker-compose.yml snippet:

services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    container_name: uptime-kuma
    ports:
      - "3001:3001"
    volumes:
      - ./kuma-data:/app/data
    restart: unless-stopped

Minimal Autonomous Server – includes Uptime Kuma for monitoring.

Alternatives

Grafana + Prometheus – more complex and resource-heavy
Nagios – older and harder to configure
Healthchecks.io – cloud-based (not autonomous)

Sources

Website
Documentation
Repository
Docker image
Community -e

Trajectory

Stable — independent.

Uptime Kuma is maintained by a single developer (louislam) with no commercial entity. Simple, focused scope. No enterprise tier. Direction: stable.