Short answer: no, not technically. Meta hosts the Cloud API itself and charges nothing for access, throughput or hosting — only per message. A provider sells you onboarding, an inbox, team seats, template management and a rupee invoice. Below roughly 3,000 marketing messages a month that convenience costs more than the messages do.
The choice is not Cloud API versus On-Premises any more
A lot of Indian buying guides still frame this as a hosting decision. It is not. Meta’s own sunset notice sets out three dates: from 9 January 2024 all new features shipped only to Cloud API; from 1 July 2024 business phone numbers “can only be registered for use with Cloud API”, with registration attempts returning error code 1005; and on 23 October 2025 the final On-Premises release, v2.63, expired, after which messages sent through it fail to deliver. That was eleven months ago.
So there is exactly one API. The real question is who stands between you and it.
What Meta gives you directly, and for nothing
Going direct means creating a Meta Business Account, adding the WhatsApp product to an app, and registering a phone number. Meta’s get-started guide hands you a test number that can message five recipients at no cost, with pre-approved templates, before you attach a real number.
Two things are worth knowing because providers rarely volunteer them.
The first is throughput. Meta documents Cloud API at “up to 80 messages per second (mps) by default”, rising to “up to 1,000 mps by automatic upgrade”, and states plainly that higher throughput “does not incur additional charges or affect pricing”. Eighty messages a second is 288,000 an hour; a 60,000-contact base clears in twelve and a half minutes on the default tier. Very few Indian senders are throughput-constrained, which makes “higher rate limits” a thinner upsell than it looks. One exception: a number used with both the WhatsApp Business app and Cloud API is fixed at 20 mps.
The second is volume tiers. Meta aggregates messages “across all of a business portfolio’s WABAs for each market-category pair” each month, tiers reset on the first of the month, and only charged messages count. Utility and authentication rates fall at volume; the aggregation is at portfolio level, not per number. We set out the four layers of a WhatsApp bill in our WhatsApp Business API pricing guide for India.
What Meta’s partner tiers actually mean
Meta publishes a taxonomy that most provider websites flatten into the single word “BSP”. The distinction matters because it determines who sends you an invoice.
A Solution Partner is defined as a Meta Business Partner providing “a full range of WhatsApp Business Platform services to other businesses (clients), such as messaging services, billing, integration support, and customer support.” Solution Partners hold credit lines they can extend to clients, and they bill clients directly for API usage. Clients they onboard skip payment-method collection entirely.
A Tech Provider offers the same services but, in Meta’s words, does “not have credit lines. Instead, clients onboarded by Tech Providers must provide their own payment method after onboarding is complete.” Meta bills those clients directly for API usage; the Tech Provider invoices separately for its own software.
A Tech Partner is “Tech Providers who are, or are eligible to become, Meta Business Partners” — same mechanics, no credit line.
This is also why onboarding differs. Embedded Signup — the one-flow setup that turns days into minutes — is available to Business Solution Providers, and Meta states that “BSPs are responsible for sharing their line of credit with the business to be billed.” Independent Service Vendors cannot use it. Going direct means doing those steps yourself, by hand.
The comparison
| Direct on Cloud API | Via a Solution Partner | Via a Tech Provider | |
|---|---|---|---|
| Who hosts the API | Meta | Meta | Meta |
| Charge for API access, hosting or throughput | None | None | None |
| Who invoices you for messages | Meta | The partner | Meta |
| Credit line available | No | Yes, extended by the partner | No |
| Payment method you must supply | Your own | None at onboarding | Your own |
| Embedded Signup onboarding | No | Yes | Yes, if a BSP |
| Platform fee | None | Yes, published by each provider | Yes |
| Inbox, team seats, template UI, broadcast tooling | You build it | Included | Included |
| Default throughput | 80 mps | 80 mps | 80 mps |
| Who is liable to WhatsApp for your messaging | You | You | You |
Where the money actually goes
A provider’s bill has two parts: a fixed monthly platform fee and a per-message charge. Only the first part is avoidable by going direct, and it behaves very differently at different volumes.
Interakt publishes a Growth plan at ₹2,799 a month plus taxes, and a Growth marketing rate of ₹0.958 per message to Indian numbers. Spread the fee across the messages you send:
| Marketing messages/month | Platform fee per message | As a share of the ₹0.958 rate |
|---|---|---|
| 500 | ₹5.5980 | 584.3% |
| 2,000 | ₹1.3995 | 146.1% |
| 10,000 | ₹0.2799 | 29.2% |
| 20,000 | ₹0.1400 | 14.6% |
| 100,000 | ₹0.0280 | 2.9% |
The crossover is at ₹2,799 ÷ ₹0.958 = 2,922 messages a month. Send fewer than that and the platform fee costs you more than every message you send, put together. Send 100,000 and the fee is under 3% of your message spend — at which point the rate card, not the fee, is the only thing worth negotiating.
A worked example at Growth rates, pre-GST: 20,000 marketing messages costs ₹2,799 + ₹19,160 = ₹21,959, or ₹1.0980 all-in per message. At 100,000 it is ₹2,799 + ₹95,800 = ₹98,599, or ₹0.9860 — the fee adds 14.6% in the first case and 2.9% in the second.
One more piece of published arithmetic. Interakt’s Advanced plan is ₹3,799 a month — ₹1,000 more — and lists marketing at ₹0.949, which is ₹0.009 cheaper. The fee gap divided by the rate gap is 111,111 marketing messages a month before the upgrade pays for itself on marketing alone. Its published Starter marketing rate of ₹0.970 sits 2.21% above Advanced’s. Other providers structure the fee differently again — Wati caps seats rather than messages, and AiSensy publishes a flat per-message rate. We note the spread; we do not assert what causes it. Both figures are on the same page, dated below, and you can check them.
Disclosure: XReach51 sells WhatsApp, SMS and voice messaging in India, so we compete with the providers discussed here. We publish no pricing of our own in this post; our pricing page is the place to look.
Where a provider is genuinely stronger
Four places, and they are not small.
Onboarding. Embedded Signup is a real advantage. Direct setup means business verification, display name review, two-step PIN and webhook plumbing by hand.
Billing. A Solution Partner’s credit line means no card on file and, in practice, a rupee invoice with GST you can hand your accountant. Meta’s developer documentation states it is “introducing local billing for eligible customers in India as of January 2026”, but we could not verify today whether a directly-integrated Indian business can be invoiced in INR without a partner. Ask before you decide on this basis.
Everything that is not the API. The Cloud API sends messages. It gives you no shared inbox, agent assignment, template library, campaign scheduling, segmentation or reporting. Build that and you have built a product.
DLT and the rest of the Indian stack. If you also send SMS or voice, a provider carries the DLT registration and header work, including the 140 and 1600 series rules. Our channel cost comparison sets out what each one costs per customer reached.
The liability point nobody mentions
The WhatsApp Business Solution Terms are worth reading before you assume a provider absorbs your risk. If you retain a third party to manage your access, that provider must act “pursuant to your instructions and authorization” under a written agreement — and “as between you and WhatsApp, you are solely and fully liable for all acts and omissions by your service providers.”
A provider can get your number banned. The terms put that on you.
Who should go direct
Go direct if you have in-house engineers, send a modest and predictable volume, need only one-way notifications, and nobody replies by hand. A logistics firm firing delivery updates out of its own ERP is the clear case.
Use a provider if people will have conversations on the number, if you have no engineering capacity, if you need a rupee invoice without arranging it yourself, or if you are above a few thousand messages a month — where the fee has stopped being the expensive part.
FAQ
Does Meta charge for Cloud API access or hosting? Nothing in Meta’s documentation indicates a charge for API access, hosting or throughput upgrades. Charges are per message. A provider’s platform fee is the provider’s, not Meta’s.
Can I switch from a provider to direct, or between providers, later? Numbers can be migrated and Meta documents the prerequisites, but it has conditions. Treat it as a project, not a toggle.
Is On-Premises API still an option for data-residency reasons? No. v2.63 expired on 23 October 2025 and messages sent through it fail to deliver.
Do I get worse rates going direct? Meta’s volume tiers for utility and authentication aggregate across your business portfolio regardless of how you onboarded. We could not verify Meta’s current India list rate card today — see below — so we are not comparing a direct rate against any provider’s published rate in this post.
Is 80 messages per second enough? For most Indian senders, yes. It clears 288,000 messages an hour, and upgrades to 1,000 mps happen automatically at no charge.
What is the difference between a BSP and a Solution Partner? “BSP” is informal. Meta’s own tiers are Solution Partner, Tech Provider and Tech Partner, and only the first holds a credit line it can extend to you.
Verification note
Every figure in this post was checked against a live source on 5 October 2026. Re-check before relying on any of it. Prices and Meta’s documentation both change without notice.
One figure we could not verify: Meta’s India INR list rate card. The rate table on whatsappbusiness.com/products/platform-pricing is populated by an endpoint that returned HTTP 400 and a missing-nonce error on every attempt today, as it has for four days. We have therefore not published a Meta per-message rate, and no comparison in this post depends on one. Separately, Meta’s pricing page still states it does “not charge for service messages” — read today — which is worth noting if you have seen claims that service messages became chargeable on 1 October 2026.
Sources, all read 5 October 2026:
- Meta for Developers — Cloud API Overview, Get Started, Throughput, Pricing, On-Premises API Sunset
- Meta for Developers — Solution Providers Overview (Solution Partner, Tech Provider and Tech Partner definitions) and Embedded Signup
- WhatsApp — WhatsApp Business Solution Terms
whatsappbusiness.com/products/platform-pricinginterakt.shop/pricing— platform fees and Indian per-message rate card