Overview
Uptime Kuma is useful for self-hosted uptime monitoring. Better-PaaS gives it a practical home on your own server with a one-click app workflow, domain routing, HTTPS, logs, and persistent storage habits.
Catalog image and ports
Better-PaaS deploys Uptime Kuma from louislam/uptime-kuma:1 on container port 3001 with health checks against /.
- Image: louislam/uptime-kuma:1
- Port: 3001
- Volumes: /app/data
Production notes for this catalog app
Persist monitor history and status-page configuration before relying on it for production uptime alerts.
Why host Uptime Kuma with Better-PaaS
Better-PaaS is designed for apps like Uptime Kuma: small services that need reliable routing, a domain, persistent data, and quick redeploys without manually editing reverse proxy files.
Deployment checklist
Before going live, decide the domain, persistent volume, backup cadence, and any environment variables Uptime Kuma needs. For Uptime Kuma, pay special attention to status pages, alerts, and persistent monitor history.
- Choose the app catalog template or Docker image
- Add required environment variables
- Attach a persistent volume if data must survive redeploys
- Deploy and inspect logs
- Add a custom domain after the app is healthy
Operations after launch
Watch logs during the first deploy, confirm storage survives a redeploy, and include the app data in server backups. If the service exposes an admin area, use a strong password and restrict access where appropriate.
FAQ
Can Uptime Kuma run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does Uptime Kuma need persistent storage?
Most monitoring apps need some persistent storage or database plan. Treat app data and config as something to back up.