Self-Hosted vs SaaS WhatsApp Platforms: Which Is Right for Your Agency?
1 November 2026 · 6 min read · Türkçe oku
If your agency manages WhatsApp messaging for clients, you'll eventually ask whether to keep paying for a hosted SaaS tool for each client or run your own platform. Both are legitimate choices, and the right one depends on how many clients you have, who on your team can look after a server, and how much you want to own the product your clients see.
This article sets out the trade-offs plainly. We sell a self-hosted product, so we've tried to be especially careful about where SaaS is simply the better choice.
First, what "self-hosted" doesn't mean
On the WhatsApp Business Platform, the messaging API is always hosted by Meta. Meta retired the On-Premises API, whose final client expired on 23 October 2025, so every integration now uses the Cloud API.
So the real choice is about the platform layer on top of the API: the inbox, contacts, templates, campaigns, automation, team accounts and billing. That layer either runs on someone else's servers (SaaS) or on yours (self-hosted). Several things stay the same either way:
- Meta's rules on templates, the 24-hour window, opt-in and messaging limits apply to everyone.
- Meta's per-message charges go to the WhatsApp Business account that sends the messages, whatever software sits on top.
- Message content still passes through Meta's Cloud API.
Anyone claiming a self-hosted tool gets around Meta's rules or fees is wrong. Tools that appear to do so usually rely on unofficial WhatsApp connections that aren't part of Meta's Business Platform, which is not something you want client numbers on.
The two models at a glance
| SaaS platform | Self-hosted platform | |
|---|---|---|
| Setup | Sign up and connect a number | Install on your server, then connect numbers |
| Cost shape | Recurring fee, often per seat, per number or per contact tier | Licence (one-off or recurring) plus hosting and your time |
| Updates | Automatic | You apply them |
| Uptime and security | Vendor's responsibility | Yours |
| Data location | Vendor's infrastructure | Your server and database |
| Branding | Vendor's brand, unless they offer a white-label or reseller plan | Your domain and your platform name |
| Client billing | Usually you resell or pass costs through | You set your own plans and charge clients directly |
| Customisation | Limited to vendor settings and APIs | Full access to the code, depending on the licence |
| Exit | Export whatever the vendor allows | You already hold everything |
Where SaaS wins
Speed to first message. With SaaS you sign up, connect the Cloud API and you're working the same day. Nobody needs to know what a cron job is.
No operations work. Server patches, backups, TLS certificates, PHP upgrades and uptime monitoring are all handled for you. For a small agency without a technical person, that's worth a lot.
Predictable responsibility. If the platform goes down, the vendor is on the hook. With self-hosting, you are.
Fewer clients, lower cost. If you have two or three clients, SaaS subscriptions can easily cost less than the time it takes to run a server properly.
Where self-hosting wins
Ownership of the product. Your clients log in at your domain, under your platform name. The client relationship stays with you rather than with a vendor whose logo is in the corner.
Your own pricing. You decide the plans, limits and prices you offer clients, rather than marking up someone else's tiers.
Data control. Contacts, conversations and opt-in records sit in a database you control. That can make it easier to answer client questions about where their data is stored, though you're also responsible for securing it.
Costs that don't scale per seat. SaaS fees often grow with seats, numbers or contacts. Self-hosted costs grow mostly with server capacity, which tends to be cheaper per client once you have several.
No dependency on a vendor's roadmap. If a SaaS vendor changes pricing, drops a feature or shuts down, you have to move every client. With self-hosting, the software keeps running on your server.
The real costs of self-hosting
To make an honest comparison, put these in the self-hosted column:
- Hosting. A properly configured VPS or shared hosting plan, with HTTPS. Meta only delivers webhooks to HTTPS endpoints with a valid certificate.
- Your time. Installation, updates, backups, monitoring that scheduled jobs are running, and someone to call when something breaks.
- Security. Keeping the server patched, protecting access tokens and App secrets, and controlling who has database access.
- Support boundaries. A licence usually includes help with the product, not general server administration.
- Meta-side onboarding. Each client still needs their own Meta app or connection, a verified number and template approvals. Software can guide clients through this, but it can't skip it.
If nobody on your team is comfortable doing these things, either budget for a freelancer or choose SaaS.
How to decide
Go with SaaS if:
- You have only a handful of clients and don't expect that to change soon.
- Nobody in the team can maintain a server.
- You'd rather pay more each month than take on operational responsibility.
Go with self-hosted if:
- WhatsApp messaging is (or will be) a product you sell under your own brand.
- You have, or can hire, someone who can run a web server.
- You want to set your own plans and bill clients directly.
- You care where client data is stored and want it on infrastructure you control.
Many agencies start on SaaS while testing demand, then move to self-hosting once WhatsApp becomes a real revenue line. That's a perfectly reasonable path.
Questions to ask any vendor
Whichever model you choose, check:
- Does it use the official Cloud API only? Avoid QR-code pairing or unofficial connections for client numbers.
- Who does Meta bill? Ideally each client's own WhatsApp Business account, so messaging costs don't run through yours.
- Can you export contacts, consent records and message history?
- How are opt-in and opt-out handled? Meta requires opt-in before messaging people and expects opt-outs to be honoured.
- Do delivery reports show Meta's actual error codes, or just "failed"?
- What does maintenance involve, and what does support cover?
Where Mesvilo fits
Mesvilo is a self-hosted, multi-tenant platform built on the official Cloud API. You install it once (PHP 8.3, MySQL or MariaDB, HTTPS and a single cron job; shared hosting works for the base package). Your clients sign up for their own workspaces, connect their own numbers so Meta bills them directly, and pay you a subscription through Stripe or PayPal on plans you define. One licence covers one production domain, and the licence check sends only the key, domain and version, never customer or message data. Updates and support are included for six months from purchase. The documentation lists the full requirements, and pricing shows the licence options.
The best way to judge whether it suits your agency is to click around: try the live demo and read the product page.
Sources
Run your own WhatsApp platform
Mesvilo is a self-hosted WhatsApp Cloud API SaaS with a shared inbox, templates, campaigns and subscription billing.