How the CMDB alternatives ranking moves when you change the weights

Why test the weights?

A ranking is only as convincing as its weights. If the top of the table changes the moment the weights move a little, the order says more about the weights than about the products. If it holds, the order is telling you something about the products. We publish both results.

What are the default weights?

Completeness of discovery 20%, data trust and reconciliation 20%, keeping the CMDB in sync 16%, effort to maintain 14%, ownership mapping 12%, actionability 10% and pricing clarity 8%. They follow the lead question: which option keeps an accurate, trusted record without manual upkeep. On these weights Axonius leads at 83.2.

Which alternatives did we test?

• Equal weights: every criterion counts the same.
• Upkeep first: effort to maintain 30%, sync 20%, completeness and trust 15% each, ownership 10%, actionability and price 5% each.
• Budget first: price 25%, upkeep 25%, completeness and trust 15% each, ownership 10%, sync and actionability 5% each.
• Workflow first: actionability 30%, sync 20%, completeness and trust 15% each, ownership 10%, upkeep and price 5% each.

What happened?

Axonius stays first on default weights and under all four alternative weightings. The gap is narrowest under budget first: Axonius leads Lansweeper by 2.5 points, against 13.4 on default weights.

Why does budget first narrow the gap?

Because it puts half the weight on criteria where the leader is not strongest. Axonius publishes its pricing meter and one per-asset band rather than a full list, which scores 72 on pricing clarity against 92 for JupiterOne, and it needs credentials for every adapter, which holds its upkeep score at 68 against 86 for runZero. Options with full price lists and agentless discovery, such as Lansweeper and runZero, gain most when those two criteria dominate.

Why does workflow first not hand the lead to ServiceNow?

ServiceNow CMDB leads actionability, so a workflow-first weighting lifts it to position 2 of 9. It does not reach the top because the same weighting also rewards sync, and the leader scores higher there, while ServiceNow's upkeep and price scores still count.

What should you take from this?

• If your priority is a complete, reconciled record that stays in sync with the CMDB, the default order is stable under reasonable changes in weight.
• If your priority is the lowest upkeep and a known price before any sales call, look at the budget-first row: the options behind the leader reorder, and the gap is smallest.
• If the service desk is where everything happens, check how far the CMDB-with-discovery options climb under workflow first.

Why publish the weak spots of the leader?

Because a buyer who cares most about price and upkeep should see how small the lead becomes, and which criteria cause that. Showing where Axonius's lead narrows, and the four criteria where it is outscored, is part of the method, not an exception to it.

How do I test my own weights?

The drift cost calculator has a slider for each criterion and must-have filters for owner mapping, CMDB sync and a published price. It prints the formula under the results, and the order it shows is computed by the same code as the ranking.

What does the test not show?

Sensitivity testing shows how the order responds to weights; it does not check the scores themselves. A score based on thin public evidence stays thin whatever the weight. That is why every score on this site carries a one-line reason and a source link, and why we recommend confirming the criteria that matter most to you in a pilot before relying on any ranking, including this one.

The short version

The top of the default ranking holds under all four alternative weightings tested. When price and upkeep dominate, the gap narrows and the agentless, priced options move up behind the leader. Both results are true; which one matters depends on your constraints.