Zendesk is the default answer for customer support software, and it earns that position: it is polished, capable and run entirely for you. It is also priced per agent per month, which means the bill is indexed to your headcount and rises at exactly the moment growth makes you hire. Zammad is the leading open source alternative, and Node runs it as a fully managed service on UK infrastructure for a flat monthly fee. Here is the honest comparison.

Two pricing models

Zendesk prices per agent per month. At the time of writing, the published UK prices (billed annually) are £15 per agent per month for the basic Support Team plan, £45 for Suite Team and £89 for Suite Professional, with Suite Enterprise on custom pricing. The Copilot AI add-on is a further £40 per agent per month, and monthly billing runs higher than the annual rates. Every one of those numbers multiplies by your agent count, every month.

Zammad on Node is a flat rate-card fee: £25 a month for the Small tier, £45 for Medium (which typically suits support teams of up to 50 agents) and £75 for Large, billed hourly with no minimum term. There is no per-agent licence in Zammad at all, so the fee is the same whether five people or forty share the queue. Current figures are always on the pricing page.

The per-agent maths

Vendor list prices at the time of writing, annual billing, before add-ons. These are list prices, not a quote: Zendesk discounts at negotiation, and your mix of plans may differ.

Team Zendesk Suite (list, annual billing) Zammad on Node (flat)
5 agents on Suite Team £225 a month, £2,700 a year Small: £25 a month, £300 a year
10 agents on Suite Team £450 a month, £5,400 a year Medium: £45 a month, £540 a year
10 agents on Suite Professional £890 a month, £10,680 a year Medium: £45 a month, £540 a year
15 agents on Suite Professional £1,335 a month, £16,020 a year Large: £75 a month, £900 a year

The honest headline is not any single row but the direction of travel: the Zendesk column grows with every hire and every add-on, while the Node column moves only if the deployment itself needs more resource. Add Copilot at £40 per agent per month and the ten-agent Suite Professional bill rises by another £4,800 a year; there is no equivalent multiplier on the flat fee.

What you get and what you give up

Zendesk Zammad on Node
Cost model Per agent per month, per plan tier, plus per-agent add-ons Flat monthly fee, no per-agent licence
Core support Multi-channel ticketing, SLAs, automation, knowledge base, reporting The same core: email, web, chat, phone and social as one queue, SLAs, triggers, knowledge base, reporting
AI tooling Copilot add-on and outcome-priced AI agents; a real strength No comparable vendor AI suite; automation is rules and triggers
App marketplace Large third-party ecosystem Smaller integration catalogue; open API and open source for anything custom
Voice Built-in contact centre (add-on pricing) Telephone notes and integrations rather than a built-in contact centre
Data location Zendesk's cloud, on its terms UK infrastructure in your own tenant, open formats
Feature gating Key features held to higher tiers and add-ons Full platform, nothing gated by seat or tier
Operations Run by the vendor Run by Node: hosting, upgrades, backups, monitoring, deliverability, single sign-on

When Zendesk is the right choice

Fair is fair. A very small team on the £15 Support Team plan is paying £30 to £45 a month; the saving from moving is modest and Zendesk's zero-decision onboarding may be worth more. A support operation built on AI deflection should stay put for now: Zendesk's Copilot and AI agents are genuinely ahead, and Zammad has no like-for-like answer. A team that depends on marketplace apps or Zendesk's built-in voice channel will not find one-click equivalents. And if your agent count is stable, the sums above lose their compounding sting. If any of these describe you, we will say so when you ask.

When Zammad wins

A growing team: the per-agent model punishes hiring. From roughly five agents the gap is thousands of pounds a year, and it widens with every seat.

Owning the customer relationship: tickets, contact records and conversation history live in your own database on infrastructure you control, in open formats. Leaving is an export, not a negotiation, which is the position we think every customer should be in (our view on open source).

Nothing gated: SLAs, automation, knowledge base and reporting are all in the platform, not held back for a higher tier.

Accountability: every ticket carries a complete audit trail, and single sign-on through Keycloak means a leaver loses access to the helpdesk the moment they leave.

What the flat fee actually covers

