osTicket vs Zammad 2026: Open-Source Help Desk Compared

osTicket vs Zammad: the short version

osTicket and Zammad are the two most-searched open-source help desk platforms, and they solve the same problem from opposite directions. osTicket is the older, lighter option: free to self-host, runs on basic PHP and MySQL, and asks almost nothing of your server. Zammad is the newer, heavier option: also free to self-host with unlimited agents, but it wants 4-8GB of RAM and a more involved deployment in exchange for a modern interface and native multi-channel support across email, chat, and Telegram. Neither one is actually free once you count your own time. A production-grade self-hosted deployment typically runs $1,300-2,400/year in infrastructure costs alone, before adding the hours spent on patching, backups, and version upgrades [AWS Marketplace and hosting-cost estimates compiled by eesel AI, 2026]. The question that actually matters is not which tool is "better" in the abstract, it is whether your team has server capacity and PHP or Ruby comfort for Zammad's stack, or whether osTicket's dated-but-simple approach is the better fit, especially with a full rewrite, osTicket 2.0, already moving toward a release candidate as of mid-2026.

That admin's concern is worth sitting with for a moment, because it is only half right. osTicket's core PHP architecture genuinely dates back over two decades, and parts of the plugin ecosystem have not been touched in years. But the project itself is not abandoned: version 1.18.4 shipped on June 17, 2026, and the GitHub repository shows 115 total releases and roughly 8,900 commits on the develop branch [GitHub, checked 2026-07-21]. The more accurate read is that osTicket is actively maintained but architecturally old, which is exactly the gap osTicket 2.0 is built to close.

Quick comparison

osTicket: the simpler, older option that is about to be rebuilt

osTicket has been the default answer to "free help desk software" for close to two decades, and the reasons are unglamorous but real: it installs on shared PHP hosting most small teams already pay for, the core feature set (email-to-ticket, a customer portal, agent assignment, canned responses) covers what a lot of internal IT or small support teams actually need, and there is no per-agent fee at any scale. It holds a 4.3/5 rating on G2 and a 4.3/5 rating from 76 verified reviews on Capterra [G2 and Capterra, 2026], with reviewers consistently praising the setup speed and customization for the price, and consistently flagging the same two things: an interface that "can feel somewhat outdated compared to newer help desk platforms," and a first-time install that assumes more PHP familiarity than the documentation admits, one reviewer specifically noted that a required PHP version detail was "not mentioned anywhere in the install docs" [Capterra, 2026]. Mobile is the sharpest weak point: the iOS app sits at 2.5/5 and the Android app at 1.9/5, with app-store reviewers reporting it "crashes constantly" and that agents cannot assign tickets or work offline from a phone [app store reviews aggregated via SoftwareSuggest and CheckThat.ai, 2026]. If technicians need to triage tickets from a phone regularly, that is a real, specific dealbreaker, not a minor rough edge.

The news that changes the calculus here: in March 2026, the osTicket team publicly announced osTicket 2.0, a complete rewrite of the backend on Laravel with a React front end, replacing the PHP/jQuery monolith entirely. The new architecture is API-first, meaning the web UI becomes just one client on top of the same APIs that could power a proper mobile app or AI-driven integrations later. The announced feature list includes dark mode with auto-generated color themes, a CMS-style page builder for the customer portal, built-in incident and status pages, a cross-object "View Builder" for system-wide filtered queues, drag-and-drop SLA and CSAT dashboards, and support for PostgreSQL alongside MySQL [osTicket team announcement, next.osticket.com, March 2026]. As of this writing there is no public release date, the team is finishing Release Candidate 1 and has been explicit that they are prioritizing stability over a ship date [osTicket roadmap discussion, GitHub, 2026]. Existing plugins and themes will not carry over. If your evaluation timeline has any flexibility, it is worth knowing this is coming before you invest heavily in osTicket 1.x customization that a future migration would have to redo.

Zammad: the modern pick, if your server can handle it

