Circuit lifecycle management
The system of record for cross-connects and circuits.
Track every service from A-End to Z-End, keep LOAs/CFAs, costs, renewals, migrations, and facility details attached to one operational record, and flag decommissioned services that may still be carrying MRC.
No signup required to try the import. Sample data is available. Uploaded files stay in your browser.
Circuit record · sample data
One record, full lifecycle
One operational record for the complete circuit lifecycle
A service is ordered, installed, documented, moved, and eventually renewed or disconnected. In Orbnex Connect that whole arc lives on one record instead of five spreadsheets and an email thread — which is what makes a question like "what is this, where does it land, what proves it, and what does it cost us" answerable by anyone on the team rather than one person.
Every circuit record holds
- PathA-End and Z-End, with the physical route between them
- PartyProvider or carrier of record, and the facility it lands in
- HandoffCabinet, panel, port and demarc detail
- ReferenceYour external case, ticket, order or provider circuit ID
- ProofLOA/CFA documents and path proof, versioned per record
- CostMonthly recurring charge and the renewal date
- HistoryMigrations and an audit trail of every change, with owner and timestamp
- PowerRPP, panel and breaker context where the service depends on it
How it works
From spreadsheet to operational control
You already have the data. The work is getting it into a shape your whole team can operate from.
Import existing records
Upload a CSV or Excel export. Orbnex Connect suggests the column mapping and you confirm it — there is nothing to rebuild by hand.
Validate and normalize
Required fields are checked, values are normalized, and duplicates are flagged by both circuit ID and physical path. You review what was flagged, then publish.
Operate from a shared workspace
One workspace for the team, with roles, saved views, CSV export and an audit trail on every change. Re-import later and records reconcile against what is already there.
Try it on your own spreadsheet first
The import sandbox runs entirely in your browser. Your file is parsed locally, is never uploaded, and nothing is stored — so you can see how your own columns map before you create an account.
No signup · sample data available · nothing leaves your browser
Capabilities
What teams can do with Orbnex Connect
Inventory & path
Circuit inventory and A-to-Z tracing
Search and filter the whole estate, then open any service to see its physical route end to end.
- A-End, provider, facility and Z-End on every record
- Search by circuit ID, customer, provider, facility or external reference
- Bulk edits and CSV export from any view
- Saved views for the filters you run every week
Documentation
LOA/CFA and facility documentation
Generate provider-ready paperwork from the record itself, so the document and the inventory can't drift apart.
- LOA, CFA and A-to-Z path proof as versioned PDFs
- Internal commercial data excluded from provider-facing output
- A queue of records still missing document proof
Commercial visibility
Renewals, MRC, and potential recoverable spend
Every record carries its cost and renewal date, so the exposure sitting in your inventory is something you can sort and work through.
- Renewal buckets — overdue, 7, 30 and 90 days — with the MRC attached
- Flags records marked decommissioned that still carry MRC, for billing review
- A data-health score across path completeness, documents, renewals and MRC coverage
- An optional weekly email digest of the same queues
Change & capacity
Migrations, power context, and audit history
Move a service without losing the story: what the old path was, who owned the rollback, and what proved the change.
- Plan, validate, execute and close out, with the old path preserved
- RPP, panel and breaker capacity checks before a cabinet change
- Fiber strand capacity and diversity warnings at a site
- An audit entry with owner and timestamp behind every change
Who it's for
Built for the teams that own physical connectivity
Colocation operators
One shared view per customer
Sales engineering, project management and operations answer connectivity and capacity questions from the same records.
Carriers & providers
Clean handoffs
Provider demarc, customer port, LOA/CFA and external reference stay attached to the service they belong to.
Enterprise network teams
Inventory you can trust
Hundreds of cross-connects across multiple providers and facilities, with cost and renewal dates in the same place.
Project & migration teams
Change with a record
Plan a move, assign the owner, keep the old path, and close out with proof rather than an email thread.
Where it fits
Fits into your existing stack
Orbnex Connect takes over the layer where physical connectivity is actually tracked today. It is not trying to replace the systems around it.
Replaces
- Circuit spreadsheets, and the stale copies of them
- Renewal calendars kept by one person
- Hand-filled LOA/CFA templates
- Disconnected email threads about a single circuit
- Institutional memory that leaves when someone does
Complements
- DCIM — Connect tracks services, not a full facility model
- CRM and ticketing — link by case, ticket or order reference
- Billing and AP — Connect holds your record of cost, not the invoice
- Network monitoring — the physical and commercial record, not live telemetry
- Provider portals — your own record, across every provider at once
Nothing has to be switched off to adopt Connect. It is a layer, not a migration.
Security & ownership
Security, ownership, and enterprise readiness
The controls below are the ones actually implemented today. We list what we do, not what we aspire to.
Workspace-scoped data isolation
Your workspace is resolved from the authenticated session on the server and re-checked against membership on every request. A client cannot reach another tenant's data by supplying a workspace ID.
Row-level security in the database
Isolation is enforced in the application and again by PostgreSQL row-level security — two independent layers rather than one.
Cross-tenant tests on every change
A cross-tenant test suite and a static isolation check run in continuous integration on every pull request, and fail the build on an unscoped tenant query.
Append-only audit history
Record changes, migrations, membership and billing events are written to a workspace-scoped audit log, each with an owner and a timestamp.
Stripe-hosted payments
Checkout and billing are handled by Stripe. Card details never reach our servers, and Stripe webhooks are signature-verified.
Export and portability
Export any view to CSV whenever you want, and cancel from the billing portal yourself. The operational record you build stays yours.
Authentication and access control
Identity comes from the session token, never the request body. Write access is role-gated server-side, plan limits fail closed to the most restrictive tier, and login, signup and reset endpoints are rate limited.
Dedicated environment option
Enterprise deployments can run on their own hostname and their own database, fully separate from the shared environment, with no silent fallback to it.
The public sandbox touches nothing
The import sandbox on this site parses your file in the browser. It makes no API or database call and stores nothing, so it cannot reach customer data at all.
The security page covers each control in plain language, along with our data-retention and deletion process, the limits of what we can attest to today, and the certifications we do not hold. Security questionnaires and vulnerability reports go to info@orbnexlabs.com.
Read the security overview →Pricing
Pick the plan that matches your footprint
Every plan includes unlimited circuits, A-to-Z path records, migration planning, renewal and MRC tracking, CSV import and export, and the full audit history. Facilities and users are what scale.
Starter
A small team and up to two facilities. The right start if one person owns the spreadsheet today.
- 2 facilities · 3 users
- Unlimited circuits
- Email support
Growth
More facilities and more users, same workflow. Step up when Starter's limits are what's in the way.
- 5 facilities · 10 users
- Provider records and tasks
- Audit exports
Professional
The complete operational workflow, including documents, power controls, and reporting.
- 10 facilities · 25 users
- LOA/CFA and path-proof documents
- Power/RPP capacity controls
- Renewal, spend and audit reporting
Secure checkout via Stripe · manage or cancel anytime
Enterprise
Unlimited scale, with a dedicated environment and a security review. For teams with isolation or procurement requirements.
- Unlimited facilities and users
- Dedicated environment: your own hostname and database
- Security review and guided onboarding, with your data loaded first
Orbnex Connect is early, and we say so. We are onboarding a limited number of founding teams: we load your existing spreadsheet before your first login, your rate is fixed for twelve months, and you get a direct line to what we build next. Month-to-month through Stripe, with CSV export whenever you want it.
See it on your own records
Map your spreadsheet in the browser in a couple of minutes, or have us walk through it with you.