ServiceNow ITOM licensing in 2026. How managed CIs become the bill.

ServiceNow bills ITOM through a pool of subscription units consumed by managed CIs. The contract sets the pool, but your Discovery schedules and CMDB hygiene decide how fast you use it.

How is ServiceNow ITOM licensed?

ServiceNow licenses ITOM through subscription units tied to managed configuration items: the servers, devices and cloud resources that Discovery, Event Management and AIOps actually touch. You buy a pool of units on the order form, and the platform meters consumption against that pool.

That makes ITOM economics closer to cloud billing than to seat licensing. The order form is signed once per term, while Discovery schedules, cloud accounts and monitoring feeds change every week, and each change can move the count.

What counts as a managed CI?

A managed CI is any resource the licensed ITOM products actively discover, monitor or correlate, and that includes cloud instances. Autoscaling groups, short lived containers and broad subnet scans all create billable CIs. Default Discovery schedules scan widely, and the CMDB records everything they find.

Different resource types convert to subscription units at different ratios. ServiceNow publishes a Subscription Unit Overview for ITOM, and the ratios have changed between versions. Your own order form decides which table applies to you, so check it before you model anything.

Read the table with one caution. A friendlier ratio on a newer SKU helps only if your contract references that SKU. Buyers on older paper keep the older ratios until they renegotiate, which makes the ratio table itself a renewal topic.

Which ITOM products consume subscription units?

Discovery consumes units per discovered and managed infrastructure CI. Event Management meters the monitored CIs that feed events in. AIOps and Health Log Analytics meter the same resource base at a higher price per unit, so one ungoverned Discovery schedule inflates all three lines at once.

Events also count when they come from something the CMDB does not know. ServiceNow calls these unresolved monitored objects and records them in the em_unique_nodes table. A monitoring feed full of hostnames that never reconcile to a CI is a licensing cost as well as a data quality problem.

Why does the ITOM CI count keep rising?

The count rises because five ordinary operational habits add CIs without anyone approving the spend. No one sets out to inflate it. The inflation is structural, which is why it does not stop on its own, and each driver has a specific fix.

Why does cloud inflate the count fastest?

Cloud resources appear and disappear by the hour, and Discovery records each one it sees. Say an autoscaling group peaks at 60 instances for a month end batch. Unless a rule excludes them, those 60 instances can stay on as server CIs after the batch ends. A container platform can create thousands of short lived records in a week.

The newer container ratio softens this, but only on newer SKUs, and it does nothing for autoscaled virtual machines that count one to one. The durable fix is a rule that excludes ephemeral resources from managed status, agreed between the cloud team and the CMDB owner.

Why review the CI count like a cloud bill?

The billable CI number changes with operational decisions made far from whoever holds the budget, the way cloud spend does. The operations team sees no invoice when a new subnet is added to a schedule, so the review has to happen on a calendar.

We recommend a quarterly review, owned jointly by the CMDB owner and whoever holds the ServiceNow budget. Compare the count with the previous quarter and with the entitlement, and ask for a named cause behind every jump.

What does a managed CI cost, and how much does a cleanup save?

Divide the ITOM line on your order form by the billable CI count from subscription unit reporting. The result is your price per managed CI, the benchmark number for the renewal, and most buyers have never calculated it. Divide by subscription units, not raw CI records, or containers and PaaS resources will make the price look lower than it is.

The example below is hypothetical and uses the April 2026 ratios.

At $540,000 for 3,000 units, each unit costs $180 a year. Removing 750 units is a 25 percent reduction, worth $135,000 a year at the same rate, or $405,000 over a three year term. Nothing in the cleanup touched a resource the operations team actually monitors.

The unit price also exposes the quote. If ServiceNow proposes a 5 percent discount on a renewal priced for 3,000 units, you are still paying for 750 units you do not need. The cleaned count and the unit rate come first, and the discount comes last.

How do you check your own ITOM subscription usage?

Start with the platform's own licensing report, then trace every surprising number back to the schedule or source that created it. These are the places we look first.

• Licensable CI report. Go to All, ITOM License, Report ITOM Licensable CIs. Pick the application (Discovery, Visibility, Health, HLA, Optimization or Governance), select Populate licensable CIs, then Show licensable CIs. It needs the sn_itom_license.reader role.
• Subscription unit consumption reporting. Pull the trailing year, by month. The trend line shows when the count jumped, and the jump usually matches a schedule change or a cloud account onboarding.
• Discovery schedules and IP ranges. List every schedule, its ranges and its exclusions. Any schedule that targets a whole subnet deserves a question.
• CMDB Health dashboard. The correctness score counts duplicate, orphan and stale CIs, which is most of the cleanup list. Duplicates usually trace back to Identification and Reconciliation rules that let two sources create separate records.
• CMDB Data Manager policies. Check whether retire and archive policies exist and run, so decommissioned servers leave managed status.
• The em_unique_nodes table. It lists event sources that never matched a CI, which is where unresolved monitored objects come from.

Then put three numbers side by side: the entitlement on the order form, the count the platform reports today and the count you expect after a cleanup. The difference between the last two is what you take into the renewal.

Is the full ITOM suite worth buying, or should you license by tier?

