Zammad vs FreeScout: which to choose

Zammad vs FreeScout: when each helpdesk fits

If you are a support leader who needs a self-hosted shared inbox and must choose between Zammad and FreeScout, start with how much of the identity and workflow stack you need in the core product. Zammad is a ticket-centric helpdesk with a fuller feature set in the base product, and its self-hosted software carries no license fee. FreeScout is a lightweight shared inbox under AGPL-3.0 with unlimited agents, tickets and mailboxes in the free core, but LDAP, SAML SSO, the knowledge base and workflows are sold as paid lifetime modules for a single instance. Zammad fits a team that wants ticketing, identity and automation in one product from day one. FreeScout fits a team that mainly needs mailbox triage, can run on modest hosting, and is willing to add only the modules it truly requires.

Four factors should drive the decision. First, identity: if you must sign agents in through LDAP or SAML, price the FreeScout LDAP and SAML SSO modules alongside the base install. Zammad supports SAML and OpenID Connect in its core product, so confirm that the identity provider you use matches the options listed in its third-party login documentation. Second, channel mix: FreeScout centralizes email, WhatsApp, Telegram, Facebook, Slack and live chat, so list each channel you need and check how each one is delivered in both products. Third, team size and reporting depth: a larger queue with service levels and detailed reporting usually points toward Zammad, while a small team sharing a few mailboxes may not need that. Fourth, the module total: add up the FreeScout lifetime licenses you would need, then compare that figure with the Zammad support subscription tier you would buy for the same team.

Before you choose, ask both vendors for a written list of which features are in the free core and which require payment, and confirm the lifetime module terms and what counts as a single instance. Also confirm hosting requirements for your expected volume. Zammad needs PostgreSQL 15 or newer and Redis 7 or newer, and Elasticsearch is optional but strongly recommended. FreeScout runs on MySQL, MariaDB or PostgreSQL with PHP 7.4 to 8.x. Those differences affect your hosting and maintenance effort more than the license line does, so price the database, search and operations work for each product before you commit.

Which helpdesk fits which support scenario

This table maps common support scenarios to the platform that fits each one best, and the condition that makes it so. Read each row as a decision: if the stated condition holds for your team, the named platform is the stronger starting point. FreeScout module prices and terms must be confirmed on its modules page before you budget.

Scenario	Better fit	Condition that makes it so
A small team sharing one mailbox	FreeScout	A shared inbox with unlimited agents, tickets and mailboxes over SMTP, IMAP or POP3 covers the need, and the README lists no minimum CPU or RAM, so modest hosting is enough.
Team must use SAML SSO and LDAP from day one	Zammad	Zammad lists SAML and OpenID Connect in its included third-party login options. On FreeScout, LDAP Integration and SAML SSO are paid modules, so their lifetime license cost must be added before go-live.
Operation needs a knowledge base	Zammad, or FreeScout with a budget for the module	FreeScout's Knowledge Base is a paid lifetime module, so confirm its current price on the FreeScout modules page. Zammad is the choice if you want the knowledge base scoped under the same platform and license terms, but confirm its feature set against your requirements.
Team expects multi-channel support across chat and social	Zammad, if ticket-centric channels are enough; FreeScout for a lighter multi-channel inbox	FreeScout's README lists email, WhatsApp, Telegram, Facebook, Slack and live chat centralized in one place. Confirm each channel's setup and maintenance effort in both products against your actual channel mix before choosing.
Team plans to rely on Elasticsearch-backed search and reporting	Zammad	Zammad uses Elasticsearch for faster search, reporting and attachment content search. It is optional but strongly recommended, so budget for the extra service to run and maintain.
Small operation wants a minimal, low-footprint host	FreeScout	FreeScout runs on Nginx, Apache or IIS with PHP and MySQL, MariaDB or PostgreSQL, and its README describes shared hosting as possible. Zammad needs PostgreSQL 15 or newer and Redis 7 or newer, which is a heavier stack.
Team needs vendor-backed self-hosted support with a defined plan	Zammad	Zammad sells self-hosted support subscriptions, and its pricing page states that self-hosted customers handle updates, backups and availability. Ask Zammad what each plan covers before signing.
Team that already runs its own PHP and Laravel operations	FreeScout	FreeScout is built on Laravel and offers a Docker image and one-click installs. Your team must still handle updates, backups and any paid modules you add.

