Logical & physical network inventory
Every port, path and service in one living record.
Multi-tenant logical and physical network inventory, connected to your network management and billing systems.

The business problem
What Nodex fixes.
Without it
- The inventory spreadsheet drifted from the real network years ago.
- Nobody can say which customers sit on a port before it is changed.
- Monitoring, inventory and billing each hold a different version of the truth.
With Nodex
One inventory of devices, ports, paths and services, fed by your monitoring and billing integrations so it stays true without manual updates.
Core functionality
Everything in one place.
Physical inventory
Sites, racks, devices, cards and ports.
Logical inventory
Paths, circuits and services end to end.
NMS integrations
Mapping templates and an ingest API for monitoring systems.
Billing link
Services tied to what customers are billed for.
Impact view
See who is affected before you touch a port.
Node assistant
Find any port, path or customer in plain language.
Meet Node, the Nodex assistant.
Built on the same governed pattern as every Alexon assistant.
- Off until an administrator enables it
- Sees only what the user may see
- Every question and action is audited
Built on the unified platform
The foundation comes standard.
The same security and governance practices sit under every platform. Read the trust centre.
Email sign-in, with roles per organisation.
Row-level security in the database.
Every change and approval recorded.
Open exports and documented APIs.
Also in Network & Geospatial
Engineering disciplines behind it
Who is Nodex for?
Multi-tenant logical and physical network inventory, connected to your network management and billing systems.
What problem does Nodex solve?
The usual starting point: The inventory spreadsheet drifted from the real network years ago. With Nodex: one inventory of devices, ports, paths and services, fed by your monitoring and billing integrations so it stays true without manual updates.
Is our data kept separate from other organisations?
Yes. Each organisation's data is separated by row-level security in PostgreSQL, enforced by the database itself, and every sign-in, change and approval is written to an audit trail.
Do we have to use the Node assistant?
No. Node is switched off until an administrator in your organisation turns it on. When it is on, it sees only what the signed-in user is allowed to see, and its questions and actions are audited.
Can Nodex connect to our other systems?
Yes. Every Alexon platform has documented APIs and webhooks, and connections set up once in the integrations hub can be reused across products. We confirm the specific connectors you need during discovery.
Can we get our data out?
Yes. Your data can be exported in open formats at any time, and everything the interface can do is also available through documented APIs.
How quickly can we get started?
Discovery takes one to two weeks. You then work in an environment on your own data while we configure, integrate and prove the platform, typically by weeks four to eight depending on scope and data migration.
See Nodex on your own data.
A working session with an engineer, not a slide deck. Bring the process you want to fix.