Chatwoot self-hosting: the real tradeoffs

Chatwoot comes up in almost every "open source Intercom alternative" search, and for good reason: it is a real, Docker-deployable helpdesk with a genuinely useful free tier. But "free" is doing a lot of work in that sentence. Chatwoot Community Edition costs nothing to license and everything to run. This post is not a roundup. It is a decision guide for the specific question a technical founder actually has to answer: should we self-host Chatwoot, or should we pay someone else to own the infrastructure. We will be honest about both sides, including where HelpYap fits and where it does not.

What do you actually get with Chatwoot Community Edition?

Community Edition is the self-hosted version of Chatwoot: free forever, source available, and deployable on your own servers via Docker. It gives you a shared inbox, a website widget, canned responses, and the core helpdesk workflow, but it ships without Captain, Chatwoot's AI agent, and without SSO.

That last part matters more than it looks at first glance. A lot of the reason teams go looking for a helpdesk in 2026 is the AI agent, not the ticket list. Community Edition gives you the ticket list. The AI and the enterprise login are both gated behind Chatwoot's paid tiers, which changes the actual comparison you are making: it is not "free helpdesk vs. paid helpdesk," it is "free helpdesk with no AI vs. paid helpdesk with AI."

What does Chatwoot Cloud cost, and what does it include?

Chatwoot Cloud is $19 per agent per month billed annually, and it includes 300 Captain AI credits. That is the same headline number as HelpYap's entry seat price, which makes the two products worth comparing directly rather than treating self-hosting as the only Chatwoot option.

If you are already leaning toward paying for Chatwoot Cloud, the self-hosting question mostly disappears: you are buying a hosted product either way, and the choice becomes which hosted product fits better. The self-hosting question only really matters for the segment of readers who are seriously weighing "run this ourselves for free" against any paid option at all. That is who the rest of this post is for.

When does self-hosting Chatwoot genuinely make sense?

For a real subset of teams, self-hosting is the correct call, not a compromise. Four situations stand out.

• Strict data residency requirements.If your customer conversations legally have to sit in a specific country, a specific data center, or entirely off a vendor's cloud, then running Chatwoot on infrastructure you control settles the question outright. No amount of vendor compliance paperwork replaces physical control when the requirement is that specific.
• An existing platform or DevOps team. If you already run Postgres, Redis, and containerized services in production, and someone on staff owns patching and on-call for them today, Chatwoot is one more service in a stack you already operate. The marginal cost of adding it is much lower than it would be for a two-person team standing up that stack from scratch.
• A genuine zero-budget constraint. A side project, an early-stage tool with no support volume yet, or a nonprofit with no line item for software: Community Edition on a small VPS running the Docker stack is a real, working helpdesk for the cost of a cheap server.
• Full control over the code. Teams that want to fork the product, add a custom channel integration, or embed Chatwoot inside a larger internal tool get a degree of control no hosted product offers, paid or not.

If two or more of those describe your team, self-hosting is not a risk you are taking on, it is the right infrastructure decision. The rest of this post is aimed at everyone else: teams that do not have strict residency requirements, do not already run a platform team, have some budget, and mainly want a helpdesk with a working AI agent, not a new infrastructure project.

What does self-hosting actually cost, beyond the server bill?

The VPS or EC2 instance is the smallest number in the equation. The real cost is everything that keeps that instance a production service instead of a demo, and it does not show up on an invoice because it shows up as someone's time.

Upgrades are the recurring one: Chatwoot ships new releases regularly, and staying current means testing and applying database migrations against your own instance, on your own schedule, with no one else responsible if a migration goes sideways. Postgres and Redis need their own operational care: backups that are actually tested by restoring them, connection pooling and memory tuning as conversation volume grows, and monitoring so you find out about a problem before a customer does. Email deliverability is its own quiet project: SPF, DKIM, and DMARC records have to be configured correctly and kept correct, or support replies start landing in spam and you find out from an angry customer, not a dashboard. Security patching for the OS, the container images, and Chatwoot itself is ongoing and unglamorous work that is easy to defer until it is overdue. None of this is exotic. It is exactly the kind of maintenance any self-hosted production service requires, and it is precisely the kind of maintenance a team without spare DevOps capacity underestimates going in.

Can you get a working AI agent without paying for Captain anyway?

