A multi-provider SMS gateway you install on your own infrastructure. Cut Twilio and LC Phone costs by 60–80%. Works with GoHighLevel and any CRM that supports webhook-based SMS.
Your gateway provider bills you like clockwork. Miss a payment, service dies. Try to scale, per-sub-account pricing bites.
Powering itself down when the battery gets tired. Losing signal when the cell tower reboots. Firing false heartbeat alerts at 3am when carrier service texts come through and confuse the health check.
In your country of business? Great. Travelling? Your gateway lives in a drawer 15,000km away.
AU SIM sending to a US number? Sometimes it works. Sometimes it doesn't. Sometimes it works for a week then stops. No visibility into why.
Raise prices. Get acquired. Shut down. Every SMS your business sends goes through infrastructure you don't control and can't audit.
Point your CRM at it. Point it at Telnyx, or a physical SIM device, or both. Your SMS flows through your code, on your servers, priced at wholesale carrier rates.
Total infrastructure cost at agency volume: ~$12/month. No per-seat fees. No per-sub-account fees. No vendor billing you every 30 days for the privilege of existing.
The examples elsewhere use ~150 outbound/month. Yours will differ. Run your actual volume through here.
| Monthly outbound | Traditional SIM service | Twilio via LC Phone | Gateway (Telnyx) | Gateway (Telnyx + SIM) |
|---|---|---|---|---|
| 500 | ~$97+ SIM | ~$40 | ~$14 | ~$6 + SIM |
| 2,000 | ~$97+ SIM | ~$160 | ~$52 | ~$18 + SIM |
| 5,000 | ~$97+ SIM | ~$400 | ~$127 | ~$42 + SIM |
| 10,000 | ~$97+ SIM | ~$800 | ~$253 | ~$83 + SIM |
The higher your volume, the bigger the win over Twilio/LC Phone. Traditional SIM services stay flat but cap out because they can't handle real scale reliably. Your Telnyx bill scales linearly with actual usage.
The actual code files, licensed to your agency, yours to deploy, modify, and extend.
Telnyx (cheapest international, US 10DLC compliant), Android SIM gateway (domestic-rate SMS via physical SIM), add your own in ~50 lines.
US-bound → US 10DLC number. International → the number that gets 2-way replies working. Documented and battle-tested.
Multi-tenant architecture serves every sub-account, every phone number, from a single Railway instance.
Every inbound, outbound, failure — timestamped, provider tagged, error captured. Your data. Your query.
Ed25519 webhook verification. Rate limiting. Secrets in env only. RLS-locked database. 75+ automated tests.
This isn't a hackathon project. It's the exact code powering my own agencies' SMS infrastructure right now — routing across multiple phone numbers, two countries, and two providers daily.
Live production traffic. This is the code you're buying.
I built this because I was paying $97/month for a SIM gateway service, dealing with false alerts, and locked to one carrier. Now I run everything on this code. My total monthly SMS infrastructure cost is under $15. When you buy the source, you're getting the same code I trust for my own business.
Stripe checkout. Get the full ZIP + license key delivered to your inbox within seconds.
Docker-ready. Push to Railway, Fly.io, or DigitalOcean. Env vars documented. Typical time: 15 minutes.
Configure GHL's Custom Conversation Provider (or your CRM's webhook) at your new endpoint. 15 minutes.
Total setup: 30–60 minutes if you're comfortable in a terminal. Comes with an interactive setup guide, a 12-minute Loom walkthrough, buyer-only Facebook community, and email support that doesn't expire.
Because sales pages that only list wins feel dishonest. Here's what you're not buying.
SMS-only in v1. Voice is fundamentally different infrastructure and would be a separate product.
No legitimate API exists. Every "iMessage from your CRM" service relies on Mac relay farms that Apple keeps killing. We won't build on sand.
Coming in v2 with a loyalty upgrade discount for v1 buyers. Apple added RCS support in iOS in late 2024, so iPhone recipients will get rich messaging features once we ship it.
v1 handles text SMS only. If your workflow is MMS-heavy, wait for v1.x or use Twilio direct.