In development, early access

Exact patch lengths for your entire datacenter.

SpanWise routes each patch along your cable ducts — not as the crow flies — and returns the route, the exact cut length and a patch list your technician can work from.

Route page from a SpanWise patch list PDF: floorplan of a datacenter hall with the route from rack 324 to rack 116 drawn in cyan along the cable ducts.
Actual output — a route page from the generated patch list.

The tape measure is not a planning tool

  • Lengths get estimated, or measured as the crow flies. Either way they're wrong.

  • Too-long patches leave metres of slack coiled in the tray, wrecking airflow.

  • Wrong lengths mean reordering mid-install — and waiting.

  • So your technician ends up on the floor with a tape measure.

One route? Use the free calculator.

Two racks, one patch cord: work out the patch cable length for a single route, with the full breakdown and the standard length to order.

How it works

  1. Import your floorplan

    Load the drawing you already have and set the scale. No asset database, no port mapping.

  2. Draw the cable ducts

    Trace trays, risers and crossings once. Racks and ducts rarely change — neither does this.

  3. Click two racks

    You get the route, the exact cut length and a print-ready patch list PDF.

The output your technician actually wants

First page of a SpanWise patch list PDF: a table of routes with rooms, from/to rack labels, terminations, cut lengths in metres and fibre counts.
Route page from the same PDF: floorplan with the route from rack 77 to rack 121 drawn in cyan, a per-route table and the cut-length build-up line.
  • Patch list with cut lengths, fibre counts and from/to rack labels — ready for the floor.

  • A page per route with the floorplan, the drawn route and a scale bar.

  • Every metre is auditable.

No black box — every metre accounted for

duct 19.8 + risers 0.8 + trunks 0.0 + allowance 4.0 + slack 0.0 = 24.6 m

The cut length is a sum you can check, not a guess: duct distance, risers, trunk segments, termination allowance and slack. It's printed on every route page.

Anonymised example project (PDF)

Not a DCIM — and that's the point

Mature DCIM suites calculate cable lengths too — after you've modelled every device, port and terminator, and for as long as you keep that model true. If you need a digital twin, buy one. SpanWise answers one question: how long is the patch between these two racks?

Days, not quarters

Floorplan in, ducts drawn, first cut lengths the same week you start.

Nothing to keep alive

Racks and cable trays rarely move. Leave the model untouched for a year and the answer is still right.

Works in someone else's datacenter

Integrators, installers and tenants don't get the colo's DCIM. A floorplan and what you can see on the floor is enough.

If you need a DCIM, we're not it. If you need exact patch lengths, we're faster, cheaper — and we ship the cable too.

Why on-prem

One static binary

No stack to run: no database cluster, no containers, no agents. Copy it onto a machine and it works.

Air-gapped friendly

No licence pings, no telemetry, no cloud dependency. Runs where the internet doesn't.

Your floorplans stay yours

Plans and duct layouts never leave your environment.

From length to delivery

SpanWise ends where FiberNxt begins: it gives you the exact length, we supply the patch cable cut to it — tested, labelled, delivered.

A first look

v0.1 preview

Screenshots from the current development build. The UI will change; the numbers won't.

SpanWise v0.1 screenshot placeholder: floorplan import dialog over a hall drawing.
Import the floorplan and set the scale.
SpanWise v0.1 screenshot placeholder: cyan duct lines being drawn over the floorplan, with a live length readout.
Draw ducts, risers and crossings on top.
SpanWise v0.1 screenshot placeholder: two selected racks with the routed path and the resulting cut length of 57.9 metres.
Pick two racks — route and cut length appear.

Register your interest

SpanWise is in development and we're selecting early-access participants. Early users steer the roadmap — tell us how you patch today.

A FiberNxt engineer replies within two business days — no sales sequence.