The Cloud API for WhatsApp Business is the version of the WhatsApp Business Platform hosted by Meta (or by a provider on top of its infrastructure), while the On-Premises API is the older version that companies had to install and maintain on their own servers. Meta has announced the progressive discontinuation of the On-Premises API and requires all businesses to migrate to the Cloud API; the exact timeline can vary case by case, so it's worth confirming it with your provider or directly with Meta.
What the On-Premises API was and why it existed
When Meta launched the WhatsApp Business API, the only way to integrate it was by deploying a Docker container on your own servers (on-premise or on a private cloud), with a technical team responsible for keeping it updated, patched, and available 24/7. This gave some companies full control over where their data lived, but it also made them responsible for the infrastructure, certificates, backups, and every update Meta released.
Over time, maintaining that infrastructure became an operating cost that was hard to justify against a simpler alternative: letting Meta's cloud (or a Meta Business Partner) handle all of it.
What the Cloud API is and what it solves
The Cloud API is the same WhatsApp Business API / Business Platform, but hosted on Meta's infrastructure. Your company no longer installs or maintains servers: you connect through a REST API or, more commonly, through a platform like LiveConnect that layers on CRM for WhatsApp, multi-agent support, AI chatbots, and omnichannel (Instagram, Messenger, Telegram, email, web chat) on top.
In practice, most companies that aren't software developers don't consume the Cloud API directly: they access it through a Meta Business Partner that has already solved the infrastructure side, message template delivery, and compliance with the 24-hour window, while also adding sales and support tools on the same number.
Key differences between Cloud API and On-Premises API
| Aspect | On-Premises API | Cloud API |
|---|---|---|
| Infrastructure | Own servers, internal maintenance | Hosted by Meta or by the provider |
| Updates | Manual, your technical team's responsibility | Automatic, no client intervention |
| Availability | Depends on your own operation (uptime, backups) | Managed by Meta's infrastructure |
| Setup time | Weeks (server setup, certificates, network) | Days, especially via a Meta Business Partner |
| Meta's support | Being phased out | The active, supported path |
| Maintenance cost | Infrastructure + dedicated technical team | Included in the provider's plan |
Why this matters now if you're on the On-Premises API
If your company rolled out the Official WhatsApp Business API several years ago, chances are it was built on On-Premises, since that was the only option available at the time. Staying there today carries two concrete risks: missing out on security and feature updates as Meta moves them exclusively to the Cloud API, and depending on a server that, if it fails, leaves you without WhatsApp coverage until your own team fixes it.
Migrating isn't optional in the medium term: it's only a matter of time before the On-Premises infrastructure loses support entirely.
What happens to your number and history when you migrate
Migrating from On-Premises to Cloud API happens at the infrastructure level, not the number level: your WhatsApp Business number stays the same, along with your business verification with Meta. What changes is where the service that processes your messages lives. Conversation history stored in your own database usually doesn't migrate automatically to the new provider's platform — that's why it's worth planning ahead if you need to keep it, and confirming with your provider exactly what data it exports and in what format.
Benefits of migrating to Cloud API with LiveConnect
Migrating to a Meta Business Partner like LiveConnect means you stop operating infrastructure and start operating the business: multi-agent support from a single number, AI chatbots to handle repetitive requests, a CRM for WhatsApp with per-contact history, automation for reminders and follow-ups, and omnichannel coverage to add Instagram, Messenger, Telegram, email, and web chat without multiplying tools. The technical team that used to maintain the On-Premises server can focus on integrating the API with internal systems instead of patching containers.
Common mistakes when migrating
The most frequent one is waiting until the last minute, once Meta has already restricted the On-Premises service and the migration turns urgent instead of planned. Another mistake is assuming conversation history will transfer on its own, without confirming it beforehand with both the outgoing and incoming providers. It's also common to underestimate the onboarding process: even though the Cloud API itself is simpler, it still requires coordinating business verification, approved templates, and training the support and sales team that will use the new platform.
How to start the migration
The first step is a simple diagnosis: which provider currently runs your On-Premises API, which templates and automations you have active, and what data you need to keep. From there, LiveConnect's plans and pricing let you choose the level of multi-agent support and automation you need, and the support team coordinates the technical migration. If you'd rather sort out your questions first, you can message us on WhatsApp and we'll walk you through your specific case.
Staying on On-Premises out of inertia has a growing cost: less support, more operational risk, and a technical team stuck maintaining infrastructure instead of improving customer service.
