English
Chatwoot Hosting
Handle customer conversations from email, live chat, and social channels in one shared inbox.
No setup fees-
One click deploy -
4 GB RAM Memory needed -
50 GB Disk Space Needed -
From 10 € Price
Official links
Chatwoot’s official links and original website
Chatwoot Website
More
Tech
- Docker image
- chatwoot/chatwoot:latest
- Default port
- 3000
- Database
- postgres
How Chatwoot works
Chatwoot receives conversations from configured inboxes and displays them to agents in one browser workspace. A website widget can start a live conversation, while supported external channels connect through their own provider credentials and configuration. Contacts, messages, notes, assignments, teams, labels, and statuses preserve the service history around each customer.
Automation rules can route or update conversations, and canned responses help agents handle recurring questions consistently. Reports show activity and performance across inboxes or agents. The catalogue stack includes PostgreSQL, Redis, a web service, and a background worker, with account signup disabled and an administrator account prepared during deployment.
Key Chatwoot features
A shared inbox gives agents visibility into active and resolved conversations. Assignments and teams make ownership explicit, while private notes allow internal collaboration. Labels, filters, contact attributes, and conversation status help organise a growing support queue.
The website widget is the most direct channel in this catalogue configuration. Other channels require separate accounts, tokens, webhooks, or provider approval. Email functions are disabled at the application level, so an email inbox, outbound email, invitations, mail notifications, and email-based account recovery are not available.
Chatwoot vs Intercom
Chatwoot is a self-hosted customer-conversation platform with live chat, contacts, inboxes, agent collaboration, automation, and reports. Intercom is a vendor-managed customer-service platform combining AI agents, messaging, an inbox, help-centre content, proactive support, automation, reporting, and commercial integrations.
Intercom may suit organisations that want a provider-operated service, AI products, and a broad commercial support ecosystem without managing infrastructure. Chatwoot is attractive when the requirement is an operator-controlled conversation workspace and the team is prepared to configure channels and understand which third-party services remain separate.
Who uses Chatwoot
Support teams use Chatwoot to answer website visitors and retain conversation history. Sales groups can handle pre-sales questions through the widget, while online services organise contacts and route inbound conversations among agents.
The platform does not make every channel available automatically. Teams need to choose supported providers, obtain credentials, configure callbacks, define ownership, and test message delivery. In this deployment, a workflow that depends on application email is unavailable, so the live-chat and separately configured external-channel use cases should be evaluated first.
Self-hosting Chatwoot: requirements and cost
Load grows with agents, contacts, conversations, messages, attachments, active widgets, automation, reports, integrations, WebSocket activity, and background jobs. PostgreSQL stores primary records and Redis supports queues and real-time work. AvaHost includes PostgreSQL but leaves it unmanaged, with its memory outside the exported application minimum.
The database-adjusted recommendation is Plan 4 at €20. The Chatwoot deployment includes one-click setup, support-domain HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so email inboxes, outbound messages, invitations, mail notifications, and password recovery are unavailable. External messaging channels are not bundled and require their own provider accounts and credentials.
F.A.Q
Chatwoot starts at €20 on Plan 4 after allowing capacity for PostgreSQL beside the 4096 MB application minimum. Agents, contacts, conversations, messages, attachments, active widgets, automation, reports, external channels, Redis queues, and worker activity shape demand. Teams should test the actual channel mix and peak concurrency before relying on an initial estimate.
AvaHost provisions PostgreSQL, Redis, the Chatwoot web application, and a background worker. PostgreSQL is included but unmanaged. Contacts, conversations, messages, account settings, and other records depend on the database, while queued jobs depend on Redis and the worker. Plan updates, secrets, persistent files, and recovery across the complete stack together.
A custom hostname can serve Chatwoot with automated HTTPS after its DNS records point to AvaHost. Use the final URL when embedding the website widget or configuring provider callbacks. After changing it, verify agent sign-in, widget loading, WebSocket connections, webhooks, channel callbacks, links, and integrations that may still reference the previous address.
The website widget can be configured from the hosted application. External messaging channels require separate provider accounts, credentials, approvals, and callbacks, and none is bundled with the plan. Application email is disabled, so email inboxes, outbound email, invitations, mail notifications, and password recovery do not work in this configuration.