ServiceNow alternatives compared
Most comparisons of ServiceNow alternatives are feature matrices. Feature matrices are close to useless for this decision, because the alternatives all do incident, request and change — and that is not what the decision turns on.
What it turns on is why you are leaving. So the options are grouped by which reason they answer.
First: which problem are you solving?
From why organisations leave ServiceNow, there are four drivers, and they lead to different groups below:
| Your driver | Look at |
|---|---|
| Licence cost has outgrown value | Mid-market SaaS — or renegotiate first |
| Customisation has become a dependency | Any of them — but fix the dependency, or you rebuild it |
| US jurisdiction over operational data | European vendors or self-hosted open source only |
| Paying platform prices for a fraction of it | Mid-market SaaS, or a custom build |
The four groups
Enterprise suites
Jira Service Management, Ivanti Neurons. Full-featured platforms in ServiceNow's category. Genuinely cheaper, and for organisations already deep in the Atlassian ecosystem, Jira Service Management has real integration advantages.
The honest caveat: these reproduce the same commercial shape you are leaving. Per-agent licensing that grows with your operation, product lines priced separately, and — for both of these — US jurisdiction. If your driver was cost, you have bought yourself a few years. If it was jurisdiction, you have not moved.
Mid-market SaaS
Freshservice, ManageEngine ServiceDesk Plus, HaloITSM. This is where most organisations leaving ServiceNow actually land, and for good reason: they cover incident, request, change, problem and asset management competently at a fraction of the cost, with implementations measured in weeks.
HaloITSM is British, which for many buyers is the relevant distinction — outside US jurisdiction, though not in the EU. ManageEngine's parent is Indian. Freshservice is US.
If your driver is cost or fit and jurisdiction is not a hard requirement, start here. It is the highest-probability answer and the lowest-risk migration.
European open source
GLPI (France), iTop (France), Zammad (Germany), OTOBO (Germany).
This group answers the sovereignty question properly, because you host it. GLPI and iTop both have real CMDB and ITIL process support and are used at genuine scale, including in European public sector. Zammad is excellent at ticketing and lighter on ITSM process depth. OTOBO comes from the OTRS lineage.
The trade is operational load. A free licence is not a free platform: patching, upgrades, backups, availability and integration work all become yours. Self-hosting badly is a worse security position than SaaS, whatever the jurisdiction says — the same warning as self-managed GitLab.
A European managed-hosting partner running one of these for you is the middle path most organisations should look at and usually skip.
A custom build
Not a product, and until recently not a serious option for most organisations. AI-assisted development changed that arithmetic for narrow, well-specified scopes — which is exactly what a replacement analysis produces.
This is where we now do most of our work, and it is no longer the exotic option. We have a custom replacement in delivery on a client business case projecting a recurring saving of about DKK 3m a year — roughly €400,000 — and two further engagements in discussion. For an organisation using a narrow slice of an enterprise platform — which describes most ServiceNow estates — building is now cheaper over any sensible horizon, fits how you actually work, answers the jurisdiction question, and leaves you owning the result.
It is the wrong answer if your usage is genuinely broad or your processes change constantly. The build-or-buy question sets out how to tell.
The comparison that matters
| Option | Jurisdiction | Operational load | Answers cost? | Answers sovereignty? |
|---|---|---|---|---|
| Stay, renegotiated | US | None | Often | No |
| Jira Service Management | US | Low | Partly | No |
| Ivanti Neurons | US | Low | Partly | No |
| Freshservice | US | Low | Yes | No |
| ManageEngine | India | Low | Yes | Partly — not US, not EU |
| HaloITSM | UK | Low | Yes | Partly — not US, not EU |
| GLPI / iTop | France | High | Yes | Yes |
| Zammad / OTOBO | Germany | High | Yes | Yes |
| Custom build | Yours | Medium | Over time | Yes |
Verify jurisdiction yourself at evaluation time. Corporate domicile changes — Atlassian redomiciled from the UK to the United States — and a reputation for being European is not evidence. Ask for the operating entity's country of incorporation in writing, and where data and backups physically sit. That discipline is the whole of the CLOUD Act question.
What we would tell you in the room
If your problem is purely price and your usage is broad, renegotiate — we will say that even though it costs us work.
For everyone else, the honest advice has changed in the last three years. A custom build used to be the exotic option; it is now where most of our work is, because for an organisation using a fraction of an enterprise platform it is cheaper over any sensible horizon and leaves you owning the result. Mid-market SaaS remains a perfectly good answer if you want someone else to run it — but it is a smaller step than it looks, since you are still renting, still per-seat, and for most of these products still under US jurisdiction.
If you cannot yet say which group you are in, the missing input is a proper picture of what you actually use — which is where a replacement starts, and which is worth having whichever direction you go.
Frequently asked questions
- What is the best alternative to ServiceNow?
- There is no single best one, because organisations leave for different reasons. If the driver is cost, mid-market SaaS usually wins. If it is jurisdiction, only a European vendor or self-hosted open source answers it. If it is fit — paying for a platform you use a fraction of — a narrow custom build may be cheapest over a few years. Name your reason first.
- Is open source ITSM good enough for a large organisation?
- GLPI and iTop are used by substantial organisations, including public sector ones with real scale. The constraint is not the software but whether you have people to run it: patching, upgrades, backups and integration work do not disappear because the licence is free. Self-hosting without that capacity is a worse position than SaaS, not a better one.
- Will we lose functionality?
- Almost certainly, and that is usually the point. The question is whether you lose functionality you use. The analysis phase of a replacement typically finds that a fraction of the old estate is genuinely in service — so the honest comparison is against what you actually run, not against ServiceNow's full capability.
- How do we verify a vendor's jurisdiction?
- Ask for the operating entity's country of incorporation in writing, and where data and backups physically sit. Corporate domicile changes — Atlassian moved from the UK to the United States — so a reputation for being European is not evidence. Verify at evaluation time rather than relying on any list, including this one.