Key Takeaways
- Android SMS gateway open source self-hosted means you run the control plane and still keep a phone on a SIM.
- Do not rewrite the open-source hub; this spoke is panel/server ops.
- Self-hosting does not include operator airtime or remove OEM battery work.
- Air-gapped LAN paths are a real reason to DIY. “Free forever cloud SMS” is not.
- You own TLS, backups, and CVEs on the panel. The SIM still Dozes.
- A maintained SaaS plane trades that for a device + volume fee — phones stay yours.
Self-host the panel, not the radio
Android SMS gateway open source self-hosted is the search for a panel on your VPS plus an Android that actually sends. You take TLS, backups, upgrades, and 02:00 disk-full. The radio path does not move into the rack. The phone still needs pairing, OEM exemptions, and a voucher.
Category comparison: open-source hub. Related bulk spoke stays separate. Product setup if you pick the maintained plane: device setup.
“Self-hosted means you own the outage ticket. It does not mean the SIM lives in nginx.”
Hub owns the OSS category
README red flags, license notes, and when SaaS wins stay on the hub. This page is ops: what you run when the control plane is yours. Live parameters for this product remain in the Developer Center— a random self-hosted fork is not our API.
What you operate when you self-host
| Layer | You own on DIY | Still true on SaaS plane |
|---|---|---|
| Panel / API | VPS, TLS, backups, CVEs | Vendor operates the plane |
| Android app | Sideload, OEM, pairing | Same class of phone ops |
| SIM / airtime | Yours | Yours |
| DLR / webhooks | Your endpoint, your HMAC | Webhooks |
| Devices | Whatever you wire | Plan caps 1 / 2 / 5 / 15 |
When air-gap is the reason
LAN-only, no third-party control plane, regulated sites — those are honest DIY reasons. “Avoid a subscription so SMS is free” is not: operator credit remains, and staff time is the real meter. If zero phone ops is mandatory, evaluate CPaaS instead of either path. Twilio vs Android SMS gateway.
TLS, keys, updates
Self-hosted panels that listen on HTTP are a gift. Rotate keys after contractors leave. Do not log full OTP bodies into shared Slack. HTTPS webhooks. External TLS baseline: Mozilla SSL Configuration Generator.
Cost
DIY TCO is VPS + labor + phones + airtime. Maintained TCO is device + platform volume + phones + airtime. We do not sell prepaid carrier packs. Free 300 lifetime / Developer 25,000 per year if you use this product. Pricing.
Checklist
- Written reason for self-host (policy/air-gap), not “SMS should be free.”
- TLS, backups, update owner named.
- Phone OEM exemptions still on the runbook.
- Webhook signatures on your callback.
- OTP isolated from any bulk job on that panel.
Next steps
Open-source hub, features, Android app.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
- SMS API documentationLive endpoint reference
- download the Android gateway appGet the APK