How Zammad and FreeScout are built and what that means for operations

Both tools are self-hosted and open source, but they sit on different stacks with different dependency counts. The cards below cover each component group and what it means for patching, backups and day-two effort. Confirm each version and sizing requirement against the current vendor documentation before you commit to a host plan.

Runtime and framework

Zammad is a Ruby on Rails application, so your patch process must follow Zammad's own release line and its Ruby dependencies. FreeScout is a PHP application on the Laravel framework and runs on PHP 7.4 to 8.x. Because FreeScout's supported PHP range is wide, check whether your PHP version is still receiving security fixes, since an end-of-life runtime becomes your risk to carry. Ask each vendor which runtime versions their current release supports.

Primary database

Zammad stores its content in PostgreSQL 15 or newer, so your database team must already run and back up PostgreSQL at that version. FreeScout accepts MySQL 5.0 or later, MariaDB 5.0 or later, or PostgreSQL. If your organization standardizes on MySQL or MariaDB, FreeScout fits the existing skill set more directly. Confirm the exact database versions FreeScout currently supports before you plan the upgrade path.

Cache, realtime and search

Zammad requires Redis 7 or newer for realtime websocket communication. Elasticsearch is optional, but Zammad documents it as strongly recommended for faster search, reporting and attachment content search. Without it, search is very limited, so budget for an extra cluster if your agents depend on search. FreeScout does not list Redis or Elasticsearch as requirements, which means fewer moving parts to patch and back up.

Multi-instance caching

Zammad needs Memcached when you run several application instances, such as containers or cluster nodes. A single installation can use the file system cache instead. This matters if you plan a highly available layout, because it adds a service that needs its own patching and monitoring. For FreeScout, confirm with the project whether any shared cache is needed when you scale beyond one server.

Web server footprint

FreeScout runs on Nginx, Apache or IIS, and its README states there are no minimum CPU or RAM requirements and that it can run on shared hosting. That lowers the entry cost but does not replace a sizing test with your real mailbox volume and attachment load. Zammad supports Nginx or Apache as its reverse proxy. Size both against your expected ticket and agent counts, and ask each vendor for its recommended resources for that volume.

Package, container and Helm deployment

Zammad documents package installation, Docker Compose and a Kubernetes Helm chart. Its support for Kubernetes covers only the Zammad application, not Kubernetes-specific problems, so your platform team owns the cluster. FreeScout offers a Docker image plus one-click installs through Softaculous, Cloudron and managed hosts. Choose the path your operations team can patch on a fixed schedule, and check that your backup tool captures the database, the attachment store and the configuration together.

Zammad vs FreeScout capability by capability

This table compares Zammad and FreeScout on license, core features, channels, authentication, search, migration, mobile and support. Each row shows whether a capability is free, sits behind a paid FreeScout module, or depends on Elasticsearch, and where the answer is unconfirmed it names what to ask each vendor. The main takeaway is that FreeScout's free core can grow in cost as modules are added per instance, while Zammad's paid tiers are support subscriptions on a free self-hosted license.

