# WhatsApp Cloud API vs BSP: Go Direct to Meta or Use a Provider? > Go directly to Meta's WhatsApp Cloud API if you have developers who can build and maintain the inbox, webhooks, template handling and billing, and you only need messaging plumbing. Use a provider (a BSP or Meta Tech Provider) if you want a ready team inbox, automation and support without engineering work. Direct access avoids a provider margin; a provider saves months of development. Source: https://chat.or.ke/blog/whatsapp-cloud-api-direct-vs-provider Published: 2026-10-20 | Updated: 2026-10-20 | Publisher: chat.or.ke Meta made the WhatsApp Cloud API open to any business with a developer account, so a question we hear from Kenyan founders and IT managers is simple: why pay a provider when you can connect to Meta yourself? It is a fair question, and for some businesses going direct is the right answer. This article lays out what you actually get from Meta, what a provider adds on top, and how to decide. It is written for business owners and the developers advising them. ## Key takeaways - The Cloud API is the raw connection to WhatsApp, hosted by Meta. It sends and receives messages; it does not give you an inbox, a chatbot builder or reports. - Going direct means your team builds and runs everything around it: webhooks, storage, agent screens, template management and Meta billing in US dollars by card. - A provider (a Business Solution Provider or a Meta Tech Provider) wraps the same Cloud API in ready software, onboarding help and local support. - Direct is cheaper per message on paper; a provider is usually cheaper overall unless you already have developers with spare time. - Many businesses start with a provider and move direct later only if they need deep custom integration. ## What do you get from Meta's Cloud API on its own? You get an API, not an application. Meta hosts the infrastructure and lets your server send messages, receive messages through webhooks, manage templates and read delivery statuses. Meta's [Cloud API documentation](https://developers.facebook.com/docs/whatsapp/cloud-api) covers the endpoints. Everything a business user sees has to be built: the screen where agents read and answer chats, assignment between agents, contact records, saved replies, automation, broadcast scheduling, opt-out handling and reporting. You also need to store message history yourself, because Meta does not keep a browsable inbox for you. ## What does a WhatsApp provider add? A provider gives you the finished product on top of the same Cloud API. On chat.or.ke, for example, that means a [shared WhatsApp inbox](https://chat.or.ke/features/whatsapp-inbox) for your team, [no-code automation flows](https://chat.or.ke/features/automation), an [AI assistant](https://chat.or.ke/features/ai-assistant) trained on your business, a template library, broadcasts with delivery reports, and a CRM. Providers also handle onboarding. chat.or.ke is a Meta Tech Provider, so it creates your Meta business profile with you, submits verification, registers your number and submits starter templates. You never touch Meta tokens, phone number IDs or webhooks. To understand the roles, read [what a Meta Tech Provider is](https://chat.or.ke/blog/what-is-a-meta-tech-provider). ## How do direct and provider access compare? Here is a side-by-side view as of October 2026. | | Direct to Meta's Cloud API | Through a provider | |---|---|---| | What you receive | An API and documentation | A working inbox, automation, reports and support | | Developer effort | High: build and maintain everything | None to low | | Time to go live | Weeks to months of development, plus verification | Mostly the time Meta takes to verify your business | | Meta business verification | You do it yourself | Provider usually guides or does it with you | | Paying Meta | Directly, by card, in US dollars | Depends on provider; some bill locally | | Message cost | Meta's rates only | Meta's rates plus the provider's margin or fees | | Support | Meta developer support and docs | Provider's support team | | Customisation | Unlimited | Within the product, often with webhooks and APIs | | Risk if a developer leaves | High | Low | ## What does going direct really cost? The per-message price from Meta is only part of it. Meta charges for delivered template messages by category and country, and its [pricing page](https://developers.facebook.com/docs/whatsapp/pricing) lists current rates. If you stop there, direct always looks cheaper. The hidden costs are people and time. A small team has to build a reliable webhook receiver, queue messages so nothing is lost, store media, track the 24-hour customer service window, manage template approvals, handle opt-outs and build screens for agents. Then someone must keep it running when Meta changes its API versions, which happens regularly. For a Mombasa hotel or a Kisumu clinic, that is a software project, not a messaging upgrade. Billing is the other practical hurdle. Paying Meta directly typically means a card payment in US dollars, which not every Kenyan SME has set up. A provider like chat.or.ke lets you top up a KES wallet with M-Pesa instead, with Meta's charges included in each message price. ## When is going direct to Meta the better choice? Going direct makes sense when messaging is a feature inside a product you are already building. A fintech sending loan statements from its own core system, a large hospital group with an in-house development team, or a software company embedding WhatsApp into its own app may prefer full control. It also suits teams that only need one narrow job, such as sending authentication codes from an existing backend, with no human agents involved. In those cases the extra features of a provider add little. If you are in that position, go direct. You will avoid any provider margin and keep every decision in your own hands. ## When is a provider the better choice? A provider is better when the people using WhatsApp are sales attendants, receptionists and support agents rather than developers. Most SMEs fall into this group. Consider a Nairobi furniture shop running Click-to-WhatsApp ads. It needs leads to land in a shared inbox, be tagged by the ad they came from, be followed up by three salespeople and be offered a broadcast when new stock arrives. Building that on the raw API would take a developer months. Through a provider it is configuration. Providers also help when something goes wrong: a template is rejected, the display name is not approved, or a number's quality rating drops. A local team who has seen the problem before saves days. ## Which should you choose? Choose direct access if you have developers, a clear technical use case and the budget to maintain your own system for years. Choose a provider if your goal is to serve customers faster this month without hiring engineers. There is also a middle path. Pick a provider that exposes webhooks or an API so your developers can connect your own systems later. chat.or.ke flows can call a webhook, for instance, so you can push lead details into your own software while agents keep using the shared inbox. Compare options in our roundup of [WhatsApp Business API providers in Kenya](https://chat.or.ke/blog/best-whatsapp-business-api-providers-kenya). ## Frequently asked questions ### Is the WhatsApp Cloud API free? Access to the Cloud API is free in the sense that Meta does not charge for the software or hosting. Meta charges per delivered message for template categories such as marketing, utility and authentication, at rates that vary by country, and its pricing rules for replies inside the customer service window have changed over time. ### What is the difference between the Cloud API and the On-Premises API? The Cloud API is hosted by Meta, so you do not run WhatsApp servers yourself. The older On-Premises API required businesses or providers to host the software on their own servers. Meta has moved the platform to the Cloud API and providers now build on it. ### Do I need a BSP to use WhatsApp Business API in Kenya? No. Any business can register on Meta's developer platform and use the Cloud API directly if it has the technical skills. A provider is optional, but most small and medium businesses use one because it removes the development work and handles onboarding. ### Is a Meta Tech Provider the same as a BSP? They are related but not identical. A Business Solution Provider, now called a Solution Partner, can offer WhatsApp services and extend credit for Meta charges. A Tech Provider builds software on the platform and onboards businesses through Meta's Embedded Signup. Both give businesses access to the same WhatsApp Business Platform. ### Can I switch from a provider to direct access later? Usually yes. Your WhatsApp number and business portfolio belong to your business, so a number can be moved to a different setup. Plan the move carefully, export your contacts and history first, and expect a short period of setup on the new side.