The pull of open source ITSM is simple: own your data, dodge per-agent pricing, and run the same incident, problem, change, and asset workflows ITIL describes - without writing ServiceNow a check. The pain is just as simple: somebody has to host it, patch it, upgrade it, and keep the database from rotting. This guide compares the 12 open source ITSM tools that ship enough today to run a real service desk in 2026, with the trade-offs and review scores laid out side by side so you can shortlist in an hour.

TL;DR: Open Source ITSM at a Glance

ToolBest ForLicenseG2 Rating
GLPIAll-in-one ITSM and asset management for mid-size ITGPL v34.6
iTopCMDB-first ITIL teamsGPL v3 (community)4.3
ZammadMulti-channel modern helpdeskGNU AGPL v34.5
OTOBOEnterprise workflow and ITIL processesGPL v3n/a
KIX StartService desk and asset for SMB ITGPL v3n/a
Snipe-ITPure asset and license trackingAGPL v34.6

Open source ITSM in 2026 means free software you self-host (or pay a partner to host) covering ticketing, asset management, knowledge base, and ITIL-aligned process work. The 12 tools below are the ones still actively maintained, with public GitHub releases inside the last 12 months.

Why Pick Open Source ITSM Over a SaaS Suite

ServiceNow, Jira Service Management, and Freshservice each charge per agent, per month, often with a multi-year commitment. For a 10-person internal IT team or a small MSP, that's $15k to $60k a year before plugins. Self-hosting GLPI or Zammad costs the price of a VM, maybe a part-time admin, and a bit of patience during upgrades. The same calculus applies to open source RMM choices and to most of the rest of the modern IT stack.

The trade is real. You inherit the patching schedule, the database tuning, the SSO setup, the SAML cert rotation, the email parser quirks. Worth it when:

  • Data sovereignty matters. Healthcare, defense contractors, EU-only customers, government work - keeping ticket data on hardware you control closes a compliance gap.
  • Workflow customization is core. You want to fork the source, add a custom queue type, or wire ticketing into an internal app SaaS vendors won't touch.
  • Budget beats convenience. A $0 license fee plus one fractional admin still beats six figures of SaaS for many teams.

The flip side: if you don't have someone who's comfortable editing config files and reading Apache logs, the savings evaporate into outage hours.

The 12 Best Open Source ITSM Tools in 2026

1. GLPI

GLPI (Gestionnaire Libre de Parc Informatique) is the heavyweight of the open source ITSM world. It covers ticketing, change, problem, asset inventory, software licenses, contracts, and a self-service portal in one PHP/MySQL stack. The plugin marketplace adds CMDB depth (Fields, FusionInventory, Formcreator) without touching core code. Active since 2003, still shipping monthly point releases, GLPI 10 brought a refreshed UI that finally feels current.

Strong fit for: internal IT teams of 20 to 500, MSPs running a customer-tenanted instance per client, schools and public-sector orgs that already standardized on it across Europe. GLPI has deep adoption in French and Brazilian public-sector IT, which is the kind of reference list that closes procurement conversations.

Weak fit for: teams that need an enterprise SLA out of the box, or anyone who can't tolerate a PHP stack on the backend. Plugins are uneven, and upgrade-time plugin compatibility is the most common Reddit complaint.

Reviews: G2 4.6/5, Capterra 4.5/5. No Trustpilot listing as of May 2026.

2. iTop (Combodo)

iTop is the open source ITSM tool to pick when the CMDB drives everything. Combodo built it around ITIL v3 processes from day one, so configuration items, relationships, and impact analysis are first-class objects, not a bolt-on. The community edition is free under GPL v3; Combodo also sells a paid iTop Hub with extensions and support.

Best for IT shops with a mature ITIL practice and a real configuration management database to populate. Teams that just want fast ticketing usually find iTop's setup curve too steep for the payoff.

Reviews: G2 4.3/5, Capterra 4.4/5. No Trustpilot listing as of May 2026.

3. Zammad

Zammad is the modern face of open source helpdesk. The Ruby on Rails app ships with email, Telegram, X, Facebook Messenger, WhatsApp, and SMS channels, plus a clean agent UI that doesn't feel like 2012. It's AGPL v3, so source-code obligations apply if you build a public-facing modified version. For internal self-hosting that's irrelevant.

Where it wins: teams that route customer or employee tickets across more than two channels, and care about agent experience. Where it loses: deep CMDB work and ITIL change boards. Zammad doesn't go there.

Reviews: G2 4.5/5, Capterra 4.5/5, Trustpilot 3.2/5 (single-review German page; treat with skepticism).

4. OTRS (Open Ticket Request System)

