WhatsApp Business API vs 360dialog: Raw API or a Platform You Own?
360dialog is one of the cleanest ways to get the WhatsApp Business API: a flat per-number hosting fee, Meta's conversation cost passed through, and a number that genuinely belongs to you. The question is not whether it is good value — it is what you still have to build afterwards before a team can actually work in the channel.
TL;DR
- 360dialog: the WhatsApp API and a portable number you own. No agent inbox, no CDP, no automations, no other channels — the application layer is yours to build.
- Arino One: the same number ownership plus a full owned instance — inbox, CDP, consent ledger, automations, 18+ channels and GDPR tooling — deployed in an EU region.
Side-by-side comparison
| Dimension | 360dialog | Arino One |
|---|---|---|
| What you get | Raw WhatsApp Business API access | Full owned platform on top of the API |
| Agent inbox | None — bring or build your own | Included in the instance |
| CDP & consent | You build and store it yourself | Contact store and append-only consent ledger included |
| Other channels | WhatsApp only | 18+ channels in one inbox |
| Number ownership | Yours, portable | Yours, portable |
| Data residency | Their hosting environment | EU-WEST, single-tenant instance |
| Customisation | Whatever you write yourself | Full — it is your instance |
| Time to first message | Fast | Days to weeks (build + sender approval) |
The real differentiator is the application layer
360dialog does not add a per-message markup — you pay a flat hosting fee per number and Meta's conversation cost at cost. That is a fair, transparent model and it is not what separates the two options. The separation is scope: an API endpoint is not a place where an agent answers a customer, where consent is recorded and provable, or where a campaign is scheduled and measured.
Every team that starts on a raw API eventually builds that layer. The honest comparison is between 360dialog plus your own build (and its maintenance) and an owned platform that already contains it — see our build vs buy analysis for the cost shape.
Number ownership: a genuine shared strength
Number portability is where 360dialog is strong, and it is worth saying plainly: your WhatsApp Business Account is registered to you, so you are never held hostage by the provider. Arino One takes exactly the same position. If either of us stops earning the relationship, the number leaves with you.
Where a full platform pulls ahead
- Humans need to answer conversations, with routing, assignment and SLAs.
- Consent and erasure have to be provable to a regulator, not reconstructed from logs.
- WhatsApp is one of several channels the same team handles.
- Automations, templates and campaigns need to be operated by non-engineers.
- Data residency must be nameable in a DPIA — a single EU tenant, not a shared environment.
When 360dialog is the right call
- You only need programmatic notifications from an existing system.
- You already have an inbox or CRM you intend to keep.
- Your engineering team wants the API and nothing on top of it.
- You want to be sending this week with minimal commitment.
How Arino One fits
Arino One provisions a dedicated, EU-hosted instance and connects it to a BSP, then hands you the keys. The inbox, CDP, automations and consent ledger run on infrastructure you own, across WhatsApp, SMS, voice and 18+ other channels in one place. You keep the number ownership 360dialog would have given you — and skip the build that would otherwise follow it.
Apply this to your own deployment
This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.