What does helpdesk software cost when you build, partner or subscribe?
The software license is rarely the main cost of a helpdesk, whether you self-host or subscribe. Zammad, FreeScout and osTicket are free to download under open-source licenses, so the total depends on the people who run and support the desk, the infrastructure it runs on, the cost of moving existing tickets and customers, and whether you buy vendor support. For a team paying per agent today, the question is which of those costs replace the SaaS fee and which add to it. Zendesk's pricing page, as read in October 2026, lists Support Team at US$19, Suite Team at US$55 and Suite Professional at US$115 per agent per month paid yearly, with Suite Enterprise by quote. Freshdesk's pricing page, as read in October 2026, lists Growth at $19, Pro at $55 and Enterprise at $89 per agent per month billed annually.
Self-hosting converts the per-agent fee into a mix of one-time and recurring costs. Zammad has no license fee when self-hosted, and its paid self-hosted support subscriptions are Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year, according to its pricing page. A support subscription is optional, and the work of hosting, upgrading and securing the platform stays with your team or a partner. Confirm with each vendor whether its support plan covers security releases and what response times it commits to in writing. Also confirm whether Elasticsearch, Redis and PostgreSQL hosting, backups and monitoring are included in your quote or billed separately.
The estimate depends on agent count, ticket volume, the number of channels you connect, how much history you migrate from Zendesk or Freshdesk, and how many environments you need for testing and disaster recovery. Ask any implementation partner for a fixed-scope quote that lists each component: installation, migration, channel setup, search configuration, single sign-on, backup and restore testing, security patching and handover. Ask which items recur monthly or yearly and which are one-time. Compare that total over three years against the SaaS list price multiplied by your agent count, plus any suite add-ons you would need to match current features.
Which cost components apply to in-house, partner and SaaS helpdesks
This table compares who is paid for each helpdesk cost item under an in-house build, an implementation partner engagement and per-agent SaaS, and whether each item is one-time or recurring. Read each row across the three columns to see where spending moves. The main takeaway is that self-hosting removes the per-agent licence line but keeps hosting, administration and security work on your side, so confirm who carries each row before comparing totals.
| Cost component | In-house build | Implementation partner | Per-agent SaaS |
|---|---|---|---|
| Software license | No license fee for self-hosted Zammad, FreeScout or osTicket; support is optional | Same open-source licence; partner fees cover delivery, not the software | Recurring per-agent subscription, billed by the vendor |
| Hosting and infrastructure | Recurring, paid to your cloud or data center provider; you size PostgreSQL, Redis and search | Recurring, paid to your provider; partner may size and document it | Included in subscription; vendor hosts the service |
| Implementation and configuration | One-time staff time for channels, roles, SLAs and automations | One-time, paid to the partner against a written scope | Mostly one-time internal admin time; vendor setup services are quoted separately |
| Migration of tickets and attachments | One-time; Zammad includes migrators for Freshdesk, Kayako, OTRS and Zendesk, others need API work | One-time, paid to the partner; confirm attachment handling and history mapping | One-time, often by the vendor or a third party; confirm what the vendor exports |
| Integrations | Recurring maintenance of CRM, telephony and SSO connectors on your staff | One-time build plus recurring support for connectors you agree to maintain | Vendor marketplace apps may be included or billed separately; confirm per connector |
| Ongoing administration | Recurring internal staff time for users, queues, backups and upgrades | Recurring only if you buy a retainer; otherwise your team keeps this work | Lower internal effort for the platform, though agent licences still need admin |
| Security releases | Recurring internal effort to apply vendor security updates promptly, tested first | Recurring if included in a retainer; confirm patch windows and testing | Applied by the vendor to the hosted service; you confirm customer-side changes |
| Vendor support | Optional paid subscription from the software vendor, tiered by level; confirm what each tier covers | Partner support is recurring if contracted; vendor subscription may still be needed | Included in the per-agent plan, with support tiers that differ by plan |
What per-agent SaaS helpdesk plans list for
Zendesk's list prices, as read on its pricing page in October 2026, are US$19 per agent per month for Support Team, US$55 for Suite Team and US$115 for Suite Professional, each paid yearly. Suite Enterprise is priced by quote only. The same page offers a 14-day trial of Suite Professional (Zendesk pricing). Freshdesk's pricing page, read in the same month, lists Growth at $19, Pro at $55 and Enterprise at $89 per agent per month, billed annually, with a 14-day trial of the Enterprise plan (Freshdesk pricing). Both vendors price per agent, so a team of 10 agents on a mid-tier plan pays roughly ten times the per-seat figure each month before any add-on, and the seat count is the first number to fix in any comparison.
These figures are list prices, not what a buyer pays. Add-ons such as advanced AI features, extra channels, sandboxes, analytics or premium support are usually sold separately, and enterprise terms, volume discounts and multi-year commitments change the total. Ask each vendor for a written quote that lists every module, the billing currency, the renewal uplift and the data export terms. Confirm which plan includes the features your scope depends on, such as SSO, audit logs, SLA rules and data residency, because those features often sit on the higher tiers. Use the trial period to test your real migration and channel setup, not only the interface.
Price the SaaS option against the self-hosted option on the same basis: per-agent seats and add-ons on one side, and on the other, hosting, support, administration and migration effort. A per-seat price is recurring, while implementation and migration are usually one-time costs. The cost of a self-hosted helpdesk depends on your infrastructure and support choices, so request quotes from your partner and your platform hosts rather than assuming a figure. Compare totals over the period you plan to keep the tool, including the price increases that vendors may apply at renewal.
What moves the helpdesk cost up or down
Self-hosted Zammad has no license fee, so the total depends on the people, infrastructure and support decisions around it. The cards below show which choices push the cost up or down, so you can ask a partner for a quote that reflects your own scope.
Agent count and growth
Per-agent SaaS pricing scales directly with headcount, so every agent you add raises the recurring bill. Self-hosted Zammad, FreeScout and osTicket do not charge per seat, but more agents still mean more concurrent sessions, more notifications and more load on the database and Redis. Ask a partner how the hosting plan is sized for your peak agent count and how it will be resized as the team grows.
Channels and integrations
Each extra channel, such as email inboxes, chat, web forms or telephony, adds connector setup, testing and ongoing maintenance. Integrations with a CRM, identity provider or telephony system add build effort and change-control work each time an upstream product updates. List every channel and integration in writing before you request a quote, and ask which items are included in the fixed scope.
Data volume and Elasticsearch
Elasticsearch is optional for Zammad, but the documentation strongly recommends it for faster search, reporting and searching email attachment content. Adding it means a separate search cluster to size, patch, back up and monitor, which adds infrastructure and operations cost. Ask whether attachment content search is required, because that requirement is the main reason the search tier grows with history.
Multi-instance hosting and Memcached
Container deployments and cluster nodes need Memcached, while a single installation can use the file system cache. Moving from one server to a multi-instance layout adds components, load balancing and more hosting capacity, so the infrastructure bill rises with the architecture. Confirm early whether you need high availability, since that decision changes the number of servers, the cache design and the operations hours to support them.
Migration source and attachment volume
Zammad includes migrators for Freshdesk, Kayako, OTRS and Zendesk, and other systems need API import or custom development. Attachment volume often drives the migration effort and storage size more than ticket count does. Ask the partner which source system you have, how many years of tickets and attachments must move, and whether historical data is in scope or only open tickets.
Support subscription tier
Self-hosted Zammad has no license fee, but vendor support subscriptions are an optional recurring cost tiered by level. Choosing a subscription shifts part of the support risk to the vendor, while a partner retainer covers hosting, upgrades and security releases. Compare the subscription scope against the partner scope so you do not pay twice for the same response commitment, and confirm which security releases each option covers.
Why self-hosted Zammad has no license fee but still has running costs
Self-hosted Zammad carries no license fee, because Zammad is licensed under the GNU Affero General Public License version 3. FreeScout, licensed under AGPL-3.0, and osTicket, licensed under GPL-2.0, are also free to download and run. The money you spend goes to the infrastructure that runs the helpdesk, the people who operate it, and any support you choose to buy. Before comparing totals with a per-agent SaaS price, list those components as separate line items so the comparison is like for like.
The recurring infrastructure for Zammad starts with PostgreSQL 15 or newer, which stores the content, and Redis 7 or newer, which handles realtime websocket communication. Elasticsearch is optional but strongly recommended for faster search, reporting and searching email attachment content, so it is a sizing decision you should make early. Multi-instance deployments such as containers or cluster nodes also need Memcached, while a single installation can use the file system cache. A reverse proxy, Nginx or Apache, sits in front of the application. Ask your partner to size each of these for your agent count, attachment volume and backup retention, and confirm who patches them and on what schedule.
Zammad sells optional self-hosted support subscriptions named Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year, according to the Zammad pricing page. These tiers buy vendor support for the application itself, so they suit teams that want a contractual response path without hiring specialist staff. They do not cover your database, network or hosting, and Zammad documents that Kubernetes support covers only the application. Confirm in writing exactly what each tier includes, what response commitments apply, and whether security releases are covered, before you treat the subscription as a substitute for internal operations.
How to build your own helpdesk cost estimate
This sequence turns a vague comparison of self-hosted helpdesk and SaaS into a three-year total that finance and IT can check line by line. Each step produces a named input, so the estimate can be rerun when headcount, channels or support terms change.
Count current agents and seats
Start with a headcount of people who will work in the helpdesk, split into agents, team leads and occasional users such as second-line engineers. Ask the support lead and HR for the current roster and the expected change over the next three years, because SaaS vendors price per agent and self-hosting costs grow with concurrency and users. The step is done when you have one agent count per year and a list of which roles need full licenses or a read-only view.
List channels and integrations
Write down every channel that creates tickets (email, web form, chat, phone, social, in-app) and every system the desk must talk to, such as CRM, identity provider, telephony and billing. Each channel and connector adds configuration work, testing and sometimes a paid add-on on SaaS plans, so the list drives both build effort and licence tier. The step is done when each channel and integration has an owner and a stated requirement.
Inventory tickets and attachments to migrate
Measure the existing ticket history, attachment volume and the number of open tickets that must move. Confirm the source platform and whether a migrator exists for it, since Zammad documents migrators for Freshdesk, Kayako, OTRS and Zendesk and supports other sources through its API or custom development. The step is done when you have record counts, total attachment size, a decision on how much history to keep, and a quote line for migration work with a named owner.
Choose hosting and environments
Decide where the platform runs and how many environments you need, typically production plus a test or staging copy for upgrades and security releases. Self-hosted Zammad requires PostgreSQL 15 or newer, Redis 7 or newer and a reverse proxy, and multi-instance deployments need Memcached, while Elasticsearch is optional but strongly recommended for search. The step is done when you have a hosting bill of materials per environment and an estimate of the infrastructure team time to run it.
Decide the support tier
Choose between running the open-source edition with internal staff, buying a vendor support subscription, or buying implementation and ongoing support from a partner. Zammad's published self-hosted support subscriptions are priced at 2,999 EUR, 5,999 EUR and 9,999 EUR per year (the Zammad pricing page), and other options should be priced from written quotes. The step is done when the support tier is written down with its response scope and what it excludes, such as Kubernetes platform issues.
Add internal administration time
Estimate the recurring work your own team will carry: security releases, backups and restore tests, user and role changes, automation tuning, reporting and monitoring. Security releases matter here because Zammad published fixes on several lines in the same period, so the upgrade process has to be repeatable. The step is done when you have an hours-per-month estimate by role, agreed with the people who will do the work.
Compare three-year totals against SaaS
Build one table with three columns of cost over the same three years: self-hosted (licence, hosting, support, migration, internal time), partner-supported self-hosting, and per-agent SaaS. For SaaS, use the list prices on the vendor pricing pages you read, multiplied by your agent count and any add-ons, and state the billing basis (monthly or annual). The step is done when the table shows which costs are one-time, which recur, and which assumptions would change the result if headcount grew.
Request a written quote from a partner
Ask any implementation partner for a fixed-scope written quote that lists the deliverables, the assumed agent count, channels, integrations, migration volume and environments, along with the support tier and what is excluded. Ask for the effort split between setup and recurring work, the handover documentation and the process for applying security releases. The step is done when the quote can be placed beside your three-year table line by line, and any gaps are closed in writing before work begins.
Questions buyers ask about helpdesk cost, effort and time
How much internal effort does a self-hosted helpdesk need?
Self-hosting shifts effort from the vendor to your team. The software itself has no license fee for Zammad, FreeScout or osTicket, so the effort is in running the stack: a PostgreSQL database, Redis for realtime updates, a reverse proxy, backups, and patching. Zammad also documents Elasticsearch as optional but strongly recommended for search and attachment content, and Memcached for multi-instance deployments such as containers or cluster nodes. Recurring work includes applying security releases, which Zammad published for both the 6.5 and 7.x lines in October 2026, and testing upgrades before they reach production. Ask your team to size these tasks in hours per month, including who is on call when a ticket channel stops receiving email.
Can our team run a self-hosted helpdesk without outside help?
Some teams can, especially those with existing Linux, database and container skills and a clear owner for the helpdesk. The harder parts are rarely the first install. They are email channel setup, identity integration, search tuning, backup restores and the upgrade path after a major release. Zammad documents package installation, Docker Compose and a Kubernetes Helm chart, but its Kubernetes support covers only the Zammad application, not cluster issues. Decide early which tasks stay in-house and which need a partner under a written scope, and confirm who holds the on-call duty for ticket intake.
How long does migration from Zendesk or Freshdesk usually take?
The duration depends on data volume, the number of channels being reconnected, custom fields, automations and how much history must move. Zammad includes migrators for Freshdesk, Kayako, OTRS and Zendesk, while other systems usually need the Zammad API or custom development. Plan separate work for attachments, user identities, SLA rules and macros, and test a full import on a copy before cutover. No duration can be given here without a scoped inventory of your current tool, so ask any partner for a migration plan that lists these items before quoting time.
Is per-agent helpdesk SaaS cheaper for small teams?
Often the monthly subscription looks lower for a very small team, but the comparison must include what the subscription does not cover. Zendesk lists Support Team at US$19, Suite Team at US$55 and Suite Professional at US$115 per agent per month paid yearly, with Suite Enterprise by quote. Freshdesk lists Growth at $19, Pro at $55 and Enterprise at $89 per agent per month billed annually. These prices scale with headcount and plan tier, and they are read from October 2026 pages, so check current rates. Self-hosting has hosting, staff time and support costs instead, and the break-even point depends on your agent count, plan needs and internal skills.
What should a partner quote for a helpdesk project include?
A useful quote lists the scope in writing before work starts: the platform and version, hosting target, channels to connect, identity integration, migration sources and volumes, search and reporting setup, backup and restore testing, documentation, and handover. It should separate one-time work from recurring items such as support, upgrades and security updates. Ask how release management is handled, who tests after each security release, what happens if scope changes, and what evidence is delivered for compliance reviews. DeployOpen works on fixed-scope engagements agreed in writing, with ongoing support and upgrades available as retainers, and quotes follow from that written scope.
What does the work need from our own staff?
Expect demands on several roles: an executive owner for the decision, a support lead who defines queues, SLAs and macros, an IT or platform engineer for hosting and identity, and a mail administrator for the support mailboxes. Staff must confirm the source of truth for users and groups, provide test accounts, approve the migration sample, and attend acceptance testing. Time from these people is usually the largest internal cost, so ask any partner to name the decisions they need from you and the dates by which they are needed.
When is a vendor support subscription worth paying for?
A support subscription is worth evaluating when the cost of an outage or a slow security fix exceeds the subscription, or when internal skills are thin. Zammad sells self-hosted support subscriptions named Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year, according to its pricing page. Compare those figures with your internal on-call cost, your required response expectations, and whether a partner retainer covers the same need. Confirm exactly what each tier includes, such as response times and the scope of vendor support, before deciding.
What an implementation partner should scope and price separately
A fixed-scope quote for a self-hosted helpdesk should separate every component that someone will be paid to build, run or hand over, because each one recurs or ends at a different point. Discovery comes first: current ticket volume, channels in use, agent roles, SLA rules, the data to migrate and the identity provider to connect. Hosting setup covers the cloud account or data center build, the reverse proxy (Nginx or Apache), PostgreSQL and Redis, backups and monitoring. Migration is priced separately because the effort depends on the source system, the attachment volume and how much history must survive. Ask the partner whether Zammad's built-in migrators for Freshdesk, Kayako, OTRS and Zendesk apply to your source, or whether an API import or custom development is needed. Channel and SSO configuration (email inboxes, web forms, SAML or OpenID Connect login, role mapping) should be a named line item, since each channel and identity provider adds testing. Search and caching deserve their own lines: Elasticsearch is optional for Zammad but strongly recommended for search and attachment content, and Memcached is needed for multi-instance or container deployments. Testing, documentation, and handover to your operations team should each appear with acceptance criteria. Ask what the partner will test, who signs off, and whether handover includes runbooks for restores and upgrades. Finally, separate the retainer. Upgrades and security releases (Zammad published security updates for both the 6.5 and 7.x lines in October 2026) are recurring work, and a support subscription from the software vendor is a different contract from a services retainer. Confirm in writing what the retainer covers, response expectations, and whether Kubernetes-specific issues are in scope, since the vendor's support covers only the application on that platform. DeployOpen does not publish a price list; a quote follows from the written scope, so the more precisely these lines are defined, the more comparable the quotes will be.
How DeployOpen scopes, delivers and supports a helpdesk implementation
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted helpdesk platforms inside your own cloud accounts, data centers or air-gapped networks. For a cost decision, that means the estimate starts from a written scope that separates license, hosting, migration, integration and support effort, so you compare like with like against a SaaS quote.
How we scope
- Inventory current agents, teams, channels, mailboxes and monthly ticket volume to size the self-hosted option accurately.
- Define the written scope for Zammad, FreeScout or osTicket, including hosting target, database and cache components, and integrations.
- Agree deliverables, timelines and exclusions in writing before work starts, since most engagements are fixed-scope.
How we build
- Deploy the chosen helpdesk with PostgreSQL, Redis and reverse proxy components sized to your hosting and availability needs.
- Plan and run migration from the current tool, with test imports and reconciliation of tickets, users and attachments before cutover.
- Test authentication, email channels, search and backups against the agreed scope before handing the environment over.
How we hand over
- Document the architecture, configuration, runbooks and cost model so your team can compare running costs over time.
- Provide a handover that names who owns hosting, updates and security releases after the project closes.
- Record the controls and evidence produced during delivery so your compliance team can use them in assessments.
How we support
- Offer ongoing support, upgrades and security patch application as a retainer, scoped separately from the build.
- Confirm with the platform vendor which support subscription tier, if any, is included in your scope and which remains yours.
- Review hosting, licensing and support costs at each planned upgrade so the build versus SaaS comparison stays current.
