Free Open-Source Ticketing Systems for MSPs (2026)

Updated: August 2026

Freshdesk costs $79/agent/month on the Enterprise plan. Zendesk starts at $55 and climbs fast once you need automations. For a 10-person MSP, that's $6,600-$9,480 per year - just on ticketing.

Meanwhile, a self-hosted open-source helpdesk handles 80-90% of the same workload for $0 in licensing. The trade-off is setup time and self-management. For MSPs already running their own infrastructure, that's not a trade-off - it's Tuesday.

This guide compares 11 open-source ticketing systems worth running in 2026: osTicket, Zammad, FreeScout, GLPI, Request Tracker, UVdesk, Faveo Helpdesk, Helpy, OTOBO, Trudesk, and Diamante Desk. We'll cover features, integrations, Docker deployment, community size, and - most importantly - when you should skip open-source entirely and pay for a commercial tool.

TL;DR

• The short answer. FreeScout for the lightest install, Zammad for the strongest agent UI, GLPI if you need assets and tickets in one tool.
• Lightest install. FreeScout runs on 1 GB and goes live in under 30 minutes.
• Avoid on client queues. Helpy and Diamante Desk are unpatched, no commits since 2023.
• Check the license. Trudesk and Diamante Desk ship with no declared license file.

Open Source Ticketing Systems Compared

Every viable option, compared on what matters before you commit a client-facing queue to it. License and maintenance figures were pulled from each project's GitHub repository in August 2026. For a broader look at service-desk platforms with ITIL capabilities, see our open source ITSM comparison.

Platform and Maintenance

Two entries need a warning rather than a footnote. Helpy has had no commits since March 2023 and Diamante Desk none since November 2023. Both still install and both still work, but nobody is shipping security patches. Neither belongs on a client-facing queue in 2026. They stay on this list because they solve problems the others do not, and because a roundup that quietly drops dormant projects is how people end up deploying them by accident.

Two also ship without a declared license. Trudesk and Diamante Desk have no SPDX license file GitHub can read, which means the usage terms are whatever the repository owner says they are. That is a procurement problem before it is a technical one.

Capabilities

Every tool here does email-to-ticket and every one exposes an API, so neither is a differentiator. SLA depth, maintenance, and install cost are where they separate.

Install Difficulty, Rated

The ratings above use a fixed scale, so they mean the same thing across every tool:

The rating covers getting to a working install, not tuning. Every tool on this list needs backups, TLS, and an upgrade plan before it touches a client queue, and that work is the same regardless of level.

Level is not quality. FreeScout is a 1 and Request Tracker is a 4, and Request Tracker is the more capable system. The number tells you what the first afternoon costs, not what you get.

No tool wins across the board. Each one fits a different MSP setup. Here's how they break down.

Which Self Hosted Ticketing System Fits You

Five questions, asked in order. Stop at the first one that matches.

The specialist branches, if none of the above fit: tickets need Shopify or Magento order context → UVdesk. Your team lives on phones → Trudesk. You already run Oro CRM → Diamante Desk, accepting it is dormant. You want a public forum in front of the queue → Helpy, same caveat.

If you are choosing between only two, the split that matters most often is FreeScout against osTicket. FreeScout is a shared inbox that grew ticket structure; osTicket is a ticketing system that reads email. Pick FreeScout if your team thinks in conversations, osTicket if it thinks in queues.

Where Open Source Ticketing Pays Off

Ticketing is one of the easier line items to bring in-house, because the things that usually make self-hosting hard don't apply to an MSP:

• The infrastructure is already there. You're managing servers for clients. One more Docker container is not a new capability.
• Ticket volume rarely justifies the enterprise tier. A 500-endpoint MSP processing 200-400 tickets a month is paying for AI routing and advanced automation it will never queue up.
• The ticket history stays portable. A self-hosted tool keeps the database under your control, so a future migration is an export rather than a support case.

A free open-source ticketing system won't replace your PSA. It can replace the helpdesk component, particularly for internal ops, client-facing portals, or teams that don't need the full ConnectWise stack.

osTicket - The Reliable Workhorse

