[verdict][curated prompt][source: wabery.com]
Can I vibecode Wabery?
// buildable in a weekend, but real gaps stay open
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.
confidence: high
what it is: WhatsApp API infrastructure for AI agents, automations, Flows, webhooks, and inboxes
Buildability index · an editorial game
- Price from 15 $ · usage-based weight: plus 2
- Time multi-day weight: plus 1
- Category developer tools no weight
- Moat integrations · infrastructure scale weight: minus 3
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site wabery.com (si apre in una nuova scheda) no weight
They cancel out. This is where it comes down to how much the subscription annoys you.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.
what you need
- 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.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
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.Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- 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
Why people still pay
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.
moat: Integrations Infrastructure scale what a moat is
Meta approval/compliance/managed infrastructure
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (1) — and why
- WAHA (si apre in una nuova scheda) — A polished unofficial WhatsApp Web bridge, not Meta's supported business API.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Meta WhatsApp Cloud API (opens in a new tab) — The official API is the shortest DIY path for a single business that can complete Meta's setup and verification. (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
