Title: I'm building a Resend alternative from Serbia — 40% cheaper, prices locked for 12 months
Resend doubled their prices overnight in October 2024. No announcement, no warning — just a doubled invoice.
I'm a solo developer from Serbia building apps with AI. Every app I build needs transactional emails. I was paying Resend $20/mo for 50k emails. Then it doubled.
So I decided to build my own.
PrimeTimeMail — a transactional email API for developers. Same AWS SES infrastructure as Resend under the hood. Simpler API. 40% cheaper.
Quick comparison:
50k emails/mo → Resend charges $20, we charge $12
500k emails/mo → Resend charges $90, we charge $49
One thing I promise that nobody else does: prices are locked for 12 months when you sign up. No overnight surprises.
Currently building in public. Backend is in progress, landing page is live.
If you're tired of email providers pulling the rug — join the waitlist: primetimemail.com
Would love feedback from anyone who's dealt with this problem.
This is a strong wedge because the pain is specific: developers do not just want cheaper email, they want predictable infrastructure pricing they can trust before transactional email becomes part of every app they ship.
I’d make that the center of the positioning. “40% cheaper” gets attention, but the 12-month price lock is the more trust-building promise. That is what makes this feel less like another low-cost clone and more like stable email infrastructure for solo devs and small teams.
One thing I’d pressure-test early is the brand frame. PrimeTimeMail is clear, but it may make the product feel more like a newsletter or general email tool than a developer-first transactional email API.
Xevoa .com would fit this direction better as a clean dev-infrastructure/workflow brand. Same product, same pricing promise, but with a name that can carry API, delivery, logs, automations, and developer trust if the product grows beyond the first Resend comparison.
Since the landing page is live but the backend is still in progress, this is the right moment to test the name before docs, API references, and waitlist users lock around the current frame.
Thanks for the thoughtful feedback. You're right — the price lock is the stronger promise and I should lead with that more.
On the name — fair point. PrimeTimeMail does lean newsletter. I'll pressure-test it with early users before committing to docs and API references. If it becomes a blocker, a pivot is still easy at this stage.
Appreciate you taking the time.
That makes sense, especially since the backend is still in progress.
The only thing I’d be careful with is waiting until the name becomes a visible blocker. With developer products, the brand starts getting baked in quietly through docs, API references, examples, waitlist emails, and early user memory before anyone explicitly says “the name is a problem.”
PrimeTimeMail is clear, but it makes people think email product first. The stronger version of what you’re building is closer to predictable transactional email infrastructure: price lock, API, logs, delivery reliability, and developer trust.
That is why Xevoa.com felt worth pressure-testing now. It gives you a cleaner infrastructure/platform frame while the product is still early enough to switch without much cost.
I would compare both names against the future product, not the current landing page: PrimeTimeMail for low-cost email, or Xevoa for stable email infrastructure developers can build on.
Good point on the brand baking in early. I'll keep Xevoa in mind as a benchmark — but for now I'm committing to PrimeTimeMail while the product validates. If the name becomes a real friction point with users, I'll know soon enough.
Appreciate the persistence on this — it's the kind of feedback that's easy to ignore and worth sitting with.
This comment was deleted a day ago.