I built a Resend alternative from Serbia — waitlist is open, looking for first feedback
I got tired of Resend pulling the rug on pricing.
In October 2024 they doubled prices overnight. No warning, no email — just a doubled invoice. I was building AI apps and every single one needed transactional email. That was the moment I decided to build my own.
So I started PrimeTimeMail — a transactional email API for developers. Same AWS SES infrastructure under the hood. Simpler API. 40% cheaper than Resend.
One promise I'm making that nobody else does: prices are locked for 12 months when you sign up. You won't wake up to a doubled invoice.
Where I'm at right now:
Landing page is live
Backend is running locally (register, API key auth, send, list emails — all working)
AWS SES production access pending
Waitlist is empty and I need first humans to tell me if this is useful
If you've ever been burned by an email provider — I'd love to hear about it. And if this sounds useful, the waitlist is open: https://primetimemail.com
Not asking you to pay anything. Just asking: would you use this?
This is a clear wedge because transactional email is one of those tools developers only think about when pricing, deliverability, or API friction suddenly becomes painful. The 12-month price-lock angle is actually the strongest part because it gives people a simple reason to try a new provider instead of just comparing you feature-by-feature against Resend.
The thing I’d pressure-test early is the product name. PrimeTimeMail explains email, but it also keeps the product boxed inside “mail provider” language. If the roadmap ever expands into logs, templates, routing, webhooks, alerts, deliverability insights, or developer messaging workflows, the name may start feeling more narrow than the infrastructure layer you are building.
Before waitlist users, docs, API keys, and developer memory build around the current name, I’d think through whether you want a broader developer-platform brand.
Xevoa .com would fit that direction better because it can carry transactional email today, but still leaves room for messaging workflows, developer APIs, alerts, and automation without sounding limited to mail only.
Appreciate you coming back with more detail. The platform direction makes sense and the naming concern is noted — I'll revisit it before docs and API keys lock the brand in. For now, shipping is the priority.
That is the right priority. I would not slow shipping down for a long branding exercise.
The only reason I’d pressure-test it now is because developer infrastructure names get harder to change once docs, API keys, examples, waitlist emails, and early integrations start forming around them.
PrimeTimeMail is clear for the first wedge: transactional email with predictable pricing. But if the product becomes a broader developer messaging layer, the name may keep pulling people back to “email provider” even when the platform is moving into routing, logs, alerts, templates, webhooks, and workflow automation.
That is why Xevoa.com feels worth comparing before those surfaces lock in. It gives you a cleaner platform shell without fighting the current product direction.
So I agree: ship first. I’d just make the name call before the first serious developer-facing assets become expensive to unwind.
Fair point on the naming ceiling — noted for when the platform expands. For now, shipping beats renaming. Will revisit before docs and API keys lock it in.