Twilio
The largest CPaaS by reach, and the most mature US long-code, short-code and A2P ecosystem. If you already run on Twilio, connecting it here changes nothing about your account or your bill.
Twilio setup →Use the SMS providers you already pay for
Whaleal Messaging never sells you message credits. You keep your existing provider account, your negotiated rate and your invoice — and paste that account’s API credentials here. We handle routing, pacing and the send log.
Why bring your own. If we resold message volume we would have to sit between you and your provider: our margin, our routing choices, our support queue. We do none of that. Your account, your quota and your negotiated rate stay yours, and the relationship with your provider stays in your name.
Available now (6)
Self-service: create the connection in the console yourself, no conversation with us required. Each page lists the exact credential fields that provider needs.
Vonage
Formerly Nexmo. Rich direct routes across Europe and North America, and one of the highest default throughput tiers we ship with.
Vonage setup →Infobip
A full-stack CPaaS with standout coverage across the Middle East, Africa and Southeast Europe — the regions where the big two are often routed through aggregators.
Infobip setup →MessageBird
Known for strong European direct routes with high delivery rates across the Benelux and the wider EU region.
MessageBird setup →Plivo
A high-value US-centric provider with a Twilio-style API, which makes it a common choice for cost-sensitive high-volume traffic.
Plivo setup →AWS End User Messaging
Native AWS messaging that lands on your existing AWS invoice — the natural choice if your infrastructure already lives in AWS.
AWS End User Messaging setup →Beyond this list
The SMS channel is backed by an adapter library covering 33 providers. The six above are the ones wired into self-service configuration today; the rest are unlocked on request, because each one needs its credential fields mapped and its delivery receipts verified before we let anyone rely on it.
- Two different numbers, deliberately. “Available now” counts providers you can connect unattended. The 33-provider figure counts adapters that exist in the SDK — most are not self-service yet.
- Need one that is not listed? Open the connection page in the console and register the request there, so it is counted rather than lost in an inbox.
- Custom or private gateways are a different job again — endpoints, signing and status mapping have to be built per provider. That is development work, not a configuration checkbox.
What every connection gets
- Credential custody. AES-256-GCM at rest, masked in the console, plaintext never logged and never returned to the browser. Rotate or delete at any time — the credentials are yours.
- Route selection and failover (SMS channel). Bind several providers and senders to one route, with priority and weight, so a provider outage does not stop the send.
- Pacing (SMS channel). Each connection has a send rate you control; we queue to that rate rather than firing as fast as the provider will accept.
- Delivery receipts and a send log (SMS channel). Metadata per message — time, recipient, provider, status, error code. Message bodies are never stored, so the log is safe to keep.
- One error vocabulary. Provider error codes are normalised so the same failure reads the same way across providers, with the raw provider code kept alongside.
What stays in your name
Because we never resell your traffic, there is nothing in the middle of the money — and nothing in the middle of your relationship with your provider.
- Your negotiated rate and your provider invoice, untouched
- Sender IDs, numbers and short codes, registered in your own name
- Your volume commitments, which never move to a balance we hold
- Your relationships with the carriers and networks you already send through