ITSM tools are software that records, orchestrates, and measures the delivery of IT services, from the initial service desk ticket to incident resolution and the change that prevents recurrence. By 2026, the concept covers five integrated layers: service desk, incident management, observability, CMDB and ITAM, and IT automation. The relevant decision has shifted from which tool to buy to how these layers share data.
What are ITSM tools and why has the concept expanded?
ITSM (IT Service Management) is the discipline that organizes IT as a service provider, with processes such as incident, problem, change, request, and knowledge management, typically referenced in ITIL 4. For a long time, ITSM tools were synonymous with ticketing systems. This definition became too narrow: an incident originates from a monitoring alert, depends on knowing which asset and service were affected, and is often resolved through automation. Each stage of this chain has its own market of tools.
The map below organizes ITSM tools by the question each layer answers and the data it produces. It is this data, and not the interface, that determines whether the operation can correlate an alert with a business service or whether each team works with its own version of the facts.
| Layer | Question that answers | Given that it produces | Examples of tools |
|---|---|---|---|
| Service desk | What was requested or reported, by whom, and by what deadline? | Calls, SLAs, service history, knowledge base | ServiceNow, Jira Service Management, Freshservice, BMC Helix |
| Incident Management (Incident Ops) | Who needs to act now, and how is the response coordinated? | On-call schedules, callouts, incident timeline. | PagerDuty, incident.io, Rootly, xMatters |
| Observability | What is happening in the systems and why? | Metrics, logs, traces, and events | Datadog, Dynatrace, Splunk, Prometheus, Grafana |
| CMDB and ITAM | What exists, who owns it, how much does it cost, and what does it depend on? | Configuration items, relationships, lifecycle, and licenses | ServiceNow CMDB, Flexera One, Lansweeper, Device42 |
| IT Automation | How to perform the correction or change without manual work? | Executions, playbooks, declared state of the infrastructure. | Ansible, Terraform, Rundeck, Workato, n8n |
Magic Quadrant 2026 for ITSM platforms: what the report shows
Gartner published its Magic Quadrant for IT Service Management Platforms on July 27, 2026, authored by analysts Rich Doheny, Jen Lichucki, and Ankita Hundal. According to... Public summary of the report, The research evaluates 16 vendors: Atlassian, BMC Helix, EasyVista, Freshworks, Halo, Ivanti, ManageEngine, Matrix42, OpenText, Salesforce, ServiceNow, SymphonyAI, SysAid, TeamDynamix, TOPdesk, and Xurrent.
The report treats ITSM platforms as a system of record for infrastructure and operations leaders to deliver integrated IT services. This framework reinforces the thesis of this article: the Magic Quadrant evaluates the service desk and process layer, not the observability, incident ops, or automation tools, which are evaluated in separate research.
A ServiceNow communicated to have been positioned as a Leader in the 2026 edition and to have obtained the highest score in three use cases of the supplementary report Critical Capabilities for IT Service Management Platforms: Service Desk Operations, Intermediate ITSM, and Advanced ITSM. The position of the other vendors should be consulted in the report itself or in the official announcements of each company.
Gartner and Magic Quadrant are trademarks of Gartner, Inc. and/or its affiliates, used with permission. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not recommend that technology users select only those vendors with the highest ratings. Gartner research publications represent the opinions of its research organization and should not be construed as statements of fact.
Service desk tools: the registration layer
The service desk is the layer where the user opens the ticket, where the SLA is measured, and where knowledge is published. It is also the most mature layer in the ITSM tools market: all the options below cover incidents, requests, and service catalog. The difference between them lies in the depth of change management, configuration data model, extension to areas outside of IT, and AI governance.
| Tool | Supplier | Rated in the ITSM 2026 Magic Quadrant |
|---|---|---|
| ServiceNow IT Service Management | ServiceNow | Yes |
| Jira Service Management | Atlassian | Yes |
| BMC Helix ITSM (formerly Remedy) | BMC Helix | Yes |
| Freshservice | Freshworks | Yes |
| HaloITSM | Halo | Yes |
| Ivanti Neurons for ITSM | Ivanti | Yes |
| ServiceDesk Plus | ManageEngine | Yes |
| TOPdesk | TOPdesk | Yes |
| SysAid | SysAid | Yes |
| SolarWinds Service Desk | SolarWinds | Not included in the list of evaluated suppliers. |
For large companies and regulated sectors, the criterion that most differentiates service desk tools is not the agent's experience, but rather what happens behind the scenes of the call: whether the incident is linked to a trusted configuration item, whether the change undergoes risk assessment based on real dependencies, and whether the request triggers the approval and service workflow without rework. The guide ITSM ServiceNow in practice It details how to structure these processes on the platform.
Incident management tools: on-call, activation and coordination
Incident ops tools originated in engineering and SRE teams to solve a specific problem: transforming an alert into a person being dispatched, with a duty roster, escalation rules, and an organized war room. They cover the interval between detection and resolution, while the service desk records the impact on the business.
| Tool | Supplier or current situation |
|---|---|
| PagerDuty | PagerDuty |
| incident.io | incident.io |
| Rootly | Rootly |
| FireHydrant | Freshworks announced an acquisition agreement on December 15, 2025. |
| xMatters | Everbridge |
| Opsgenie | Atlassian, being discontinued (end of support on 05/04/2027) |
| SolarWinds Incident Response (formerly Squadcast) | SolarWinds announced the acquisition on March 3, 2025. |
| Better Stack | Better Stack |
| warning | warning |
| PagerTree | PagerTree |
The most relevant aspect of this layer is not any specific functionality, but rather the consolidation process. Atlassian The sale of Opsgenie has ended. The product will be shut down on June 4, 2025, and will be deactivated on April 5, 2027, with the deletion of non-migrated data, redirecting customers to Jira Service Management and Compass. SolarWinds acquired Squadcast to combine observability and incident response. Freshworks announced the purchase of FireHydrant to integrate incident management into Freshservice.
Three ITSM platform vendors have absorbed or incorporated incident ops tools in less than a year. The takeaway for those choosing ITSM tools is straightforward: the boundary between service management and IT operations is being eliminated by the vendors themselves, and hiring a standalone on-call tool today requires assessing the risk of it being discontinued or incorporated tomorrow.
Observability tools: the signals that power ITSM
Observability is the ability to understand the internal state of a system from metrics, logs, and traces. The tools in this layer detect degradation before the user opens a ticket and provide a technical diagnosis of the failure. They do not replace ITSM: they produce the signal, while the ITSM platform transforms the signal into an incident with an assigned owner, priority, and business impact.
| Tool | Supplier or maintainer | Model |
|---|---|---|
| Datadog | Datadog | Commercial SaaS |
| Dynatrace | Dynatrace | Commercial SaaS |
| New Relic | New Relic | Commercial SaaS |
| Splunk | Cisco | Commercial |
| AppDynamics | Cisco | Commercial |
| Honeycomb | Honeycomb | Commercial SaaS |
| Elastic Stack (Elasticsearch and Kibana) | Elastic | Commercial with open-source components |
| Grafana | Grafana Labs | Open source and commercial version |
| Prometheus | Cloud Native Computing Foundation (CNCF) | Open source |
| Zabbix | Zabbix | Open source |
The critical integration point between observability and ITSM is correlation. An environment with three monitoring tools generates a volume of events that no service desk can handle one by one. The solution is to aggregate and correlate events before opening incidents, associating each alert with the affected configuration item and service. This layer reduces MTTR, as shown in the article on [topic to be inserted here]. ITOM and AIOps, and that's where the ITOM on ServiceNow It acts on signals coming from other tools.
CMDB and ITAM tools: the layer that decides the rest.
CMDB (Configuration Management Database) is the repository of configuration items and their relationships. ITAM (IT Asset Management) manages the lifecycle, cost, and compliance of hardware and software assets. Of the five layers, it is the only one whose quality affects all the others: without a reliable CMDB, incident management doesn't know which service was impacted, change management doesn't assess risk based on dependencies, and automation acts on the wrong target.
| Tool | Supplier | Main function |
|---|---|---|
| ServiceNow CMDB, HAM, and SAM | ServiceNow | CMDB with CSDM model, hardware and software asset management. |
| Flexera One | Flexera | ITAM and software and cloud licensing and cost management |
| Snow Software | Flexera | Software Asset Management (SAM) |
| Device42 | Freshworks | Discovery and dependency mapping |
| Lansweeper | Lansweeper | Discovery and inventory of assets |
| Oomnitza | Oomnitza | Technology asset management |
| Matrix42 | Matrix42 | Service and asset management |
| ServiceDesk Plus CMDB | ManageEngine | CMDB integrated with the service desk |
| i-doit | Synetics | IT Documentation and CMDB |
| Lifecycle Insights | ScalePad | Inventory and asset lifecycle for managed service providers |
The table mixes tools that discover assets and tools that are a system of record, and this distinction defines the architecture. Discovery and inventory tools are data sources. The CMDB is where this data is reconciled, deduplicated, and linked to services. When multiple sources feed into the same database, the identification and reconciliation rule, such as the ServiceNow Identification and Reconciliation Engine (IRE), is what prevents duplication and attribute conflicts.
In ServiceNow, the CSDM (Common Service Data Model) organizes this foundation into layers that connect infrastructure, applications, and business services. The guide to Implementing CMDB in ServiceNow with CSDM details the modeling, and the page of CMDB and CSDM describes the service approach. For the difference between asset disciplines, the article SAM x ITAM It delves deeper into the topic.
IT automation tools: from manual fix to governed execution.
IT automation tools implement changes to infrastructure, applications, and processes. They are divided into three groups with distinct functions, and confusing these groups frequently leads to overlapping licenses and automations lacking traceability.
| Group | Tool | Supplier or maintainer |
|---|---|---|
| Infrastructure as code and configuration management | Ansible | Red Hat (IBM) |
| Terraform | HashiCorp (IBM) | |
| Puppet | Perfect | |
| Chef | Progress | |
| Salt Project | Broadcom | |
| Runbook automation and event-driven | Rundeck | PagerDuty |
| StackStorm | Open source project | |
| Integration and automation of workflows (iPaaS) | Workato | Workato |
| Zapier | Zapier | |
| n8n | n8n |
Automation without governance transfers risk instead of reducing it. A change executed by Terraform or Ansible outside of the change management process alters the infrastructure without logging, without impact assessment, and without updating the CMDB. The mature model is automation triggered by ITSM: the request or incident triggers the playbook, the execution is logged in the ticket, and the result updates the configuration item.
ITSM tools: single platform or specialized/niche tools?
Every company that evaluates ITSM tools arrives at the same structural decision: consolidate the layers into a single platform or combine the best tools from each category through integration. Neither option is correct in the abstract, and the choice depends on the operational model, data maturity, and the ability to sustain integrations.
| Criterion | Consolidated platform | Integrated specialized or niche tools |
|---|---|---|
| Data model | A shared CMDB and service model across all processes. | Each tool has its own model; consistency depends on reconciliation. |
| Integration | Native between modules | Built and maintained by the team, with recurring costs. |
| Depth per layer | Wide, with varying depths between modules. | Maximum in each category |
| Governance and auditing | Single registration trail | Distributed paths among tools |
| AI applied to the operation | Operates on unified data. | Limited to the data provided by each tool, except for deep integration. |
| Best fit | Companies that prioritize governance, regulated sectors, ESM in addition to IT. | Engineering-oriented organizations with a mature SRE and prior investment in observability. |
In practice, most large companies adopt a hybrid model: a platform as a system of record for services, assets, and changes, integrated with specialized observability tools. Consolidation appears as a market trend on both sides. ServiceNow reports to its clients that PepsiCo consolidated 33 legacy IT tools and processes into the ServiceNow AI Platform. On the vendor side, the acquisitions mentioned above show ITSM platforms incorporating incident ops.
The factor that makes either model governable is the same: a reliable CMDB, with a defined service model and rules for reconciliation between sources. Without this foundation, the consolidated platform becomes an expensive call repository, and the model of specialized or niche tools becomes a set of systems that disagree on what exists in the environment.
Criteria for evaluating ITSM tools
The criteria below serve to compare ITSM tools in a neutral way, regardless of the vendor. They prioritize what generates cost or risk throughout the contract, not the commercial demonstration.
- Configuration data model: Does the tool offer a CMDB with a documented service model, relationships, and reconciliation rules between multiple discovery sources?
- Integration with other layers: Are there documented APIs and vendor-maintained connectors for the observability, discovery, and automation tools already in use?
- Adherence to processes: Do incidents, problems, changes, requests, and knowledge follow recognized practices, such as ITIL 4, without structural customization?
- AI with governance: Do AI resources operate on controlled data, with traceability of decisions and the possibility of auditing?
- Roadmap and continuity: Does the product show signs of investment or discontinuation, as demonstrated by the cases of Opsgenie and recent incident ops acquisitions?
- Total cost: licenses, integrations, support, and the cost of maintaining reconciled data between tools over five years.
- Regulatory requirements and LGPD (Brazilian General Data Protection Law): Data location, access control, retention, and industry-compliant audit trail.
Common mistakes when choosing ITSM tools
The most frequent mistake is choosing a service desk tool based on the agent's experience and discovering, after go-live, that the CMDB doesn't support change management or event correlation. The second is maintaining monitoring, on-call, and ticketing tools without integration, which multiplies triage work and prevents measuring end-to-end MTTR. The third is automating before governing: playbooks executed outside the change flow reduce effort in the short term and create untracked changes in the environment.
4MATT, a ServiceNow Elite Partner in Brazil with Product Line Achievement (PLA) in ITSM Pro and over 180 certified specialists, conducts the ITSM implementation in ServiceNow with CMDB and CSDM as a basis, in projects with defined scope and price or in managed services.
Frequently Asked Questions
What are ITSM tools?
ITSM tools are software that supports IT service management, covering processes such as incidents, problems, changes, requests, and knowledge. By 2026, the term encompasses five layers: service desk, incident management, observability, CMDB and ITAM, and IT automation, which need to share data for the operation to function end-to-end.
What is the difference between a service desk tool and an ITSM platform?
The service desk tool logs and handles service requests, with SLAs and a knowledge base. The ITSM platform goes further: it integrates change management, issues, CMDB, and assets into a common data model, allowing for the assessment of change risk and the impact of incidents on business services.
Which vendors did Gartner evaluate in the ITSM 2026 Magic Quadrant?
The Magic Quadrant for IT Service Management Platforms, published on July 27, 2026, evaluates 16 vendors: Atlassian, BMC Helix, EasyVista, Freshworks, Halo, Ivanti, ManageEngine, Matrix42, OpenText, Salesforce, ServiceNow, SymphonyAI, SysAid, TeamDynamix, TOPdesk, and Xurrent. ServiceNow announced that it has been positioned as a Leader in this edition.
Do observability tools replace ITSM tools?
No. Observability tools like Datadog, Dynatrace, Splunk, and Prometheus detect and diagnose technical failures. ITSM tools record the impact on the service, define responsibility and priority, control the change that corrects the problem, and maintain the audit trail. The two layers are complementary and connect through the correlation of events.
Why does CMDB carry such a large weight in the choice of ITSM tools?
Because it's the only layer on which all others depend. Without a reliable CMDB, incident reporting doesn't identify the affected service, change management doesn't assess dependencies, and automation might act on the wrong item. The quality of the CMDB determines whether the investment in ITSM tools generates service visibility or just call volume.
What should those who still use Opsgenie do?
Atlassian will discontinue sales of Opsgenie on June 4, 2025, and will shut down the product on April 5, 2027, at which time any unmigrated data will be deleted. Those still using the tool need to plan their migration before that date, either to the options recommended by Atlassian, Jira Service Management and Compass, or to another incident management tool integrated with their current ITSM platform.