Not really. Captain, Chatwoot's AI agent, is gated to paid tiers whether you self-host or not. Running Community Edition does not unlock a free AI agent, it unlocks a helpdesk with no AI agent at all.

That is the detail that changes the math for a lot of teams evaluating self-hosting specifically to save money. If the actual goal is "free helpdesk," Community Edition delivers it. If the goal is "free AI-powered helpdesk," it does not exist in Chatwoot's pricing structure: you either pay for Captain on top of your own infrastructure, or you build your own retrieval and response pipeline from scratch, which is a second full engineering project layered on top of the first one. Self-hosting avoids a software license fee. It does not avoid the cost of AI, because Chatwoot never offered AI for free in the first place.

What happens when something breaks and you need vendor support?

With Community Edition, there is no support line. Community forums, GitHub issues, and your own read of the source code are the troubleshooting path when a migration fails at 2am or a queue worker stops picking up jobs during a traffic spike. That is a fine tradeoff for a team that already debugs its own infrastructure issues as a matter of course. It is a rough one for a team that expected a support tool to reduce how much of their week goes to keeping software running, not add to it.

This is really the crux of the self-hosting decision, more than the dollar figure on the server bill: are you willing, and staffed, to be your own support team for your support software.

How does HelpYap compare for teams that want the AI without owning the ops?

HelpYap exists for the teams on the other side of that question: the ones who want an AI agent that actually answers from their documentation, without taking on Postgres tuning, backup testing, and SPF records as a second job. Every plan is fully hosted and AWS-managed: RDS Postgres, ECS Fargate, S3 and CloudFront. There is no server to patch, because there is no server for you to see.

The pricing shape mirrors the honest comparison from earlier in this post. Starter is $19 per seat per month, in the same range as Chatwoot Cloud, with 300 AI conversations included per seat on the AI agent and no separate AI line item to track. Pro is $49 per seat with 1,000 AI conversations per seat, agent tools, Conversation Memory, and two-way Slack. Business is $89 per seat, unlimited seats, 2,500 AI conversations per seat, an Opus add-on at $0.10 per conversation for the hardest questions, all 7 channels, and the Learning Loop that improves answers from negative ratings over time. The same knowledge base that Chatwoot would need Captain to search sits underneath every plan, and the team inbox handles the human side when the AI escalates. Every plan starts with a 7-day free trial, no credit card required.

On security, the pitch is the same one a self-hosted setup has to build by hand: secrets encrypted with AES-256-GCM, SSRF and DNS-rebinding defenses on outbound requests, an RDS database encrypted in isolated subnets, Cognito-backed auth, and application secrets stored in AWS Secrets Manager rather than a config file on a box. The honest limitation: HelpYap does not run on your infrastructure, so if data residency on hardware you physically control is a hard requirement, this is not the product for that requirement, and Chatwoot self-hosted (or another self-hosted tool) remains the right answer.

So who should actually self-host Chatwoot?

Run through it plainly. Self-host Community Edition if you have a strict data residency requirement, an existing team that already operates Postgres and Redis in production, a genuine zero budget, or a need to fork and control the code, and you are comfortable being your own support line when something breaks. Pay for a hosted product, Chatwoot Cloud or HelpYap, if you want a working AI agent without also becoming its infrastructure team, if nobody on staff currently owns database operations, or if the value of your time this quarter is better spent on your actual product than on upgrade scripts and SPF records.

Neither answer is the wrong one. It depends entirely on whether the DevOps capacity self-hosting requires already exists on your team or would have to be built for the occasion. We wrote more generally about what a small team should weigh when picking any AI support setup in AI customer support for small teams, which covers the same decision from the buyer's side rather than the ops side.

The bottom line

Chatwoot Community Edition is free in license, not in labor: it is a genuinely good self-hosted helpdesk for teams with data residency requirements, existing platform capacity, a zero-dollar budget, or a need for full code control, and a quietly expensive second project for everyone else once upgrades, database operations, email deliverability, backups, and security patching are counted honestly, especially since even self-hosting does not get you Captain's AI agent for free. If you recognize your team in the first group, self-host it and do it properly. If you recognize your team in the second, that is exactly the gap HelpYap is built to close: a fully hosted AI support platform, one price per seat starting at $19, with the AI agent, the knowledge base, and the infrastructure already run for you. Compare the full plan matrix on pricing and try it against your own documentation during the 7-day trial before you commit either way.