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, email and WhatsApp accounts you already pay for
Whaleal Platform 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.
SMS — 6 providers available now
Text messages over the provider account you already hold. 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 →Email — 4 providers available now
Transactional and inbound mail over the mail account you already hold. Self-service: create the connection in the console yourself, no conversation with us required. Each page lists the exact credential fields that provider needs.
Resend
A developer-first mail API. The connection needs a single key, and the provider reports delivery and inbound mail back over a signed webhook — which is the only email path where the console can show you what happened after acceptance.
Resend setup →Mailgun
Send from a domain you have verified in Mailgun. The connection carries both the key and the domain, so it is unambiguous which identity a message leaves as.
Mailgun setup →SendGrid
A mail API you can reach with a restricted key. SendGrid returns the message id in a response header, and that id is what the send log stores.
SendGrid setup →Postmark
A transactional-first mail provider. Sending is authorized by a server token, and the From address has to match a confirmed sender signature in the account.
Postmark setup →WhatsApp — 3 providers available now
Business messages sent from your own WhatsApp Business account. Self-service: create the connection in the console yourself, no conversation with us required. Each page lists the exact credential fields that provider needs.
Meta WhatsApp
The direct route: your own WhatsApp Business account, your own number. Messages go out from the phone number ID you configure, and the status Meta reports back is normalized into the same statuses as SMS.
Meta WhatsApp setup →360dialog
A Meta Business Solution Provider. The request and response shapes are the Cloud API’s, but the account and its paperwork go through 360dialog rather than through Meta directly.
360dialog setup →Twilio WhatsApp
If you already send SMS through Twilio, this is the same account with a WhatsApp-enabled number. The credential fields are literally the same two, so there is nothing new to look up.
Twilio WhatsApp setup →Beyond this list
Everything above is wired end-to-end in the console, and it is the same set you see when you open the connection page. What sits behind it is a per-channel adapter library, which is why a provider we do not list yet is a build rather than a rewrite.
- Two different numbers, deliberately. “Available now” counts provider accounts you can connect yourself, across all three channels (6 on SMS, 4 on email, 3 on WhatsApp — 13 in total). The 33 figure counts SMS adapters in the SDK, which is a different thing: adapters are per-vendor code paths, some of them address the same vendor’s regional endpoints, most are not self-service yet, and the number says nothing about email or WhatsApp.
- 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.
- A send log for every message. Metadata per send — time, recipient, provider, channel, status, error code — on all three channels. Message bodies are never stored, so the log is safe to keep.
- Delivery receipts, normalized. Where the provider reports delivery back (every SMS provider, Resend on email, Meta on WhatsApp), the outcome is normalized into one status and can be pushed to an endpoint you configure.
- One error vocabulary. Provider error codes are normalized so the same failure reads the same way across providers and channels, with the raw provider code kept alongside.
- Route selection and failover (SMS channel). Bind several providers and sender numbers to one route, with priority and weight, so a provider outage does not stop the send.
- Pacing to the quota you actually have (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.
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 on SMS; verified domains on email; the business account and number on WhatsApp
- Your volume commitments, which never move to a balance we hold
- Your relationships with the carriers and networks you already send through