Home / Software Alternatives

Open Source Zendesk Alternatives: The License Bench

Detailed view of server racks with glowing lights in a data center environment.

Photo: panumas nikhomkhai / Pexels

The license is the product you are buying

Nobody self-hosts a help desk to save the price of a server; they self-host to own the system, and ownership is defined by the license. AGPL-3.0 projects (Zammad, FreeScout) give you the full product and ask that network deployments of modified code share their source. An MIT core (Chatwoot) is more permissive, but Chatwoot's enterprise features live in a separately licensed directory inside the same repository, which makes it open core rather than plain open source, a distinction recycled lists flatten. osTicket's GPL-2.0 is the older copyleft, permissive about internal use in practice and showing its age in the codebase. UVdesk's OSL-3.0 is a real open source license that few procurement teams recognize, which can matter more than its terms. This bench states each license per project, separates open core from clean open source, and then grades the desks on channels, polish, and the maintenance signals that decide whether a project will still be patched when you need it.

ProjectLicense, exactlyShapeHealth signal, dated
ZammadAGPL-3.0Full help desk, email-first with chat and socialLong-running project, hosted option in the EU
FreeScoutAGPL-3.0Shared inbox desk, Laravel-basedActive module ecosystem
ChatwootMIT core, enterprise directory under a separate licenseOmnichannel engagement suiteVery active; cloud tier beside self-host
osTicketGPL-2.0Classic ticket system, email-drivenMature and slow-moving
UVdeskOSL-3.0Help desk with ecommerce integrationsSmaller community
PeppermintArchivedTicketing, formerly recommendedRepository archived by its owner; do not adopt

The desks, graded

Zammad is the bench's default recommendation for a team leaving Zendesk for ownership: a polished, complete desk (email, chat, phone, and social channels, knowledge base, and reporting) with no feature gating on the self-hosted build, plus a hosted option priced in euros for teams that want the product without the roster. FreeScout is the shared-inbox answer, lighter than Zammad, built on Laravel, with a module ecosystem that adds reporting, CRM-ish features, and integrations piece by piece; it suits email-heavy small teams that found Zendesk's machinery oversized. Chatwoot is the engagement suite: live chat, email, WhatsApp and social inboxes, a Captain AI layer, and the strongest omnichannel story here, with the open core caveat graded honestly, since some enterprise features (advanced assignment, SLA tooling in the enterprise directory) are not under the MIT terms. osTicket is the veteran: unglamorous, email-driven, extremely well understood, and the right answer mainly for conservative shops that value a decade of operational folklore over interface polish. The comparison below puts Zammad, FreeScout, and Chatwoot side by side from the dataset.

Interactive tool

Comparison Builder

Pick two or three products and see them side by side on the numbers that decide the purchase.

MeasureZammadFreeScoutChatwoot
Starting paid priceFreeFreeFree
Free optionFree plan: self-hosted free under AGPL-3.0Free plan: free core application, self-hostedFree plan: self-hosted free; cloud Hacker plan free for 2 agents
PlansSelf-hosted: free · Hosted: not publishedCore: free · Modules: not publishedSelf-hosted: free · Cloud Hacker: free · Cloud paid tiers: not published
PlatformsWeb, Self-hostedSelf-hosted, WebWeb, Self-hosted, iOS, Android
Best forEU teams, self-hosters, email-heavy support deskssmall teams with one shared inbox, agencies, cost-sensitive supportstartups, self-hosting teams, WhatsApp-heavy support
StrengthsMature, polished open source help desk; Hosted option inside the EU; No feature gating on the self-hosted buildNo per-agent pricing at all; Runs on cheap shared PHP hosting; Unlimited agents and mailboxesReal open source core you can audit; Omnichannel inbox including WhatsApp; Cloud free tier for tiny teams
Watch out forAGPL terms for modified deployments; Hosted pricing is euro-denominated; Smaller integration marketplace than ZendeskYou host, patch, and back it up; Extras live behind paid modules; Email-centric; no native live chat depthEnterprise folder is under a separate license; Self-hosting needs maintenance; Cloud free tier is live chat only

Lowest entry price: Zammad at Free per user/mo billed annually. Real free plan: Zammad, FreeScout, Chatwoot. Entry price is the floor, not the decision: check the plan line above for the tier that actually includes the feature you need.

All figures from vendor pricing pages, checked November 18, 2026. Some vendors price by contacts, tasks, or operations instead of seats; those notes are in the plan data and the linked pricing guides.

Project health is a grading axis, not a vibe

