Portal hopping
Log into the provider portal, find the right report, and download asset exports by hand — over and over.
Equinix colocation, ingested into plain-English truth.
Stop hopping the portal and deciphering spreadsheet exports. AutoPyl.IT ingests Equinix reports into searchable, plain-English, NetBox-ready cross connects, cabinets, and ports — the foundation for inventory lifecycle management, end-to-end traceability, billing visibility, decommission tracking, and automated trouble tickets.
The old way
Managing colo by portal and spreadsheet is its own full-time job.
Anyone who runs colocation across providers knows the drill — and how much of it is manual, error-prone, and invisible to everyone else.
Messy spreadsheets
Decipher inconsistent columns, merged cells, and cryptic codes just to trace a single cross connect end to end.
Billing drift
Reconcile invoices against what’s actually installed — hunting for recurring charges that no longer map to anything.
Zombie cross connects
Spot the cross connects that should have been decommissioned months ago and are still quietly billing.
Manual trouble tickets
When a cross connect goes down, someone has to notice it, then open the provider ticket by hand.
No shared truth
None of it lives where NetBox, your diagrams, or your other teams can use it — so it’s rebuilt again and again.
The engine
Reports in. Canonical assets out.
The ingestion engine reads Equinix inventory and maps every value to source truth — so cross connects, cabinets, and ports become structured, searchable records instead of disposable downloads.
Equinix exports, mapped — not guessed.
Select the report, target the panels, and ingest. Cross connects, cages, cabinets, and occupied-port reports become linked records, with every final field able to explain exactly where its value came from.
Every cross connect, every field explains itself.
Final endpoints, A/Z counterparts, connector types, and the raw report mappings they came from — side by side. Search a circuit in plain English instead of scrolling a spreadsheet.
Reconcile against NetBox — visually, port by port.
Rear-port A/Z state, NetBox cache status, and ownership are visible right on the grid. Correct terminations stay untouched; gaps become explicit, auditable staged actions.
Follow any cross connect to its counterparty — and the devices on each end.
One click walks a cross connect end to end: the A/Z counterparties it lands on, the cabinets and panels it traverses, and the devices and ports connected on both sides — correlated from the same canonical model, with no spreadsheet cross-referencing.
What it automates
From canonical assets to closed-loop operations.
Once the data is clean and reconciled, the workflows that used to eat your week become automatic.
In development
Billing summary & breakdown
See spend by cage, cabinet, and circuit — and catch charges that no longer map to a live asset.
Decommission tracking
Flag stale cross connects automatically and drive a clean teardown instead of silent recurring cost.
Trigger-based trouble tickets
When a cross connect goes down, open the provider trouble ticket automatically — no waiting for someone to notice.
Cross-connect lifecycle
Add and remove cross connects through guided, auditable workflows tied to the same source of truth.
Fabric failover
Trigger-based Fabric port and virtual-service failover and failback when a path degrades.
Bandwidth changes
Adjust Fabric virtual-service bandwidth on demand, from the same UI that holds your inventory.