Network closets · early prototype

Plan the network closet before you build it.

Infranatomy turns one design file into a closet pack: the rack in 3D, the PoE budget, UPS runtime, a cable schedule and a parts list. For MSPs, cabling contractors and IT teams.

Everything shown is sample data.

The closet problem

Most closets grow one patch cord at a time

Ports run out, labels go missing, and the UPS predates the cameras. At refresh time, nobody can say what the closet must carry.

How it works

A digital twin of the closet, before you build it

Describe the rack, devices, links and power in one design file, and Infranatomy builds a digital twin of the closet from it.

Sample design: a 12U closet rack.

See the closet before anyone racks it

Front, rear and room views, with every device, cable and U position labeled.

Sample design. Every claim carries an evidence label.

PoE, power and links checked before you order

Checks every link at both ends, the PoE budget with one supply lost, UPS runtime and single points of failure.

Sample design, from the same file as the 3D rack.

The pages a closet proposal needs

Topology with HA and failure views, an L1 cable schedule, L2, L3 and zone pages, and a parts list as HTML, CSV and JSON.

12U MDF (sample design)

A branch-office closet with a firewall pair, two PoE switches and a UPS.

Sample design in 3D: a 12U open rack frame for a small network closet. From the top: the carrier's fiber panel at U12, the carrier's box on a shelf at U11, a WAN switch at U10, a cable manager at U9, a firewall pair at U8 and U7, a patch panel at U6, two access switches at U5 and U4, a second patch panel at U3, and a 2U UPS at U1 and U2. The network gear is labeled with its rack unit; the UPS and the rear PDU have no labels in the render. — Sample data 12U rack, front view

Rack units, U12 to U1

U12 · Carrier A fiber panel
U11 · Shelf with the carrier's box (NID)
U10 · WAN switch A, shared by both firewalls
U9 · Cable manager
U8 · Firewall 1, primary
U7 · Firewall 2, standby
U6 · Patch panel 1
U5 · Switch 1, PoE access
U4 · Switch 2, PoE access
U3 · Patch panel 2
U3 rear · PDU A, fed from the UPS
U1 to U2 · UPS A: 20.8 min at the design load

PoE: 535.68 W for 40 assumed endpoints · 874 W available with one supply lost
UPS: 20.8 min at 791.6 W · 11.7 min at full nameplate load
Single points of failure: 128 failures walked · 16 found
Parts list: 37 lines · HTML, CSV, JSON

Sample L1 cable schedule from the 12U sample design, grouped by purpose. Each row gives the cable's purpose, both ends and their ports, the cable ID, the assembly SKU, the medium, the speed, the length and the stored slack, with values marked derived, assumption or template. — Sample data 12U cable schedule

Sample resilience page from the 12U sample design: a declared-topology cut analysis listing 16 accepted single points of failure, each tied to the accepted risk behind it (a single carrier circuit, or one feed and one UPS), with what sits outside the claim and the unverified shared risks above the list. — Sample data 12U resilience page

Sample parts list from the 12U sample design, a firewall HA pair over a two-switch access stack: 37 lines and 159 items, PoE 535.68 W needed and 874 W available with one supply lost, CSV and JSON downloads, then quantities, part numbers and descriptions. — Sample data 12U parts list

For MSPs and cabling contractors

Closet refresh proposals your client can follow

Show your client the new closet before they sign: rack views, topology, cable schedule, PoE and UPS numbers, and a parts list that opens in a spreadsheet.

Every number says whether it was measured, cited or assumed. The pack is a concept to price, not an install plan.

Larger racks

Planning the network side of a data-center rack?

The same file covers the network gear in a 42U rack. Servers, storage and GPUs are not modeled yet.

The 42U sample

The full-height sample design shown as a 3D rack. A firewall pair sits above a two-switch access stack, with each device labeled at its rack unit. — Sample data 3D rack view

Sample 2D network topology marked CONCEPT. A carrier hand-off connects to a FortiGate 120G firewall pair and a Cisco Catalyst 9300 switch stack. Addresses are masked. — Sample data 2D topology

Sample L1 physical page from Infranatomy showing the building entry plan for a one-site design. — Sample data L1 cabling page

Sample parts list from the full-height sample design, for a firewall pair over a two-switch access stack. It lists quantities, part numbers and descriptions, with a PoE budget and license summary at the top. — Sample data Parts list

Demo

Watch a design file turn into a closet plan

Clip coming soon

Pricing

Planned launch prices

Tell us how many closets you plan a year, and we will email you when plans open.

Solo

$79 per closet pack

Planned launch price. Nothing is charged during early access.

For one closet.

One closet pack, paid once
3D rack, cable schedule and 2D pages
Parts list as HTML, CSV and JSON

Team

$149 a month

Planned launch price. Nothing is charged during early access.

For a small MSP or IT team.

Everything in Solo
Unlimited closet packs
Up to 3 users

Organization

From $399 a month

Planned launch price. Nothing is charged during early access.

For larger teams with many closets.

Everything in Team
More than 3 users and unlimited closet packs
Price set with you on a demo call

Questions from closet buyers

What does Infranatomy do today?

It plans one closet at a time from a design file. It knows FortiGate, FortiSwitch, Cisco Catalyst 9300 and Cisco Meraki MX and MS, plus patch panels, cords and power.

Will it work for a short or wall-mount rack?

Yes, from 1U to 60U. A design can name a wall-mount cabinet, but the 3D view draws every rack as an open frame.

Can I order parts straight from the parts list?

No. Every page and document the engine writes is marked "concept, not for procurement or installation". It shows what to check. It does not replace a site survey.

What doesn't it do yet?

It never reads a running network, so it plans the closet you will build, not the one on the wall. You write the file by hand, and it models network gear only: no servers, storage, GPUs, heat or airflow.

What is coming?

Plain-language input, servers and storage, and more vendors. Not built yet; no dates.