Asset InventoryRanked

Sheet 02 · Dataset · Survey date: September 2026

Asset Inventory Coverage Grid: 7 Asset Classes, 7 Tools

Bottom line

No tool in this ranking documents all seven asset classes. Axonius documents the most (6.5 of 7, with network devices partial). runZero and Lansweeper tie at 5.5. Identities and OT and IoT devices are the classes most often not documented.

How do you read the grid?

Rows are asset classes. Columns are tools, in ranking order. Each cell records what the vendor documents on its own public pages, reviewed September 2026: Documented (D), Partial (P) or Not documented (N). Coverage through an integration counts, because that is how most tools reach most assets. Not documented means we did not find it, not that the product cannot do it. Vendors who want a cell corrected can write to us through the contact page with a public link.

Asset coverage grid: which asset classes each tool documentsWeighted coverage counts, documented counts one and partial counts one half: Axonius 6.5 of 7; JupiterOne 4.5 of 7; runZero 5.5 of 7; Lansweeper 5.5 of 7; Armis 4.5 of 7; Oomnitza 4.0 of 7; Device42 3.5 of 7.E1AxoniusE2JupiterOneE3runZeroE4LansweeperE5ArmisE6OomnitzaE7Device42N1Laptops and workstationsLaptops and workstations · Axonius: DocumentedDLaptops and workstations · JupiterOne: DocumentedDLaptops and workstations · runZero: DocumentedDLaptops and workstations · Lansweeper: DocumentedDLaptops and workstations · Armis: DocumentedDLaptops and workstations · Oomnitza: DocumentedDLaptops and workstations · Device42: Not documented. Not documented; the product focuses on data center and cloud infrastructure.NN2ServersServers · Axonius: DocumentedDServers · JupiterOne: Partial. Covered through integrations; the platform page lists devices, networks and applications rather than naming server or cloud workload classes.PServers · runZero: DocumentedDServers · Lansweeper: DocumentedDServers · Armis: Partial. Covered as IT assets; not called out separately.PServers · Oomnitza: Partial. Physical hardware is covered; servers are not called out.PServers · Device42: DocumentedDN3Cloud workloadsCloud workloads · Axonius: DocumentedDCloud workloads · JupiterOne: Partial. Covered through integrations; the platform page lists devices, networks and applications rather than naming server or cloud workload classes.PCloud workloads · runZero: DocumentedDCloud workloads · Lansweeper: Partial. Cloud discovery is documented; providers are not named on the product page.PCloud workloads · Armis: DocumentedDCloud workloads · Oomnitza: DocumentedDCloud workloads · Device42: DocumentedDN4SaaS appsSaaS apps · Axonius: DocumentedDSaaS apps · JupiterOne: DocumentedDSaaS apps · runZero: Not documented. Not covered on the pages we reviewed.NSaaS apps · Lansweeper: Partial. AI usage tracking only.PSaaS apps · Armis: Not documented. Not documented as asset classes.NSaaS apps · Oomnitza: DocumentedDSaaS apps · Device42: Partial. Software licenses are tracked; SaaS discovery is not documented.PN5IdentitiesIdentities · Axonius: DocumentedDIdentities · JupiterOne: DocumentedDIdentities · runZero: Partial. Directory data from Entra ID and Active Directory integrations enriches device records.PIdentities · Lansweeper: Partial. User data is merged into asset records.PIdentities · Armis: Not documented. Not documented as asset classes.NIdentities · Oomnitza: Partial. Okta and Entra integrations feed user data.PIdentities · Device42: Not documented. Not documented; the product focuses on data center and cloud infrastructure.NN6OT and IoTOT and IoT · Axonius: DocumentedDOT and IoT · JupiterOne: Not documented. Not listed among the asset classes on the platform page.NOT and IoT · runZero: DocumentedDOT and IoT · Lansweeper: DocumentedDOT and IoT · Armis: DocumentedDOT and IoT · Oomnitza: Not documented. Not documented.NOT and IoT · Device42: Not documented. Not documented; the product focuses on data center and cloud infrastructure.NN7Network devicesNetwork devices · Axonius: Partial. Covered through adapters to network tools; the pages we reviewed do not describe a native network scanner.PNetwork devices · JupiterOne: PartialPNetwork devices · runZero: DocumentedDNetwork devices · Lansweeper: DocumentedDNetwork devices · Armis: DocumentedDNetwork devices · Oomnitza: Not documented. Not documented.NNetwork devices · Device42: DocumentedD
DocumentedPartialNot documented

