151–160 of 277 posts
I think if you’re targeting developers, SES is your biggest competitor. Their very cheap pay as you go pricing is more attractive than your monthly pricing. If email templates with react is your usp, I think I’ve seen libraries that offer that already.
Earlier quoted context omitted.
> Most people doing anything of medium complexity is already using some abstraction layer, such as MJML Citation needed. I’m an admin for the largest email community online (emailgeeks) and when folks talk about code, everyone is talking about writing this stuff by hand.
Manual coding is getting very inefficient since it takes hours plus it requires a lot of testing (ie with litmus or emailonacid). There are modern alternatives to manual coding both for developers (embeddable editors for SAAS) such as beefree, unlayer, chamaileon, stripo and for email designers like beefree, stensul, knak, stripo, taxiforemail...
Once that’s done it does drastically improve the speed of email creation though.
Microsoft Azure offering https://learn.microsoft.com/en-us/azure/communication-servic...
• $0.00025 x 1,000,000 = $250 for sending emails
• $0.00012 x 10 KB x 1,000,000 = $1.2 for transferring data
• Total cost = $251.2
Earlier quoted context omitted.
Could you not find a million other ways to provide this feedback less abrasively? People like you unnecessarily exacerbate the stress of launching a new endeavor.
I'm sorry was I not asked to give feedback on a launch post? Did you not see this line: > I would love to hear your ideas, experiences, and feedback on any and all of the above.
What i would really love to see in a developer email service is also some workflows baked into the emails. There's a ton of times you would want to wire up a service and just set it for transactional events but also as sequences and with a default set of templates wired up. Think Zapier meets Sendgrid for emails and a set of templates maybe wired for default dev flows like Signup, Verification, Billing receipts. We d…
2 points I would bring :
- You need a cheaper plan. Mailgun have their flex plan that's 0$ for 1000 emails per month, and then 1$ for any extra 1000. It would cost more to send 50k emails, but I'm not there yet, I need a cheap starter plan with a lot less emails. My total infra cost is going to be around 30$, so I'm not going to drop an extra 66% to send maybe 1000 emails per month.
- If I reach my plan limits, you need to still deliver my emails and I' ll happily pay for them. Your FAQ says : If you exceed your plan limits, you will be notified and given the option to upgrade to a higher plan. If you don’t upgrade and repeatedly exceed your plan, your account may be temporarily deactivated.
My platform relies on emails to register users, MFA backup and transactions invoices. So if my email provider doesn't send my emails, my platform is broken. Yes, I could "just" keep an eye on my usage, look at it multiple times per day. I could also take some of my time to put some monitoring in place to wake me up at 3AM if there's a spike in traffic and I need to upgrade my plan.
Or, I can do none of that and register to a Mailgun Flex plan, or a 20$ Sendgrid plan, and not spend my time babysitting my email provider. Both Mailgun and Sendgrid allow going over plan quota and just charge you a premium. Don't not deliver emails, you're an email provider, that's disruptive.
Earlier quoted context omitted.
Looks like they're using AWS SES. From personal experience, none of them (SES, Mailgun, Sengrid) are suited for critical, transactional emails. I'm working in the same space and we're running our own backend.
@ctas since you're running your own backend, how did you solve the reputation problem to ensure good deliverability? I would have thought that using a dedicated IP on an existing provider like Sendgrid would be the best solution for critical transactional email.
We run an exclusive transactional email service, meaning customers go through an approval process before they can send live emails. Transactional emails by definition are sent as a reaction to a users' action and _should_ therefore have a low spam-rate and fast time-to-open. If you can ensure that your customers are good email citizens and actually send only transactional emails, you don't even need to upsell dedicated IPs to your customers, as the deliverability of a high-quality, shared IP pool is better than that of an isolated IP address.
Email is in my bio, if you have other questions.