WhatsApp On-Premises API<\/strong> was a self-hosted version, typically run as a Docker container on a business\u2019s own servers (or a cloud provider like AWS or GCP). It gave businesses direct infrastructure control but required them to manage hosting, scaling, and maintenance themselves.<\/p>\n\n\n\n Meta announced the deprecation of the On-Premises API back in October 2023, and after a phased wind-down, the final supported client version expired on October 23, 2025. As of that date, On-Premises can no longer be used to send messages to WhatsApp users under any circumstances \u2014 existing deployments simply stopped working unless migrated to Cloud API beforehand.<\/p>\n\n\n\n If you inherited a system that still points at On-Premises endpoints, those messages are not being delivered. There is no fix other than migrating the business phone number to Cloud API.<\/p>\n\n\n\n Meta\u2019s own migration documentation lays out several reasons behind the transition:<\/p>\n\n\n\n If your business is only now realizing it needs to move off a legacy On-Premises setup, here\u2019s the practical path forward:<\/p>\n\n\n\n Since On-Premises is no longer an option, understanding what Cloud API offers is really understanding what the WhatsApp Business Platform offers, period:<\/p>\n\n\n\n Is there any legitimate reason to still be running On-Premises?<\/strong> Will my message history and templates transfer automatically when I migrate?<\/strong> Do I need a Business Solution Provider (BSP) to use Cloud API?<\/strong> Has pricing changed along with the API transition?<\/strong> The \u201cCloud API vs On-Premises API\u201d comparison that used to shape architecture decisions is now, functionally, a migration guide \u2014 On-Premises is fully retired, and Cloud API is the only path forward on the WhatsApp Business Platform. For any business, developer, or agency still working from older documentation, the priority isn\u2019t choosing a side; it\u2019s confirming your systems are fully migrated and verifying your integrations against Cloud API\u2019s current requirements.<\/p>\n<\/body>","protected":false},"excerpt":{"rendered":" For years, businesses building on the WhatsApp Business Platform had…<\/p>\n","protected":false},"author":6,"featured_media":7523,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7522","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-newsletter"],"yoast_head":"\nThe Current Status: On-Premises Is Gone<\/h2>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/www.mdsmedia.co.in\/blog\/wp-content\/uploads\/2026\/08\/WhatsApp_API_cloud_migration_inf%E2%80%A6_202608211217-1024x572.jpeg?resize=1024%2C572&ssl=1\")
<\/figure>\n\n\n\nWhy Meta Made the Switch<\/h2>\n\n\n\n
\n
What This Means If You\u2019re Migrating Now<\/h2>\n\n\n\n
\n
Cloud API: What Businesses Get Today<\/h2>\n\n\n\n
\n
Frequently Asked Questions<\/h2>\n\n\n\n
No. As of October 23, 2025, On-Premises cannot send WhatsApp messages under any configuration \u2014 there is no supported use case for continuing to run it.<\/p>\n\n\n\n
Message templates generally need to be verified post-migration, and it\u2019s important to confirm your business phone number registration completes successfully on Cloud API before assuming continuity.<\/p>\n\n\n\n
No \u2014 direct integration through the Meta Developer Console is fully supported. A BSP is optional and typically chosen for added support, tooling, or faster onboarding rather than being a technical requirement.<\/p>\n\n\n\n
Yes \u2014 separately from the On-Premises sunset, Meta moved to per-message template billing in July 2025, replacing the earlier conversation-based pricing model. It\u2019s worth reviewing current rates directly with Meta or your provider, since messaging pricing has changed more than once in recent years.<\/p>\n\n\n\nFinal Thoughts<\/h2>\n\n\n\n