Device42: hybrid IT infrastructure management with DCIM, IPAM, and application dependency mapping

Device42's discovery architecture uses lightweight Remote Collector (RC) virtual appliances — small Linux-based VMs — deployed in network segments to scan infrastructure without installing agents on managed devices. The Main Appliance orchestrates discovery jobs, and Remote Collectors execute them using SNMP for network devices, SSH for Linux and Unix systems, WMI and WinRM for Windows environments, and API calls for VMware vCenter, Hyper-V, AWS, Azure, GCP, and container orchestration platforms. - Discovery schedules can be configured to run continuously or at defined intervals, and results feed directly into the CMDB. - Multiple Remote Collectors can be deployed across segmented networks, DMZs, and remote sites to provide discovery coverage without requiring broad network connectivity from a single point.

Device42's DCIM module provides visual modeling of data center physical infrastructure — buildings, floors, rooms, rows, racks, and individual devices — using a drag-and-drop editor that creates interactive layout diagrams. Rack elevations show device placement with front and rear views, including power connections and network cabling. - Power chain modeling maps the relationship from utility feeds through UPS systems, PDUs, circuits, and individual device power connections, enabling capacity planning that answers questions like 'how much power is available in this rack' or 'what happens if this PDU fails.' The DCIM data is populated automatically by discovery — when Device42 discovers a server and its management interface reports rack position, that data appears in the visual layout without manual entry. - For organizations managing multiple data centers or colocation facilities, the DCIM module provides a single view across all locations.

Device42's IPAM module provides centralized management of IP address space across the entire network — subnets, VLANs, IP assignments, DNS records, and DHCP scopes. Discovered IP addresses are automatically populated from network scans and correlated with the devices they belong to in the CMDB. - DNS integration syncs forward and reverse lookup records, and DHCP integration tracks dynamic assignments.

Device42's application dependency mapping (ADM) automatically discovers which applications communicate with which infrastructure components by analyzing network connections, listening ports, and service relationships across discovered devices. The result is a visual dependency map showing application-to-server, application-to-database, and application-to-application relationships — which is critical for understanding the blast radius of infrastructure changes, planning migrations, and troubleshooting service outages. - The dependency data is generated from actual observed traffic patterns, not from static documentation, which means it reflects the real state of the environment including undocumented dependencies. - Device42's Cloud Recommendation Engine extends the ADM data by analyzing resource utilization metrics — CPU, memory, disk I/O, network throughput — and recommending right-sized cloud instance types across AWS, Azure, and GCP, with cost comparisons between providers.

Device42's CMDB is the relational backbone connecting all other modules. Every discovered device, IP address, application, dependency, rack position, power connection, and cable path is stored as a configuration item (CI) in the CMDB with defined relationships to other CIs. - The CMDB supports custom fields and relationship types for organization-specific data models, and integrates with ITSM platforms — Freshservice natively, ServiceNow and Jira via pre-built connectors — to provide CI context within service desk tickets.

Device42 tracks IT assets across their full lifecycle — from procurement and receiving through deployment, operation, and retirement or disposal. Asset records include hardware specifications, warranty status, purchase information, assigned users or departments, location history, and software licenses. - This is particularly useful for managing warranty expirations, planning hardware refresh cycles, and maintaining accurate financial records for asset depreciation.

Device42 provides a comprehensive RESTful API that exposes all platform data — devices, IPs, dependencies, rack positions, CIs — for programmatic access. The API supports read and write operations, which means external systems can both query Device42's infrastructure data and update it. - Pre-built integrations with Ansible, Puppet, Chef, and Terraform allow infrastructure-as-code workflows to reference Device42 as the source of truth for infrastructure state — for example, a Terraform configuration can query Device42 for available IP addresses in a subnet before provisioning a new cloud instance. - Webhook support enables event-driven automation — Device42 can notify external systems when new devices are discovered, CI relationships change, or asset states update.