Launching today
CapScope
Self-hosted Docker observability in one binary
2 followers
Self-hosted Docker observability in one binary
2 followers
Containers never truly disappear. Persistent container logs, crash snapshots and metrics in one self-hosted binary.
Free
Launch Team
Atlassian LoomShow, don't just tell with Loom
Promoted
What it is
A self-hosted container observability tool for ๐ต๐ผ๐บ๐ฒ๐น๐ฎ๐ฏ๐ฏ๐ฒ๐ฟ๐, ๐๐น๐ผ๐๐ฑ & ๐๐ฒ๐๐ข๐ฝ๐ ๐ณ๐ผ๐น๐ธ๐, ๐ฎ๐ป๐ฑ ๐ฎ๐ป๐๐ผ๐ป๐ฒ ๐ฟ๐๐ป๐ป๐ถ๐ป๐ด ๐๐ผ๐ฐ๐ธ๐ฒ๐ฟ ๐ผ๐ป ๐ฎ ๐๐ถ๐ป๐ด๐น๐ฒ ๐๐ฒ๐ฟ๐๐ฒ๐ฟ. It keeps your logs and metrics around, and it notices when a container crashes. Itโs one Go binary with no Prometheus stack, no external database, and no Loki to babysit. One container, one volume, one password.
Why I built it
Most log viewers show you ๐๐ต๐ฎ๐โ๐ ๐ต๐ฎ๐ฝ๐ฝ๐ฒ๐ป๐ถ๐ป๐ด ๐ฟ๐ถ๐ด๐ต๐ ๐ป๐ผ๐.
CapScope remembers what happened ๐ฏ๐ฒ๐ณ๐ผ๐ฟ๐ฒ ๐๐ต๐ฒ ๐ฐ๐ผ๐ป๐๐ฎ๐ถ๐ป๐ฒ๐ฟ ๐ฑ๐ถ๐๐ฎ๐ฝ๐ฝ๐ฒ๐ฎ๐ฟ๐ฒ๐ฑ.
๐ธ๏ธ Persistent logs in SQLite, still searchable after a redeploy
๐ Crash snapshots with exit code, last log lines, memory and CPU trend, and a plain-language summary (OOM killed? Exit 137? Youโll know)
๐ Restart-loop detection, with a badge in the UI
๐ CPU and memory charts from 15 minutes up to 7 days
๐ก An access-log dashboard from your reverse proxy logs (status codes, top paths, client IPs)
๐ Deploy markers, so you can line up crashes with the release before them
๐ Secret redaction that masks JWTs, tokens, and credentials before they hit disk
๐ Full-text, regex, or raw SQL search over your logs
Who itโs for
๐๐ผ๐บ๐ฒ๐น๐ฎ๐ฏ๐ฏ๐ฒ๐ฟ๐ ๐๐ถ๐๐ต ๐ฎ ๐ฑ๐ผ๐๐ฒ๐ป ๐ฎ๐ฝ๐ฝ๐ ๐ผ๐ป ๐ผ๐ป๐ฒ ๐ฏ๐ผ๐ , self-hosters on CapRover, Coolify, Dokploy, Dokku, Portainer, or plain Docker, and Cloud & DevOps engineers who want answers ๐๐ถ๐๐ต๐ผ๐๐ ๐ฟ๐๐ป๐ป๐ถ๐ป๐ด ๐ฎ ๐๐ต๐ผ๐น๐ฒ ๐๐ฟ๐ฎ๐ณ๐ฎ๐ป๐ฎ ๐๐๐ฎ๐ฐ๐ธ.