Self-hosted vs per-message cloud SMS gateways
Both approaches send SMS from your software, but they differ in cost model, sender identity and who holds control. This is a comparison of the two categories — not specific vendors — to help you choose the right fit.
The two models in a sentence
A self-hosted SMS gateway sends through a SIM in a device you control, so messages go from your own number and your marginal cost is whatever your carrier already charges. A per-message cloud SMS gateway routes your messages through a provider's carrier connections and bills you for each one, typically from a shared shortcode or a registered sender ID.
Side by side
| Category | Self-hosted gateway | Per-message cloud gateway |
|---|---|---|
| Cost model | Your existing mobile plan; no per-message markup | Priced per message, often plus number/keyword fees |
| Sender identity | Your own number and SIM | Shared shortcode or rented sender ID |
| Control of data | Runs on hardware you own | Routed through the provider's platform |
| Setup effort | Install an app, pair a phone | Account, compliance and number provisioning |
| Throughput | Bounded by the handset and SIM | Carrier-grade, very high volume |
| Global reach | Best for your own region/number | Many countries via carrier routes |
Where self-hosted wins
If you message at low-to-moderate volume, value sending from a recognised number, and want to keep costs and data under your own roof, self-hosting is usually the better fit. It is ideal for two-way conversations — sales follow-ups, support, appointment confirmations — where replies to your real number matter more than raw throughput. There is no per-message bill to watch and nothing shared with other senders.
Where cloud per-message wins
If you send enormous volumes, need to reach many countries at once, or require carrier-grade compliance and registration handled for you, a per-message cloud provider is built for that scale. The trade-offs are ongoing per-message cost, a sender identity you rent rather than own, and your traffic flowing through a third-party platform.
How to choose
- Pick self-hosted when conversations, your own number, predictable cost and data control matter most.
- Pick cloud per-message when massive, multi-country, high-throughput delivery is the priority.
- Consider both — many teams self-host their two-way and domestic traffic and reserve a cloud route for bulk international sends.
Scan to install
Try the self-hosted approach
Install the Android app, pair your phone, and send your first message from your own number.
Related
Send from your own SIM · SMS for your ERP · Self-hosted OTP · REST API reference