Walytic Web vs Walytic Cloud: which transport should you use?
Walytic Web is the linked-device protocol; Walytic Cloud is Meta's official Cloud API. Most teams should run both.
The short answer
If you're sending under 500 messages a day, conversational, opt-in audience: Walytic Web is fine and faster to set up.
If you're running campaigns to cold audiences, sending more than 500 messages a day, or you need an SLA: Walytic Cloud.
If you do both: connect both, and let the smart router pick per message.
What each one is
Walytic Web uses the WhatsApp linked-device protocol. The same one that powers WhatsApp Web and WhatsApp Desktop. You scan a QR code and Walytic acts as another linked device on your number. Setup takes two minutes. The trade-off is that Meta watches sending patterns; if you send like a bot, the number can be flagged.
Walytic Cloud uses Meta's official WhatsApp Cloud API. You bring a WhatsApp Business Account (WABA), a registered phone number, and an access token from Meta. There's effectively no ban risk because Meta is the one running the rails. The trade-off is that messages outside the 24-hour conversation window must use pre-approved templates.
Side-by-side
| Capability | Walytic Web | Walytic Cloud |
|---|---|---|
| Free-form text inside 24h window | Yes | Yes |
| Free-form text outside 24h window | Yes | Template only |
| Pre-approved templates | Hack only | Native |
| Bulk send (1k+ recipients) | Risky | Designed for it |
| Group send | Yes | No |
| Status views, presence | Yes | No |
| Onboarding friction | QR scan, 2 mins | WABA + token, 1 day |
| Ban risk | On user | Effectively zero |
When to use both
The cleanest setup for a serious team is one Walytic Web session and one Walytic Cloud session under the same brand. The smart router (Auto transport) then picks the right one per message:
- Customer reply within 24 hours → Web (free-form, conversational tone)
- 1,000-recipient broadcast → Cloud (rate-stable, no flagging)
- Group message → Web (Cloud has no group send)
- Cold-contact outreach → Cloud with a template
- Status view → Web (Cloud has no stories)
You don't have to manually choose. Set the flow node's transport to Auto and Walytic decides at dispatch time.
How to add the second transport
If you already have Walytic Web connected:
1. Go to WhatsApp Connections.
2. Click the Walytic Cloud tab in the "Start New WhatsApp Client" panel.
3. Paste your WABA ID, Phone Number ID, and Access Token.
4. Click Connect Cloud Number.
5. Configure the webhook URL in your Meta App as instructed on screen.
If you'd like to migrate an existing Web number to Cloud (preserving contacts and history), use the Migrate to Cloud button under Settings → Integrations. The migration is one-click and contacts, flows, and conversation history are preserved.
Common questions
Do I need separate phone numbers for Web and Cloud?
No, you can connect the same number on both transports. The smart router knows they're interchangeable for the same brand.
Can I run only Walytic Cloud and skip Web entirely?
Yes. Some teams prefer this for the zero-ban guarantee. The trade-off is templates outside the 24-hour window and no group sends.
Which one is more expensive?
Pricing is the same on Walytic's side. Walytic Cloud has additional Meta-side costs (per-conversation fees) that Walytic Web does not. See Plans and quotas for the full breakdown.
Need more help?
Browse the rest of the help center or contact support directly.