Glossary
What was the WhatsApp On-Premises API, and is it still available?
The self-hosted WhatsApp Business API that Meta retired on 23 Oct 2025, how it differed from the Cloud API, and why old guides mentioning it are out of date.
By Broadchat teamPublished 2 min read
Definition
On-Premises API: The On-Premises API was the original, self-hosted version of the WhatsApp Business API. Businesses or their providers ran WhatsApp's software in containers on their own servers and handled scaling, storage and upgrades themselves. Meta stopped new On-Premises sign-ups on 1 Jul 2024 and shut the API down on 23 Oct 2025, with v2.63 as the last version. Only the Cloud API remains.
Also called: On-Prem API, WhatsApp Business API client, Self-hosted WhatsApp API
What the On-Premises API was
Before Meta hosted the API itself, a business that wanted WhatsApp at scale had to run the WhatsApp Business API client: a set of Docker containers plus a database, installed in its own data centre or cloud account. Messages were encrypted and decrypted on those servers. The operator handled backups, certificates, scaling and regular upgrades, and the client software expired if it was not kept up to date.
That is why early providers were mostly large companies with infrastructure teams. The Cloud API moved all of this to Meta.
Timeline
| Date | Change |
|---|---|
| 1 Jul 2024 | New On-Premises sign-ups stopped |
| 23 Oct 2025 | On-Premises API shut down; v2.63 was the last version |
| Today | Only the Cloud API is available |
On-Premises vs Cloud API
| On-Premises (retired) | Cloud API | |
|---|---|---|
| Who hosts | You or your provider | Meta |
| Upgrades | Manual, on a deadline | Done by Meta |
| Scaling | Add your own servers | Throughput upgrades handled by Meta |
| Status today | Shut down | The only option |
How to spot outdated advice
You will still find blog posts, tender documents and vendor brochures from before 2025. Signs that advice is out of date:
- It asks you to choose between "Cloud" and "On-Premises" hosting.
- It quotes server sizing, container counts or database requirements for WhatsApp.
- It claims data stays on your servers because of On-Premises hosting.
Example. Arjun, IT head of a cooperative bank in Nagpur, receives a vendor proposal in 2026 offering "dedicated On-Premises WhatsApp API hosting". That product no longer exists. He should ask the vendor to confirm it is built on the Cloud API and to state where its own data (contacts, chat history) is stored, which is a separate question from where WhatsApp runs.
Where Broadchat fits
Broadchat is built on the official WhatsApp Business Platform (Cloud API) and is not affiliated with or endorsed by Meta. There is nothing to install: connect a number under Channels → All Channels and start from the setup guide. For background, read what the WhatsApp Business API is.
Sources
- On-Premises API sunset — Meta for Developers, checked 12 October 2026
- WhatsApp Business Platform changelog — Meta for Developers, checked 12 October 2026
Broadchat team · Product and partner success team
The people who build and support Broadchat, the white-label WhatsApp Business API platform. We write from what we see while onboarding partners and their clients on the official WhatsApp Cloud API, and we check every article against Meta's current documentation.
Last updated:
Frequently asked questions
Can I still use the WhatsApp On-Premises API?
No. Meta shut it down on 23 Oct 2025. All WhatsApp Business Platform messaging now runs on the Cloud API.
Does the Cloud API store my customers' messages?
Meta hosts the WhatsApp side of the API, and media you upload is kept for a limited time. Your contact list and chat history in a platform are stored by that platform, so ask your provider where and how it stores them.
Did numbers on the On-Premises API have to re-register?
Numbers had to move to the Cloud API before the shutdown. A number that was not moved needs to be registered on the Cloud API, usually through a platform's Embedded Signup flow.