Skip to main content
No. ipmideck is fully self-hosted and runs entirely on your own network. It makes no external calls, no telemetry, no cloud, no account. It talks directly to your BMCs and stores everything locally.
Any server with an IPMI 2.0 BMC should connect for sensor monitoring, power control, SEL, and FRU. Dell PowerEdge / iDRAC is fully tested; Supermicro, HPE iLO, Lenovo XCC, and IBM IMM are experimental. See Supported Hardware.
Only for the pip install, where the package shells out to your system ipmitool. The Docker image bundles everything it needs, so you only need Docker with --network host.
ipmideck reaches BMCs over UDP port 623 on your local network. Host networking lets the container talk to that port directly instead of sitting behind Docker’s NAT. See Installation.
3000 by default. Change it in config.yaml (server.port) or with the IPMIDECK_SERVER_PORT environment variable.
One year by default (data.retention_days: 365). Override it with IPMIDECK_DATA_RETENTION_DAYS. Older data is cleaned up on the schedule set by data.cleanup_interval.
Yes, set auth.enabled: false in config.yaml, or IPMIDECK_AUTH_ENABLED=false. Only do this on a trusted, isolated network: with auth off, anyone who can reach the dashboard can control your hardware.
FanPilot fails safe. Fans are forced to 100% at or above the critical temperature, and the control loop runs autonomously in the background even with the dashboard closed. See Security for the full hardware-protection details.
Add each BMC from the dashboard. ipmideck manages multiple BMCs from a single instance and shows a panoramic status overview of all of them.