Discovery, reconciliation or a better CMDB: what the scores say about each route

What are the three routes?

• CMDB with discovery: ServiceNow CMDB, Freshservice and Device42. The record fills itself through the product's own discovery.
• Network discovery: Lansweeper, runZero and Armis. Devices are found on the network and handed to a CMDB.
• Reconcile and sync: Axonius, Oomnitza and JupiterOne. The record is built from tools you already run and written where people work.

How do the routes average out?

The table below is computed from the scores on this site: the mean score of the three options in each route, per criterion, and the mean total.

Where is each route strong?

Network discovery is strongest on effort to maintain. No agents for runZero, passive detection by default for Lansweeper and passive identification for Armis keep the record current without much work, and two of the three publish prices.

Reconcile and sync is strongest on completeness and data trust. Building the record from many tools reaches SaaS apps and identities that network discovery does not document, and matching sources against each other is the point of the design. It also holds the two ownership leaders in this set: JupiterOne, which models owners in its graph, and Oomnitza, which ties assets to people through lifecycle workflows.

CMDB with discovery is strongest on actionability. When the record lives in the service desk, incidents, changes and requests act on it directly. ServiceNow CMDB leads that criterion at 94.

Where is each route weak?

Network discovery tools stop at the network: SaaS apps and identities are mostly outside what they document, and they hand work to a service desk rather than acting themselves.

Reconcile-and-sync platforms depend on credentials for every source, so upkeep grows with the number of connected tools, and their price disclosure varies from a full list (JupiterOne) to partial (Axonius) to none (Oomnitza). Their write-back also varies: Axonius documents creating, updating and retiring ServiceNow records; Oomnitza documents two-way sync that writes validated values back; JupiterOne's ServiceNow integration doc describes ingesting CMDB data, not writing it back.

CMDBs with discovery have fewer outside sources to reconcile, which shows in data trust scores, and the largest of them needs the most administration to stay current.

Why do many teams combine routes?

Because the weaknesses do not overlap. A common pattern keeps the CMDB as the system of record, adds network discovery for devices no agent knows, and adds a reconciliation layer that compares everything and writes corrections back. The criteria on this site were chosen so that each route's contribution shows up somewhere in the scores.

Which single option does best across routes?

On default weights Axonius leads at 83.2, from the reconcile-and-sync route, followed by Lansweeper and runZero from network discovery. The best single option is not always the best combination: the calculator re-weights the ranking for your priorities, and Compare records puts any two to five side by side.

How should you choose a route?

Start with the gap. Missing devices on your own network point to network discovery. A record that is full but contradictory points to reconciliation. No CMDB at all, with the service desk at the center of IT work, points to a CMDB with discovery. Lesson 4 walks through the same decision with more detail on each route.

What does this mean for the client's position?

Axonius sits in the reconcile-and-sync route. That route's averages are high on completeness, trust and sync and behind network discovery on upkeep and price, and Axonius follows a similar shape: it leads three criteria and is outscored on four. The route table above is computed from the same scores as the ranking.

The short version

Each route solves one part of the record problem well. Read the averages as a map of strengths, not as a verdict on any one product.