Key Takeaways
- A bulk campaign on an open-source GitHub SMS gateway is still GSM on SIMs you own. Stars do not include consent.
- Checklist is opt-in source, STOP that sticks, quiet hours, staff canary, then pace. Not a hammer until the classifier blinks.
- OEM rate ceilings are so the production phone can send consented traffic. They are not unlimited carrier SMS and not a bypass.
- This is not SMS Gateway’s GitHub. DIY repos still need pairing, airtime, and a human who honors STOP offline.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Every row in the CSV still burns operator credit.
OSS GitHub is not a blast licence
Cornerstone: Android SMS gateway open source. Production hygiene: OSS GitHub production checklist. The forge is GitHub. Maintained bulk: bulk SMS from Excel and CSV.
If the campaign only works when you hide the sender or disable STOP, you do not have a GitHub problem. You have a consent problem.
Bulk campaign checklist
| Item | Pass | Fail |
|---|---|---|
| List | Documented opt-in | Purchased dump |
| Copy | Named sender, GSM-7 | OTP-shaped promo |
| STOP | Sticky, inbox awake | Keyword that only replies “ok” |
| Pace | Handset + fair-use | Hammer to “find the filter” |
| Radio | Promo SIM, charged | Shared with login OTP |
One radio, operator fair-use
Raise OEM/Android SMS rate ceilings if the phone throttles consented send. That is not unlimited operator SMS. Ethics (no evasion): spam-filter ethics. Careful ramps: load test carefully. Industry baseline: CTIA.
Ship a campaign without becoming a filter story
- Prove opt-in per row. Source stored next to the MSISDN. Drop harvested dumps. Export STOP flags before you migrate repos.
- Identify the sender in every PDU. Program name. Recipients should know who is texting.
- Wire STOP before the first wave. Keyword to sticky suppression. Inbox must be awake or STOP sits on the SIM.
- Canary staff numbers at campaign pace. Not a 10k RPS script. Watch DLR unknown and pairing.
- Pace like a handset. Raise OEM ceilings if Android throttles consented send. Do not snowshoe SIMs to dodge caps.
- Keep OTP on another radio. A filtered promo CLI must not take login down.
STOP product: auto-reply and STOP. Quiet hours: scheduled SMS.
Never share the auth SIM
OTP verification and multi-device. Dual SIM ≠ spare campaign modem.
Airtime still counts
Service pricing is based on device count and total SMS sent through the gateway. You need a working Android phone with a SIM and SMS credit from your mobile operator. Operator message costs are yours—we do not sell carrier SMS balance. OSS does not include pulsa. Maintained from $19/month; Free 300 SMS lifetime is not a campaign. Device and SMS volume pricing.
Next steps
Consent on the row, STOP that sticks, staff canary, promo off OTP. Then decide if DIY GitHub is worth the 2am pairing.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- bulk SMS from Excel and CSVSpreadsheet campaigns
- bulk SMS with consent best practicesHigh-volume outreach
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
