Can AI replace Wabery?
The core loop (send, receive, verify webhooks, retry, inspect conversations) is one-shottable for a single business using Meta's WhatsApp Cloud API. What you cannot one-shot is the reason managed WhatsApp providers exist as products: production messaging infrastructure must stay reliable, secure, monitored, and compliant, while onboarding other businesses requires Meta business verification, app review, and approval for the relevant Tech Provider and Meta Business Partner capabilities. The honest DIY move is to build for your own verified WhatsApp Business Account and phone number; matching Wabery as a multi-tenant provider means operating that infrastructure and completing Meta's approval process.
01What it costs
Checked Aug 14, 2026 · source: wabery.com.
| Plan | Monthly | Billed yearly | What you get |
|---|---|---|---|
| Free | Free | Free | 500 messages/month; all product features. |
| 125K messages | $15 | — | 125,000 messages/month; all product features. |
| 600K messages | — | — | 600,000 messages/month; all product features. |
| 3.5M+ messages | — | — | 3,500,000+ messages/month; all product features. |
Hidden costs: Meta's WhatsApp conversation/message charges are billed directly to the connected WhatsApp Business Account and are not included; AI-model tokens are also separate.
02Could AI build it for you?
The core job: For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.
What a working version needs:
- Meta Developer account and WhatsApp Cloud API access
- verified business, WhatsApp Business Account, and phone number
- always-on HTTPS server
- PostgreSQL
- monitoring and backups
The API is vibe-codeable. Becoming an approved, reliable provider is not.
03What you'd give up
- Meta Business Partner status and approved Tech Provider onboarding path
- turnkey onboarding for multiple customer businesses and phone numbers
- managed queues, retries, monitoring, security, and production reliability
- WhatsApp Flows builder, encryption, and data-exchange hosting
- hosted functions, MCP tooling, and a production team inbox
The REST endpoints are the easy part. Wabery packages Meta onboarding, secure multi-tenant infrastructure, durable event delivery, Flows plumbing, monitoring, and ongoing API and policy changes into a service that is ready for production. A DIY gateway is reasonable for one business; becoming an approved and reliable provider for other businesses is a company, not a weekend project.
04Free and cheaper alternatives
The missing inbox, flow builder and API for Meta's Cloud API; Meta still sends the bill.
whatomate.io →05The build prompt
Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.
Build me a single-business WhatsApp API gateway to replace Wabery for my own company. Requirements: - Node 22 + TypeScript + Fastify + PostgreSQL; Docker Compose behind Caddy HTTPS on my always-on VPS. - One Meta WhatsApp Business Account and phone number only. Keep the Cloud API access token, app secret, verify token, and phone number ID in .env. - An authenticated REST API to send text, template, and media messages. Accept an Idempotency-Key and return both the local record and Meta message ID. - Implement Meta webhook verification and verify POST signatures with the app secret. Persist each event before responding, deduplicate it, and normalize inbound messages, delivery statuses, and errors into PostgreSQL. - Use pg-boss for outbound jobs with three retries and exponential backoff. Failed jobs go to a dead-letter view and can be replayed manually. - Forward normalized events to one configured webhook, signed with HMAC. Store every attempt, response status, and next retry time. - A small admin inbox behind one ADMIN_TOKEN: conversations, message status, failed jobs, webhook health, and a reply box. No public user accounts. - Add health/readiness endpoints, structured logs, migrations, rate limits, daily database backups, and tests for signatures, deduplication, and retries. - No telemetry beyond calls to Meta. Secrets must never be logged or committed. - Out of scope: multi-tenant customer onboarding, Embedded Signup, billing, Meta Business Partner or Tech Provider status, WhatsApp Flows tooling, hosted functions, MCP, and production SLAs. Those require infrastructure and Meta review or approval beyond what code can provide. - README: exact Meta app, WABA, number, webhook, and template setup; business verification caveats; deployment, backup restore, and secret rotation.
06Open-source starting points
- Meta WhatsApp Cloud API: The official API is the shortest DIY path for a single business that can complete Meta's setup and verification.
App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.
Get new verdicts in your inbox.
One short email when new verdicts land: what AI can now do for you, and what it still gets wrong. No spam. Unsubscribe anytime.