osTicket has been around since 2010. It's not flashy, but it works. If you need a straightforward ticketing system open-source that handles email-to-ticket conversion without fuss, this is the default choice for a reason.

What MSPs like: Dead-simple setup. Email piping works out of the box. Custom forms and fields let you build intake workflows for different client types. The agent panel is functional - not pretty, but fast.

What MSPs don't like: The UI looks like 2015. No built-in chat or social media channels. The plugin ecosystem is thin compared to Zammad or GLPI. Reporting is basic without third-party tools.

Best fit: MSPs under 500 endpoints who want email-based ticketing with a client portal. If your workflow is "client emails, ticket gets created, tech resolves it" - osTicket does that cleanly.

Docker Deployment

bash
git clone https://github.com/osTicket/osTicket.git
cd osTicket

The community Docker image most commonly used is devinsolutions/osticket:

bash
docker run -d --name osticket \
  -p 8080:80 \
  -e MYSQL_HOST=db \
  -e MYSQL_DATABASE=osticket \
  -e MYSQL_USER=osticket \
  -e MYSQL_PASSWORD=your_secure_password \
  devinsolutions/osticket

Pair it with a MySQL container and you're running in under 10 minutes.

Zammad - The Modern Pick

Zammad is what you'd get if someone rebuilt Zendesk as open-source. It's the most polished helpdesk open-source option available - clean UI, multi-channel support, solid search powered by Elasticsearch.

What MSPs like: Real multi-channel ticketing - email, phone, chat, Twitter, and Telegram all feed into one queue. The interface is fast and modern. Built-in knowledge base. Mentions and internal notes work like you'd expect from a 2026 tool. LDAP integration out of the box.

What MSPs don't like: Resource-heavy. Zammad needs Elasticsearch, PostgreSQL/MySQL, and Redis running alongside it. A minimum of 4 GB RAM for the server - more like 8 GB if you're handling 1,000+ tickets/month. Ruby stack means fewer MSP techs can troubleshoot it compared to PHP tools.

Best fit: MSPs with 10+ technicians who need multi-channel support and care about the agent experience. If your team complains about the interface in ConnectWise, Zammad will feel like a massive upgrade. Our Zammad review for MSPs goes deeper on fit and limits.

Docker Deployment

Zammad provides an official Docker Compose setup:

bash
wget https://raw.githubusercontent.com/zammad/zammad-docker-compose/master/docker-compose.yml
# Edit .env for your passwords and domain
docker compose up -d

This spins up Zammad, PostgreSQL, Elasticsearch, Redis, and Memcached. It's heavier than osTicket, but the compose file handles the complexity.

FreeScout - The Lightweight Contender

FreeScout markets itself as a free Help Scout alternative. It's the leanest option on this list - runs on shared hosting if you want, though Docker is cleaner.

What MSPs like: Minimal footprint. If you just need shared mailbox functionality with ticket tracking, FreeScout does it without the overhead. Module system lets you add only what you need. The interface is clean and fast. PHP-based, so your team already knows the stack.

What MSPs don't like: Core features are thin. SLA management, satisfaction surveys, and advanced automations all require paid modules ($2-$19 each). That "free open-source ticketing system" pitch gets muddied when you need $50-$100 in modules for a real setup. No built-in chat or phone integration.

Best fit: Small MSPs (under 5 techs) who want a shared inbox with structure. Also works well as an internal IT helpdesk alongside your main PSA.

Docker Deployment

bash
docker run -d --name freescout \
  -p 8080:80 \
  -e DB_HOST=db \
  -e DB_DATABASE=freescout \
  -e DB_USERNAME=freescout \
  -e DB_PASSWORD=your_secure_password \
  -e SITE_URL=https://helpdesk.yourmsp.com \
  tiredofit/freescout

FreeScout runs comfortably on 1 GB RAM. For the full rundown, see our FreeScout review. Pair with MariaDB and you're set.

GLPI - The Asset Management Play

GLPI isn't primarily a helpdesk - it's an IT asset management platform that happens to include solid ticketing. If you need a free ticketing system open-source that also tracks every laptop, switch, and license in your client environments, GLPI is the only real option.

