Automation and integrations decision
Bouncer
You can build a narrow team inbox and automation ruleset yourself in a few weeks, but full WhatsApp onboarding, deliverability, compliance, and enterprise-grade features make keeping the hosted product reasonable for production teams.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off120 h to build
$50/mo6 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Receive inbound WhatsApp messages → persist messages → display in team inbox UI → route/assign to agents → send templated or rule-driven replies via WhatsApp API.
What it still won’t have
- Business verification, official Meta/WhatsApp-managed inbox onboarding and deliverability guarantees
- Any proprietary analytics, reporting, and built-in team features of the hosted product
- Vendor SLAs, hosted scaling, and product support
- Prebuilt templates and template-approval workflow integrated with Meta (if provided by vendor)
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Bouncer does not publish a price we could read, so there is nothing to compare against. What building costs is below.
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 WhatsApp team inbox and automation service using Node.js (Express) backend, Postgres database, React frontend, and Twilio WhatsApp (or Meta WhatsApp Cloud API) as the messaging provider. Core features in scope: webhook receiver to persist inbound messages; Postgres schema for threads/messages/users; REST APIs for thread listing and message sending; React inbox with thread view, assignment, message composer, basic search; routing rules allowing templated auto-replies and agent assignment; user auth with simple RBAC; real-time thread updates via WebSocket; basic daily analytics (message counts). Out of scope: handling Meta business verification process, enterprise deliverability optimization, multi-region scaling, and advanced analytics. Include input validation, robust error handling, unit and integration tests for API endpoints, and Docker Compose for local dev and a deployment guide to a single VPS or managed host.
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
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 →Integrity checks
What held up, and what did not.