Open source help desks fail quietly: a repository slows, a maintainer leaves, and your security patch cadence becomes your own problem. Grade health with dates, not stars. Check the last release date and the commit rhythm across the last year, whether security issues get advisories, and whether a commercial entity or foundation stands behind the project (Zammad and Chatwoot both sell hosted versions, which funds maintenance; FreeScout sells modules). Peppermint is this bench's cautionary exhibit: a tidy ticketing tool that still appears in 2026 roundups although its repository was archived by its owner in current reads, which means no patches, ever, for a system holding your customers' conversations. A desk you self-host is a desk you co-maintain, and the project's pulse is part of the price.

The middle door: hosted open source

Between Zendesk's seats and a server of your own sits an option this bench should name: the same open source desks, hosted by the projects themselves. Zammad sells a hosted tier, Chatwoot sells cloud plans (free for 2 agents in the dataset, then per agent), and FreeScout has hosting partners in its ecosystem. What you keep is the license: your data lives in a system whose code you can inspect and whose self-hosted twin you can move to, which makes the exit real rather than theoretical. What you give up is the $0 running cost and some control over upgrade timing. For many teams this is the correct first step off Zendesk: migrate once into an open system, let the vendor carry the roster while you learn it, and self-host later only if the economics or the compliance case actually demands it. The license grading above applies unchanged, because the license, not the hosting, is what you are really choosing.

The hosted door also changes the trial economics in your favor: a team can run its real queues on hosted Zammad or Chatwoot Cloud for a month, measure agent acceptance and channel quality with production traffic, and treat self-hosting as a later infrastructure decision made with evidence. Compare that with the Zendesk trial, which measures a product you would still be renting at the end. Ownership compounds; rent does not.

What to check before you self-host a help desk

Four checks, in order. License fit: AGPL network terms if you modify and expose the desk, the enterprise directory boundary if you choose Chatwoot, and license recognition if procurement must approve an OSL-3.0. Channel reality: test your actual first channel (email threading, chat widget, WhatsApp) in a pilot, because channel quality varies more than feature lists admit. Migration: Zendesk exports move tickets and users imperfectly; pilot with one queue and measure what survives. Duty roster: name who patches, backs up, monitors, and answers at renewal time; if the answer is nobody, Zammad's hosted tier or the flagship's hosted desks are the honest comparison.

The verdict

Complete desk, ownership, polish: Zammad under AGPL-3.0. Shared inbox, light and modular: FreeScout. Omnichannel with chat at the center: Chatwoot, accepting the open core boundary. Conservative email ticketing: osTicket. Ecommerce-flavored support: UVdesk, with its smaller community priced in. Do not adopt Peppermint at any price; archived software is a liability with a login screen. And the stay case: if your team's real objection to Zendesk is the AI meter rather than tenancy, the AI bench and the flagship will save you a migration you do not need.

Interactive tool

The self-host duty checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 6 complete

0% done

Related guides

The shortlist does not end here. These related guides cover the sibling tools, matchups, and pricing questions closest to this one.

Frequently asked questions

What is the best open source alternative to Zendesk?

Zammad for most teams: a complete, polished help desk under AGPL-3.0 with no feature gating on the self-hosted build and a hosted option if you later want the roster gone. FreeScout is lighter for shared-inbox teams, and Chatwoot is stronger when live chat and messaging channels are the center of support.

Is Chatwoot really open source?

Its core is, under the MIT license. Some enterprise features live in a separate directory of the repository under a different license, which makes Chatwoot open core rather than plain open source. The core covers the main inbox, chat, and channel work; check the enterprise directory's feature list against your needs before assuming a feature is MIT.

What does AGPL-3.0 require if I self-host Zammad or FreeScout?

You may use and modify the software freely. If you run a modified version as a network service for users, AGPL asks you to offer those users the source of your modified version. Unmodified internal deployments carry no practical burden beyond keeping the license notices, which is why AGPL is rarely an obstacle for in-house help desks.

Is Peppermint a good open source help desk?

Not anymore. Its repository was archived by its owner in current reads, which means development has stopped and security issues will not be patched. It still appears in recycled roundups; treat its presence in a list as a freshness test the list failed.

How much does it cost to self-host a help desk?

The license is $0. The real costs are a server (a small VPS handles a small team), installation, updates, backups, monitoring, and security, paid mostly in staff time. Teams that already run infrastructure find the trade easy; teams that do not should compare against Zammad's hosted tier and the hosted desks in the flagship.

Photo credits: panumas nikhomkhai (Pexels). Photos are served from this site; follow the credit to the library page for the original.