AUTOLINX · FEATURES · RESOURCE MANAGEMENT Live IP, VLAN, interface, and ASN inventory — derived from the live graph, not a spreadsheet See pricing →
AutoLinx / Features / Resource Management
AUTOLINX FEATURE · 03 RESOURCE MANAGEMENT

Every IP, VLAN, interface, ASN —
always live, never stale.

AutoLinx Resource Management gives you a continuously updated view of every IP block, VLAN range, port allocation, ASN, and subnet across the network — derived from the discovery graph. Spreadsheets die. Capacity decisions become data-driven. AutoIPAM landed at the Laos national telco in 2026.

See pricing → How it works
LIVE RESOURCE INVENTORY · UPDATING IN REAL TIME
TYPE BLOCK USED FREE UTIL% IPv4 subnet 10.0.0.0/8 enterprise pool 9.4M 7.4M 56% IPv6 prefix 2001:db8::/32 service pool 2.1k /48 63k /48 3% VLAN range 100-3999 tenant pool 2,847 1,053 73% ASN private 65000-65535 internal eBGP 47 489 9% Port edge router edge1-edge12 100G ports 142 26 85% + NEW IPv4 /28 allocated 10.42.7.0/28 service VRF just now 9.4M IPv4 · 2,847 VLANs · 142 ports · derived from live graph
Auto-reconcile vs Discovery · drift detected → reconciliation change → seconds
WHAT IT DOES

Three capabilities that replace your spreadsheet.

Resource Management isn't a separate IPAM you maintain. It's a derived view of what's already on your network — what's allocated, what's free, what's drifted.

Live inventory · derived

IP · VLAN · interface · ASN · subnet

Built continuously from the Discovery graph. Every IP assigned to an interface, every VLAN configured on a trunk, every BGP ASN announced — all roll up into a single inventory you query, never maintain. When the network changes, inventory changes.

Free-resource allocation

next free /28 · next free VLAN · next free port

Ask "give me a free /28 in this VRF" — Resource Management returns one, atomically reserves it, and hands it to Provisioning. No spreadsheet duels, no race-condition double-allocations. Reservations expire if not committed within configurable window.

Drift & reclamation

find stale allocations · reclaim unused IPs

Compare CMDB records against live observation. IPs allocated in your CMDB but not actually on any interface? Flagged for reclamation. VLANs configured but with zero MAC entries? Candidates for cleanup. Audit-friendly, never auto-deletes.

HOW IT WORKS

Inventory follows the network, not the spreadsheet.

Four stages, continuous loop. The model: your network is the source of truth. The CMDB reflects it, not the other way around.
01 · OBSERVE From live graph interface IPs VLAN configs BGP announces 02 · CLASSIFY Pool + purpose tenant boundaries VRF mapping role context 03 · RECONCILE vs CMDB find drift stale records missing entries 04 · EXPOSE Query + allocate REST + GraphQL atomic reserve webhook events CONTINUOUS · NETWORK IS THE SOURCE OF TRUTH CMDB REFLECTS THE NETWORK · NOT THE REVERSE
WHERE IT SHIPS

Production proof.

Resource Management is the latest capability to ship as a productized AutoLinx feature — but the underlying work has 6+ years of production history.
ANCHOR 02 · LAOS NATIONAL TELCO
AutoIPAM
2026 · current generation

The production deployment of our AI-augmented IPAM at the Laos national telco. Live IP allocation, reconciliation against legacy CMDB records, and free-resource queries powering broadband provisioning workflows. The newest, most refined version of the capability.

ANCHOR 02 · LAOS NATIONAL TELCO
IPM · IP Management System
2020 · still running · 6 years

The first production IPAM we shipped at the Laos national telco, integrated with the CCMSS (Centralized Configuration Management System). Six years of production refinement informed the capability that ships as Resource Management today.

ANCHOR 02 · LAOS NATIONAL TELCO
LLP · Lease Line Provision
2025 · BPI Phase #2 expansion

