Customer support decision
Chatwoot Cloud
A technically capable engineer can build a narrow replacement (widget + inbox + OpenAI reply suggestions) in a few months, but replicating Chatwoot Cloud’s enterprise compliance, broad official channel integrations, and managed scaling is not realistic without significant investment.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
Code Chatwoot Cloud publishes itself
Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
What a replacement has to do
- Receive messages from a website widget or channel → persist conversation → surface in an agent inbox UI → generate reply suggestions via an LLM → send reply back to the user
What it still won’t have
- Enterprise compliance (SOC 2 Type II) and associated attestation
- Official, production-grade multi-channel integrations (WhatsApp official, full social channels)
- Scale, SLA, and managed cloud operations
- Built-in Captain AI credits/managed AI billing and native voice/phone features
- Vendor support, refunds, and account management
What remains hard
- Compliance and regulation
SOC 2 Type II compliant
- Brand trust
Trusted by 15,000+ businesses
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 4 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal hosted customer-support product using React for the agent UI, a lightweight embeddable JS chat widget, Node.js (Express) for the API, Postgres for persistence, Redis for realtime presence and job queue, and Docker for deployment on AWS ECS or EC2. In scope: embedable website chat widget, REST/WebSocket ingestion, Postgres schema for conversations/messages/agents, React inbox with conversation list and message composer, IMAP/SMTP email channel integration, an LLM-based reply-suggestion endpoint using OpenAI API (configurable API key), Docker Compose/ECS deployment manifests, basic auth for agents, metrics and health endpoints. Out of scope: SOC 2 attestation, official WhatsApp Business API integration, multi-tenant billing, advanced analytics, phone/voice calls. Deliverables must include retry/backoff and validation for external APIs, unit and integration tests for core components, Dockerfiles and a deploy guide for AWS, and automated DB migration scripts.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Hard moats found in the evidence-3
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productChatwoot official product page
- official pricingChatwoot pricing
- official docsChatwoot features
- open sourcepapercups-io/papercups
- open sourcechatwoot/chatwoot
Integrity checks
What held up, and what did not.
