WhatsApp API Comparison: On-Premises vs Cloud API WhatsApp API Comparison: On-Premises vs Cloud API

WhatsApp API Comparison: On-Premises vs Cloud API

DK Sah

Question

As Vonage clients switch to Cloud API from On-Premises API, what are the differences in these 2 APIs which should be noted?

Applies To

  • Only for WhatsApp clients or partners having WA numbers registered to On-Prem API

Answer

Note: With the impending deprecation of On-Prem API in Q3'25 by Meta, switching to Meta's Cloud API is a mandatory step to be taken by every On-Premises API user

 

Feature On-Premises API Cloud API
Opex High Opex Reduced setup, hosting and maintenance costs.
TPS Low TPS (Default 20 TPS) (40 TPS on request)

Much faster throughput (Default: 80 TPS) (1000 TPS on request)

Reliability Low Reliability High Reliability: 99.9% uptime and < 5 seconds p99 latency
Security Low Security GDPR and LGPD compliance, SOC2 and SOC3 certification
Encryption Message content End-to-end from Vonage-hosted WhatsApp software to end-user device End-to-end from Meta to end-user device.
Dashboard Indicator Shown as "Hosted by Vonage" in social channels None
Supported? To be Deprecated in Q2'25 Available now
Server Location EU, US, AP (Vonage AWS geos)

EU, US, AP (which can be selected at number registration on request).

For data with WhatsApp, WhatsApp Cloud API Local Data Storage is available

Monitoring and uptime Olympus engineering team Meta is responsible
Number provisioning Up to 3 mins through WhatsApp Provisioning API (deprecated) Almost instant
Contextual replies
Not supported

Supported

Outbound media files download IPs

Media files are downloaded on the Vonage Platform. The download request comes from Vonage IPs.
Media whitelist is not supported 

Media files are downloaded in the Meta infrastructure. The download request comes from Meta IPs

Stickerpacks Stickerpacks supported

Does not support stickerpacks.

 

Additional Information

For Meta documentation, please see here