Built by people who had to track this in a spreadsheet.

The problem we kept running into

This product came out of firsthand experience running data-center connectivity work: ordering and installing cross-connects, chasing LOAs and CFAs, migrating circuits between cabinets and providers, and standing up deployments where the physical path mattered and the paperwork had to match it.

The same failure kept repeating. The authoritative record of what was connected to what lived in a spreadsheet — usually several, each slightly different. The renewal dates lived in one person's calendar. The LOA lived in an email thread or a folder nobody else could find. The reason a circuit had been moved lived in someone's memory, and when that person changed roles it left with them.

None of the obvious tools fixed it. DCIM platforms model the facility and are a project to roll out. CRM and ticketing systems track the conversation, not the physical path. Billing systems know the invoice but not whether the circuit on it was decommissioned eight months ago. The gap was a system of record for the services themselves — the layer between all those tools where the spreadsheet had quietly become the source of truth.

Orbnex Connect is that layer. It is deliberately scoped: it holds the circuit, its path, its documents, its cost, its renewal date, and its history, and it is honest about not being a DCIM, a monitoring platform, or an accounts-payable system.

How we build it

• Operational detail is not a nice-to-have A-End and Z-End, panel and port, RPP and breaker, external reference. If a field matters when you are standing in a cage or on a provider call, it belongs on the record.
• The product is the source of truth about the product We would rather ship a smaller, accurate claim than a broad one. Where something is configuration-only or not yet built, we say so — on the pricing page, in the security overview, and in the product itself.
• Your data stays portable Import from a spreadsheet, export back to CSV, cancel yourself. Nothing about the design assumes you are locked in.
• Isolation before features Tenant isolation is enforced in the application and in the database, and tested on every change. That work came before the feature list, not after it.

Where we are today