I Measured What Self-Hosted Chatwoot Actually Uses

Описание и применение

Один VPS с 4 ГБ ОЗУ может запустить самодостаточный Chatwoot с 34 пользователями и 348 703 сообщениями, потребляя лишь 1,8 ГБ памяти; нагрузка зависит от объёма сообщений, а не от количества пользователей. Самостоятельный хостинг оправдан при наличии операционной поддержки, иначе лучше использовать облачную версию.

Задача

Clients need realistic resource estimates for self‑hosted Chatwoot, but pricing articles only list tier numbers without showing actual usage.

Результат

A single 4 GB VPS can comfortably run a self‑hosted Chatwoot instance with 34 seats and 348,703 messages using only 1.8 GB RAM; resource usage is driven by message volume, not seat count. Self‑hosting is viable if ops capacity exists; otherwise Cloud is cheaper due to reduced operational overhead.

Рабочий процесс

• Set up a single‑box Docker deployment of Chatwoot (rails, postgres, sidekiq, redis).
• Run docker stats during steady state to capture container memory usage.
• Record disk usage of Postgres (997 MB) and total system usage (20 GB of 38 GB).
• Calculate message volume per seat and per inbox.
• Compare retention limits on Chatwoot Cloud tiers to actual conversation history length.
• Publish findings on personal blog for transparency.
• Provide guidance on when self‑hosting is cost‑effective versus Cloud.
• Offer affiliate code for Cloud discounts.
• Document operational challenges encountered (connection‑pool exhaustion, Redis eviction, log rotation, upgrade issues).

Доказательства

348,703 messages across 20 inboxes fit inside about 1.8 GB of RAM.

Источник

The whole box sits at 20 GB of 38 GB used and 2.4 GB of 3.7 GB RAM — and that box hosts other things too.

Источник

Adding an agent to a self-hosted install costs nothing. On Cloud, every seat is another line on the bill, every month, for as long as you have it.

Источник