Zammad launched in 2016, built in part by members of the original OTRS team, specifically to be the open-source help desk that feels like a modern SaaS product instead of a decade-old ticket queue. That shows in day-to-day use: a dashboard-first layout, real-time updates, and native channels for email, chat, and Telegram without bolt-on plugins. The Community Edition is genuinely free under AGPLv3, with no artificial cap on agents or tickets, and LDAP and SAML SSO ship standard rather than gated behind an enterprise tier [Zammad, "Why Our Helpdesk Is Open Source," 2026]. Paid options exist alongside it: cloud-hosted plans start at €7/agent/month (Starter, up to 5 agents) and scale to €25/agent/month (Plus, unlimited agents with phone and WhatsApp channels), and separately, Zammad GmbH sells annual support contracts for self-hosted deployments starting around €2,999/year for teams that want vendor-backed SLAs on top of the free software [Zammad pricing page, 2026]. Buying that support is optional. The software itself does not require it.

The tradeoff is infrastructure. Zammad is built on Ruby on Rails with Elasticsearch for search, and the official documentation recommends 4-8GB of RAM for a production instance, well beyond what osTicket needs and enough to rule out the cheapest shared-hosting tiers. On G2, Zammad is listed as a High Performer in the help desk category, with reviewers consistently citing the clean interface and ease of setup as the reason they picked it over legacy tools [G2, 2026]. On Capterra, it currently holds 4.6/5 from a small sample of 7 reviews, worth noting precisely because the sample is small, with 5.0/5 specifically on value for money [Capterra, 2026]. Real self-hosters echo that in less polished terms. In one active r/selfhosted thread from January 2026 where an admin was choosing a second ticketing tool alongside an existing Zammad deployment, they summed it up as: "Zammad main pain point is not being multi-tab. Outside that, it's very feature-complete and straightforward to use," and separately noted that "Zammad 7.0 might come with their new UI that is supporting multi tab and some potential AI features" based on community roadmap discussion [r/selfhosted, January 2026]. Not every team agrees it is the right amount of tool, though: in a German-language r/de_EDV thread, a small/mid-size business owner described trying to roll out Zammad and abandoning it because the role and permission fine-tuning, macros, SLA management, and automation depth were "komplett überdimensioniert", completely oversized, for a team that only needed emails converted to tickets with basic status and assignment tracking [r/de_EDV, 2026]. That is a genuinely useful data point: Zammad's depth is a feature for IT teams with real workflow complexity and a liability for a five-person team that wants Outlook with better organization.

What "free" actually costs when you self-host

The license is free for both. The infrastructure and labor are not. A realistic production deployment, sized for a mid-size support team, runs roughly $1,300-2,400/year in raw infrastructure (compute, database, backups, bandwidth) on a platform like AWS, and $2,800-8,400/year once you price in the engineering hours for setup, security patching, and version upgrades over a year [AWS Marketplace listings and hosting-cost breakdowns compiled by eesel AI, 2026]. That is before anything goes wrong. Open-source licensing means you are not paying a vendor for uptime, and if the server goes down at 2am, the "vendor" is whoever on your team owns the box. For a team already running a mature ops function, that is a rounding error. For a two-person IT department, it is a real ongoing commitment that a $19/agent/month SaaS plan trades away entirely, see our best help desk software roundup if the calculation points you back toward a hosted option instead.

The math changes fast with headcount, though, which is the actual argument for self-hosting. A 50-agent team paying even a modest $19/agent/month for a hosted tool is looking at $11,400/year in license fees alone, before add-ons, on top of which self-hosted osTicket or Zammad costs the same $2,800-8,400/year in infrastructure and labor whether you have 5 agents or 50, because neither charges per seat. That crossover point, usually somewhere between 15 and 30 agents depending on your existing ops capacity, is where self-hosting genuinely starts winning on cost rather than just avoiding a monthly bill.

Other open-source options that came up in our research

osTicket and Zammad are the two names people search for, but they are not the only two real options, and it would be dishonest to write this as though they were. In the same r/selfhosted thread cited above, the admin evaluating tools for a 150-user company ultimately passed on both and picked GLPI instead, specifically because of its GitHub activity level relative to every other option they tried, plain LAMP deployment, and because it combines IT asset management with ticketing rather than treating them as separate tools. GLPI is worth a look if asset tracking (who has which laptop, warranty status, software licenses) matters as much to you as the ticket queue itself.