Capability	Zammad	FreeScout
License	AGPL-3.0. Self-hosted use carries no license fee.	AGPL-3.0. Core is free, with paid lifetime modules per instance.
Free core features	Self-hosted license is free. Confirm which core features your edition includes.	Unlimited agents, tickets and mailboxes in the free core, per the README.
Channels	Confirm the full channel list (email, chat, social) with Zammad before you commit.	Email plus WhatsApp, Telegram, Facebook, Slack and live chat, per the README.
Email protocols	Confirm SMTP, IMAP and POP3 support and OAuth options with Zammad.	SMTP, IMAP and POP3, plus OAuth for Microsoft 365 and Google Workspace.
SSO and LDAP	SAML, OpenID Connect, Microsoft, Google, GitHub and GitLab login. Confirm LDAP directly.	LDAP and SAML SSO are paid lifetime modules. OAuth for Microsoft 365 and Google is free.
Knowledge base and workflows	Confirm whether a knowledge base and workflow automation are included in your edition.	Knowledge Base and Workflows are paid lifetime modules for a single instance.
API and webhooks	API is used for imports. Confirm webhook support and API scope with Zammad.	API and Webhooks are a paid module. Zapier and Make integrations are linked from the README.
Search	Elasticsearch is optional but strongly recommended. Without it, search is very limited.	Confirm search capability without an external index with FreeScout before you rely on it.
Migration tools	Migrators for Freshdesk, Kayako, OTRS and Zendesk. Other systems via API or custom work.	A migration service to FreeScout from other help desks, per the README. Confirm source coverage.
Mobile apps	Confirm mobile app availability and feature parity with Zammad.	Android and iOS apps with the same functionality and modules as the web version.
Self-hosted support	Paid support plans at 2,999, 5,999 and 9,999 EUR per year, per Zammad's pricing page.	Confirm paid support options directly. Docker, Softaculous, Cloudron and managed hosts are listed.

Zammad vs FreeScout licensing and paid editions

Zammad is licensed under the GNU Affero General Public License version 3, and self-hosting it carries no license fee. Your costs come from the infrastructure you run (PostgreSQL 15 or newer, Redis 7 or newer, and Elasticsearch if you want full search) and from the staff who operate it. Paid support is optional and comes as yearly self-hosted subscriptions.

Zero license fee: Self-hosted Zammad is free to run, so the recurring cost is your hosting and operations time.
Business plan: A support subscription at 2,999 EUR per year, per the Zammad pricing page.
Enterprise plan: A support subscription at 5,999 EUR per year.
Corporation plan: A support subscription at 9,999 EUR per year.
Hosted plans: Zammad's pricing page lists hosted plans from 7 EUR per agent per month, which moves the cost from infrastructure to a per-seat fee.

Check whether a self-hosted support subscription covers the upgrade and security work your team would otherwise do, and ask Zammad which channels and features each support tier includes before you compare totals.

What drives the total cost once FreeScout modules are added

The license line is only part of the bill for either product. Each card names who is paid, what is one-time versus recurring, and what moves the number, so the two options can be priced on the same basis. Costs for Zammad and FreeScout should be requested in one written scope so they are comparable.

Software license and modules

Self-hosted Zammad has no license fee, while FreeScout is AGPL-3.0 but sells modules as lifetime licenses for a single instance. For FreeScout, count every module you need, such as LDAP Integration, SAML SSO, Knowledge Base, Workflows and Time Tracking, and confirm whether each is a one-time purchase per instance. If you run separate instances for separate teams or environments, the module cost multiplies. Ask the vendor to confirm current module prices and whether updates remain included.

Zammad support subscription

Zammad support is optional for self-hosting, but the vendor's pricing page lists support plans named Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year. This is a recurring cost paid to Zammad GmbH if you choose a plan. Compare what each plan covers with the support you would otherwise buy from a partner or keep in-house. Confirm the plan tier, renewal terms and whether the subscription includes upgrade help.

Infrastructure and hosting

Zammad needs PostgreSQL 15 or newer and Redis 7 or newer, and Elasticsearch is optional but strongly recommended for search and attachment content. Memcached is needed for multi-instance deployments. FreeScout runs on PHP with MySQL, MariaDB or PostgreSQL and has no documented minimum CPU or RAM, so it can run on shared hosting. Both costs recur monthly, and the gap widens as you add search nodes, backups and staging copies. Ask for the sizing assumptions behind any hosting estimate.

Administrator time for patching and backups

Self-hosting shifts updates, backups and availability to your team, a point Zammad's pricing page states for self-hosted customers. Zammad has a fast release cadence with security releases in parallel lines, and FreeScout ships releases roughly weekly. Each product also adds module updates to track. This is usually the largest recurring cost in practice and it is internal, so price it as staff hours. Ask who owns patch windows, restore tests and on-call coverage.

Implementation and migration services

