Most DCIMs are systems of record — great once your estate exists, painful for planning one. Railyard fills that gap: draw the racks, drop in devices from a built-in library, wire up structured cabling and power, let the design review catch the mistakes — then export clean, importable data so your DCIM starts life correct.

One document is the contract end to end — the same Project JSON flows through the editor, the REST API and every export, so what you sketch is exactly what you ship.

• 📐 Visual estate editor — a five-level hierarchy from location down to the rack unit, with a pannable rack board and floor-plan navigation. Local-first: the whole editor runs in your browser with no sign-in.
• 🔌 Structured cabling — named ports per device, MPO breakouts, patch-panel pass-through and trunks, with end-to-end circuit tracing through the panels.
• ⚡ Power & thermal — feed devices from PDUs, with per-rack load (kW), heat (BTU/hr) and weight, and over-budget warnings right on the board.
• 📚 690+ device library — the netbox-community device-type library built in and searchable, plus your own organisation-shared catalogue.
• 👥 Live collaboration — several people edit one estate at once, in real time (server-authoritative, last-writer-wins).
• 📤 Import-ready export — NetBox / Nautobot CSV and JSON, plus installer reports (cable schedule, cable labels, power) generated in the browser.
• 🧩 Extensible — a REST API with personal access tokens, an MCP server for AI agents, and DCIM sync plugins.

Open railyard.sh — explore the example estate with no account, or sign in to save your work and collaborate. Everything you design exports as clean, importable data, so there's no lock-in.