Figure 1. Asset coverage grid. Status reflects vendor documentation reviewed September 2026, not product testing.

Asset coverage grid, text version, with the cell notes behind each status.
Asset classAxoniusJupiterOnerunZeroLansweeperArmisOomnitzaDevice42
Laptops and workstationsDocumentedDocumentedDocumentedDocumentedDocumentedDocumentedNot documentedNot documented; the product focuses on data center and cloud infrastructure.
ServersDocumentedPartialCovered through integrations; the platform page lists devices, networks and applications rather than naming server or cloud workload classes.DocumentedDocumentedPartialCovered as IT assets; not called out separately.PartialPhysical hardware is covered; servers are not called out.Documented
Cloud workloadsDocumentedPartialCovered through integrations; the platform page lists devices, networks and applications rather than naming server or cloud workload classes.DocumentedPartialCloud discovery is documented; providers are not named on the product page.DocumentedDocumentedDocumented
SaaS appsDocumentedDocumentedNot documentedNot covered on the pages we reviewed.PartialAI usage tracking only.Not documentedNot documented as asset classes.DocumentedPartialSoftware licenses are tracked; SaaS discovery is not documented.
IdentitiesDocumentedDocumentedPartialDirectory data from Entra ID and Active Directory integrations enriches device records.PartialUser data is merged into asset records.Not documentedNot documented as asset classes.PartialOkta and Entra integrations feed user data.Not documentedNot documented; the product focuses on data center and cloud infrastructure.
OT and IoTDocumentedNot documentedNot listed among the asset classes on the platform page.DocumentedDocumentedDocumentedNot documentedNot documented.Not documentedNot documented; the product focuses on data center and cloud infrastructure.
Network devicesPartialCovered through adapters to network tools; the pages we reviewed do not describe a native network scanner.PartialDocumentedDocumentedDocumentedNot documentedNot documented.Documented

Weighted coverage counts

  • Axonius: 6.5 of 7
  • runZero: 5.5 of 7
  • Lansweeper: 5.5 of 7
  • JupiterOne: 4.5 of 7
  • Armis: 4.5 of 7
  • Oomnitza: 4.0 of 7
  • Device42: 3.5 of 7

Documented counts as 1, Partial as 0.5.

Which asset classes are hardest to cover?

Identities are fully documented by 2 of 7 tools (Axonius and JupiterOne) and partially by 3 (runZero, Lansweeper and Oomnitza). SaaS apps are fully documented by 3 (Axonius, JupiterOne and Oomnitza). OT and IoT split the field: Axonius, runZero, Lansweeper and Armis document it; JupiterOne, Oomnitza and Device42 do not. Laptops are the easiest class: 6 of 7 tools document them.

Why is coverage not the same as trust?

A tool can reach an asset and still hold a wrong record of it. Two tools that both see a laptop may disagree on its owner, its operating system or whether its EDR agent is running. That is why the ranking weights correlation and deduplication at 18% next to coverage at 22%: an inventory is only useful when the records from different sources have been matched and the conflicts resolved.

Can you use this dataset?

You may quote or reproduce the grid with a link to this page. Cite it as: Asset Inventory Ranked, Asset Coverage Grid, September 2026, https://assetinventoryranked.com/coverage-grid.

Frequently asked questions

Which asset inventory tool covers the most asset classes?

On vendor documentation reviewed in September 2026, Axonius documents six of seven classes fully and network devices partially, for 6.5 of 7. runZero and Lansweeper follow, tied at 5.5.

Which tools cover SaaS apps?

Axonius, JupiterOne and Oomnitza document SaaS coverage. Lansweeper and Device42 document partial coverage. runZero and Armis do not document it on the pages we reviewed.

Does "Not documented" mean a tool cannot cover that asset class?

No. It means the vendor's public pages we reviewed did not describe it. Buyers should ask the vendor directly.