Installing BetterDB Monitor
BetterDB Monitor is a single container (backend + dashboard) that connects to the Valkey or Redis instance you want to watch. Run it whichever way fits your environment — every method ships the same product and serves the dashboard on port 3001 by default.
| Method | Best for | One-liner |
|---|---|---|
| Docker | Quickest start, servers, air-gapped hosts | docker run -d -p 3001:3001 betterdb/monitor:latest |
| Kubernetes (Helm) | Clusters, GitOps, durable / HA installs | helm install betterdb-monitor betterdb/betterdb-monitor |
| npm / CLI | Local runs without Docker, laptops | npx @betterdb/monitor |
| LLM (MCP) | Driving the monitor from Claude or an MCP client | npx @betterdb/mcp |
Storage (in-memory, PostgreSQL, or SQLite), licensing, and every tunable are shared across all methods — see Configuration.
Which should I use?
- Just trying it out — Docker. One command, open
localhost:3001. - Running in Kubernetes — the Helm chart, which layers Secrets, persistence, ingress, and air-gapped licensing on top of the image.
- No Docker on the box — the npm CLI, which walks you through setup.
- You want your AI assistant to query the database — the MCP server.