all work
Private network — only Traefik is publicly exposed.
in dev infrastructure · ops Apr 2026
Self-hosted observability stack
Real-time monitoring, alerting and access control for my Hostinger VPS — without a SaaS bill.
[ flow ]
Internet :80 / :443 only
Traefik edge · bcrypt · rate limit
Beszel host & container metrics
Uptime Kuma service checks
Dozzle live container logs
Telegram bot private channel · my phone
[ approach ]
- edge
- Traefik fronts everything; only :80/:443 exposed publicly.
- auth
- Every internal dashboard sits behind basic auth with bcrypt-hashed credentials.
- signals
- Beszel for resources, Uptime Kuma for service checks, Dozzle for live logs.
- alerting
- Uptime Kuma → small relay → private Telegram channel.
[ claude / me ]
claude
Read docs faster, drafted the middleware chain, and pushed back on my threat model.
me
Picked the tools, designed the auth boundary, wrote the Traefik config, tuned what's worth alerting on at 02:00.