2 open source alternatives to Intercom
Conversational support and marketing. Here are the open source projects real teams use instead — ranked by fit, with honest pros and cons for each.
What people don't love about Intercom
- Heavy per-seat pricing.
- Data locked in Intercom cloud.
- Some features gated behind premium tiers.
Current Intercom pricing (for reference): From $39/seat/month.
Quick comparison
| Alternative | Best for | License | Self-host | Hosted cloud? |
|---|---|---|---|---|
|
Chatwoot Open source customer engagement — chat, email, social inboxes. |
The most Intercom-like open source experience today. | MIT | ★★★☆☆ | Yes |
|
Zammad Ticketing system with email, chat, and telephony. |
When your support is email + telephony rather than live chat. | AGPL-3.0 | ★★★☆☆ | Yes |
1. Chatwoot — The most Intercom-like open source experience today.
Open source customer engagement — chat, email, social inboxes.
Strengths
- Multi-channel inbox — web chat, email, Facebook, WhatsApp.
- Modern UI and mobile apps.
- Active development with frequent releases.
Weaknesses
- Self-hosting requires several services (DB, Redis, Sidekiq).
- Integrations with third-party tools still growing.
- Some features are gated in hosted "Enterprise" tier.
Chatwoot homepage · Source on GitHub · Intercom vs Chatwoot →
2. Zammad — When your support is email + telephony rather than live chat.
Ticketing system with email, chat, and telephony.
Strengths
- Strong email-first ticketing.
- Integrations with LDAP, telephony, monitoring.
- Detailed SLAs and reporting.
Weaknesses
- UI complexity can intimidate new agents.
- Docker setup is heavy on resources.
- Smaller app marketplace than Zendesk.
Not what you're looking for?
Browse other tools in Helpdesk & Support, or check out open source projects by category on the full category index.
Recommended reading
When self-hosting goes wrong: seven failure modes and how to avoid them
An honest retrospective on the ways self-hosted setups break — not in theory, but in practice — and the small habits that prevent most of them.
Will the open source project you depend on still exist in three years?
Bus factor, maintainer burnout, funding models, and the signals that separate OSS projects that survive from those that quietly decay.
From SaaS to self-hosted: a 30-day migration playbook
A week-by-week plan to move one service off SaaS and onto your own server without breaking your team's workflow.