FreeScout came up too, recommended by another commenter as an email-only alternative, but a reply in the same thread claimed "the self hosted version is deprecated" and no longer genuinely open source, a claim we could not independently confirm on FreeScout's own site as of this writing, so treat it as a reason to double-check FreeScout's current licensing directly before planning around it, not as settled fact. ERPNext also ships a help desk module bundled into its broader ERP suite, mentioned in passing by the same thread's participants as an option worth a look for teams that already run ERPNext for other operations, though none of the commenters had evaluated it in depth.

Which one should you actually pick

Pick osTicket if: your hosting is shared or budget-constrained, your ticket workflow is simple (email in, assign, resolve, close), and you are comfortable with a dated interface for now, with the option to evaluate osTicket 2.0 once it reaches a stable release. It is also the more forgiving choice if nobody on the team has strong Ruby or Elasticsearch experience, since PHP/MySQL skills are far more common on small IT teams.

Pick Zammad if: you can dedicate a server with 4-8GB of RAM, you want a modern agent experience without paying per seat, and your support volume actually spans multiple channels (email, chat, and social) rather than just email. It is the stronger pick specifically for teams migrating off a paid SaaS tool like Freshdesk or Zendesk who want the closest self-hosted equivalent to what they are used to, rather than a step back in interface quality.

Reconsider both if: your team is under 5 people and your workflow is genuinely simple, the German r/de_EDV thread above is a useful cautionary example of Zammad's depth working against a small team, and in that case a lighter tool, or even a well-organized shared inbox, may serve you better than either. Budget-constrained nonprofits and small IT shops evaluating this tradeoff should also see our help desk software guide for nonprofits, and if you are actively planning a move away from a paid tool, our migration cost and timeline data covers what actually transfers when you switch, a question that applies whether you are moving to a self-hosted tool or another SaaS platform.

Frequently asked questions

Is osTicket actually free, or is there a catch? The self-hosted, open-source version is completely free with no agent limits and no feature paywall, the osTicket team states this plainly on their own site. The only paid option is SupportSystem, a separate cloud-hosted version of the product for teams that do not want to manage their own server, and its pricing is not published, you have to request it [osticket.com, 2026].

Does Zammad's free self-hosted version have a real limit on agents or tickets? No. The Community Edition is licensed under AGPLv3 and includes unlimited agents and tickets, with LDAP and SAML SSO included standard rather than gated to a paid tier. The paid self-hosted "Business/Enterprise/Corporation" plans starting around €2,999/year are optional vendor support contracts, not a requirement to run the software [Zammad, "Why Our Helpdesk Is Open Source," 2026].

Is osTicket still actively maintained in 2026? Yes, though the concern is understandable. Version 1.18.4 shipped June 17, 2026, and the project has 115 total releases on GitHub. The more accurate criticism, and the one driving the osTicket 2.0 rewrite announced in March 2026, is that the underlying PHP architecture is aging even though the project is not abandoned [GitHub, osTicket/osTicket, checked 2026-07-21; osTicket team, next.osticket.com, 2026].

How much RAM does Zammad actually need to self-host? Zammad's own documentation recommends 4-8GB of RAM for a production instance, since it runs on Ruby on Rails with Elasticsearch for search indexing. That rules out the cheapest shared-hosting tiers that osTicket's basic PHP/MySQL stack can run on comfortably [Zammad system requirements, 2026].

Is self-hosting actually cheaper than a paid help desk tool? It depends heavily on team size. Self-hosted infrastructure and labor typically run $2,800-8,400/year regardless of agent count, since neither osTicket nor Zammad charges per seat. A paid SaaS tool charging even $19/agent/month costs $11,400/year at 50 agents. The crossover where self-hosting starts winning on cost is usually somewhere around 15-30 agents, below that a hosted plan is often genuinely cheaper once your own time is priced in [cost estimates compiled from AWS Marketplace and vendor pricing pages, 2026].

What do real users say is the biggest drawback of each tool? For osTicket, it is the mobile experience specifically, the iOS app rates 2.5/5 and Android 1.9/5, with reviewers reporting crashes and missing ticket-assignment functionality on mobile [app store reviews aggregated via SoftwareSuggest and CheckThat.ai, 2026]. For Zammad, real self-hosters most often cite the lack of multi-tab browsing as the day-to-day friction point, with a fix reportedly planned for a future v7 UI update, and separately, some smaller teams report Zammad's permission and automation depth is simply more than they need [r/selfhosted and r/de_EDV, 2026].