WhatsApp Cloud API vs On-Premise API
Meta has been migrating everyone to Cloud API since 2022. The On-Premise API is officially deprecated. Here's what that actually means for your stack.
WhatsApp originally offered the Business API as an on-premise solution — you (or your BSP) hosted Docker containers that connected to Meta's servers. In 2022 Meta launched Cloud API, hosting the same functionality on Meta's infrastructure. On-Premise was deprecated in October 2023 and Meta has been migrating brands off it through 2025-2026.
If you're starting fresh today the answer is Cloud API — there's no real choice. If you're still on On-Premise (some enterprise BSPs), this guide covers the migration path and what changes.
The headline differences
Four practical differences that matter.
- Hosting: Cloud API runs on Meta's infrastructure; On-Premise runs in your BSP's data center or your own.
- Performance: Cloud API is faster and more reliable at scale — Meta operates the servers globally with sub-100ms median latency in most regions.
- Cost: Cloud API has no hosting cost (Meta absorbs it); On-Premise required BSP infrastructure cost, baked into platform fees.
- Features: New Meta features (catalog, payments, RCS preview) ship to Cloud API first or Cloud API only.
Why On-Premise was deprecated
Three drivers. Operational complexity: managing Docker containers across geographies, handling version upgrades, scaling for peak loads — expensive for both Meta and BSPs. Compliance overhead: keeping On-Premise instances in sync with new Meta policy rollouts was slow. Feature fragmentation: Meta couldn't ship new capabilities without On-Premise customers needing manual upgrades.
What changes when you migrate
On the BSP side, integration moves from BSP-hosted endpoint to Meta-hosted endpoint. Webhook URLs need re-pointing. Authentication moves from BSP-issued tokens to Meta-issued access tokens (System User tokens). For brands on a managed BSP (LandinChat, Wati, AiSensy, etc.) this happens behind the scenes — you experience zero downtime.
Brands that built custom integrations directly against On-Premise need to re-implement against Cloud API endpoints. The endpoint shapes are similar but not identical; budget 1-3 engineering days for a straightforward migration.
Migration timeline
Meta's deprecation timeline closed in late 2024 — any remaining On-Premise instances are running on grace-period extensions or specific enterprise carve-outs. Brands still on On-Premise should plan migration this quarter; new feature access is the operational pressure driving the move.
What you gain on Cloud API
Better latency globally, automatic access to new features (catalog updates, in-chat payments, calling features as they roll out), lower BSP costs (most BSPs reduced platform fees after migrating off On-Premise hosting), and one less infrastructure component to monitor.
What you lose (or have to handle differently)
Data residency: On-Premise let you keep message data in your own data center, useful for some regulatory regimes. Cloud API data sits in Meta's infrastructure (multi-region, but Meta-operated). Brands in regulated industries (banking, healthcare with specific residency requirements) need to confirm Cloud API's data-handling meets their compliance requirements — for most it does, for some specific regulators it requires legal review.
Choosing a BSP after migration
All major BSPs operate on Cloud API today. Decision criteria are the same as before: pricing model (flat vs per-message markup), feature depth (commerce, automation, chatbot), seat economics (per-seat vs unlimited), and support quality. The Cloud vs On-Premise question is no longer part of the BSP comparison.
Key takeaways
- → On-Premise API is deprecated — Cloud API is the current product.
- → Migration is zero-downtime when handled by your BSP.
- → Custom integrations may need 1-3 engineering days to re-point.
- → Data residency is the only meaningful trade-off — material for some regulated industries.
- → All new Meta features ship to Cloud API first.
FAQs
Can I still use On-Premise API in 2026?
Only on grace-period extensions or specific enterprise carve-outs. Meta is actively migrating remaining customers off.
Is Cloud API more expensive?
Usually cheaper. Meta absorbs hosting; BSPs passed savings into lower platform fees.
Does my WhatsApp number change?
No — only the underlying API endpoint changes. Number, history, templates and contacts remain.
How long does migration take end-to-end?
1-7 days depending on integration complexity. Managed BSP: hours. Custom integration: 1-3 engineering days.
Is Cloud API rate-limited differently?
Same per-WABA rate limits, but Cloud API handles burst traffic more gracefully thanks to Meta's infrastructure.
Run WhatsApp marketing with LandinChat.
Official Meta Tech Partner. 500+ businesses worldwide. Broadcasts, chatbot, shared inbox, integrations — one flat plan.
See pricing