Bring your own account
The platform has no provider account of its own. That one design decision changes who owns the numbers, who holds the quota, and who appears on the invoice.
Read the guide →Bring your own provider accounts vs buying message credits from a platform
We connect to the provider accounts you already pay for, and we never sell you message credits. That one decision sets your rate, your switching cost, and who owns the relationship — everything below follows from it.
Why we connect instead of reselling
- Your rate is your rate — nothing is added on top of the price you already negotiated, because there is no balance in the middle to mark up
- Your commitment stays with your provider, so a change of tools never strands volume you already bought
- You remain the customer of record — for pricing, for registrations, for sender identity
- Disconnecting leaves your account untouched: leaving is a configuration change, not a migration
What a credit balance changes
A prepaid balance is genuinely simpler to budget — one invoice, one number to watch. What it moves out of view is the rate underneath: you know what you paid, not what the message cost. That is also why leaving a balance-holder means migrating accounts rather than changing a setting.
- Your provider invoice, at your rate — versus one blended balance
- Volume commitments you control — versus a balance somebody else holds
- Switching tools by changing configuration — versus moving accounts
How to get the most out of this model
Bring the account you already have and keep the registrations in your own name. The layer adds routing, pacing, receipts and logs on top; everything commercial stays exactly where it was, so there is nothing to unwind if you ever stop.
Questions this usually raises
- Does Whaleal take a margin on messages?
- No. There is no credit balance to mark up — you pay your provider directly, and the platform never sits in the middle of the money.
- Can I start with a single provider?
- Yes. Connecting one account is a fully supported setup, and it is where most teams start. Routing and failover are there for the day you add a second.
- What happens to our provider contract if we adopt the platform?
- It stays yours, on your terms and your rates. The platform is given credentials to send through the account and read status back — nothing more, and nothing that touches the contract.
Keep reading
Orchestration layer vs becoming your own BSP
We chose to sit above the provider APIs rather than hold carrier relationships — because that is the arrangement that keeps your rates, your registrations and your sender identity in your own name. Here is what that choice puts in your hands.
Open →Several connected accounts vs one
A single account is a single point of failure you cannot see breaking until customers tell you. Connecting a second turns that into failover you configure once — which is why routing belongs in the layer rather than bolted on later.
Open →Building the layer yourself vs using one
Calling a provider API takes an afternoon. Making messaging dependable is a list of unglamorous problems that only show up in production — and that list is what we maintain so your team does not have to.
Open →Sending straight from a provider vs through a layer
Sending direct is the fastest way to send the first message. The layer is what keeps messaging dependable once a second provider, a second team or a second failure arrives — and it adds nothing you have to migrate away from.
Open →Scope. Whaleal Messaging is an orchestration layer over the CPaaS or BSP accounts you already hold. Your contracts, your rates and your sender identities stay yours, and nothing in the middle reprices them. Comparisons here are architectural: they hold for any vendor you might choose, and depend on no third party's roadmap.