Device42 CMDB: Features, Limitations, and a Strong Alternative (2026)

Device42 CMDB is an agentless configuration management database that discovers hardware, software, and application dependencies across hybrid IT environments and stores them as configuration items (CIs) in a central repository. Now part of Freshworks, which completed its acquisition of Device42 in June 2024, it is a capable platform with real strengths in dependency mapping and data center infrastructure management. It also carries limitations that surface repeatedly in user reviews: a steep onboarding curve, constrained subcomponent change reporting, add-on costs for capabilities buyers expect in the base license, and slower performance at large scale.

This guide evaluates where Device42 fits, where it strains, and how Virima compares for teams that need accurate CI data feeding their ITSM platform. The stakes are rising. Gartner has forecast that 33% of enterprise software applications will include agentic AI by 2028, up from less than 1% in 2024. As AI agents begin acting on infrastructure data, the CMDB underneath them has to be accurate and explainable, not a three-week-old snapshot. That raises the bar for any CMDB you evaluate, Device42 included.

What is Device42 CMDB?

Device42 CMDB is an agentless configuration management database that discovers and maps IT assets across physical, virtual, and cloud environments, then stores them as CIs with defined relationships. Freshworks acquired Device42 in 2024 to strengthen its IT asset management and ITSM portfolio. The platform is well regarded for application dependency mapping and remains a common shortlist entry for organizations running on-premises data centers alongside cloud workloads.

Device42 Feature Evaluation

Agentless discovery

Device42 uses agentless discovery to identify IT assets across physical, virtual, and cloud environments, with no software agents required on target devices. Coverage spans on-premises servers, virtual machines (VMware, Hyper-V), cloud resources on AWS, Azure, and GCP, containers, and network devices. Device42 also offers AI-assisted data enrichment that standardizes vendor and software names, deduplicates CI records, and adds lifecycle data such as end-of-life and end-of-support dates.

Centralized CI repository

Device42 maintains a central repository for configuration items with pre-built CI classes and relationship types that reduce initial setup. The schema is customizable: teams can add CI classes, define relationships, and attach metadata fields. Data comes in through spreadsheet upload, a REST API, and a library of out-of-box integrations across IT asset management, configuration management, and SIEM tools.

Application dependency mapping

Dependency mapping is the capability users praise most. Device42 maps connections between applications, services, and infrastructure, upstream and downstream, so teams can see how a change to one component ripples across everything connected to it. Reviewers on sites like PeerSpot and G2 frequently identify this as the platform’s strongest area.

Data center infrastructure management (DCIM)

Device42 includes DCIM: power and capacity management for physical data centers, rack diagrams, environmental monitoring, and IP address management (IPAM). For organizations running on-premises infrastructure alongside cloud workloads, this is a real advantage over ITSM-native CMDBs that have no DCIM at all.

Cloud migration planning

Device42 analyzes current infrastructure usage to recommend cloud placement for workloads, which helps teams planning hybrid optimization or an active migration.

ITSM integrations

Device42 connects with a range of platforms, including Freshservice, ServiceNow, Jira Service Management, and Zendesk on the ITSM side, plus configuration tools such as Puppet, Chef, and Ansible, and SIEM destinations such as Splunk. Most of these are connector-style integrations rather than two-way sync.

Device42 CMDB Limitations

Every platform has trade-offs. The ones below come up repeatedly in enterprise user reviews on G2 and PeerSpot.

Steep learning curve

New users frequently describe the interface as complex and the navigation as non-intuitive, especially without prior CMDB administration experience. Initial configuration takes meaningful time, which delays time-to-value for teams that lack a dedicated CMDB administrator.

Limited subcomponent change reporting

Device42 does not export detailed change reports for subcomponents, such as CPU or memory modification history for a specific device. The data exists inside the application but cannot be pulled out, which limits its usefulness for hardware change audits. Multiple reviews call this out specifically.

Add-on costs for core capabilities

Several capabilities buyers expect in a base CMDB license, including certain discovery modules, advanced reporting, and specific integrations, are sold as add-ons. Reviewers report that total cost climbs once the required pieces are included. Device42 does not publish list pricing, and figures vary widely by node count and selected modules, so model your own configuration rather than relying on a single published number.

Performance at scale

Reviewers managing very large environments report slower performance during complex queries and bulk operations on big data sets.

Device42 vs. Virima CMDB: Side-by-Side

Here is how Device42 stacks up against Virima across the criteria that matter most to evaluators. For a deeper three-way view, see our side-by-side comparison of Virima, Device42, and BMC Discovery.

How Virima Approaches CMDB Accuracy