Implementation is a one-time cost paid to whoever configures the platform, such as an internal team or a services partner. Zammad includes migrators for Freshdesk, Kayako, OTRS and Zendesk, and other systems need the API or custom development. FreeScout offers a migration service for moving from other help desks. Costs rise with mailbox count, channel setup, SSO and LDAP configuration, and workflow design. Request a fixed-scope quote listing each channel, integration and migrated data set.

Staff training and change management

Agents and administrators need time to learn the new tool, and that time is a one-time cost that also recurs when new staff join. Zammad's ticket-centric model and FreeScout's shared-inbox model differ in how agents work, so training content differs too. Factor in the time to document workflows and the knowledge base, and to run parallel operation during cutover. Ask the vendor or partner for training materials and whether they are included in the quote.

Moving between Zammad and FreeScout later

This sequence shows how a team moves its tickets, mailboxes, users, authentication, workflows and knowledge content from one tool to the other, and what has to be checked at each stage before the old system is retired. Zammad includes migrators for Freshdesk, Kayako, OTRS and Zendesk, and FreeScout offers a migration service for moving other help desks into it, so the first decision is which direction and which source system you are starting from.

Confirm the direction and data mapping
Before any export, the migration owner lists which objects must move: open and closed tickets, threads and attachments, mailboxes, agents, customers, groups, tags and custom fields. Zammad's documentation describes its migrators for Freshdesk, Kayako, OTRS and Zendesk, and other systems through its API or custom development from Zammad. FreeScout describes a migration service for moving other help desks into FreeScout. Ask each vendor, in writing, how every object type maps to the target, which fields have no equivalent, and whether history and attachments are carried over. This step is done when the team has a signed-off mapping table with each gap named and an owner for it.
Export tickets, mailboxes and users
The migration engineer exports conversations and attachments from the source system and pulls the list of mailboxes and user accounts, including agent roles and customer records. Where a vendor migrator covers the source, use it. Where it does not, use the target's API import and confirm that ticket states, timestamps and sender addresses survive the transfer. Run a small test batch first and compare record counts and sample threads. This step is done when a test batch on a non-production instance matches the source on counts, states and a sample of full conversations.
Rebuild authentication and directory access
The identity owner recreates sign-in on the target. Zammad documents third-party login through SAML, OpenID Connect, Microsoft, Google, GitHub and GitLab, among other providers. FreeScout's LDAP Integration and SAML SSO are paid modules sold as lifetime licenses for a single instance, so confirm module availability and licensing before rebuilding. Map LDAP group membership to agent roles and test login for agents, administrators and customers separately. This step is done when each user type signs in through the intended path and group-based role assignments match the source.
Recreate workflows, automations and knowledge content
The support lead rebuilds routing rules, macros, SLA-style escalations and canned responses in the target, since automation logic seldom migrates intact. FreeScout's Workflows and Knowledge Base are paid modules, while Zammad includes its own automation and knowledge features in the product, so check each feature's status in your chosen edition. Export articles from the source knowledge base, convert formatting where needed and republish them with the same URLs or redirects where customers rely on them. This step is done when a checklist of every routing rule and article is ticked against the target and a sample of support scenarios produces the expected assignments.
Update mail routing and DNS records
The infrastructure owner changes where inbound mail is delivered. This means updating MX or forwarding records, shared mailbox connections, SMTP and IMAP or POP3 credentials and any OAuth connections for Microsoft 365 or Google Workspace that FreeScout uses. Keep the old system receiving mail during a short overlap so no messages are lost while DNS propagates. This step is done when test messages sent to every mailbox arrive in the target, replies leave with the correct sender address, and the old system receives no new inbound traffic.
Test every channel and integration
The QA owner tests each channel the team relies on, including email, web forms, API consumers, chat or social integrations and any webhooks or Zapier and Make connections. Zammad documents Elasticsearch as optional but strongly recommended for search, so verify search results against known tickets on the target. Confirm notifications reach agents and that attachments open correctly for customers. This step is done when a written test script covering every channel passes with named sign-off from the support lead.
Cut over, keep read access and retire the source
The migration owner switches agents to the target, freezes the source for new work and keeps it in read-only mode for an agreed period so staff can check historical records. Archive the source database and attachments under your retention policy, record where the archive is stored and who can restore it, and then decommission the old instance. Confirm the retention approach with your compliance team before deleting anything. This step is done when the archive is verified as restorable and the source is shut down with a dated record of the decision.

