Devices & the library
Real hardware models, with ports, power and weight built in.
Device types vs devices
A device type is a hardware model — a specific switch, server or PDU, with its U-height, ports, power draw and weight. A device is one of those types placed into a rack. Because the type carries the detail, a placed device already knows its ports (which drive ) and its power and weight (which feed the and ).
The built-in library
Railyard ships 692 device types from the open netbox-community device library — real models from the vendors you actually rack, complete with per-interface detail. Open the library from the tool rail, search it, and add the types you use to your project. Once a type is in your project it appears in the palette, ready to drop into a rack.
Placing devices
With a rack open in Physical mode, drop a device type onto a free span of the elevation. It snaps to the U grid and occupies its natural height. Select it to edit its name, role, face and position in the inspector, or nudge and resize it from the keyboard. Non-rackable gear — a floor-standing unit, a 0U side PDU — is modelled too, so nothing is left out of the design.
Custom device types
When a model isn't in the built-in set, define your own device type — give it a height, ports and power/ weight figures — and it behaves exactly like a catalogue part: it cables, it counts toward the budgets, and it can be reused across the project.
An org-shared library
Custom types you want the whole team to reach can live in an organisation-shared library. Curate it once and every project in the org can pull from it, so a team standardises on the same hardware definitions rather than re-drawing the same custom switch in every estate.