8 Best Open Source Helpdesk and AI Customer Support Platforms (2026)
If you are shopping for a helpdesk in 2026, the pitch from Zendesk, Intercom, and Chatbase is the same: hand us your customer conversations and pay per seat, per resolution, or per message, forever. Open source flips that deal. Your support data stays on your infrastructure, the software costs nothing, and when the vendor changes pricing you shrug.
The catch is that "open source helpdesk" now means two different things. The classic generation (osTicket, Zammad, FreeScout) is ticketing software: solid, proven, and mostly built before AI answered anything. The new generation treats an AI agent as the first responder and the humans as the escalation path. Both are on this list, because which one you need depends on the team you run.
Full disclosure before we start: Murphy is our product. It is on this list because it belongs here, but you should read that entry knowing who wrote it. Every other tool below gets the same honest treatment, including the things they do better than we do.
What to actually compare
Three questions sort the whole field faster than any feature grid:
Do you want AI answering first, or humans? Bolting a chatbot onto a ticketing system is not the same as a platform designed around an agent. If most of your volume is repetitive questions, AI-first saves real hours. If your support is mostly judgment calls, a great ticketing workflow matters more.
What can you afford to run? Some of these go live on a $5 VPS with shared hosting. Others want Postgres, Redis, Elasticsearch, and 4GB of RAM before they say hello. Self-hosting is only free if you price in the ops.
Does the license matter to you? MIT and GPL are simple for internal use. AGPL (Zammad, FreeScout, Murphy) adds a network clause that only bites if you modify the software and resell it as a service. For running your own support desk, any of them is fine.
1. Murphy
Stack: Next.js and Postgres. License: AGPL. The angle: AI-first, and the only tool here that works with your coding agents, not just for your customers.
Murphy is an AI support agent you train on your own site and docs in a few minutes. It answers chat and email in the customer's language, follows your written rules for things like refunds and cancellations, and hands the conversation to a human the moment it is not sure instead of guessing. Every answer comes with a trace: what it retrieved, which rules applied, what it said. When it gets one wrong, you correct it once and the correction becomes a pinned answer.
The unusual part is what happens after the conversation. Murphy ships an MCP server, so Claude Code or any MCP client can pull tickets and work cases. And with Dispatch, a support ticket becomes a GitHub issue that your coding agent picks up and turns into a pull request. A customer reports a bug, a human clicks approve, and the fix arrives as a PR. No other tool on this list closes that loop.
Where it loses: it is the youngest project here by a decade in some cases. Fewer channels than Chatwoot (no WhatsApp or Instagram yet), no phone support, and no long enterprise track record. If you need a battle-tested ticket queue for a 40-person support org today, Zammad is the safer pick.
Best for: startups and product teams who want AI handling the volume and their existing coding agents fixing the causes.
2. Chatwoot
Stack: Ruby on Rails, Postgres, Redis. License: MIT core. The angle: the most complete open source Intercom alternative.
Chatwoot is what most people find first when they search for an open source Intercom alternative, and the reputation is earned. Website live chat, email, WhatsApp, Telegram, Facebook Messenger, and Instagram all land in one shared inbox. The product is polished, the community is large, and it is actively developed.
Where it loses: AI is an add-on, not the core. Captain, their AI layer, is part of the paid tier, so the self-hosted free experience is mostly a (very good) human-first inbox. It also wants real infrastructure: Rails plus Postgres plus Redis is not a weekend shared-hosting install.
Best for: teams that want the full omnichannel suite and have humans ready to staff it.
3. Zammad
Stack: Ruby on Rails, Elasticsearch. License: AGPL. The angle: the serious ticketing system, structurally closest to Zendesk.
If you searched for an open source Zendesk alternative, Zammad is the honest answer. Full ticket management, SLA policies, escalation rules, macros, a knowledge base, and reporting that an operations manager would recognize. It is governed by a foundation and developed commercially from Berlin, which is a healthy setup for longevity.
Where it loses: weight. Elasticsearch and 4GB of RAM before you start, and the interface feels like the enterprise software it is. AI capabilities are not the point of the product.
Best for: IT teams and support orgs that live in tickets, SLAs, and process.
4. FreeScout
Stack: PHP (Laravel). License: AGPL. The angle: the lightest real helpdesk you can run.
FreeScout is a self-hosted clone of Help Scout, and it is famously easy to run: about 1GB of RAM, works on shared hosting, live in under half an hour. The core is a clean shared mailbox, and a large catalog of inexpensive paid modules adds whatever else you need.
Where it loses: the module model means the out-of-box experience is intentionally minimal, and AI is not part of the story. It is email-first; if chat is your main channel, look elsewhere.
Best for: small teams and solo founders who want a real helpdesk on a $5 VPS.
5. osTicket
Stack: PHP. License: GPL. The angle: the veteran that will not die, in a good way.
osTicket has been running support desks since 2003. It is stable, deployed everywhere, documented to death, and runs on nearly nothing. Schools, city governments, and internal IT desks run it for years without thinking about it.
Where it loses: it looks and feels its age, and modern channels and AI are simply not what it does. You adopt osTicket for reliability, not delight.
Best for: budget-constrained internal IT and anyone who values boring stability above all.
6. Frappe Helpdesk
Stack: Frappe framework (Python). License: AGPL. The angle: the modern-feeling newcomer from the ERPNext family.
Frappe Helpdesk brings the clean UI energy of newer SaaS tools to self-hosted ticketing, and it plugs naturally into the rest of the Frappe ecosystem if you already run ERPNext.
Where it loses: it makes the most sense inside that ecosystem. As a standalone pick it is younger and less proven than Zammad or osTicket.
Best for: teams already on Frappe or ERPNext.
7. UVdesk
Stack: PHP (Symfony). License: MIT. The angle: helpdesk with an e-commerce bent.
UVdesk comes from Webkul and leans toward store owners, with integrations aimed at e-commerce workflows. The community edition is genuinely open source under a permissive license.
Where it loses: development pace has been slower than the leaders here, and the audience focus is narrow.
Best for: e-commerce shops that want a permissive-license helpdesk.
8. Papercups (a warning, not a recommendation)
Papercups deserves a mention only because people still search for it as an open source Intercom alternative. It was a promising Elixir-based project, and it has been effectively dormant for years. Do not build your support stack on it in 2026. If Papercups is what brought you here, Chatwoot covers the same ground actively, and Murphy covers the AI-first version of it.
The comparison at a glance
| Platform | AI-first | Channels | Runs on | License | Best for |
|---|---|---|---|---|---|
| Murphy | Yes, plus agent dispatch | Chat, email, API/MCP | Small VPS or Vercel | AGPL | Startups with coding agents |
| Chatwoot | Add-on (paid) | Chat, email, WhatsApp, social | Real server | MIT core | Omnichannel human teams |
| Zammad | No | Email, chat, phone, social | Heavy (4GB+) | AGPL | Process-driven support orgs |
| FreeScout | No | Email-first | Shared hosting | AGPL | Small teams, tiny budgets |
| osTicket | No | Email, portal | Nearly anything | GPL | Internal IT, stability |
| Frappe Helpdesk | No | Email, portal | Frappe stack | AGPL | ERPNext users |
| UVdesk | No | Email, portal | PHP hosting | MIT | E-commerce |
| Papercups | No | Chat | Dormant | MIT | Nobody in 2026 |
So which one?
If your support volume is mostly repeated questions and your team ships software, pick the AI-first tool and let humans handle exceptions. That is the bet Murphy makes, and you can try it hosted or read the code first, since the whole point of this list is that you never have to trust a vendor's word again.
If your support is human judgment all the way down, Chatwoot for breadth, Zammad for process, FreeScout for lightness, and osTicket for longevity are all legitimate answers, and none of them will ever send you a per-resolution invoice.