WhatsApp Cloud API vs On-Premises API
Meta launched Cloud API in 2022 as the modern, fully-hosted replacement for the legacy On-Premises API. As of 2026, Cloud API is the default for new integrations and Meta has paused On-Premises onboarding. Here's the practical difference and what migration looks like if you're still on On-Prem.
TL;DR
Use Cloud API. It's hosted by Meta, free of infrastructure overhead, faster to set up, gets new features first, and costs the same per conversation as On-Premises. The only reason to consider On-Premises was self-hosted control — a niche need that Meta no longer supports for new accounts. Zaptilo uses Cloud API, like all major BSPs.
Side-by-side comparison
| Feature | Cloud API | On-Premises API |
|---|---|---|
| Hosting | Meta hosts on Google Cloud | Self-hosted (you or your BSP runs Docker containers) |
| Setup time | Minutes | Days — server provisioning, Docker setup, DB |
| Maintenance | Zero — Meta handles upgrades | Regular: client updates, security patches, DB backups |
| Infrastructure cost | ₹0 — Meta absorbs infra | Servers, monitoring, ops time — significant |
| Per-conversation cost (Meta) | Same as On-Prem (Meta sets the rate) | Same as Cloud |
| Scalability | Auto-scales (Meta-side) | Limited by your server capacity |
| Reliability | Meta production SLA | Whatever your hosting provides |
| Latest features | First — new features ship here | Often delayed or never |
| WhatsApp Flows support | ✅ Yes | ❌ Limited |
| Available for new accounts (2026) | ✅ Yes | ❌ No — Meta paused new onboardings |
| Used by Zaptilo | ✅ Yes | ❌ No |
Why Meta moved everyone to Cloud API
- Easier onboarding. No server, no Docker, no infra ops. Sign up, get a token, send a message.
- Lower total cost. Identical Meta per-conversation rate, but no infrastructure or maintenance overhead.
- Faster feature rollout. Meta ships new capabilities (Flows, interactive enhancements, message types) to Cloud API first — sometimes only.
- Better reliability. Meta runs production infrastructure with multi-region failover. On-Prem reliability depended on whoever was hosting.
- Auto-scaling. Cloud API absorbs traffic spikes without you provisioning more capacity.
Migrating from On-Premises to Cloud API
If you're still on the legacy On-Premises API, your BSP handles most of the migration. Typical sequence:
- Confirm with your current BSP — many BSPs are migrating customers automatically; some have already.
- Backup chat history from your On-Prem instance if you need it (chat history doesn't move).
- Update API endpoints in your code — On-Prem endpoints (`/v1/messages`) become Cloud API endpoints under the BSP's domain.
- Update webhooks — webhook payload schema is similar but a few field names changed.
- Re-verify any dynamic templates if the migration changes WABA ID. Most templates carry over.
- Cut over phone number — Meta migrates the number from On-Prem to Cloud API in Business Manager. There's a brief outage window (typically minutes).
- Decommission On-Prem servers after a stable period.
If you're moving from a different BSP's On-Premises stack to Zaptilo's Cloud API, our team handles steps 3-7 with you.Contact us to discuss.
Read next
Frequently asked questions
What is WhatsApp Cloud API?
WhatsApp Cloud API is Meta's hosted version of the WhatsApp Business Platform API. Meta runs the infrastructure on Google Cloud — businesses just call REST endpoints. It launched in May 2022 as a successor to the older self-hosted On-Premises API and is now the default for new integrations.
What was the WhatsApp On-Premises API?
The On-Premises API (also called the WhatsApp Business On-Premises Client) required businesses or BSPs to self-host the WhatsApp client on their own servers (typically in Docker), with regular updates and infrastructure management. Meta has been deprecating it since 2024 — new accounts can no longer onboard, and existing accounts have been encouraged to migrate to Cloud API.
Is WhatsApp On-Premises API still available?
Meta has paused new On-Premises API onboardings and is sunsetting existing deployments. New WhatsApp Business API customers must use Cloud API. Most BSPs (including Zaptilo) only support Cloud API.
What's the difference in cost between Cloud API and On-Premises API?
Both pay the same per-conversation rate to Meta. Cloud API has no infrastructure cost — Meta hosts it. On-Premises required servers, ops, monitoring, version upgrades, and BSP-side hosting fees. Cloud API is unambiguously cheaper for nearly every business.
How do I migrate from On-Premises to Cloud API?
Your BSP handles most of it. The phone number is migrated in Meta Business Manager from the On-Premises stack to a Cloud API WABA. Templates, business profile, and verification status carry over. Webhook URLs and API endpoints change — your dev team needs to update integration code to point at the BSP's Cloud API endpoints.
Does Cloud API have feature parity with On-Premises?
Yes, and more. Cloud API has all the messaging features of On-Premises plus newer features like WhatsApp Flows, improved interactive messages, faster template approval, and better webhook reliability. There's no longer any feature reason to stay on On-Premises.
Is Cloud API more reliable than On-Premises?
Generally yes — because Meta runs it on their own production infrastructure with 24/7 monitoring, multi-region failover, and automatic version upgrades. On-Premises uptime depended on whoever was hosting it (you or your BSP).
Start with WhatsApp Cloud API today
Free signup. Hosted by Meta. INR pricing. GST invoice.
Get Started Free