Resource allocation tied directly to enterprise lease-line ordering — from sales order to provisioned circuit, with IP, VLAN, and interface allocation handled atomically. The bridge between OSS and the network's actual state.

ANCHOR 02 · LAOS NATIONAL TELCO
Network & Service Inventory System
2020 · foundational infrastructure

Resource Management's older cousin: a network-wide inventory of services, interfaces, IPs, and tenant associations. Still production today, providing audit and capacity context for the Laos national telco's planning team.

RESOURCE COVERAGE

Every resource type, one inventory.

Resource Management covers the full set of network-allocatable objects. Same query language across all of them.
IPv4
subnets · hosts
IPv6
prefixes · /48 · /64
VLAN
tags · ranges
VRF
tenants · contexts
ASN
public · private
Interface
physical · logical
MPLS
label · VPN ID
VNI / VXLAN
overlay tunnel
Loopback
router IDs
Customer / tenant
scope · isolation
HUMAN-IN-THE-LOOP

Reads run auto. Reclamation needs approval.

Querying inventory is safe. Reserving free resources is safe. Reclaiming or deleting allocations always asks first — these affect billing and customer service.
L1 · QUERY Look up IP usage · VLAN allocation · interface utilization · ASN status auto
L2 · RESERVE Atomic reservation of free resources · expires if not committed auto
L3 · ALLOCATE Commit a reserved resource to a service · feed Provisioning workflow auto
L4 · RECLAIM Flag stale allocations for cleanup · reclaim unused IPs · prune empty VLANs approval
QUESTIONS

What people ask first.

Does this replace our existing IPAM (Infoblox, NetBox, etc.)?
Not necessarily. Most customers keep their IPAM as the system of record and let Resource Management reconcile against it — finding drift, surfacing free resources, feeding Provisioning. For greenfield deployments or where IPAM has fallen out of sync with reality, Resource Management can become the system of record. Bi-directional sync supported.
How does atomic reservation handle race conditions?
Reservations are transactional with TTL — the next free /28 query returns a unique block, locks it for ~5 minutes (configurable), and releases if not committed. Two concurrent allocations always get different blocks. Used in production at scale at Anchor 02 for parallel BPI provisioning workflows.
Can we expose allocation as a self-service API to other teams?
Yes. Resource Management exposes REST and GraphQL endpoints with RBAC — typical pattern is the SRE team consumes it from their CI/CD, the broadband team consumes it from their order-management system. Anchor 02 uses this exact pattern with BPI and LLP workflows.
What about multi-tenant separation?
VRF and tenant boundaries are first-class. A free-resource query in tenant A's scope never returns resources in tenant B's scope, even if the underlying address space overlaps. Tenant isolation is enforced at the query layer, not the response filter — so accidentally crossing tenants is impossible.
How do we handle the cold-start case — new deployment, no prior inventory?
Discovery does the cold start. Within the first few hours after deployment, Resource Management has a complete picture of what's currently on the network. From there, you can either import your CMDB on top (reconciling differences) or treat the live network as the new source of truth. Customer choice.
Does it handle IPv6 properly?
Yes — IPv6-native. Prefix delegation, SLAAC observation, EUI-64, and per-customer /48 or /56 allocation patterns all supported. Customers running dual-stack deployments use the same query interface for both address families.
SISTER FEATURES

Resource Management is one capability. It plugs into the others.

Discovery feeds it observations. Provisioning consumes its reservations. Compliance audits its policies.
FEATURE 01

Discovery

The live graph that Resource Management derives from. Every observed IP, VLAN, interface lands here first.
Read →
FEATURE 02

Provisioning

Pulls free resources from Resource Management atomically · commits them as part of the change pipeline.
Read →
FEATURE 04

Compliance Audit

Audits resource allocation against policy · catches over-allocation, tenant breach, stale assignments.
Read →

Stop maintaining the spreadsheet. Start querying the network.

A 4-week pilot builds your live inventory in week one — then your team queries it instead of editing the spreadsheet. Free-resource allocation feeds your provisioning workflows by week three.

See pricing → Read product overview