RackFlowsite racks, ports, cleanup plans

Local only

Sites and racks

Create one site, then add MDF/IDF racks. Each rack has its own elevation, devices, ports and cleanup status.

Placement behavior Rack density

Rack Inventory

Zoom

Front elevation - drag/drop - snap to U gridNot saved yet

0devices

0ports

0mapped

0score

Site name Customer / owner

Address / location

Rack room Status

Rack notes

Select a device to edit asset fields, U position, notes and port mapping.

Name / label

Type Color

Start U Height U Ports

Model Serial / asset tag

Management IP Role / function

Notes

Port	To / Room	Trace / patched to	Function	VLAN	Status	PoE	Photo

Set the physical rack. Existing devices are kept where possible.

Rack name Rack standard

Height in U Width Depth

Recommended survey flow: create the rack as it exists today, export JSON as a baseline, duplicate the rack, then build the target cleanup layout.

Use a Supabase project URL and publishable anon key. Data is protected by user login and row level security.

Supabase project URL Publishable anon key

Email Password

Your current user ID: sign in to show

Add engineer by Supabase user UUID Role

Do not paste a service role key here. Browser apps use the publishable anon key only; row level security decides what each engineer can access.

Fast path from spaghetti rack to reliable inventory and cleanup plan.

Create the customer site, then add each MDF/IDF rack.
Survey the current rack first: drag devices in from top to bottom and record model, serial, management IP and role.
For patch panels and switches, fill ports with room labels, function, VLAN, status and PoE.
Use the cleanup score and insights to find missing labels, unmanaged ports, U conflicts and missing cable management.
Duplicate the rack as a target plan before moving real cables.
Sync to Supabase so another engineer can load the same site from a shared static frontend.

Field rule: every cable should have a known near end, far end, service owner, VLAN/function and a reason to stay patched.