Virima is built around a simple idea: when a person or an AI agent acts on your CI data, that data should be current and explainable, not a snapshot from the last scheduled scan. Rather than scanning everything around the clock, Virima’s CMDB watches the confidence of its CI data and refreshes records on demand when that confidence drops. This extends what Virima already does today, such as service map rescans, into a model where data gets refreshed when a decision actually needs it.

High-frequency discovery cycles

Virima’s IT discovery engine runs high-frequency discovery cycles across on-premises, virtual, and cloud infrastructure on AWS and Azure. CMDB health scoring tracks accuracy, completeness, and staleness, flagging CIs that have not been confirmed recently and prioritizing them for refresh. The result is a live, explainable, policy-aware data foundation rather than a static inventory.

ViVID Service Mapping with live ITSM context

Virima’s ViVID™ Service Mapping builds dynamic dependency maps from the CI relationships Virima Discovery detects, such as which applications run on which servers and which hosts communicate with each other. Teams can refine those maps with their own knowledge. ViVID™ then overlays live ITSM records from your connected platform, so responders see the open incidents and change requests tied to each affected CI without switching tools.

ITSM integration depth

Virima maintains bidirectional sync with ServiceNow, Ivanti, Halo, Jira Service Management, and Xurrent. Discovery-sourced CI data flows into your ITSM platform’s CMDB on a regular cadence, which reduces the data drift that erodes service desk trust.

What Agentic IT Operations Demand From a CMDB

As AI agents begin routing incidents, assessing change impact, and triggering runbooks, the CMDB they query has to clear a higher bar than traditional inventory accuracy. If you are unsure what a CMDB actually is in this context, start there. When you evaluate any platform, including Device42, test it against five requirements:

1. Live asset state: CI data confirmed by a recent discovery cycle, not a stale cache.
2. Verified ownership: a clear record of which team owns each CI, linked to ITSM records.
3. Dependency impact mapping: upstream and downstream context for any proposed change.
4. Auditable change history: what changed, when, and who (human or agent) made the change.
5. Policy-aware governance: rules defining what actions are permitted on each CI class before an agent acts.

Device42 is strong on live asset state, dependency mapping, and change history. Ownership linking and policy-aware governance are where ITSM integration depth becomes the deciding factor.

How to Choose Between Device42 and Virima

Choose Device42 if:

• You run a physical data center and need DCIM alongside your CMDB.
• Cloud migration planning is a primary use case.
• You have CMDB administrators who can absorb the onboarding effort.

Lean toward Virima if:

• Your CMDB has to feed accurate, current CI data into an ITSM platform.
• You are preparing for AI-driven IT operations and need a CMDB that stays explainable and current.
• You need service dependency maps with live ITSM incident context, not just topology.
• CMDB data drift has been undermining your service desk.

Frequently Asked Questions

What is Device42 CMDB?

Device42 CMDB is an agentless configuration management database that discovers and maps IT assets, including servers, applications, network devices, and cloud resources, and stores them as CIs in a central repository. Freshworks acquired Device42 in 2024, and the platform is particularly strong in application dependency mapping and DCIM.

What are the main limitations of Device42 CMDB?

Based on enterprise reviews on G2 and PeerSpot, the four most common limitations are a steep onboarding learning curve, the inability to export subcomponent change reports, add-on costs for capabilities buyers expect in the base license, and slower performance in very large environments.

How much does Device42 CMDB cost?

Device42 does not publish list pricing. It uses a node-based model, and total cost rises once required add-ons are included, so the right figure depends on your node count and modules. Contact Device42 or Freshworks for a current quote.

What is a strong Device42 CMDB alternative?

Virima is a strong alternative for teams that prioritize ITSM integration depth. It offers bidirectional sync with ServiceNow, Ivanti, Halo, Jira Service Management, and Xurrent, CMDB health scoring to surface stale data, and ViVID Service Mapping that overlays live ITSM records onto discovery-sourced dependency maps.

Does Device42 support hybrid cloud environments?

Yes. Device42 supports agentless discovery across on-premises servers, VMware and Hyper-V virtual machines, and cloud resources on AWS, Azure, and GCP, and it can recommend cloud placement for workloads during migration planning.

How does Virima compare to Device42?

Virima’s strengths are ITSM integration depth, CMDB health scoring for data staleness, agentic-IT readiness, and a cloud-native SaaS deployment with a faster path to first scan. Device42’s strengths are DCIM and cloud migration planning. The right choice depends on whether DCIM or ITSM integration depth matters more to you.

What CMDB capabilities does agentic IT require?

A CMDB supporting AI-driven operations should provide live asset state from recent discovery, verified ownership linked to ITSM records, dependency impact mapping, auditable change history, and policy-aware governance that constrains what an AI agent can do to each CI class.