Open-Source Intercom Alternatives in 2026

The reason teams start looking for an Intercom alternative is rarely the product. It's the invoice — and specifically the discovery that the invoice has three axes. You pay per seat, then per AI outcome, then per channel. Add a person and it goes up. Get busier and it goes up. Succeed at automating support and it still goes up, because the automation is metered too.

Why do teams look for an Intercom alternative?

Because the bill scales on three axes at once. Intercom's seat plans start at $29/seat/month annually ($39 monthly) and run to $132–$139/seat on Expert. On top of that, Fin costs $0.99 per AI outcome after the 50 included with a $49/month subscription — and SMS, WhatsApp, phone, and email campaigns are metered separately. Note the wording: Intercom bills per outcome rather than per resolution, charged at most once per conversation, with qualification priced at $9.99.

Zendesk has the same shape. Published seat prices run from $19 per agent per month for Support Team to $115 for Suite Professional, with Enterprise quoted by sales rather than listed. Then the add-ons: Copilot at $50/agent/month and the Workforce Engagement Bundle at $50/agent/month. Stack those on Suite Professional and you are at $215 per agent per month — 87% over the base plan. AI agent usage is billed separately, per automated resolution drawn from a resolution allowance, and since 18 May 2026 resolutions arrive in three tiers: an assisted escalation costs nothing, an unverified contained resolution costs nothing, and only a verified resolution draws down the allowance. Zendesk does not publish the per-resolution rate on its pricing page — the figures in its own documentation are marked as placeholders — so that number arrives from a salesperson.

None of this makes them bad products. Both are mature, both have reporting a decade deep. It makes them expensive in a specific way: the more successfully you automate, the more you pay for having done it. It is the same pattern every meter in this industry has — counting something other than the work.

What is the best open-source Intercom alternative?

Chatwoot is the most mature and the default recommendation — live chat, email, social, and WhatsApp in one inbox, and the closest like-for-like replacement. Zammad is better if you need SLA management and ticketing discipline. FreeScout is the lightest. Munin is the pick if you want the support inbox to share one customer record with your CRM, knowledge base, and content, and to be operated by AI agents.

The honest framing: three of these four replace your inbox. One replaces the reason you had four systems. If it's the CRM side of that you're weighing rather than the inbox, the open-source CRM field compares differently — and mostly on the licence.

Is Chatwoot a good replacement for Intercom?

Yes — Chatwoot is the most mature open-source customer messaging platform available and the closest thing to a drop-in Intercom replacement. It handles live chat, email, social inboxes, and WhatsApp from one unified interface. Expect roughly 2–4 hours to stand up on a VPS, with 2 GB RAM minimum and 4 GB recommended once you're past a few hundred conversations a day; how that footprint compares to running a whole platform on one host is its own piece.

The prices are published, which is more than Zendesk manages. Chatwoot Cloud is $0 on Hacker for up to 2 agents and 500 conversations a month, then $19, $39, and $99 per agent per month billed annually on Startups, Business, and Enterprise, with Captain AI credits included per tier — 300, 500, 800 — and further credits at $20 per 1,000. Self-hosted, the Community Edition is free forever, and the supported editions are $19 and $99 per agent per month. Worth reading the shape rather than only the number: self-hosting removes the vendor from your data path, and the paid self-hosted editions are still counted per agent.

One thing to read carefully before you commit: the community edition is MIT, but everything under the enterprise/ directory ships under a separate proprietary, source-available licence. You can read that code, but running those features in production requires a paid Chatwoot subscription and an active agreement. That's open core — a perfectly legitimate business model, and not the same thing as the MIT badge on the front page.

Chatwoot covers WhatsApp, Instagram, and Facebook natively; Munin's four channels are email, chat widget, SMS, and voice. If most of your support arrives through social channels, take Chatwoot. If it arrives through email and chat, and the problem is that your inbox knows nothing about the customer sitting in it, that is the job Munin was built for — one record behind the inbox, MIT throughout, and no enterprise/ directory to buy back.

What about Zammad and FreeScout?

Zammad is a helpdesk rather than a chat tool. It takes email, chat, phone, and social, converts them into tickets, and gives you SLA management, reporting, and a knowledge base — the things a support org with contractual obligations actually needs. Its licence is also the cleanest in the category: AGPL-3.0 throughout, with no ee/ directory and no cut-down community edition, and self-hosting needs no licence key to get the full feature set. The cost is setup: Ruby on Rails dependencies on a Linux server, a higher bar than the Docker-based options.

FreeScout is a lightweight shared inbox on PHP/Laravel, under 256 MB RAM idle, installable on any LAMP host. It's the right answer when what you want is a shared mailbox that isn't Gmail, and nothing more. Its paid modules are unusual in this field for being AGPL-3.0 as well — what you buy is a download key and support, not different terms.