OTRS is the granddaddy. The commercial fork from OTRS Group is now paid-only, but the codebase lives on through its forks (covered below). The original OTRS still appears on review sites with strong scores from teams running older self-hosted versions or the paid SaaS.

Useful as a reference point and for orgs that already have an OTRS install humming along. New deployments should start with OTOBO or Znuny, not OTRS itself, since the community-edition tap closed in 2020.

Reviews: G2 4.4/5, Capterra 4.5/5. Trustpilot page exists with no reviews as of May 2026.

5. OTOBO

OTOBO is the most active open source OTRS fork. The Rother OSS team picked up where the community edition left off, modernized the Perl backend, added a Docker-based install, and shipped a redesigned agent interface. ITIL incident, problem, change, and service catalog modules all stayed.

Best for teams that need full ITIL process coverage in open source. That's a narrow club, and OTOBO is the strongest entrant. Documentation is improving but still trails GLPI.

Reviews: Capterra 4.5/5. No G2 or Trustpilot listings as of May 2026.

6. KIX Start

KIX is a German-engineered open source ITSM platform with a free "Start" edition and a paid "Pro" tier. Start covers ticketing, asset management, customer portal, and a knowledge base. KIX 18 (the current series) ships as a containerized stack and includes a mobile-first agent app, which is unusual in this category.

Strong for technical customer support teams - field service, plant maintenance, manufacturing - where the asset-to-ticket link matters more than ITIL change ceremony.

Reviews: Capterra listing live. No G2 or Trustpilot listings as of May 2026.

7. Request Tracker (RT)

Best Practical's RT is the workhorse of academic and engineering teams. The Wikimedia Foundation, Best Buy, and a long tail of universities and research labs run on it. The interface looks like 2006 and that's a feature - it loads in 200ms on any browser, runs on a Raspberry Pi, and the queue/SLA/scrip model has been stable for two decades. Recent releases added a REST 2 API and saner email parsing.

Pick RT when you want a configurable engine to track anything (incidents, FOIA requests, asset checkouts, contracts) and the agents are technical enough to live without a modern UI. For teams comparing it to broader IT ticketing software, RT trades UI polish for unmatched flexibility.

Reviews: G2 listing live, Capterra listing live. No Trustpilot listing as of May 2026.

8. osTicket

osTicket is the PHP/MySQL helpdesk that millions of SMBs cut their teeth on. The free Community Edition handles email-to-ticket, web forms, canned replies, SLA timers, and a basic knowledge base. The paid Cloud Edition adds AI and managed hosting.

Where it shines: a single IT person who needs a ticket queue today and a Sunday afternoon to install it. Where it shows its age: the UI is firmly mid-2000s, and there's no native multi-channel beyond email and web.

Reviews: G2 4.3/5, Capterra 4.4/5. No Trustpilot listing as of May 2026.

9. UVdesk

UVdesk from Webkul is an open source helpdesk built on Symfony, with a strong angle toward e-commerce support (Shopify, Magento, OpenCart connectors). The Community Edition is free under MIT; the enterprise SaaS version costs per agent. Multi-channel support, workflow automations, and a knowledge base ship in the open source build.

Best fit: SMB merchants and the IT teams that support them. Less useful for classic internal IT work. The data model is helpdesk, not full ITSM.

Reviews: G2 4.4/5, Capterra 4.4/5. No Trustpilot listing as of May 2026.

10. FreeScout

FreeScout is the open source clone of Help Scout. PHP/Laravel, shared inbox model, conversation threading, and a free-forever core with optional paid modules for SLA, time tracking, and a knowledge base. Active GitHub repo, lively community on Discord.

Pick FreeScout when the team works out of a shared inbox today and graduating to a true ticketing tool feels like overkill. It's not ITSM in the ITIL sense, but for IT teams under ten people it covers 80% of the day-to-day need.

Reviews: Capterra 4.5/5. No G2 or Trustpilot listings as of May 2026.

11. HESK

HESK is the lightest weight tool on this list. A single-file PHP installer, MySQL backend, runs on shared hosting that costs $5 a month. The free Community Edition gives you ticketing, a knowledge base, canned responses, and email piping. The SysAid-backed paid version layers automations and cloud hosting on top.

Right call when you need a ticket queue inside a week, the IT team is one person, and you don't expect to scale past 1,000 tickets a month.

Reviews: G2 listing live, Capterra 4.6/5. No Trustpilot listing as of May 2026.

12. Snipe-IT

Snipe-IT isn't a ticketing tool. It's the open source IT asset management system that pairs with every tool above. License tracking, hardware check-in/out, depreciation, accessories, consumables, audit log. Laravel, Docker install, REST API.

