UltraMsg charges $39 per instance, and one instance is one WhatsApp number. That model is fine at one number and brutal at ten. Here is the arithmetic, the alternatives that bundle sessions instead, and what you give up by leaving.
WasenderAPI is a good, cheap, developer-focused WhatsApp API, and it is our closest competitor. Here is a straight comparison of pricing, features and trade-offs, including the cases where we would tell you to stay put.
Whapi.Cloud is a good product with one expensive characteristic: $35 per number per month. Here is where that price is worth paying, where it is not, what you lose by leaving, and exactly how to migrate if you decide to.
The official on-premises WhatsApp API shut down in October 2025. Self-hosting now means running the WhatsApp Web protocol yourself. Here is what that actually involves, which open source projects are worth deploying, what it costs once you count engineering time, and whether it genuinely solves your GDPR problem.
Working code for sending WhatsApp messages from Node.js, Python and curl, plus the parts most tutorials skip: phone number formatting, media uploads, retry logic, rate limiting, and receiving replies.
n8n plus a WhatsApp API gets you a working automation in an afternoon, no code required. Here is how to wire the two together, three workflows worth building, and the mistakes that turn a clever automation into a banned number.
Volume is not what gets numbers banned. Blocks and reports are. Here is how WhatsApp's enforcement actually works in 2026, a realistic warm-up schedule, the operating rules that keep numbers alive, and what to do in the first hour after a restriction lands.
Meta's rate card is only the first layer of your WhatsApp bill. Here is the full 2026 picture: per-message rates by country, BSP markups, the free windows that close in October, hidden costs nobody warns you about, and three worked examples.
There used to be three ways to reach WhatsApp programmatically. One died in October 2025. This is a working engineer's comparison of what is left: Meta's Cloud API and the session-based alternatives, with the trade-offs laid out honestly.