Everything worth knowing, nothing that isn't.
What was the WhatsApp On-Premises API?
A self-hosted client. The business, or its provider, ran WhatsApp's software containers and a database in its own data centre or cloud account and looked after scaling, the media store and upgrades. It gave control over where the client ran, but every release had to be installed on Meta's schedule, and the hosting and operating cost sat with whoever ran the servers.
When did Meta retire the On-Premises API?
In stages, according to Meta's developer documentation. From January 2024 new features shipped only to the Cloud API, while the On-Premises client received bug fixes and security patches. From 1 July 2024 new phone numbers could no longer be registered on the On-Premises API. On 23 October 2025 its final version (v2.63) expired, and messages to or from numbers still registered on it are no longer delivered. This is the status as of October 2026; check Meta's documentation for later changes.
How is the Cloud API different?
Meta hosts the API and its infrastructure. Your system calls Meta's Graph API over HTTPS and receives incoming messages and delivery statuses through webhooks, so there is nothing to install or patch — only Graph API versions to move to over time. Meta's documentation gives a default throughput of up to 80 messages per second per business phone number, with higher capacity available on upgrade, and new platform features such as WhatsApp Flows ship to the Cloud API.
Is there still a choice to make?
Not between hosting models: a new WhatsApp Business API integration is a Cloud API integration. The choice that remains is how you connect — directly to Meta, or through a Business Solution Provider that onboards your WhatsApp Business Account, manages templates and verification, and gives you support and billing in one place. BroadNet is an official Meta BSP: it onboards new numbers on the Cloud API and moves numbers that were left on an expired On-Premises client.