Strong choice when your "ITSM" pain is really "where is the MacBook I assigned to a contractor in 2024." Many teams run Snipe-IT alongside GLPI or Zammad rather than as a standalone.

Reviews: G2 4.6/5, Capterra 4.6/5, Trustpilot listing (limited reviews as of May 2026).

How to Pick the Right Open Source ITSM Tool

Three filters cut the choice down fast.

  • Process depth. If the team has formal change advisory boards, problem-management cadence, and a CMDB to maintain, the shortlist is GLPI, iTop, and OTOBO. If it's "log a ticket, fix the laptop," the shortlist is FreeScout, HESK, or osTicket.
  • Channel mix. Email-only teams can pick anything. Multi-channel (Slack, WhatsApp, Telegram, social) narrows the field to Zammad and UVdesk.
  • Self-host appetite. If nobody on staff is comfortable with Linux, Docker, and MySQL backups, none of these are a good idea. Pay for a managed hosting partner (Combodo for iTop, Rother for OTOBO, Teclib for GLPI) or use the paid SaaS tier most projects now offer.

A pilot trumps a spreadsheet. Spin up the top two contenders in a VM, import 50 real tickets, and let two agents work a week of email. Whichever loses fewer tickets wins. Teams that want a deeper feature-by-feature breakdown of ticketing options should also see the best helpdesk ticketing software roundup before committing.

Where OpenFrame Fits

For MSPs and internal IT teams that decide open source is more cost than saving, OpenFrame is the AI-native, no-lock-in alternative built by Flamingo. It ships native PSA, ticketing, asset visibility, and AI triage in one platform. No Halo bolt-on, no per-agent invoice surprise, and no Perl backend to patch on a Sunday. Pricing is published, contracts are month-to-month, and there is no rate card that doubles in year three when the budget approval can't be reopened.

Open source ITSM is the right answer when self-hosting is core. OpenFrame is the right answer when teams want the same control, the same data ownership, and the same affordability without the operational overhead of running a server farm just to triage password resets.

Frequently Asked Questions

What Is the Difference Between ITSM and a Helpdesk?

A helpdesk handles incoming tickets - email, chat, phone. ITSM is the broader practice that wraps the helpdesk in formal incident, problem, change, release, and asset processes, usually aligned with ITIL. Every ITSM tool includes a helpdesk; not every helpdesk is full ITSM. GLPI and OTOBO sit at the ITSM end. FreeScout and HESK sit at the helpdesk end.

Is GLPI Really Free, or Do You Eventually Have to Pay?

GLPI core is GPL v3 and free forever for self-hosted use. Teclib, the company behind GLPI, sells GLPI Network - a paid subscription that bundles certified plugins, security updates, and support. The free edition runs production workloads for thousands of orgs without paying a cent.

What Is the Best Open Source ITSM for an MSP?

GLPI is the most common pick because it supports multiple entities (tenants) natively, which lets one MSP run isolated views per client from a single install. Zammad and Snipe-IT pair well as add-ons for ticketing and asset tracking. The trade-off versus a commercial PSA is that you build the customer billing and rate-card logic yourself.

Does Open Source ITSM Mean No Support Contract?

No. Almost every project on this list has a commercial partner that sells L2/L3 support, hosting, and certified upgrades - Teclib for GLPI, Combodo for iTop, Zammad GmbH for Zammad, Rother OSS for OTOBO, Best Practical for RT. The license is free; the human help isn't.

How Long Does It Take to Deploy an Open Source ITSM Tool?

A solo admin can stand up GLPI, osTicket, or HESK on a fresh Linux VM in an afternoon. Production-ready, with SSO, email piping, SLA configuration, custom queues, and a populated CMDB, takes one to four weeks depending on complexity. iTop and OTOBO sit at the longer end because of the ITIL data model setup.

Can I Migrate From ServiceNow or Jira to Open Source ITSM?

Yes, with effort. GLPI and Zammad have CSV import tools that handle tickets and users; CMDB data usually needs a custom script. Expect a few weeks of mapping fields, cleaning data, and parallel-running both systems before cutting over. For tickets with deep attachment history, the API path beats the CSV path every time.

The teams who succeed with open source ITSM treat it like running their own database: a real engineering commitment, not a free lunch. The teams who fail picked it on price alone.

Kristina Shkriabina

Kristina Shkriabina

Kristina runs content, SEO, and community at Flamingo and OpenMSP. She spent years as a correspondent for Ukraine's Public Broadcasting Company before making the jump to tech. Now she covers MSP stack decisions and strategy. You can connect with her in the OpenMSP community or on LinkedIn.