For a small support team with someone available to maintain a server, Zammad and osTicket are the most useful starting finalists in this guide. Choose Zammad when shared ticket work, configurable groups and a broader service workflow justify its documented infrastructure. Choose osTicket when email, customer forms and departmental ticket queues meet the requirement and your administrator already supports PHP and MySQL. FreeScout is a third route for a mailbox-led operation willing to assemble selected capabilities through modules.
The deciding purchase is often the operating arrangement rather than the licence. A solo business with manageable email may need clearer folders and follow-up habits before another application. A larger organization seeking formal asset management or tightly specified procurement controls needs a wider evaluation than this focused shortlist.
This guide covers self-hosted help desk software for a team that wants its own application and data deployment. Renting a server still counts as self-hosting the application; it does not make backups or upgrades the hosting company’s responsibility unless the agreement says so. If nobody can take on that work, begin with the broader help desk software guide.
We inspected official project, installation and commercial documentation on 9 November 2026. These recommendations are editorial judgments from documented capabilities. We did not install the applications, benchmark resource use or observe agents working in them.
Start with the same five-agent purchase
Consider a hypothetical organization with five support agents, one support email address and a customer portal. It needs assignment, customer replies and a shared ticket history, but no telephone system, AI service or asset inventory. It has a Linux administrator and is budgeting for twelve months. All dollar amounts below are USD; no exchange-rate conversion is used.
| Configuration for this workload | Software commitment | Email and customer web access | Team work | Operating purchase still needed |
|---|---|---|---|---|
| Zammad community self-hosted installation | $0 licence for the twelve-month scenario; optional support is separate | Email channels and customer web interface documented | Groups, owner, internal notes, history and editing indicators | Suitable server, database and supporting services, backups, updates and administrator time |
| osTicket Open Source | $0 licence for the twelve-month scenario; commercial help is separate | Email intake and customer forms/portal documented | Departments, assigned agents/teams, replies and internal notes | Compatible PHP/MySQL hosting, email setup, backups, updates and administrator time |
| FreeScout core plus End-User Portal module | Free core plus paid portal module; current module amount was not exposed in the fetched page | Email in core; customer portal through the named module | Shared conversations, internal notes and collision notice | Compatible hosting, scheduled jobs, mailbox operation and module maintenance |
For the two main finalists, five agents do not produce a five-seat licence bill: the free self-hosted software is the qualifying configuration. Neither includes a managed production service merely because its download costs nothing. There is no mandatory annual software subscription in this comparison, but infrastructure and support providers can impose their own minimums or billing commitments.
Use the same cost model for both: first-year cost equals setup and migration charges, plus twelve months of server, backup storage, email-service and paid-support charges, plus maintenance effort valued at your organization’s chosen rate. Renewals remove only genuinely one-time work; upgrades, storage growth and administration remain. Leave unquoted components blank rather than treating them as zero.
Zammad publishes a hardware baseline that can inform a server quote. The osTicket installation guide specifies software prerequisites without providing a comparable five-agent capacity guarantee. Therefore this evidence does not establish which deployment has the lower total cost. An existing, compatible PHP environment can favor osTicket economically; an already-operated Zammad-compatible stack can change that calculation. Spare capacity still has maintenance and availability implications.
Zammad: buy into the service workflow, not a hosted plan’s limits
Zammad’s community site explicitly offers free installation on your own servers. Its commercial hosted tiers and optional self-hosted support contracts are different purchases. Do not apply a hosted Starter plan’s agent allowance to the community deployment or assume a support contract buys hosting.
The documented ticket workspace lets an agent change the group, priority and owner, add an internal note, send an email reply and inspect history. It also indicates other agents viewing or editing the ticket. That combination makes Zammad a reasonable finalist when several colleagues regularly coordinate within the same case. The benefit is an inference about workflow fit, not a measured reduction in duplicate replies.
Its customer web-channel settings let administrators enable ticket creation and restrict which groups customers can select. That matters when the service desk has internal escalation groups customers should not choose directly. Its email documentation also distinguishes generic email accounts from dedicated Google and Microsoft 365 channel setup, so mailbox authentication belongs in implementation planning.
The infrastructure is a concrete trade-off. Current software prerequisites document PostgreSQL and Redis, with Elasticsearch optional but strongly recommended for search and related capabilities. The hardware guide gives a minimum of two CPU cores and 6 GB RAM, plus another 4 GB when Elasticsearch shares that server. These are project guidelines, not our sizing test or a performance promise.
Prefer Zammad over osTicket when that ticket collaboration and configurable group workflow will be used and the technical team accepts its stack. Reverse the choice when the actual requirement is a conventional departmental email queue and maintaining that stack would create work without a corresponding service benefit. The next step is to map one real support category into groups, ownership and customer-visible fields before committing a production mailbox.
osTicket: keep a conventional service queue within a familiar stack
osTicket’s Open Source edition provides a free download with email integration and community support. Its commercial cloud service is a separate managed offering; using that service’s per-agent starting price would misstate the self-hosted purchase.
The useful differentiator is the documented deployment and ticket model. The current installation guide requires a compatible web server, PHP 8.2–8.4 and MySQL, and describes a browser-based installer. It still expects knowledge of web servers, PHP and databases. A wizard does not remove the need to configure the server or secure its production operation.
After installation, the administrator sets email intake, help topics, departments and staff. Help topics can route a customer’s form submission to a department and priority without exposing internal department names. Departments also affect staff access. This suits a team dividing work between, for example, billing and product support without needing a separate application for each.
The agent ticket documentation describes Open, Answered, My Tickets, Overdue and Closed queues. Agents can reply, use prepared responses, change status and add internal notes. An Answered ticket can still be Overdue; the queues express different properties rather than a single linear checklist. That is useful context when a manager defines what the morning workload actually includes.
Choose osTicket over Zammad when this departmental ticket-and-portal workflow is sufficient and PHP/MySQL operation fits the available skills. Choose Zammad instead when its collaboration indicators and configurable service workspace are material to the team’s work. This is not a finding that osTicket lacks every comparable feature: the recommendation follows the documented workflows examined here, not an exhaustive feature-by-feature absence claim.
One ongoing obligation is explicit. The upgrade instructions call for backing up the database and files, preserving the configuration file and testing ticket replies afterward. Custom code must be carried forward. Avoid unnecessary customization if the organization cannot fund its maintenance.
FreeScout: a credible alternative when the mailbox is the product
FreeScout documents unlimited agents, tickets and mailboxes, internal notes and a notice when two agents open the same conversation. Its PHP/MySQL approach is worth examining when the desired change is shared handling of email rather than a more formal service desk.
The qualification changes when the common workload includes a portal. Its End-User Portal module lets customers submit, view and reply to tickets; it is a paid module, not a capability to price at the core’s zero licence cost. The official catalogue describes lifetime licences for one instance with updates included and non-refundable payments. The fetched product page did not expose a current amount, so this guide does not substitute a directory’s remembered price.
Prefer FreeScout to either main finalist when its mailbox workflow fits better and the selected module bundle is acceptable. Keep it qualified, rather than declaring it the budget winner, until the portal price is visible. Reports, workflows and other requirements should be checked against the module catalogue individually.
There is also a documented migration detail worth settling early: its installation guide expects the connected mailbox to be accessed through FreeScout, because read-message handling affects fetching. Continuing to process the same inbox independently can change what is imported. Its portal uses an emailed authentication link, so outgoing email delivery is part of the ordinary customer experience, not an optional finishing touch.
What an ordinary working day requires first
For Zammad, the package-installation route covers repository installation, dependencies, service management and firewall considerations. Its getting-started wizard then creates the administrator, organization details, notification channel and optional first email channel. The subsequent setup includes groups, triggers, signatures, roles and agent accounts. A systems administrator handles the host and mail authentication; the support lead decides routing and customer-facing behavior.
For osTicket, the corresponding route is to prepare the PHP/database environment, upload the application, complete the installer and then configure email, departments, help topics and staff in the admin panel. FreeScout similarly documents web-server/database configuration, a web installer, scheduled jobs and mailbox setup. These are documented procedures; we have not compared their setup time or usability.
Once configured, an ordinary hypothetical request should be understandable end to end. A customer emails a question or submits a form, an agent opens the resulting ticket, assigns it, keeps colleague-only context in an internal note and sends a customer reply. The customer then follows the conversation through the supported email or portal route. Define what counts as waiting for a customer versus completed work before importing a backlog with inconsistent statuses.
Recurring work includes applying project and server updates, maintaining mail authentication, checking backup completion and reviewing access when staff change. Zammad supplies package backup scripts but explicitly excludes environment settings and documents a different path for containers. osTicket’s upgrade procedure also makes database and file backups the operator’s responsibility. A server snapshot alone should not be assumed to cover every application dependency or prove that restoration works.
Decide whether ownership earns its cost
Self-hosting earns consideration when control over deployment or application changes matters enough to fund operation. It is a poor bargain when a free licence replaces a manageable subscription with an unfunded production responsibility. A solo operator who can handle support reliably in existing email should usually simplify that process first.
For the five-agent team, compare Zammad and osTicket using two buyer-filled lines: annual external cash outlay, and annual staff effort for both support work and system operation. Record the present arrangement on the same basis. Less agent administration is useful capacity, but it becomes cash savings only if an actual expense changes. Do not cancel the current service on the strength of a theoretical hourly saving.
Paying more can be worthwhile for an explicit support commitment or specialist implementation help. Zammad documents optional support contracts while retaining free self-hosting; osTicket also offers commercial assistance. Such assistance must be scoped separately from managed hosting. Conversely, stay on the current edition or avoid extra modules when additional channels and automation do not address a demonstrated requirement.
This shortlist deliberately stops before full enterprise procurement. GLPI’s documented asset-management and help-desk combination merits a separate evaluation when tickets must connect to inventory; Frappe Helpdesk deserves attention where its ecosystem fit matters. Neither is rejected as incapable. Large organizations requiring particular identity, audit, recovery or service commitments should make those requirements decisive before using this small-team comparison.
For the primary reader, the actionable choice remains Zammad for the service workflow and osTicket for the sufficient departmental queue on a familiar stack. FreeScout is the mailbox-led alternative with a separately priced portal. Approve the operating budget alongside the software choice, then migrate a representative slice of history while retaining access to the original records until the mapping is checked.
