The REST endpoints are the easy part. Buyers get Meta onboarding handled, multi-tenant infrastructure, durable event delivery, Flows plumbing, and someone absorbing API and policy changes — a reasonable DIY gateway is one business; a provider is a company.
REPLACEMENT BRIEF
dev tools
Can AI replace Wabery?
EDITORIAL ANSWERKINDACurated prompt
Send, receive, verify webhooks, retry — one-shottable for a single business on Meta's WhatsApp Cloud API. What cannot be one-shot is why managed providers exist: production messaging needs monitoring, security, and compliance, and onboarding other businesses requires Meta verification, app review, and Tech Provider approval. Build for your own verified number; matching Wabery means becoming an approved provider, which is a company, not a weekend.
For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.
Build the personal version →AT A GLANCE
- price
- $15/mo
- listed annual price
- $180/yr
- replaceable scope
- For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.
- build time
- multi-day
Build promptreviewed prompt · not run
the prompt
Curated promptBuild 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.
Copy or open in an agent
The prompt stays readable first. Choose a launch option when you are ready.
$ open in your agent (prompt prefilled, you press enter) or copy it raw
what AI can build
For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.
The prompt was editor-reviewed; no completed build is recorded.
The honest tradeoff
why people still pay
what you lose
xMeta Business Partner status and approved Tech Provider onboarding path
xturnkey onboarding for multiple customer businesses and phone numbers
xmanaged queues, retries, monitoring, security, and production reliability
xWhatsApp Flows builder, encryption, and data-exchange hosting
xhosted functions, MCP tooling, and a production team inbox
Start with existing software
prior art · use these instead of building, if you'd rather
EVIDENCE LEDGER
What this page can prove
The verdict judges replaceability. The evidence level records what DeepFeather actually checked.
evidence level
Curated promptThe prompt was editor-reviewed; no completed build is recorded.
125K messages · monthly capacity
known limits · Meta Business Partner status and approved Tech Provider onboarding path; turnkey onboarding for multiple customer businesses and phone numbers
BUILD FEEDBACK
Did you try this build?
Report the outcome. Submissions enter a manual evidence queue and never auto-upgrade the verdict.
related verdicts
Want next week’s replacements?
New verdicts + most-wanted, weekly. Free. One-click out.
Share this verdict
questions
Can AI replace Wabery?
Possibly for a narrower core workflow, but this catalog judgment is not a verified build. Expected gaps include: Meta Business Partner status and approved Tech Provider onboarding path, turnkey onboarding for multiple customer businesses and phone numbers. Validate the prompt against your own acceptance criteria before committing.
How much does Wabery cost?
Wabery is listed at about $15/month (125K messages, checked 2026-07-30), or $180 per year. This is a pricing reference, not evidence of a completed replacement or realized savings.
What do I lose by replacing Wabery?
Honestly: 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. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Wabery?
Yes — Meta WhatsApp Cloud API (The official API is the shortest DIY path for a single business that can complete Meta's setup and verification.). Using prior art is also a valid exit; the prompt is for when you want it exactly your way.