DCIM & IPAM / Free in Vista Platform Core
Connect sites, hardware, cabling, and IP address space to the assets your team manages. See physical placement, network context, ownership, and cryptographic posture together.
Self-hosted data center infrastructure management and IP address management, built into Vista’s evidence-backed inventory.
01 / Physical infrastructure
Move from a region or site to a room, rack, device, and port. Physical infrastructure stays connected to the asset’s evidence, owner, findings, and change history.
Organize sites and nested locations. Place racks on grid floor plans. Use front and rear elevations, reserve units, and validate device placement. Compare declared draw with per-rack power budgets and supported SNMP PDU readings.
Apply device and module types to create expected interfaces, ports, and bays from templates. Track installed components, spares, RMA, warranty, and support dates with the device record.
Inspect faceplates and trace recorded cable paths through patch panels and circuit terminations. Review neighbour evidence before accepting a proposed cable.
02 / Intended wiring meets observed evidence
LLDP and CDP neighbour evidence can propose port-to-port cables for review. When observations contradict recorded wiring, drift findings give operators a concrete place to investigate.
Logical dependencies and physical cabling remain distinct. The map can show a known physical path behind a port-observed connection.
Proposals need approval. A trace is only as complete as its recorded terminations and patch-panel hops; ordinary network traffic does not prove a cable exists.
03 / Networks & IP address management
Connect interfaces and addresses to VRF-aware prefixes, ranges, and VLANs. Overlapping private address space stays separated by routing domain.
Use prefix hierarchy, utilization, and free-space views for allocation planning. Query assets by network context alongside owner, site, class, and findings.
Utilization reflects recorded inventory. It does not prove that undocumented address use is absent. Vista records and reconciles IPAM data; it does not operate DHCP, DNS, or routing.
Maintain registries, aggregates, prefix roles, VRFs, route targets, autonomous systems, and ASN ranges alongside prefixes and ranges.
Relate VLAN groups and IDs to the prefixes and interfaces that carry them. Record VLAN translation policies and virtual device contexts alongside physical and logical connections.
Record providers, circuits, and A/Z terminations. Connect declared virtual circuits to their terminating interfaces, and trace recorded physical paths into carrier circuits.
04 / Beyond the rack
The same inventory extends into virtual workloads and protected network paths, with cryptographic assessment where Vista has policy evidence.
Model clusters, hosts, virtual machines, and disks. Follow recorded placement into site and network context. Populate on-premises hypervisor membership manually, by API, or through Enterprise NetBox sync; direct hypervisor-manager collection is not available.
Record tunnel endpoints and IKE/IPsec proposals, policies, and profiles. Evaluate supplied algorithms against the shared risk catalogue and identify tunnels needing PQC migration.
Discover WLANs and associated clients from UniFi controllers, or maintain declared wireless records. Assess authentication and ciphers, with weak-WLAN findings linked to the access point.
Vista inventories and evaluates these systems. It does not operate hypervisors, VPN gateways, or wireless controllers, and stored policy is not proof of every session’s negotiated cryptography.
05 / Cryptography with operational context
A cryptographic finding belongs to an asset with an owner, location, network context, and dependencies. Rack and port views can surface cryptographic posture from that same inventory.
Use that context to prioritize quantum-vulnerable dependencies, track remediation, re-observe the result, and generate scoped CBOM evidence. Vista governs the migration workflow; your teams and vendors perform the changes.
Why connect the inventories?
Cryptographic findings become more useful when connected to the systems, owners, and dependencies they affect. Bringing that evidence into DCIM is Vista’s approach to infrastructure visibility, not a claim that cryptographic inventory is a standard DCIM requirement.
A certificate or algorithm finding needs context: which system uses it, who owns that system, and which services depend on it. Infrastructure inventory gives teams a place to connect those facts and plan the work.
The joint CISA, NSA, and NIST quantum-readiness guidance recommends correlating cryptographic inventory with existing inventories, including asset inventory. It does not prescribe DCIM or require a single platform.
Bring infrastructure context and supported cryptographic findings into the same inventory so teams can identify the affected asset, find its owner, and track the work. Discovery coverage and evidence remain explicit.
06 / Shared operational context
Ownership and history belong beside the infrastructure. Give teams a shared vocabulary and repeatable workflows without losing the source of each fact.
Use hierarchical business units, contacts, tags, images, and typed custom fields. Store and merge configuration context for an asset by site, role, or platform.
Review who changed what and where the update came from. Keep journals alongside structured history, and route inventory changes to email, Slack, or webhooks with object and action filters.
Save filters and export templates. Preview supported CSV imports row by row. Use hygiene findings and the Facilities dashboard to investigate record gaps, rack space, and power capacity.
07 / Clear edition boundaries
Sites, floor plans, racks, power, spares, lifecycle, cabling, IPAM, circuits, virtualization, VPN, wireless, governance, and supported bulk import/export. Plus discovery, cryptographic assessment, PQC readiness, and CBOM generation. No asset, sensor, seat, or time caps.
Add supported two-way infrastructure synchronization, CMDB/ITSM connectors, and migration imports. Field authority, conflict review, and dry runs keep exchanges deliberate. Enterprise also adds tenant OIDC SSO, Ed25519 CBOM signing, attestation, and artifact comparison.
Build on Enterprise with the cross-tenant management plane for service providers. All three editions are self-hosted; tenant isolation is already part of Core.
Two-way synchronization follows supported object and field rules; it does not copy every field in both directions. VPN keys and other secrets are excluded from the infrastructure synchronization boundary. Compare editions · Check release availability
Practical answers
DCIM means data center infrastructure management: sites, racks, hardware, ports, and physical connections. IPAM means IP address management: address space, prefixes, VRFs, and assignments. Vista connects both to its asset inventory and cryptographic posture.
No. The internal DCIM and IPAM workspace, including rack elevations, cable traces, and bulk import/export, is Core. Enterprise adds supported external synchronization; the internal governance workspace is already Core.
No. Discovery fills the evidence it can observe through supported, authorized sources. Device templates, imports, and operator-maintained records supply additional context. LLDP/CDP cable proposals require review, and incomplete paths remain incomplete.
Yes. Enterprise provides supported infrastructure connectors and CMDB/ITSM integrations. Synchronization follows object mappings and field-authority rules, with conflicts reviewed by a person. Core provides its own internal inventory and bulk import/export.
Core includes floor-plan placement, a Facilities capacity dashboard, and rack power budgets calculated from declared draw and rated feed capacity, alongside supported PDU measurements. These are not electrical load, redundancy-failover, airflow, or cooling simulations. Circuit records do not replace carrier billing or performance monitoring.
It connects quantum-vulnerable cryptography to the systems, owners, and dependencies involved in a migration. Vista helps inventory, assess, prioritize, track, and preserve evidence. It does not generate PQC keys or automatically migrate every system.
Infrastructure and security, in context
Run free Vista Platform Core, connect authorized discovery sources, and bring physical, network, and cryptographic context together.
Talk to Vista
Ask about Vista Platform, share feedback, or discuss your infrastructure inventory, DCIM, IPAM, cryptographic discovery, and modernization goals with the team.