What implementing each helpdesk involves and where projects run long

Implementing Zammad is mostly a platform build, and the first decision is the search tier. Zammad needs PostgreSQL 15 or newer and Redis 7 or newer, and Redis carries the realtime websocket traffic, so both belong in the written plan with their backup and high availability design agreed up front. Elasticsearch is optional, but the Zammad software prerequisites documentation describes search as very limited without it, and the documentation strongly recommends it for search, reporting and attachment content. Decide this with the support lead before build starts, because adding it later means re-indexing and extra capacity planning. If you run more than one Zammad instance, such as containers or cluster nodes, Memcached becomes a requirement rather than an option, while a single installation can use the file system cache. Confirm the deployment method (package, Docker Compose or Helm chart) early, since Zammad support does not cover Docker or Kubernetes-specific problems.

FreeScout's build is lighter on infrastructure: PHP 7.4 to 8.x on Nginx, Apache or IIS, with MySQL, MariaDB or PostgreSQL. The work shifts to configuration and module decisions. Each mailbox needs SMTP, IMAP or POP3 settings, or OAuth for Microsoft 365 or Google Workspace, and the team should verify that outbound mail from the shared inbox passes SPF, DKIM and DMARC checks before users depend on it. For identity, LDAP Integration and SAML SSO are paid lifetime modules, so the plan must list them with their licenses and test group mapping, disabled-user handling and fallback logins against your directory. Confirm the module price and lifetime terms directly with FreeScout on its modules page, and total the Knowledge Base, Workflows and API modules if your current tool uses them. Workflow rebuilds and data cleanup usually run long in both products, so the migration plan for either should budget for them explicitly.

Projects most often run long in four places: mail deliverability, identity mapping, custom workflow rebuilds and data cleanup. Mail problems surface only after cutover, when replies bounce or land in spam, so test a full inbound and outbound round trip per mailbox. Identity mapping fails when agent roles, groups and SSO attributes do not line up with the old tool's permissions, and that test should include a user who should be denied access. Workflow rebuilds grow when automations from the current helpdesk are copied one for one instead of being reduced to the rules still needed. Data cleanup, such as duplicate contacts, orphaned attachments and closed tickets with no owner, is often unscoped. Ask any implementation partner to write these tasks, acceptance tests and cutover steps into the fixed scope, and confirm which migration tools each platform supports for your source system.

Questions buyers ask before choosing Zammad or FreeScout

What does FreeScout really cost once LDAP, SAML SSO and a knowledge base are added?

The software is AGPL-3.0 and free to download, but the modules you need are sold separately as lifetime licenses for a single FreeScout instance, according to the FreeScout modules page. Add up LDAP Integration, SAML SSO, Knowledge Base, Workflows and any other paid module on your list, then compare that total with Zammad, where the self-hosted software has no license fee and the paid support plans are 2,999, 5,999 and 9,999 euros per year. Ask FreeScout for the current module prices in writing, since the modules page does not show a single bundled figure, and confirm whether lifetime updates cover every instance you plan to run. Budget for your own hosting, backups and staff time in both cases.

How much effort does running Zammad or FreeScout take at small and larger scale?

Effort scales with the number of agents, the search load and how many instances you run, not with the license. Zammad requires PostgreSQL 15 or newer and Redis 7 or newer, and its documentation strongly recommends Elasticsearch for search, reporting and attachment content, so a larger team should plan for those services and their upgrades. Memcached is needed for multi-instance deployments such as containers or cluster nodes. FreeScout runs on Nginx, Apache or IIS with PHP and MySQL, MariaDB or PostgreSQL, and its README states no minimum CPU or RAM requirements, which suits a small team on modest hosting. Confirm with each vendor the sizing it expects for your agent count and mailbox volume before you commit to a host.

