Self-hosted Intercom alternative: own the customer inbox with Chatwoot

Every support conversation your business has ever had is a record — of what customers struggle with, what they ask for, and what they were promised. Intercom and Zendesk are happy to hold that record for you, and to bill you per seat for the privilege of reading it back. Add an agent, pay again. Want a chat widget that doesn't wear someone else's logo, or a clean export of your own history? That's usually a higher tier. Chatwoot is the shared inbox and live-chat widget you actually own, running on hardware you control.

What Chatwoot is

Chatwoot is a full customer-engagement platform — an omnichannel support desk, not a stripped-down chat box. It pulls email, a website live-chat widget, WhatsApp, Instagram, Facebook Messenger, Telegram, SMS, and a generic API channel into one shared inbox, where a whole team triages, assigns, and replies. The open-source Community Edition is the real product: agents, teams, automations, a help center, satisfaction surveys, and reporting all ship in the box, not dangled behind a "contact sales" wall. Where Intercom meters you on resolutions and Zendesk stacks its features across a ladder of pricing tiers, Chatwoot hands you the whole platform and lets your bill scale with your server, not your headcount. Under the hood it's a Ruby on Rails application that plenty of teams run at real volume — the same tool, just pointed at your own domain.

The features that actually matter

• One omnichannel shared inbox. Email, live chat, WhatsApp, Instagram, Messenger, Telegram, SMS, and an API channel all land in the same place. Conversations carry a status — open, pending, snoozed, resolved — so nothing quietly falls through.
• An embeddable live-chat widget. Drop one script tag on your site and you have live chat with your own colors, position, and greeting — no "powered by" badge. Proactive campaigns can trigger a message based on the page a visitor is on.
• Real team collaboration. Private notes, @mentions, and agent collision detection — you can see when a teammate is already viewing or replying — plus assignment to specific agents or whole teams.
• Canned responses and macros. Saved replies fire from a keyboard shortcut, and macros run a multi-step sequence — label, assign, reply, resolve — in a single click.
• Automation, labels, and custom attributes. Rule-based routing and auto-assignment on new or updated conversations, labels for organizing, and custom attributes to store whatever your business actually cares about.
• A contact record for every customer. Chatwoot keeps a profile for each contact — their past conversations, custom attributes, and internal notes — so context travels with the person instead of living in one agent's head. It's a lightweight CRM you didn't have to bolt on.
• CSAT surveys and reports. Send a satisfaction rating after resolution and read overview, agent, inbox, label, and CSAT reports on the built-in dashboards. Both Intercom and Zendesk tend to gate this kind of surveying and analytics behind their pricier plans.
• A built-in Help Center. Publish a public knowledge-base portal on your own domain and deflect the repeat questions — a second subscription you no longer pay for.

Why self-host it instead of the hosted version

Three reasons, and they compound.

Your data stays yours. Every transcript, email address, and phone number lives in a PostgreSQL database on a machine you control. You can query it, export it, and be certain no third party is mining conversations or feeding them into a model. For anyone with a compliance story to tell, that's the difference between an answer and a shrug.

The cost doesn't scale per seat. Per-agent pricing punishes exactly the thing you want — growth. Chatwoot is free software; the twentieth agent costs the same as the first, which is nothing. You pay for the compute it runs on, and that's a flat, predictable line, not a number that climbs every time you hire.

You control the whole surface. Your domain, your widget styling, your Help Center branding, no vendor badge. The API and webhooks are open, so Chatwoot becomes a component you build around rather than a walled garden you rent a view into.

Who it's for

• Small support teams graduating from a shared Gmail. You've outgrown forwarding rules and "did anyone reply to this?" but a per-seat SaaS feels like a tax on the whole team getting involved.
• Agencies and MSPs. Run support for clients who want their own branded widget and their own isolated data, without paying a platform fee for every client account you spin up.
• Privacy-sensitive organizations. Healthcare, legal, education, or any EU/GDPR-bound team that simply cannot hand raw customer transcripts to a US SaaS with an opaque data policy.

The honest setup notes

We'll be straight with you: Chatwoot is a small stack, not a single binary. It's a Rails app with Sidekiq background workers, and it wants a PostgreSQL database and a Redis instance running alongside it. It also likes memory — plan for a couple of gigabytes, not a 256MB box. The email channel and outbound notifications need working SMTP, which in practice means DNS records, SPF and DKIM, and a relay reputable enough not to get you spam-filtered. Updates arrive as new Docker images and frequently carry database migrations that have to run in order. And you'll want regular backups of Postgres and the attachment storage, because a lost volume takes your conversation history with it. None of this is hard, exactly — it's just real operational work that doesn't end on install day. Or let us run it.

Deploy it in one click

Rolling your own means provisioning Postgres and Redis, wiring up Sidekiq, sorting out SMTP, setting environment variables you'll have to look up, and owning every migration and backup from then on. On Caliber Node, it's one click: deploy Chatwoot in one click and we stand up the database, the Redis instance, and the background workers for you. Outbound mail routes through our managed relay, so the email channel and notifications just work without you fighting DNS on day one. Updates and backups are handled, and you still get real logs, SFTP into the container, and a full export of your data whenever you want it. You get the Chatwoot you own, without the plumbing.

First run

1. Open your new Chatwoot URL and create the first account — that user becomes the super admin for the install.
2. Create an inbox: choose Website, give it your site's name and domain, and style the widget's color, position, and greeting.
3. Copy the generated widget script and paste it just before the closing `</body>` tag on your website.
4. Invite an agent (or just add yourself), set your business hours, and write a canned response or two so replies are fast from the start.
5. Open your own site in another tab, start a chat as a visitor, and watch it land in the dashboard — then reply, and resolve it. That's your first conversation.

The bigger picture

Support is where you meet customers on their hardest day, and the archive of those conversations is one of the most sensitive and valuable things your business owns. It's worth thinking hard about who holds it, who can read it, and what it costs you every time your team grows. Renting that inbox by the seat made sense when standing one up was a project. It isn't anymore, and it hasn't been for a while. Owning the tool your customers talk to you through is the same move as owning your email or your website — quietly foundational, and yours to keep no matter how big the team gets.

Deploy Chatwoot in a few minutes → https://calibernode.com/cloud-apps

Or browse the full app catalog to see what else you can own.

One-click self-hosted apps, managed for you — real logs, SFTP, and your data always exportable. Never a black box.