Transparent Chatwoot alternative matrix
| Option | Hosting | Strongest fit | Cost context |
|---|
| Chatwoot Community Edition | Self-hosted | Technical teams needing source access or data control | No licence fee; infrastructure, upgrades, backups and incident ownership remain yours |
| Chatwoot Cloud | Managed | Teams that want Chatwoot without operations | Published per-agent plans; verify the current official pricing |
| Tenreply | Managed | WhatsApp-led teams needing inbox, CRM, templates and automation together | Free during beta; paid launch plans will be announced in advance |
| respond.io | Managed | Larger teams with complex routing | Subscription plus channel costs; verify current vendor pricing |
| Traditional helpdesk | Managed | Email-first enterprise support | Usually per-agent with WhatsApp/channel add-ons |
For the real self-hosting surface area, review Chatwoot's official deployment documentation, not only the licence price.
A low-risk migration path
- Export contacts, conversation history and the current automation inventory.
- Connect channels in a staging workspace and rebuild only the flows still in use.
- Resubmit WhatsApp templates before moving the number.
- Run agent acceptance tests for assignment, notes, files and reporting.
- Cut over during a quiet window, verify inbound and outbound messages, then keep the old export read-only.
Why Teams Look at Chatwoot
Chatwoot is the best-known open-source customer messaging platform: a shared inbox across WhatsApp, web chat, email, Instagram and more, self-hostable, with an active community. The appeal is straightforward — no per-seat pricing, your data on your infrastructure, and the source code available to modify.
Teams then look for alternatives for equally straightforward reasons: self-hosting has an ongoing cost that does not appear on any pricing page, and the WhatsApp side in particular involves work the open-source project cannot do for you.
The Honest Cost of Self-Hosting
"Free" here means free of licence fees. The real budget line items:
- Infrastructure. A production deployment needs an application server, Postgres, Redis, object storage and a background worker. Typically current infrastructure charges for the chosen region and capacity for a small team, more when you add redundancy.
- Someone who owns it. Upgrades, database migrations, TLS renewal, backup verification, disk monitoring. A few hours a month when things are calm, an urgent afternoon when they are not.
- Availability is now yours. If the inbox is down at 11am on a Monday, that is your incident. Hosted platforms absorb this.
- WhatsApp API setup is still on you. This is the part teams underestimate most — see below.
Compare against per-seat pricing honestly: at three agents, self-hosting rarely wins on total cost once you price the maintenance time. At thirty agents on a per-seat plan, it very well might.
The WhatsApp Complication
Open-source inboxes give you the inbox. They do not give you WhatsApp Business API access, because Meta does not grant that to software — it grants it to a business through a Business Solution Provider, or directly via Cloud API with your own Meta app.
Self-hosting therefore means you also handle Meta Business verification, WhatsApp Business Account setup, template submission and approval, number registration, quality-rating monitoring, and pricing changes on Meta's side. Our guides on API requirements and approval and what a BSP actually does cover what that involves.
A related trap: some self-hosted WhatsApp tools connect through WhatsApp Web automation rather than the official API. These are cheap and genuinely risky — Meta bans numbers for it. We wrote about why WhatsApp Web-based tools put your number at risk. Evolution-API and WAHA fall in this category and should not be used for a number your business depends on.
The Alternatives
Open source, self-hosted
Chatwoot — the most complete option. Multi-channel, mature, good documentation, real community. Best choice if you are committed to self-hosting and have someone to own it.
Zammad / FreeScout — helpdesk-first rather than chat-first. Strong on email ticketing, weaker on live messaging channels. Better if your volume is mostly email with chat as a secondary.
Evolution-API / WAHA — WhatsApp gateways, not inboxes, and unofficial. Free, technical, and a genuine account risk. Avoid for production business numbers.
Hosted, no infrastructure to run
Tenreply — omnichannel inbox across WhatsApp Business API, Instagram, Messenger and web chat, with automation flows, deal-pipeline CRM, broadcasts, analytics and a REST API. Connects through Meta's official Cloud API, so the API access and template handling come with it rather than being your project.
On pricing: the whole platform is free while Tenreply is in beta, with unlimited seats and no card. That is beta pricing, not a permanent free tier — future plans and pricing will be announced with advance notice. For teams evaluating against self-hosting, the useful comparison is that during beta you are trading nothing, and after launch you will be trading a subscription against your infrastructure and maintenance cost.
respond.io — strong omnichannel routing and workflow depth, from a current vendor quote. Good fit for larger teams with real routing complexity.
Wati / AiSensy / Interakt — WhatsApp-focused, India-strong, seat and conversation limits on lower tiers. See the four-way comparison.
Intercom / Zendesk — enterprise support suites. Far more product than most small teams need, priced accordingly, with WhatsApp as one channel among many.
When Self-Hosting Genuinely Wins
Not a rhetorical section — there are real cases:
- Data residency or regulatory constraints that require conversation data on infrastructure you control.
- Large agent counts where per-seat pricing becomes the dominant cost.
- Deep customisation — you need to modify inbox behaviour, not just configure it.
- You already run infrastructure. If you have a platform team and a Kubernetes cluster, the marginal cost is much lower than the numbers above.
If two or more of those apply, Chatwoot is probably the right answer and this article should not talk you out of it.
When Hosted Wins
- Under about ten agents, with nobody whose job includes infrastructure
- WhatsApp is your primary channel and you do not want to own Meta approvals and template operations
- You need it working this week
- Uptime matters more to you than control
Frequently Asked Questions
Is Chatwoot really free?
The community edition is free to licence and self-host. You pay in infrastructure and maintenance time, and Chatwoot also offers a paid cloud version. Its enterprise features are separately licensed.
Can I use Chatwoot with the official WhatsApp Business API?
Yes — it supports WhatsApp Cloud API. You still need your own Meta app, Business verification and template approvals, and you own quality-rating monitoring.
Is a self-hosted WhatsApp gateway safe?
Unofficial gateways that drive WhatsApp Web are not safe for a business-critical number. Meta actively bans them. Use the official Cloud API, whether self-hosted or through a provider.
What is the real monthly cost of self-hosting for a five-agent team?
Budget current infrastructure charges plus a few hours of technical time. The time is the part that surprises people, and it is not optional — an unpatched inbox holding customer conversations is a liability.
Can I migrate off a hosted platform later?
Check export before you commit, not after. Contacts and conversation history should be exportable. Automation flows generally are not portable between platforms, so expect to rebuild those.
Decide on Ownership, Not on the Word "Free"
The choice is not free versus paid — it is which costs you would rather carry. If you want to own the stack and have the capacity, Chatwoot is excellent. If you would rather own the customer conversations and not the Postgres upgrades, try a hosted inbox and spend the time on customers instead.
