Repository navigation
FAQ
The Lab edition is the free, self-hosted community build. It is a complete single-site DCIM with the core views (3D, inventory, cabling, power, capacity, IPAM, monitoring), sized with these limits: 1 site, 2 rows, 4 cabinets, and 2 IPAM prefixes.
The full edition adds multi-site with larger floors, a tenant / colo customer portal, work orders and an audit trail, reporting and PUE, scoped API tokens, vendor HVAC / power / genset drivers, and SSO. Those features are not part of the Lab image.
No. The Lab runs entirely on its own Docker Compose stack. InfluxDB is only needed if you want live temperature and power telemetry. Everything else (inventory, cabling, capacity, IPAM, the 3D scene) works without it.
No. For live monitoring it reads a small, fixed schema from InfluxDB, and you fill that schema from any source (SNMP, Modbus, IPMI, or a script). See Live Monitoring.
No. Cabinets that are not part of your saved layout are hidden on purpose, so a smaller floor shows bare tiles instead of empty racks. Generate the cabinets you want in the Site Configurator and they appear.
Those are generated schematic placeholders, drawn for any device type that has no real photo yet. To install real product photos, use Download real images in Rack Manager. See Device Library and Images.
Generate a scrypt hash and set LOCAL_AUTH_PASSWORD_HASH, then restart. Full steps are in Installation. Also set LOCAL_AUTH_SECRET, or existing sessions are invalidated on each restart.
Everything lives in Docker volumes: pgdata, uploads, and devicetype-library. Back those up, or dump the database with pg_dump. See Configuration.
Yes, in an unprivileged LXC with features: nesting=1,keyctl=1 so Docker works inside it. See Installation.
Pull the latest code and rebuild:
git pull
docker compose -f docker-compose.lab.yml up -d --buildThe API runs prisma db push on boot, so schema changes apply automatically. Your data in the volumes is preserved.
RackDaddy Lab is free to use, self-hosted. Modifying or redistributing it needs permission. See the LICENSE file in the repository for the exact terms.
Open an issue on the GitHub repository.