Ivanti Neurons for ITSM is licensed by analyst, not by end user, and that single fact drives most of what you pay. You buy named or concurrent analyst seats for the people who work tickets, while the employees who raise requests are unlimited and free, and additional capability comes from separate Neurons modules layered on top. Understanding which costs sit on the analyst seat and which sit on the module is the difference between a contract you can right-size and one that drifts upward every renewal. This explainer is the entry point to the wider Ivanti Neurons pricing guide.
What an analyst license actually covers
The unit you are charged for is the analyst, sometimes called the fulfiller or agent: the person who resolves incidents, fulfills requests and works the queue inside Neurons for ITSM. Everyone else in the organization, the thousands of employees who submit a ticket or browse the catalog, costs nothing extra. This is the standard ITSM split, and it matters because your bill scales with the size of your service desk, not the size of your company. A 40,000-employee enterprise with 120 analysts pays for 120, which is why getting the analyst count right is the highest-leverage number in the whole agreement.
Within the analyst seat, Ivanti distinguishes named from concurrent licensing. A named seat is tied to one specific person; a concurrent seat is shared across a pool and counts only how many are logged in at once. Organizations running shifts or follow-the-sun support almost always pay less on concurrent, because the seat follows the active session rather than the headcount. If your contract is on named seats and your desk runs in shifts, that is the first conversation to have.
Where the modules come in
Neurons for ITSM is one module in a broader Ivanti Neurons platform, and the capabilities buyers often assume are included frequently sit in separate, separately-priced modules. Asset and configuration management, discovery, endpoint and patch management, and the more advanced automation and bot capabilities are typically their own line items rather than features of the core ITSM seat. The headline analyst price can look competitive precisely because the capability you need lives in modules that get added later. A clear breakdown of those module costs is in the Ivanti Neurons module pricing breakdown.
Editions and what they bundle
Ivanti packages Neurons for ITSM into editions that bundle progressively more capability into the analyst seat. A lower edition covers core incident, request and change; higher editions fold in capabilities such as advanced workflow, service-level management or elements of asset and automation. The upgrade decision is worth scrutiny, because editions are where a vendor moves capability you might otherwise buy as a discrete module into the per-seat rate, multiplying its cost across every analyst. Sometimes the edition is the cheaper route; sometimes buying the one module you need standalone is far cheaper than upgrading every seat to get it.
| Cost layer | What it covers | How it scales |
|---|---|---|
| Analyst seat | Core ITSM: incident, request, change, the working queue | Per analyst (named or concurrent) |
| Edition uplift | Advanced workflow, SLM, bundled extras in the seat | Per analyst, multiplied across all seats |
| Add-on module | Discovery, asset, patch, advanced automation | Per module, sometimes per device or node |
Reading your own Ivanti order form
Most of this becomes concrete the moment you open your order form. The document lists the analyst seats and their count, names the edition, and itemizes any modules, but it rarely explains how they relate, so buyers read past the structure and see only the total. Start by finding the seat line and confirming whether it says named or concurrent, then locate the edition name and note which capabilities that edition is meant to include, and finally list every separate module with its own quantity and rate. Laid out that way, the order form stops being one number and becomes three decisions: how many seats, which edition, and which modules, each of which you can question independently.
The exercise also surfaces the quiet additions. A module that appeared mid-term as a small add-on, an edition that was upgraded for a feature only one team needed, or a seat count that grew with a reorganization and never came back down, all show up when the form is read line by line. None of these are visible in the blended total the vendor leads with, which is exactly why reading the structure rather than the sum is the first step toward a contract that reflects how you actually use the platform.
Why the licensing model shapes the negotiation
Because cost concentrates in the analyst seat, the levers that move an Ivanti bill are the seat count, the named-versus-concurrent split, and the edition. Because capability concentrates in modules, the second set of levers is which modules you genuinely use versus which were bundled in and forgotten. A buyer who understands this model negotiates the seat and the modules separately rather than accepting a single blended number, which is the whole point of treating licensing as something to optimize. The discipline scales across vendors in the complete guide to ITSM license optimization.
How we use the licensing model on engagements
When we open an Ivanti contract through our license optimization service and against the Ivanti platform page, the first thing we do is separate the seat cost from the module cost and the edition uplift, because the vendor's quote almost never does. Across 500 engagements and a 30 percent average reduction, the recurring finding on Ivanti is the same: buyers pay for analyst seats and edition uplifts that no longer map to how the desk actually works. The licensing model is not complicated once it is unpacked, and unpacking it is where the savings start.
The gated Ivanti Neurons Buyer Guide maps the full licensing model, seat, edition and module, with a worksheet for separating the three on your own contract.
Frequently asked questions
- How is Ivanti Neurons for ITSM licensed?
- By analyst seat, named or concurrent, for the people who work tickets. Employees who raise requests are unlimited and free. Additional capability such as discovery, asset and automation is licensed as separate Neurons modules on top of the seat.
- What is the difference between named and concurrent Ivanti licenses?
- A named seat is tied to one specific person. A concurrent seat is shared across a pool and counts only those logged in at once. Organizations running shifts usually pay less on concurrent because the seat follows the active session rather than total headcount.
- Are asset and discovery included in Neurons for ITSM?
- Usually not. Asset management, discovery, patch and advanced automation are typically separate Neurons modules with their own pricing. The core analyst seat covers incident, request and change; the rest is layered on, which is why the headline seat price can understate the real cost.
Book an Ivanti review.
We separate seat, edition and module cost on your Ivanti contract and right-size each one. Fixed fee or gainshare.
Book an Ivanti review →