UltraMsg is a well known unofficial WhatsApp Web API: QR instance, REST, about $39 per number, no per-message fee, lots of language samples. LoginWA is a managed unofficial WhatsApp API in the same category, not Meta Cloud. Free tier (100 messages/month) and paid from $1. Always check /pricing (https://loginwa.com/pricing) for current numbers.
Honest note: UltraMsg does several things well. Setup is fast, the instance id plus token model is simple, media and webhooks are included, and a flat $39 instance does not meter each message. That wins at high volume. LoginWA is newer and cheaper at low volume (OTP, notifications). Both are unofficial WhatsApp Web gateways, not official Meta BSPs. Ban risk is the same class; nobody can honestly promise 100% anti-ban. Prices change: UltraMsg on ultramsg.com, LoginWA on https://loginwa.com/pricing.
Common reasons developers compare UltraMsg with a quota gateway:
LoginWA pricing is summarized only at a high level. Full plan table: https://loginwa.com/pricing. UltraMsg figures below are from their public site (about $39/instance) and can change.
| Aspect | LoginWA | UltraMsg | Meta Cloud / official |
|---|---|---|---|
| Hosting | Managed, no VPS for the WA session stack | Managed instance (1 number = 1 instance) | Meta-hosted Cloud API |
| API nature | Unofficial (QR multi-device) | Unofficial (WhatsApp Web protocol) | Official WABA |
| OTP / auth focus | Dedicated OTP start/verify endpoints + message API | You build OTP on top of send/receive | Official auth / message templates as allowed |
| Cost model | Free tier (100 msg/mo) and paid from $1, see /pricing | About $39/mo per instance, no per-message fee (verify on ultramsg.com) | Meta conversation pricing + BSP fees |
| Best when… | OTP / light WA API today with less ops and a $1 start | You want a documented flat instance and will send enough to justify $39 | Compliance / official Business API is required |
Solo founder or small team: WhatsApp OTP, notifications, light blast via API. Start on the free tier (100 messages/month); paid from $1. Numbers and limits live on https://loginwa.com/pricing.
A 3-day trial, $39 per number with no message meter, and REST samples across many languages. UltraMsg is the right tool when the instance model is what your stack already expects.
Banking, regulated messaging, template-only outbound at scale, or partners that require the official Business API. LoginWA will not pretend to be that path.
LoginWA and UltraMsg sit outside official WABA. Sensible send rates and account hygiene matter more than marketing anti-ban claims. Prefer honesty over guarantees.
One request to send a message. OTP has dedicated start/verify endpoints. Full reference: /docs and /reference (OpenAPI).
curl -X POST https://api.loginwa.com/api/v1/messages/send \
-H "Authorization: Bearer API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone":"62812xxxx","message":"Halo!"}'Yes, when the goal is WhatsApp OTP or messaging via API without a $39 instance. LoginWA manages the session stack; you use REST plus dashboard. It is still unofficial, not Meta Cloud.
Fast instance setup, a simple token model, media, webhooks, many language samples, and a flat $39 fee with no per-message charge. Confirm current UltraMsg prices on ultramsg.com.
LoginWA free tier: 100 messages/month. Paid plans from $1. Do not treat this page as the source of truth, open https://loginwa.com/pricing because an admin can change prices without a deploy. UltraMsg publicly lists about $39 per instance.
LoginWA and UltraMsg are unofficial. Meta Cloud is official WABA. Pick Meta when compliance requires it; pick managed unofficial when you explicitly accept that trade-off for speed and cost.
When you want a widely documented instance API, a 3-day trial, and a flat $39 instance with no message meter. For a solo founder who wants OTP and less ops, a quota gateway is usually the clearer default.
Sign up with WhatsApp OTP, pair a device, send on the free tier. Compare against your UltraMsg instance. Pricing details: https://loginwa.com/pricing.