Your Infrastructure Lives in One System. Now Procurement Can, Too.

From what exists, to how it gets there. Asset Lifecycle is now generally available on the NetBox Labs Infrastructure Intelligence Platform, extending the system of record into procurement.

Your bill of materials lives in a spreadsheet. Your purchase orders live in a vendor portal. Your shipment status lives in email, your install records in whatever doc someone updated last. Nothing ties what you designed to what you bought, what shipped, and what actually went in the rack. At hundreds of racks across multiple sites, that gap creates drag and introduces drift, slowing infrastructure deployment and introducing risk.

NetBox Asset Lifecycle, now generally available, closes that gap. A commercial capability of the NetBox Labs Infrastructure Intelligence Platform, it extends the #1 network & infrastructure system of record from documenting what exists in your infrastructure to managing how it gets there: a native procurement pipeline of Bills of Materials, Purchase Orders, Shipments, and Spares, with installation handled as a workflow against the DCIM objects you already model.

Built on the NetBox foundation your team already runs, the procurement workflow layers on top of the model you trust. No fork, no migration, no new data model to learn.

Procurement is now an infrastructure problem

AI and hyperscaler buildout is making procurement a first-class operational concern. Hyperscaler capex alone is projected to reach $650–700 billion in 2026, and Gartner forecasts 2026 data center systems spending will surpass $788 billion, up roughly 55.8% year over year. Lead times have stretched into multi-year territory: power transformers now average about 128 weeks, and Gartner expects 40% of existing AI data centers to be power-constrained by 2027. Procurement at this scale cannot run on email and spreadsheets.

It is also the next workflow asking for engineering-style rigor. Teams already apply auditable trails, structured workflows, and integration-first patterns to change control; Gartner expects 30% of enterprises to automate more than half of their network activities by 2026, up from under 10% in mid-2023. The same primitives (scope rules, status transitions, named approvers, a full REST API) now belong in the BOM, PO, and install pipeline. The system of record has to span more than what runs today: what is on order, in transit, and being installed, fed to ERP, ITSM, and finance.

From what exists, to how it gets there

What makes Asset Lifecycle different is that it is driven by the design. Unlike procurement tools that capture purchases after the fact, it generates the BOM directly from your NetBox model and carries one auditable thread from approval through installation, with every object tied to the infrastructure it represents.

Bills of Materials, Purchase Orders, Shipments, and Spares become first-class NetBox objects, with installation handled as a workflow against the planned DCIM objects. Each carries the standard NetBox UX (CRUD views, bulk edit and import, filtersets, tags, custom fields, comments, contacts) and a fully customizable tracked lifecycle status, such as Draft → Approved → Ordered → Fulfilled or Cancelled for BOMs and POs; Prepared → Shipped → Received, Cancelled, Returned, or Lost for Shipments. The Install action updates device status and captures serial number, asset tag, and the source shipment or spares pool.

Because every transition is timestamped against a named user, one auditable trail runs from BOM approval through installation. The audit trail is a byproduct of the workflow, not a quarter-end reconstruction: the change record is the audit record.

For the engineers who architect and deploy, that means design, BOM, PO, shipment, and install in one tool, the one they already use to model the network – creating a consistent data through-thread ensuring velocity and correctness at every step of the infrastructure build. For the leaders who answer for spend and success, a single, auditable procurement pipeline tied to the system of record.

BOMs that draw themselves from the model

Scope rules leverage NetBox’s native filtersets to select DCIM objects across racks, devices, modules, and cables. Equipment is automatically deduplicated by type and variant (airflow direction, cable color, cable length), so counts come from the actual design, not a hand-built spreadsheet. Auto-created CableType entries fill a long-standing gap, giving cables a native home in the data model, and Purchase Orders support 20 global currencies out of the box.

No manual equipment counting: change the design and the BOM follows. Multi-site refreshes run from one consistent definition per site, and the procurement coordination that previously gated a buildout compresses, so infrastructure comes online sooner.

Built to feed your ERP, procurement, and ITAM systems

Asset Lifecycle is built to coexist with the systems already in production, not replace them. A full REST API spans every object, with the installation workflow invokable through the same surface. You can integrate with Asset Lifecycle via the GA APIs today. On our roadmap are first-class integrations for BOM export and fixed-asset sync to SAP, Oracle, and NetSuite; webhooks to Coupa, SAP Ariba, and NetSuite on install, decommission, and move events; and inbound PO import with vendor SKU mapping (Cisco, Dell, Arista) to NetBox device types.

It is not a procurement-platform replacement, an ITAM substitute, or an ERP general ledger. SAP, Oracle, NetSuite, Coupa, SAP Ariba, and ServiceNow stay where they are and Asset Lifecycle becomes the authoritative upstream feed they consume.

What it looks like in practice

Greenfield datacenter deployment. Scope rules generate the BOM directly from a design that lives in NetBox, deduplicated by type and variant, so cable counts come from the actual cable plan rather than a loading-dock surprise. The install action then captures serial and asset tag at the rack against the source shipment.

Multi-site infrastructure refresh. A program team refreshing dozens of sites runs scope-rule-driven BOMs per site type, pulled from the design instead of hand-counted. POs split across vendors with one record each, shipment status updates per PO, and the week-of-cutover question (“did everything arrive at site 12?”) becomes one filter on a NetBox view.

Spares at the ready. When a device fails, the spares pool at the site shows a compatible unit. The replacement install records the spares pool as its source, enabling you to easily track pool depth and re-order spares before they run out .

An authoritative feed for finance and audit. The pipeline produces what fixed-asset accounting needs: purchase date from the PO, in-service date from the install timestamp, serial and asset tag from the install action, and location from the planned DCIM object. The REST API feeds the ERP, and auditors see named approvers, timestamps, and status history for every BOM, PO, and install.

Get started

Asset Lifecycle is available in the Premium tier, on NetBox Cloud and NetBox Enterprise.

If you are already a NetBox Labs customer, reach out to your account executive or customer success manager to get started; they will help you scope your first BOM, a low-risk first step that you can expand on as confidence builds.

Not a customer yet? Request a demo and we will walk you through Asset Lifecycle and the rest of the platform.