Elevations, power, cabling, networks and inventory from one infrastructure model, accurate enough to order parts from and to hand to whoever visits the site next.
No account, no trial, no card. Your diagrams live in your browser and never reach us.
Documentation that survives the visit
Most rack diagrams are pictures: true on the day they were drawn, quietly wrong six months later. Blueprint models the infrastructure instead, so the drawing cannot disagree with the rack without telling you.
Over a thousand vendor models: Cisco and Meraki, Fortinet, Palo Alto, Sophos, Ubiquiti, HPE Aruba, RUCKUS, Dell, APC and more, plus generic equipment when the badge does not matter. Filter by height when you know a gap is 1U.
Drag a device to an exact rack unit. A 2U device occupies two contiguous units, half- and quarter-width equipment sits in columns, and a zero-U PDU consumes none. A placement that cannot exist is refused, with the reason.
Mount to either face and see both. The rear shows the PDU and the power feeds; the front shows the ports you patch. Where a rear view has not been modelled the app says so instead of drawing a guess.
Two circuits, a UPS with its real VA and watt figures, PDU outlets, and which PSU each feed lands on. A dual-fed server shows both paths, so “what dies if circuit A drops” has an answer.
What the rack serves beyond its own walls, with the budget: an access point at PoE+ and 22 W, one cable, counted against the switch that feeds it.
A device appears in the rack, the topology, the networks and the inventory because it is one object. Edit it anywhere. The diagram reports its own integrity and the capacity left in each rack.
Racks · both faces
Patch panels and switch ports live at the front; power distribution, feeds and most of the cable mess live at the back. Blueprint models them as different places on the same rack, and can show them side by side.
A device mounted to the rear appears at the rear. Where a manufacturer’s rear view has not been modelled, the app labels it rather than inventing panelling that does not match the metal in front of you.
Connections · networks
Data and power links are the same kind of record: which device, which port, which outlet, which PSU. Add the cable label, the type, the length and the VLAN when you know them, and number a whole run in one action.
Networks hold each VLAN with its subnet, gateway, site and purpose, and catch overlapping subnets or a gateway outside its subnet as you type. Both leave as CSV, so the schedule can go into a ticket, a spreadsheet or a handover pack without being retyped.
Inventory · bill of materials
Every device with its category, library model, rack, face and exact position, plus height, management address, serial number and how many of its ports are connected. The bill of materials is the same data, counted.
This is the part that makes a site visit reusable: the next technician starts from a list that matches the room.
Free, and paid
A documentation tool you cannot try on your own rack is no use to anybody, so the application is not what we charge for. The membership buys the output: the documents that leave the screen with your name on them.
A Blueprint-only membership is planned for people who do not need Packet Lens. It is not on sale yet; until it is, Blueprint’s exports come with the Lens + Blueprint seat. Exports are generated on your device from the diagram’s own vectors, and nothing is uploaded whether you pay or not.
Where it sits
Packet Echo discovers what is connected and which switch port it lives on. Packet Lens explains what the traffic did. Blueprint is where that knowledge becomes documentation somebody else can use.
Nothing is uploaded. Blueprint is a static site: diagrams live in your own browser at blueprint.packetecho.net and never reach us. A backup file is how you move them between machines, so keep one if they matter.
Discover · Investigate · Document
Packet Blueprint is free in your browser. Add the Lens + Blueprint seat when the documents need to leave with your name on them.
