9
3 Comments

Twilio made SMS API complicated. We made it 5-minutes simple.

We've been building ReSMS for 2 month now, an SMS API focused on indie hackers (you!) and small teams.

Yes, going after Twilio is bold and no, we’re not 100% there yet. I wanted to share what we’re doing, what’s working, what isn’t, and ask for brutally honest feedback.

Why another SMS API?

Over the past few years I kept hitting the same walls using Twillio SMS API:

  • Setup friction: it can take hours/days to send your first SMS.

  • Pricing surprises: pay-as-you-go that snowballs, weird surcharges, country quirks.

  • Console complexity: way too much if all you want is OTPs or alerts.

  • Sender IDs hell: every country has different rules, you end up filling forms manually.

ReSMS is our attempt to make the “80% case” stupid-simple and predictable.

What we’re building

We’re aiming to make the “get going” part take 5 minutes, not half a day.

  • SDKs in multiple languages: Python, JS/TS/Node, Java. Go & Rust are on the way.

  • Automatic Sender ID registration: instead of throwing docs at you, we handle the per-country registration process behind the scenes.

  • Opinionated defaults: retries, opt-outs, deliverability reasons that humans can read.

  • Predictable pricing: monthly plans, not pay-as-you-go. You know exactly what you’ll pay, adapted to your needs.

Dev-X (how it feels)

  1. Register at resms.dev

  2. Generate your API key

  3. Add our library:

    npm i @resms/sdk

  4. Select a plan (resms.dev/dashboard/settings/billing)

  5. Then add the code, for instance:

    import { ReSMS } from "@resms/sdk";

    const resms = new ReSMS("re_12345");

    await resms.sms.send({ to: "+33612345678", message: "Welcome to ReSMS!", });

Where we’re worse than Twilio (today)

  • Coverage is still expanding country by country (currently 30 available).

  • SMS only (no voice, no WhatsApp).

  • Compliance automation is strong in the EU, less polished in the US (10DLC still a pain).

We’ll post follow-ups with concrete metrics (deliverability, latency, cost comparisons) and share the good/bad of early migrations.

posted toAvatar for product ReSMS
ReSMS
  1. 1

    Really like the way you’re tackling this 👏. Twilio is super powerful but honestly overwhelming when you just want to send simple SMS. Cutting setup down to 5 minutes and making pricing predictable sounds like a huge win, especially for small teams.

    The automatic Sender ID registration is also a killer feature — that’s one of those pain points most devs underestimate until they face it.

    Curious though: how are you handling scaling and reliability as more countries come on board? That’s usually where the complexity creeps back in with SMS APIs.

    Excited to follow your updates — please do share those early migration metrics when you have them!

  2. 1

    Sender ID can be tricky - in my country it’s required, otherwise the SMS won’t get delivered. I used to use Twilio, but the user experience wasn’t great. When they dropped their free SMTP plan it was pretty disappointing. There should be a more user-friendly alternative.