Use the raw Cloud API when messaging infrastructure is part of your product and your team will own webhooks, queues, inbox, workflow state, consent, quality, retries, security, and ongoing Meta changes. Use a platform when WhatsApp is a business channel and the operating software, controls, and support are worth more than maintaining that layer yourself.
Cloud API and a WhatsApp platform use the same Meta channel. The difference is who builds and operates everything around the endpoints. This is a build-versus-buy decision, not a question of which route is more official.
Meta hosts the messaging infrastructure and exposes endpoints, webhooks, media, templates, and account-management interfaces. It does not become your team inbox, workflow canvas, consent ledger, retry system, reporting layer, or customer-support process.
Build when messaging is a product capability you intend to own, the engineering team has a durable roadmap for it, or a regulated operating model requires control that no supplier can provide. Include maintenance and incident response in the estimate, not only the first successful message.
Buy when the business needs an inbox, structured workflows, broadcasts, consent controls, team ownership, and support without turning WhatsApp infrastructure into a permanent engineering product. Test the workflow in the provider's product before committing.
Raw Cloud API has no Meta platform subscription, but delivered template messages still use Meta's recipient-country rates and engineering is your cost. A platform can add a subscription, users, add-ons, taxes, or its own rate card. Capture Meta and provider pricing with the same effective date.
Document ownership of the Meta business assets, sender and WABA, templates, contacts, consent evidence, conversation exports, and provider credentials. Test data export before the contract is difficult to leave.
Meta does not charge a platform subscription for raw Cloud API access. Delivered template-message charges still apply by category and recipient country, and your business owns the engineering and operating cost.
Modern providers generally build an operating layer on Meta's WhatsApp Business Platform Cloud API. The software, support, pricing, and asset arrangement differ, while Meta remains the messaging channel.
Eligible assets can move, but the practical work includes permissions, sender state, templates, webhooks, history, exports, and cutover testing. Treat migration as a planned project rather than a guaranteed five-minute task.
A test message can be quick. A secure production system with inbox, workflows, consent, retries, rate controls, observability, and support has no universal timeline and should be estimated from explicit requirements.
Yes. Waaru includes AI conversation agents, Company Brain context, mid-flow recovery, self-learning from approved human resolutions, and a native MCP server alongside deterministic Logic Flows. Bring your own AI is work in progress and is not available yet.
Research notes
Meta documents Cloud API architecture, endpoints, webhooks, templates, and operational requirements.
Meta for Developers · Accessed 8 August 2026
Meta publishes WhatsApp Business Platform pricing rules and country rate cards.
Meta for Developers · Accessed 8 August 2026
About the author
AI and full-stack engineer
Tanay builds production AI systems, agent workflows, and the full-stack software around them. His work focuses on reliable state, recovery, and human handoff.
Put this into practice on your own number.
The platform is free. AI features are paid separately.
