Originally published at devtoolpicks.com
Twilio's SMS pricing looks reasonable until you read the invoice.
The advertised US rate is $0.0079 per message segment. Then the carrier surcharges land. AT&T, T-Mobile, and Verizon each add roughly $0.003 to $0.005 per segment on top, which pushes the real cost to around $0.011 to $0.013. And before you send a single message, US application-to-person SMS requires A2P 10DLC registration: a brand fee, a per-campaign vetting fee, and a monthly charge per campaign. For a solo founder sending OTP codes or order updates, the base rate was never the whole story.
Here's the short version. Telnyx is the cheapest carrier-grade option at $0.004 a segment. Plivo is the closest thing to a drop-in Twilio replacement. Vonage has the best built-in Verify API if OTP is your use case. Amazon SNS is the pick if you already live in AWS. And Bird is the one to look at for SMS plus WhatsApp in one place.
Five alternatives below, with real US pricing and who each one is wrong for.
Does switching from Twilio avoid A2P 10DLC fees?
No, and this trips people up constantly. A2P 10DLC registration and the carrier surcharges that come with it are set by the US carriers, not by Twilio. Every provider here enforces the same brand and campaign registration through The Campaign Registry, and the same per-message carrier fees apply on top of whatever the provider charges. Switching away from Twilio lowers your per-segment base rate. It does not get you out of the paperwork or the carrier fees. Keep that in mind when you compare the numbers below, because those numbers are base rates.
What actually drives your SMS bill?
Four things move your invoice, and only one of them is the headline per-segment rate.
Message segments come first. Carriers count a segment as 160 characters of plain GSM-7 text. Go over that, or drop in an emoji or a non-Latin character, and the message shrinks to 70 characters per segment and splits into more billable parts. A chatty OTP message with a branded footer can quietly cost double what you budgeted.
Then there's number rental, a flat monthly fee per phone number, usually $0.80 to $1.15. Verification is its own line if you use a managed OTP product like Twilio Verify or Vonage Verify. And the carrier surcharges and monthly A2P 10DLC campaign fees sit on top of all of it, roughly the same across every provider.
The practical takeaway: keep transactional messages short and inside a single GSM-7 segment, rent the minimum numbers you need, and compare providers on the all-in number rather than the advertised base rate.
Quick verdict
| Tool | Best for | US SMS (per segment) | Rating |
|---|---|---|---|
| Telnyx | Cheapest carrier-grade SMS and voice | $0.004 outbound | 4.6/5 |
| Plivo | Near drop-in Twilio replacement | $0.0077 outbound | 4.5/5 |
| Vonage | OTP and 2FA with a Verify API | $0.0081 outbound | 4.1/5 |
| Amazon SNS | AWS-native transactional SMS | ~$0.005 plus carrier fee | 4.0/5 |
| Bird (MessageBird) | SMS plus WhatsApp and email in one | Quote-based | 3.8/5 |
| Twilio | Broadest CPaaS ecosystem | $0.0079 outbound, plus fees | 4.0/5 |
Telnyx: the cheapest carrier-grade option
Telnyx is the cheapest credible option here, and it's cheap because it owns its network. Instead of renting routes from carriers like most CPaaS providers, Telnyx runs its own private IP backbone and connects to carriers directly. That's how it prices US outbound SMS at $0.004 a segment, roughly half Twilio's base rate, with inbound at the same $0.004 and local numbers from $1 a month.
The developer experience matches the price. The Mission Control dashboard is clean, the docs are detailed, and every account gets free 24/7 support from in-house engineers rather than a ticket queue. It covers SMS, MMS, voice, SIP trunking, number lookup, and a Verify API for OTP. For a technical solo founder, this is Telnyx at its best: cheap, fast, and flexible, with pay-as-you-go billing.
Who should not use Telnyx: non-technical builders. The platform assumes you're comfortable with telecom concepts like SIP trunking and inbound trunk groups, and there are no pre-built no-code flows, so no Zapier or GoHighLevel recipes out of the box. There's also no free plan; you fund a pay-as-you-go balance. And the carrier surcharges still stack on top of that $0.004, the same as everywhere else.
Plivo: the near drop-in Twilio replacement
Plivo is the one to pick if you already run Twilio and just want the bill to shrink. Its API was designed to mirror Twilio's, PlivoML maps closely to TwiML, and the SDKs cover the same languages, so migrating is usually a matter of hours or days rather than a rewrite. US outbound SMS is $0.0077 a segment, inbound is $0.0055, and numbers start at $0.80 a month, all with a 99.99% uptime SLA and no monthly minimum.
You get SMS and voice together with a clean API and transparent US pricing. For most teams already comfortable with Twilio's patterns, Plivo is the lowest-friction way to cut costs without retraining anyone.
Who should not use Plivo: teams leaning on Twilio's wider ecosystem. If you use Twilio Studio (the visual flow builder) or Twilio Functions (serverless), Plivo has no direct equivalent, so you'd rebuild those flows. Its integration library and non-messaging product range are smaller than Twilio's, and support depth varies by plan. The per-segment saving over Twilio is real but modest at list price, so the bigger wins show up at higher volume.
Vonage: the pick for OTP and verification
Vonage, formerly Nexmo, isn't the cheapest here. US outbound SMS runs about $0.0081 a segment, roughly the same as Twilio. You pick Vonage for two other reasons: its Verify API and its global reach. The Verify API handles OTP and 2FA across SMS, voice, and WhatsApp, and you only pay for successful verifications, which takes the retry and fraud logic off your plate. Coverage spans 190-plus countries with adaptive routing that fails over between carriers to protect deliverability.
It's a mature platform, now owned by Ericsson, with a large developer base and a straightforward pay-as-you-go model.
Who should not use Vonage: anyone chasing the lowest US SMS price. On raw US segments it doesn't beat Twilio, let alone Telnyx or Plivo, so if cost is your only driver, look elsewhere. The documentation also trails the market leaders for complex scenarios. Vonage earns its place when OTP verification or wide international coverage matters more than shaving a fraction of a cent off each domestic message.
Amazon SNS: the AWS-native option
If your stack already lives in AWS, Amazon SNS, now billed under AWS End User Messaging, is the least-friction option because there's no new vendor to onboard. You send SMS through the same SDK and IAM permissions you already use, and it's cheap: the AWS message fee is $0.005 per outbound message, and with the US carrier fee it lands somewhere around $0.006 to $0.008 a segment. Response times are fast and it scales without you thinking about it.
The catch is that it's infrastructure, not a product. There's no messaging dashboard, no visual flows, and no hand-holding.
Who should not use Amazon SNS: anyone who wants a polished messaging platform, or anyone not already on AWS. New accounts start in an SMS sandbox and need a support request to reach production, the default spend cap is $1 until you raise it, and there's no SMS free tier, so every message is billed from the first one. It's a great transactional-SMS pipe for AWS-native teams and a poor fit for everyone else.
Bird (MessageBird): the omnichannel pick
Bird, the platform formerly known as MessageBird, is the omnichannel choice. Instead of just SMS, it bundles WhatsApp, email, and Messenger into one product with a visual Flow Builder that lets non-technical teammates design messaging workflows without code. If you want to send a login code over SMS, a receipt over WhatsApp, and a newsletter over email from a single vendor, this is the shape that fits.
It's an established European platform with more than 15,000 customers and SOC 2 and ISO 27001 certifications.
Who should not use Bird: developers who want transparent, predictable API pricing. Since the rebrand from MessageBird, published SMS rates have become harder to pin down and are largely quote-based, so confirm current US pricing with Bird before you commit. The product has also broadened toward marketing and CRM rather than a pure developer API, and the roadmap has shifted more than once. If you only need a clean SMS API, one of the developer-first options above will serve you better.
How do you choose the right one?
Start from the reason you went looking.
- You want the lowest US SMS price: Telnyx at $0.004 a segment, if you're comfortable with telecom-grade tooling.
- You're already on Twilio and want to cut the bill fast: Plivo. Near drop-in API, migration in hours.
- Your main use is OTP or 2FA: Vonage's Verify API, or check whether your auth provider already does it.
- You live in AWS: Amazon SNS. Cheap and native, no extra vendor.
- You need SMS plus WhatsApp and email: Bird.
One more honest option: you might not need an SMS provider at all. If SMS is purely for login codes, email OTP costs a fraction of a cent and skips 10DLC entirely, and several auth platforms ship verification out of the box. Weigh that before you wire up any of these.
A note on what's not here: Sinch and Bandwidth are strong SMS providers, but they're built for enterprise volume. Bandwidth matches Telnyx at $0.004 a segment yet onboards through sales and really wants a million-plus messages a month, and Sinch sits around $0.0065 as a global enterprise default. Neither is a natural fit for a solo founder, which is why they're not in the main list.
The verdict
For most indie hackers, Telnyx is the smartest default. It's the cheapest carrier-grade option, the developer experience is strong, and free 24/7 engineer support is rare at this price. If you're already running Twilio and don't want to touch your integration much, Plivo gets you most of the savings for a fraction of the effort. Choose Vonage when OTP verification is the whole point, and Amazon SNS when you're deep in AWS already.
Twilio is still the most complete platform, and if you need its full range of channels and integrations, it earns the premium. But for a solo founder sending order alerts and login codes, you're paying enterprise prices for a text message. The cheaper options here do the same job, and the only thing you can't escape is the 10DLC paperwork, which follows you no matter who you pick.
If you're mapping out the rest of your messaging stack, our Resend vs Postmark vs Mailgun comparison covers the email side, and if SMS was only ever for login codes, Clerk vs Auth0 vs Supabase Auth shows which auth tools handle verification for you. For the rest of your backend, see our Supabase alternatives and Sentry alternatives guides.
Top comments (0)