What MSPs like: The CMDB is genuinely good. Automatic inventory with the FusionInventory agent (now GLPI Agent) pulls hardware and software data from endpoints. Ticketing ties directly to assets - when a client reports an issue, you see their machine specs, installed software, and warranty status in the same view. Change management, problem management, and SLA tracking are built in.

What MSPs don't like: The UI is functional but dated. Initial setup is more complex than osTicket or FreeScout because you're configuring both asset management and ticketing. The learning curve is steeper. The ticketing side alone doesn't match Zammad's polish.

Best fit: MSPs who want to consolidate asset tracking and ticketing into one self-hosted tool. Especially useful if you're already doing inventory management manually or paying for a separate ITAM tool like Snipe-IT.

Docker Deployment

bash
docker run -d --name glpi \
  -p 8080:80 \
  -e MARIADB_HOST=db \
  -e MARIADB_DATABASE=glpi \
  -e MARIADB_USER=glpi \
  -e MARIADB_PASSWORD=your_secure_password \
  diouxx/glpi

GLPI's Docker image includes Apache and PHP. Add MariaDB separately. Plan for 2-4 GB RAM depending on asset count.

Request Tracker - The Enterprise Veteran

Request Tracker (RT) has been running since 1996. It's the oldest tool on this list and shows it - but for MSPs handling complex, high-volume ticket workflows with deep customization needs, nothing else comes close in the open-source world.

What MSPs like: Extremely customizable workflows. Custom fields, lifecycle management, approval chains, and dependency tracking between tickets. Handles thousands of tickets per day without breaking. Powerful search and reporting. Integrates with LDAP, SSO, and pretty much anything via its API.

What MSPs don't like: The UI is rough. Setup requires Perl knowledge. Documentation is extensive but assumes sysadmin-level comfort. Not something you hand to a junior tech and say "figure it out." Community is smaller than the PHP-based tools.

Best fit: Larger MSPs (20+ techs) or NOC operations processing 500+ tickets/day with complex routing and approval requirements. If your ticketing needs are simple, RT is overkill.

Docker Deployment

bash
docker run -d --name rt \
  -p 8080:80 \
  -e RT_DB_HOST=db \
  -e RT_DB_NAME=rt \
  -e RT_DB_USER=rt \
  -e RT_DB_PASSWORD=your_secure_password \
  netsandbox/request-tracker

Community Docker images are available but less maintained than Zammad's or GLPI's. Many RT deployments still run on bare metal or VMs.

Those five are the general-purpose picks. The six below are narrower, each one winning in a specific situation: e-commerce order context, contractual SLA enforcement, community forums, ITSM process control, mobile-first teams, and CRM-linked support.

UVdesk - The E-Commerce Specialist

UVdesk is built on Symfony and aimed at e-commerce support. Native integrations with Shopify, Magento, WooCommerce, and Amazon pull order history into the ticket view, removing a lot of context switching.

It is open source under OSL-3.0, and the company also runs a paid SaaS version. Free covers core ticketing, knowledge base, and workflow automations. Paid tiers add reporting and priority support. Note that OSL-3.0 is a copyleft licence with patent-retaliation terms, so run it past whoever signs off on your licensing before it goes into a client-facing deployment.

Maintenance: last commit October 2025. Not dormant, but the cadence has slowed from where it was.

Best fit: D2C brands and small e-commerce shops where every ticket needs order context. Not the right pick for pure IT helpdesk use.

Reviews: UVdesk on G2 (4.2), UVdesk on Capterra (4.4), UVdesk on Trustpilot.

Faveo Helpdesk - The SLA Enforcer

Laravel and MySQL. Faveo leans into SLA management, with strong escalation rules, business hour calendars, and per-client SLA configuration. The free version on GitHub is fully usable, though some advanced features like the iOS app are paid-only.

The UI is functional, not beautiful. Email piping, knowledge base, and customer portal all work as you'd expect. Faveo has decent multi-language support, which matters if your support team spans regions.

Best fit: Support teams that need to enforce contractual SLAs and want concrete reporting on breach rates.

Reviews: Faveo on G2 (4.1), Faveo on Capterra (4.4).

Helpy - The Community Forum Hybrid