One fact all three self-hosted options share, worth stating precisely rather than vaguely: none of Chatwoot, Zammad, or FreeScout publishes an official MCP server today. Chatwoot's own extensibility for Captain is custom HTTPS tools rather than MCP, and the Chatwoot, Zammad, and FreeScout MCP servers you will find on GitHub are community projects with no vendor maintaining the contract. That is not a claim that an agent cannot drive them — a REST API and a community wrapper get you a long way — it is a claim about who is on the hook when the API changes underneath you. Munin's position is the inverse: the tool catalogue is the primary surface and the REST API is the thing that came second. If it is the cheaper hosted end of the market you are weighing instead, the Freshdesk comparison covers that field and the new meter Freshworks put on its own MCP interface.

How is Munin different from a self-hosted helpdesk?

Munin isn't a helpdesk with a CRM bolted on. Conversations, CRM, knowledge base, CMS, outreach, and analytics are six modules over one database, and the customer exists in it exactly once. When an email arrives, the sender resolves against the record your outreach campaigns and knowledge base already use. No sync job, no second version of the truth.

That matters most in the moment a support conversation needs to know something. The agent answering it can search the knowledge base, read the customer's history, and check what campaign they're in — not through integrations, but because there is one schema behind all six modules, with row-level security carrying the tenant boundary. It also runs backwards: a closed conversation is where the CRM record gets filled in, without anyone retyping what the customer just said. And what your team answered once becomes a knowledge-base article the next person finds instead of another ticket.

The second difference is who operates it. Munin exposes 204 MCP tools at one endpoint, so Claude, ChatGPT, Cursor, or your own runner does the triage, the tagging, the contact extraction, and the knowledge-base drafting directly. Not as a chatbot bolted to the front — as the thing running the desk, with humans approving what matters. Agents propose, humans decide.

And Munin is MIT throughout. No enterprise/ directory, no feature you have to buy back. We'd rather you could leave.

Self-hosted Intercom alternatives compared

Pricing and licence packaging change frequently — confirm on each vendor's own site, including ours. Figures here are indicative and were last checked on 25 August 2026.

Frequently asked questions

What is the best free open-source alternative to Intercom? Chatwoot for a like-for-like replacement — it's the most mature open-source customer messaging platform and covers chat, email, social, and WhatsApp. Munin if you want the inbox to share one customer record with your CRM, knowledge base, and content, and to be run by AI agents rather than clicked through.

How much does Chatwoot cost? Cloud is $0 on Hacker for 2 agents and 500 conversations a month, then $19, $39, and $99 per agent per month billed annually on Startups, Business, and Enterprise. Self-hosted, the Community Edition is free forever and the supported editions are $19 and $99 per agent per month. Captain AI credits are included per tier, with extra credits at $20 per 1,000.

Is Chatwoot really open source? The community edition is MIT-licensed, so yes for the core. But everything under the enterprise/ directory is proprietary source-available and requires a paid subscription to run in production. That's an open-core model. Munin has no equivalent directory — the whole suite is MIT.

How much does Intercom actually cost? Seats start at $29/month annually or $39 monthly, rising to $132–$139 on the Expert plan. Fin AI adds $0.99 per outcome after 50 included with a $49/month subscription — $9.99 if the outcome is a sales qualification — and SMS, WhatsApp, phone, and email campaigns are metered on top. Budget well above the headline seat price.

What counts as an automated resolution at Zendesk? Since 18 May 2026, resolutions are tiered. An assisted escalation, where the AI helped but a human finished, is free. A contained resolution that fails verification is also free. Only a verified resolution — no customer follow-up for 72 hours, then confirmed by a language model reading the transcript — draws down your resolution allowance. Zendesk does not publish the rate per resolution; the numbers in its own help centre are labelled placeholders, so you get the real one from sales. Worth knowing precisely, because the vendor writes the definition of the thing it bills you for.

Which of these has an official MCP server? Intercom does, at mcp.intercom.com, and so does Munin. Chatwoot, Zammad, and FreeScout do not — the servers on GitHub for those three are community-maintained. Zendesk publishes an MCP client rather than a server; the app named "MCP Server" in its marketplace is built by a third-party partner, not by Zendesk.

Can I self-host a helpdesk with AI support agents? Yes. Munin self-hosts with docker compose up — three containers, Postgres with pgvector plus a backend and a dashboard — and exposes its whole surface as MCP tools, so you point any model at it and the AI cost is whatever your provider charges, not a per-resolution fee to your helpdesk vendor.

Which open-source helpdesk has SLA management? Zammad, and it's the right pick if you're measured on contractual response times. Munin covers a different job: one customer record shared across conversations, CRM, knowledge, and outreach, operated by agents through MCP tools.

Do I need to self-host to escape per-seat pricing? No. Munin Cloud is EU-hosted with a free tier, and the paid plan is a flat €99/month per org rather than per seat. Self-hosting is free forever under MIT if you'd rather run it yourself — same code either way.

If what actually annoys you is that support, sales, and content each hold a different version of the same customer — and that you're metered on automation you could be running yourself — start on Munin Cloud in the EU, or clone the repository and run it on your own machine.

You shouldn't pay more for support the better you get at it.