ServiceNow now owns Armis: what it changes for the CMDB record

This note covers an announcement from April 2026 and Armis releases from February and March 2026, read again for this site on 27 September 2026.

What happened?

ServiceNow completed its acquisition of Armis on 20 April 2026. ServiceNow's newsroom describes the purchase as "for approximately $7.75 billion in cash, funded through a combination of cash on hand and debt". Armis's own announcement says Armis Centrix remains available as part of the ServiceNow AI Platform and as a standalone product.

What does Armis bring to a CMDB?

Armis Centrix identifies devices passively, from network traffic, without agents. Its asset management page lists IT devices whether managed or unmanaged, OT and IoT, medical devices, cloud instances and hybrid VMs. Identification draws on what Armis calls a "knowledgebase of over 6.5 billion assets", and the product pushes enriched data "back to your CMDB". Armis says a complete asset inventory arrives "within minutes to hours" and that asset management needs no on-premises hardware.

For a CMDB that ServiceNow Discovery fills, that is a different angle on the same estate. ServiceNow Discovery describes agentless insight into infrastructure and applications on-premises, in the cloud and in containers, plus a unified agent. Armis watches traffic, which is how it sees devices that cannot carry an agent: an infusion pump, a building controller, a printer nobody registered.

What does the deal not change?

Three things stay as they were on the pages reviewed.

• Coverage outside the network. Armis does not document SaaS apps or identities as asset classes. A SaaS subscription bought on a card or a service account in a cloud tenant is not something passive network monitoring sees.
• Ownership. Neither Armis's pages nor ServiceNow's CMDB pages describe how an owner is attached to each asset. On this site Armis scores 40 and ServiceNow CMDB 48 on ownership mapping.
• Prices. ServiceNow publishes no price for these products; Armis shows only an AWS Marketplace minimum of $3,250 a month for Centrix Standard, read on 11 October 2026.

Does this make Armis a ServiceNow feature?

Not on the evidence available. Armis states Centrix stays available standalone, and earlier in 2026 it kept building outward: a developer portal at dev.armis.com around API v3 in February and Armis Marketplace for partner integrations in March. Buyers who use another service desk should still ask how the standalone product will be supported, in writing.

How does it change our scores?

It does not, by itself. We score what the vendors document. Armis already documented pushing enriched data back to the CMDB, which is why it scores 74 on keeping the CMDB in sync. If ServiceNow publishes a native Armis connector with documented create, update and retire behaviour, that score would be reviewed. Armis ranks 5 of 9 at 68.0 and ServiceNow CMDB 7 at 64.9.

What should a ServiceNow customer do now?

• If unmanaged and OT devices are the gap in your CMDB, Armis is now the most direct route inside the ServiceNow family. Ask how its data maps to your CI classes.
• If the gap is SaaS, identities or owners, the acquisition does not close it. Look at the reconcile-and-sync options, which build the record from the tools you already run.
• If the gap is upkeep, compare what each route needs to keep running. The drift cost calculator helps size the manual work you are trying to remove.

What should buyers outside ServiceNow watch?

Teams whose service desk is not ServiceNow should watch three things over the coming releases: whether the standalone product keeps its integrations with other service desks, whether new features arrive first or only inside the ServiceNow platform, and whether packaging or contract terms change at renewal. None of these is announced. All of them are fair questions for an account team, and the answers belong in the contract rather than in a slide.

The short version

The deal puts passive device discovery and the system of record under one owner. That helps the device side of the CMDB. The rest of the record, the people, accounts and subscriptions around those devices, still needs a source.