Monitoring
Uptime Kuma
Simple self-hosted uptime checks and alerting for services you care about.
What this service needs
Ports
- 3001/tcp (web)
Storage
- Persistent app database
- Notification/integration configuration
Notes before you ship it
- Useful as a lightweight operational layer, but define who responds to alerts and when.
- Monitors are only as good as the notification routes and maintenance process behind them.
Want this in your stack without the guesswork?
We can assess fit, deployment shape, backup approach, and what it will take to run this service like real infrastructure instead of a side project.