Wati vs Arino One: A Shared WhatsApp Tool or an Instance You Own?
Wati is one of the easiest ways for a small team to get a real WhatsApp presence: a shared team inbox, broadcasts and simple chatbots, live in an afternoon. It earns its popularity. The question worth asking as the team grows is what happens when seats, contacts, channels and compliance all start moving at once.
TL;DR
- Wati: shared, multi-tenant, WhatsApp-centric SaaS. Priced around seats and contact volume, fixed feature set, vendor-hosted. Excellent for SMB teams getting started.
- Arino One: a single-tenant, EU-hosted instance you own — unlimited seats, 18+ channels, an append-only consent ledger and hard-delete DSARs. More to stand up; you are buying rather than renting.
Side-by-side comparison
| Dimension | Wati | Arino One |
|---|---|---|
| Tenancy | Shared, multi-tenant SaaS | Single-tenant instance you own |
| Pricing shape | Tiers by seats and contact volume, on top of Meta's conversation cost | Flat instance, unlimited seats, wholesale conversation rate |
| Channels | WhatsApp-centric | 18+ channels in one inbox |
| Data residency | Vendor hosting; region not customer-selected | EU-WEST by default (NA/APAC on request) |
| Compliance tooling | Basic opt-out handling and exports | Append-only consent ledger, hard-delete DSAR with receipt |
| Customisation | Fixed SaaS feature set | Full — it is your instance |
| Number / WABA ownership | Registered through the vendor account | You hold the WhatsApp Business Account |
| Time to first message | Hours | Days to weeks (build + sender approval) |
Where cost shape starts to bite
Seat- and contact-based pricing is fair at small scale and predictable at first. It becomes awkward at the moment you want more of your organisation in the conversation — support, success, sales, a night shift — because every additional person is a recurring line item, and every campaign that grows the audience nudges the tier. Teams often respond by sharing logins or keeping people out of the inbox, which is exactly the wrong incentive.
A flat instance removes the seat question entirely and passes Meta's conversation cost through at wholesale. Model both shapes against your real headcount and contact growth using our WhatsApp Business API pricing guide.
One channel or many
Wati's WhatsApp focus is a feature, not an oversight — it keeps the product simple. But most teams eventually add SMS fallback, a web chat widget, voice, or Instagram and Messenger. Each one added outside the platform means another inbox, another contact record and another consent trail to reconcile. Arino One keeps all of them in one place, on one contact record.
Compliance and ownership
Under GDPR you are the controller whichever tool you use. What changes is what you can evidence. A shared platform gives you exports and opt-out flags; a single-tenant EU instance gives you a named region, a short sub-processor list, an append-only consent log and hard deletion with a signed receipt. If your buyers run security reviews, that difference shows up in the first questionnaire.
When Wati is the right call
- A small team needs a shared WhatsApp inbox this week.
- WhatsApp is the only channel you plan to run.
- Contacts are not sensitive and volumes are modest.
- You would rather pay per seat than run anything yourself.
When an owned instance wins
- Seat or contact tiers are shaping who gets access to customers.
- A second or third channel has become unavoidable.
- Buyers or regulators ask where exactly the data lives.
- You need provable consent and erasure, not just an export.
- You want the number and the WhatsApp Business Account in your own name.
Moving across
Migration is a number migration plus a template re-approval. Templates are re-submitted on the destination WhatsApp Business Account, contacts and opt-in state are imported into the CDP, and the number moves in a short verification window outside peak hours. Broadcasts and chatbot flows are rebuilt once — and then owned by you.
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.