Helpy is a Rails-based helpdesk that bundles community forum, knowledge base, and ticketing in one app. The forum piece is the differentiator: it front-loads support deflection by letting users help each other before opening tickets.

Self-hosting the free version is straightforward via Heroku or Docker. Paid Helpy Pro adds CSAT surveys, a real-time chat widget, and SSO.

Maintenance: dormant. The last commit landed in March 2023. Three years without a patch means any vulnerability found since then is still there. Treat Helpy as a reference implementation of forum-plus-ticketing rather than something to deploy, unless you are prepared to maintain the fork yourself.

Best fit: SaaS companies in early-stage support that want a public knowledge base and forum alongside ticketing.

Reviews: Helpy on G2 (4.0), Helpy on Capterra (4.0).

OTOBO - The ITSM Heavyweight

OTOBO is the community fork of OTRS, which went mostly closed source in 2019. Rother OSS maintains it and offers a paid managed service. Perl backend, though you don't need to touch Perl to use it.

OTOBO is the most enterprise-shaped tool on the list. ITSM modules, change management, configuration management, dynamic fields, ACL rules, and a process workflow engine. It is what big German manufacturing IT departments run.

Best fit: Large internal IT operations that need ITSM-grade process control and have an admin willing to learn the system.

Reviews: OTOBO on Capterra (5.0, thin sample).

Trudesk - The Mobile-First Option

Trudesk runs on Node.js and MongoDB, which makes it stand out in a sea of PHP. Native iOS and Android apps, a clean UI, group-based ticketing, and a notice board for agent communication. Docker install is one of the smoother experiences here.

Development pace has fluctuated; verify recent repo activity before you commit. The MongoDB requirement is a slight friction point in a SQL-only shop.

Best fit: Small to medium internal IT teams that want a mobile-first feel and don't mind running a Node stack.

Maintenance: last commit May 2026, so it is alive. It ships without a declared licence file, though, which is worth resolving before production use.

Reviews: Trudesk has no significant presence on G2, Capterra, or Trustpilot yet. Check the GitHub repo for community activity instead.

Diamante Desk - The CRM-Linked Pick

Diamante is built on Symfony with optional Oro CRM integration. The CRM tie-in is the differentiator: tickets land in the same database as your customer records, which makes customer history queries trivial.

Maintenance: dormant. The repository moved to eltrino/diamantedesk-application and last saw a commit in November 2023. It also ships without a declared licence file, so the usage terms are unclear. The hosted site is still up, which makes the project look healthier than the code does. Only worth considering if you are already deep in Oro CRM and willing to own the maintenance.

Best fit: Teams already running Oro CRM that want a tight support layer.

Reviews: DiamanteDesk on G2 (3.9), DiamanteDesk on Capterra.

When to Use Open-Source vs. Commercial Ticketing

Open-source isn't always the right call. Here's the breakdown.

Use open-source when:

• Your monthly helpdesk spend exceeds $500 and you have a tech who can manage the deployment
• You need full control over ticket data - compliance, data residency, or simply not trusting a SaaS vendor with client information
• Your ticketing needs are straightforward: email-to-ticket, assignment, resolution, reporting
• You're already running Docker infrastructure and adding one more service costs you nothing

Pay for Freshdesk, Zendesk, or Halo when:

• You need deep PSA integration that open-source tools can't match (dispatch, billing, time tracking all connected)
• Your team doesn't have capacity to maintain another self-hosted service
• You need polished client-facing portals with branding, surveys, and chat widgets out of the box
• AI-powered ticket routing and response suggestions matter to your workflow at scale

The real question isn't "free vs. paid." It's whether your MSP has the operational capacity to self-host. If you're already running TacticalRMM, Wazuh, or other self-hosted tools, adding a ticketing system is incremental. If everything you run is SaaS, spinning up Docker infrastructure just for ticketing might not make sense.

For MSPs building an open-source stack, the OpenMSP community is worth checking - it's where operators share deployment guides, integration patterns, and real-world configurations for tools like these.

Building an open-source MSP stack? Flamingo is working on an open platform that ties RMM, ticketing, and automation together - without the vendor tax. Check out the OpenMSP community to see what MSPs are building right now.