For most buyers, license by tier. The full suite pitch failed the arithmetic in most of our files that took it. Match the package to operational maturity and let the premium tiers earn their place.

• Start from operational maturity, not the bundle pitch. Environments with a governed CMDB and basic monitoring get payback from Discovery and Event Management first.
• Let the premium tiers earn their way in. AIOps pays back only when event volumes and correlation maturity justify it.
• Price the bundle discount against scoped purchasing. The discount is real but conditional, and it rarely survives the comparison once shelfware at premium rates is counted.
• Add tiers at renewal with usage evidence. Demonstrated consumption tells you what to buy next, and it gives you something concrete to negotiate with.

Why we disagree with the advice to license the whole suite at once

Partners often advise licensing the whole ITOM suite upfront, because the bundle discount beats buying tiers later. In roughly 14 of our 25 to 35 files, full suite buyers ran AIOps at a fraction of entitlement for the entire term. The discount never offset the shelfware at premium rates.

The buyers who did better bought Discovery and Event Management scoped to a governed CMDB and proved the value first. They came to the renewal with a year of event volumes by service, which showed exactly where AIOps correlation would pay and sized the tier to those services.

What does suite shelfware cost in a simple example?

A hypothetical shows the effect. Say AIOps costs twice the Discovery unit rate and the suite adds 15 percent off. Licensing AIOps on 3,000 units at that discount costs the equivalent of 5,100 Discovery units. If only 1,000 units would benefit from correlation, buying those later at full price costs the equivalent of 2,000, less than half the suite figure.

What have we seen in ServiceNow ITOM renewals in 2024 and 2025?

Across roughly 25 to 35 ServiceNow files with ITOM components that I benchmarked between 2024 and 2025, the billable CI count was the recurring problem. Four patterns held across them.

• One in two was overpaying. Roughly one environment in two paid for managed CIs that governance would have excluded, mostly transient cloud resources.
• Rescoping recovered 20 to 35 percent. Scoping Discovery schedules to governed resources cut billable CI counts by that range with no loss of operational coverage.
• AIOps shelfware was common. Full suite buyers ran AIOps at a fraction of entitlement in 14 of roughly 30 files.
• Cadence decided the true up. Quarterly reviewers reached renewal with overage exposure near zero, while annual reviewers met true up claims.

The cleanups that worked took the five drivers in the order of the table above, starting with schedule scope and ending with AIOps tier creep. Starting with schedules matters, because every later step is smaller once unmanaged subnets stop feeding the CMDB.

The true up conversation itself is negotiable in a way most buyers do not test. Overage claims respond to scoping evidence, meaning proof that the inflated count came from ungoverned discovery rather than real infrastructure growth. They also respond to growth commitments that give ServiceNow its expansion story at rates you set.

Arrive with the trailing year's consumption report, a deduplicated CMDB and your unit price, and you negotiate a correction. Discover the CI count at renewal, and you negotiate a payment plan.

How should you negotiate a ServiceNow ITOM renewal?

Negotiate on three things: a cleaned count, the unit price benchmark and tier rightsizing. Price growth as pre agreed expansion bands at locked unit rates. Headroom bought upfront pays for units you may never use.

ServiceNow's growth model rewards account expansion, so a credible contraction threat carries weight that a discount request never does. Subscription unit consumption reporting is the document that decides an ITOM renewal, and most customers never review it between cycles.

What will the ServiceNow account team say, and how should you reply?

What contract wording should you ask for?

• A named ratio table. Reference the Subscription Unit Overview version that applies, so the conversion rates cannot change during the term.
• A definition of a managed CI. Tie it to operational status and recent discovery, so retired and stale records fall out of the count.
• Expansion bands at locked unit rates. Growth is priced before you need it, but you pay only when you use it.
• A measurement method for true ups. Agree how and when the count is taken, and a period to correct records before any claim.
• A correction window for unresolved monitored objects. Ask that event sources which do not match a CI are excluded from any true up until you have had a set period to reconcile or suppress them.
• Tier reallocation at renewal. The right to move units from AIOps back to Discovery or Event Management when usage does not support the premium tier.

How does the approach change with the size of your infrastructure?

A company with a few hundred servers and a single data center usually needs Discovery and Event Management and a clean CMDB. For that buyer, the biggest saving is avoiding a suite that the operations team will not use.

A large hybrid environment with several cloud accounts and container platforms has the opposite problem. The count changes every week, so exclusion rules and the quarterly review matter more than the package choice.

The adjacent meters follow the same logic: the ITSM pricing analysis on the seat side, the Now Assist consumption guide where the AI meters inflate the same way, and the renewal playbook for the negotiation calendar around all of it.

What to do next

1. This month. Pull the subscription unit consumption report for the trailing year, split by month and by application.
2. Once you have the report. Calculate your price per managed CI, the ITOM line divided by the billable count, and benchmark on it.
3. Within the quarter. Rescope Discovery to governed resources and exclude ephemeral cloud resources by rule.
4. Before the renewal snapshot. Dedupe and lifecycle the CMDB, because the snapshot prices the baseline.
5. Before you sign. Check which ratio table your order form references and ask for the newer one where it helps you.
6. Every quarter after. Audit the count against the entitlement and explain every increase before ServiceNow asks about it. Our ServiceNow practice can run the renewal with you.

Frequently asked questions