What do SSO and LDAP add to the work on each platform?

In both platforms, identity integration is extra configuration and ongoing testing rather than a single switch. Zammad documents third-party login through SAML, OpenID Connect, Microsoft, Google, GitHub and GitLab, among other providers, so the work is mapping roles and agent groups from your directory and testing login failure paths. In FreeScout, LDAP Integration and SAML SSO are paid modules, so the identity work also carries a license line item. Ask each vendor which directory attributes it maps, how it handles users who leave the directory, and whether group changes sync on a schedule you can audit.

Can a non-specialist administer Zammad or FreeScout day to day?

A support manager or a generalist sysadmin can handle routine tasks such as adding agents, changing queues and reviewing mailboxes in either tool. Upgrades, database maintenance, reverse proxy setup, Redis and search tuning are where specialist skill matters. FreeScout's PHP and Laravel stack is familiar to many web teams, while Zammad's stack adds Redis and optional Elasticsearch to operate. If nobody on your team will own patching and backups, a retainer or a fixed-scope operations engagement is the usual alternative to hiring. Ask DeployOpen or any implementer to document the runbook and the restore test as deliverables.

How long does migration usually take, and what does it depend on?

No supplied fact gives a migration duration, so treat any timeline as something to confirm in a written scope. The main drivers are the source system, the number of tickets and attachments, how much history you keep, and how many mailboxes and channels you reconnect. Zammad includes migrators for Freshdesk, Kayako, OTRS and Zendesk, and other systems can be imported through its API or custom development. FreeScout offers a migration service from other help desks, according to its README. Ask each option for a dry run on a copy of your data, a mapping of fields and statuses, and a plan for mail cutover.

Should we start with a paid Zammad support plan or run it ourselves first?

Start with the question of who will be on call. Self-hosted Zammad has no license fee, but the vendor's pricing page states that self-hosted customers handle updates, backups and availability, and paid support plans are priced at 2,999, 5,999 and 9,999 euros per year. A paid plan makes sense when you need vendor support for production incidents and do not have in-house Zammad experience. Teams with a strong Linux and database bench may run it first and buy support later. Ask for the plan's response commitments in writing before you choose, because the pricing page does not describe them in the supplied facts.

What should we request in a quote for either platform?

Ask for a written scope that lists agents, mailboxes, channels, identity sources, data volume to migrate and the environments you need, including staging and backups. For FreeScout, require each module, its lifetime price and what updates it covers. For Zammad, require the support tier, the install method and whether search and caching are in scope. DeployOpen plans, implements, integrates, hardens and supports self-hosted platforms in your own infrastructure, and most engagements are fixed-scope with scope and timelines agreed in writing before work starts. Ask any provider to name the deliverables and acceptance tests, and confirm every figure with the vendor before signing.

How DeployOpen helps teams choose and implement a helpdesk

DeployOpen helps teams decide between Zammad and FreeScout against their own channel, identity and reporting needs, then implements the choice inside their infrastructure. Engagements are fixed-scope, with the scope agreed in writing before any work starts.

How we scope

Map the channels your agents must answer, such as email only or email plus chat and social, before choosing a platform
List which SSO and directory features you need, and check whether each one is free or a paid FreeScout module
Agree the scope, deliverables and timeline in writing before work starts, with pricing set from that written scope

How we build

Deploy the chosen helpdesk in your cloud account, data center or air-gapped network, with its database, cache and search services
Configure mailboxes, authentication, roles and workflows, and confirm each licensed module or add-on you rely on
Test email delivery, search behavior and backup restores before cutover, and record the results

How we hand over

Document the architecture, configuration, module inventory and upgrade steps so your team can run the system
Plan any data migration from your current helpdesk, including how tickets, attachments and users are mapped
Walk your administrators through daily operations, incident response and the procedure for applying updates

How we support

Offer ongoing support, upgrades and continuous testing as a retainer after the fixed-scope engagement ends
Review each new release and security update for the platform you run, and schedule upgrades with your team
Keep the written scope as the reference point for any change, so additional work is agreed before it begins

Zammad vs FreeScout