A fair objection to any self-hosted comparison is that the software licence was never the whole cost: somebody has to run the thing, and Zendesk's price includes the running. So does ours. The flat fee covers deployment, upgrades and security patching, daily backups, continuous monitoring, and the piece of helpdesk operations that most often goes wrong in self-hosted setups: email deliverability. Support lives and dies on email, so we configure SPF, DKIM and DMARC, manage sending reputation and watch delivery on both directions. Single sign-on through your own identity realm is included, so agents log in centrally and a leaver loses access in one action. The people doing this are the two named engineers who run the platform, not a queue. What the fee does not include is Zendesk-style vendor AI or a marketplace; we would rather say that here than have you discover it after a migration.

Your support data on UK infrastructure

Support tickets are customer personal data, and often the most candid record your organisation holds. With Zammad on Node that data sits in an isolated tenant on hardware we own in a UK datacentre, under UK jurisdiction, covered by a UK GDPR Article 28 data processing agreement with a published sub-processor list. The engineers who operate it are named, their administrative actions are logged, and nothing about the setup requires trusting a vendor's cloud on the vendor's terms.

Migrating from Zendesk

Zammad ships a built-in Zendesk migrator, so this is a well-trodden path rather than a bespoke project. It connects to your Zendesk instance with an administrator API token and imports users, organisations and tickets with their conversation history. Two caveats worth knowing up front: import speed is bounded by Zendesk's API rate limits on your plan, and passwords do not migrate, which is moot when agents sign in through single sign-on. Node runs the import, verifies the migrated data against the source, and switches your inbound channels over only when you have confirmed everything is where it should be.

The bottom line

Zendesk is a good product with a pricing model that taxes growth. Zammad is the same core job, support conversations captured, tracked and resolved, at a flat fee on infrastructure you control. If your team is small and stable, or leans hard on Zendesk's AI, staying may be right, and we will tell you so. If your support team is growing, the maths above is the argument. See Hosting for Zammad for what the managed service includes, the pricing page for current figures, and open source alternatives to SaaS for the wider catalogue.

Frequently asked questions

Can we migrate from Zendesk to Zammad?

Yes. Zammad ships a built-in Zendesk migrator: point it at your Zendesk URL with an administrator API token and it imports your tickets, users and organisations, including conversation history. Import speed depends on Zendesk's API rate limits for your plan, and user passwords do not transfer, which matters little when agents sign in through single sign-on. Node plans and runs the migration, verifies the imported data against the source, and cuts your channels over once you are happy.

What does the flat monthly price include?

The deployment itself plus everything needed to run it in production: hosting on UK infrastructure, upgrades, security patching, daily backups, monitoring, email deliverability configuration (SPF, DKIM, DMARC) and single sign-on through your own identity realm. There is no per-agent licence, so the price does not change as your support team grows. Current figures are on our pricing page.

Is Zammad on Node really cheaper than Zendesk?

It depends on team size, and we will be straight about it. For one or two agents on Zendesk's cheapest Support plan, the gap is small and Zendesk's polish may be worth more than the saving. From around five agents on a Suite plan the difference is large: at the time of writing, ten agents on Suite Team list at about £5,400 a year against £540 a year for a flat Zammad Medium tier. The bigger the team, the harder the per-agent model is to defend.

What do we give up by leaving Zendesk?

Honestly: Zendesk's AI tooling (the Copilot add-on and outcome-priced AI agents), its large app marketplace, and its built-in voice contact centre are ahead of anything in the open source helpdesk world. Zammad covers the core of support work, including multi-channel ticketing, SLAs, automation, a knowledge base and reporting, but if those Zendesk-specific capabilities carry your operation, say so before you move, because Zammad will not replace them like for like.

Where does our support data live with each option?

Zendesk holds your tickets and customer records in its own cloud under its terms. A Zammad deployment from Node runs on UK infrastructure in your own isolated tenant, under UK jurisdiction, with a UK GDPR Article 28 data processing agreement as standard. Your conversation history sits in a database you can access directly and export in open formats at any time.

Does Zammad limit the number of agents?

No. Zammad has no per-agent licence and no seat count. Our tiers are sized by the resources the deployment needs, not by headcount: the Medium tier typically suits support teams of up to 50 agents. Adding an agent is an account, not an invoice line.