The verdict: can you vibe code Wabery?
Build a focused single-tenant personal subset or keep paying, because managing Meta's complex cryptographic Flows handshake, webhook retry queues, and sandboxed TypeScript execution engines requires building a full backend-as-a-service platform from scratch.
Wabery is a sophisticated developer infrastructure layer masking immense Meta Graph API complexity. While you can build a personal Express/Next.js wrapper that talks directly to the Meta Cloud API for simple message sending and receiving, reproducing Wabery's core differentiator — WhatsApp Flows asymmetric encryption, signed webhook retry queues, a hosted TypeScript serverless runner, and an MCP server for AI coding agents — represents weeks of grueling infrastructure work that easily justifies paying for the managed service.
Estimated effort: 4-6 weeks of full-time systems engineering
What you can't replicate
- Official Meta Business Partnership compliance standing and instant WhatsApp Business number onboarding
- Built-in carrier fee pass-through accounting and micro-dollar wallet infrastructure
- Ready-to-use production WhatsApp Sandbox phone infrastructure
Founded
—
Raised
—
Team
—
Cheapest paid tier
$0
What Wabery does
Developer-focused messaging platform and unified API layer for WhatsApp Business, Instagram Direct, and Facebook Messenger, featuring WhatsApp Flows, signed webhooks, hosted TypeScript functions, and native MCP servers.
Core features
- Unified Channels API (WhatsApp, Instagram, Messenger)
- WhatsApp Flows JSON authoring, RSA/AES encryption handshake, and secure data-exchange webhook routing
- Signed Event Webhooks with cryptographic signatures (v1=...), retries, and health tracking
- Managed Shared Inbox, conversation threads, and contact states
- Hosted TypeScript runtime sandbox for automated routing, replies, and tool execution
- CLI (@wabery/cli) and Model Context Protocol (MCP) server support for AI agent integration
The business
Pricing
- Free$0
- Paid Capacity Blocks$15/mo+
Funding
Unknown / bootstrapped
Pay vs build, cumulative
Break-even at month 3 — after that, every month is money kept.
The hard parts of vibe coding Wabery
- Meta Cloud API business verification, webhook token challenges, and navigating strict 24-hour customer service conversation windows
- WhatsApp Flows asymmetric encryption handshake (RSA/AES payload decryption/encryption)
- At-least-once webhook delivery engine with exponential backoff retries and cryptographic signature generation
- Secure, isolated serverless JavaScript/TypeScript runtime sandbox for running arbitrary third-party automation functions safely
- Short-lived Meta media URL ingestion, re-signing, and local/cloud storage caching before expiration
How to vibecode Wabery
Prerequisites
Node.jsfree
Required for running the TypeScript backend runtime and CLI tools
GitHubfree
Source code repository and CI/CD deployment pipelines
Meta Developer Accountfree
Mandatory for obtaining WhatsApp Business API credentials and setting up webhooks
AI coding tools
Recommended stack
| Frontend | Next.js |
|---|---|
| Backend | Node.js / Express API server |
| Database | Turso |
| Auth | better-auth |
| Payments | Stripe |
| Other | Upstash Redis for webhook retry queues, Vercel AI SDK |
Build guide
01Project Scaffolding & Database Schema
Initialize the monorepo structure with a Next.js dashboard frontend, Express backend server, and Turso SQLite database schema for projects, channels, contacts, conversations, messages, and webhook logs.
Create a full-stack project structure using Next.js for the dashboard and an Express Node.js server for the messaging API layer. Set up Turso with libSQL for the database. Design the relational schema including tables for projects, channels (storing Meta access tokens and phone numbers), contacts, conversation threads, and message history logs. Include a robust configuration-as-code parser in TypeScript that supports exporting and applying project definitions.02Meta Cloud API Integration & Message Routing
Implement core API endpoints and SDK methods to send and receive text and media messages across WhatsApp, Instagram, and Messenger channels via the Meta Graph API.
Implement the messaging engine in the Express backend that interfaces with the Meta Graph API. Build REST endpoints and a TypeScript SDK wrapper (`@wabery/sdk`) for sending text, media (images, documents, audio), and template messages. Implement inbound webhook verification routes (`GET /webhooks/meta`) conforming to Meta's token challenge protocol and handle inbound message parsing into normalized conversation events.03WhatsApp Flows Cryptography & Data Exchange
Build the encryption/decryption handshake engine required for handling WhatsApp Flows payload exchange and dynamic form data submissions securely.
Implement the cryptographic security layer for WhatsApp Flows. Write utility modules to handle RSA private key decryption and AES-128-CBC payload decryption for inbound Flow data exchange requests, and encrypt responses back to Meta according to official WhatsApp specifications. Build an endpoint handler that validates Flow payloads, executes associated data-exchange logic, and returns structured form submissions.04Signed Event Webhooks & Retry Queue
Create a reliable outbound webhook delivery system that dispatches signed cryptographic events with exponential backoff retries and endpoint health tracking.
Build an outbound webhook dispatch engine using Upstash Redis queues. When inbound messages or status events arrive, sign the payload using HMAC-SHA256 with an endpoint secret (`v1=...`) and deliver HTTP POST requests to customer webhook targets. Implement an exponential backoff retry worker for failed deliveries (HTTP non-2xx responses) and track endpoint health metrics (success/failure rates) in the database.05Hosted Functions Sandbox Runtime
Develop a server-side TypeScript execution runtime that safely executes project-scoped automation scripts and tool handlers without risking host stability.
Create a secure server-side TypeScript function runner in Node.js using isolated-vm or controlled child processes. Allow users to deploy project-scoped handler scripts that receive a context object (`Ctx`) with database access, fetch utilities, and helper methods for sending messages. Implement deployment APIs, invocation log streaming, and error boundary isolation.06CLI & Local MCP Server
Build a command-line interface tool and local Model Context Protocol (MCP) stdio server so AI agents like Claude Code and Cursor can manage project configurations and workflows.
Build a CLI tool (`@wabery/cli`) in TypeScript supporting commands like `login`, `channels list`, `flows apply`, and `functions deploy`. Additionally, implement a local MCP server over stdio that exposes Wabery resources (projects, channels, contacts, messages, flows, hosted functions) as agent-callable tools. Ensure write operations require proper confirmation tokens and respect secure local session boundaries.
Cost vs paying for Wabery
What will you build it with?
Starting total with Claude Code$0 one-time
Starting costs (one-time)
- Domain name$12/year
Total~$12 one-time
Ongoing costs (monthly)
- Fly.io & Database hosting$10/mo
- Meta WhatsApp Carrier FeesAt cost (Variable)
Total~$10/mo + carrier usage
Paying for Wabery
$15/mo (Capacity tier)
Your time to build
80-120 hours
AI tool credits
$20 (Claude Pro)
Break-even
N/A (Built for developer control and education)
Vibe code Wabery: FAQ
- Can you vibe code Wabery yourself?
- Serious undertaking — 35/100 vibecodeable. Build a focused single-tenant personal subset or keep paying, because managing Meta's complex cryptographic Flows handshake, webhook retry queues, and sandboxed TypeScript execution engines requires building a full backend-as-a-service platform from scratch.
- How long does it take to vibe code Wabery?
- 4-6 weeks of full-time systems engineering — roughly 80-120 hours of hands-on time with an AI coding agent.
- How do you build your own Wabery?
- Scoped to personal use: Next.js on the front, Node.js / Express API server behind it, Turso for data. Follow the 6-step build guide on this page — each step has a paste-ready prompt for an AI coding agent.
- How do you code your own Wabery without being an expert?
- Use an AI coding tool (Claude Code or Cursor) and work in small steps: scaffold, data model, core screens, then deploy. Realistic effort: 4-6 weeks of full-time systems engineering. The prompts on this page are written so the AI does the heavy lifting.
- How much does it cost to vibe code Wabery instead of paying?
- About ~$12 one-time to start and ~$10/mo + carrier usage to run, versus $15/mo (Capacity tier) for Wabery. Break-even: N/A (Built for developer control and education).
- What stack should you use to vibe code Wabery?
- Next.js; Node.js / Express API server; Turso; plus Upstash Redis for webhook retry queues, Vercel AI SDK.