[nope1000]

It's funny. All the examples they show in the blogpost are just things that were already pretty easy without agents. Sending an email when the CI pipeline passes, when a support request is incoming, when an order is shipped. I think we haven't found a problem for this solution.

[written-beyond]

The problem is how bullshit transactional emails are when you're outside of AWS. If you're not expecting to use 10,000 emails a month but would like the option to go over the free tier without committing to 10,000 more. Just let me pay per use FFS.

[jedberg]

The reason AWS does that is because there is a lot of base level work to verify you as "not a spammer" and to keep verifying you. So this is their way of making sure you pay the base cost.

They could price per use, but it would have to start with a base fee that is about the same at 10,000 emails.

[written-beyond]

The base fee doesn't need to be monthly, they can take $50 dollars as a one time registration verification fee. That should be enough to cover their compute costs for the year, specially when you pool in that from multiple customers. Who is spamming with 100 monthly emails? How much compute do they need to verify you aren't spamming. They can bake all of that into the pay per use price, they choose not to and I'm glad cloudflare is offering this.

[jedberg]

Maintaining the reputation of an IP address is the issue here. If one bad actor sends just a few emails that get marked as spam, the entire IP gets marked as bad. That's basically what you're paying for.

Also, the person who just wants to send a few 100 emails a month is actually far more likely to be a spammer. So it's also a way for them to eliminate those folks.

And lastly, the support burden can be high.

AWS has basically said they only want serious customers, let the other guys worry about the small senders.

[purrcat259]

Scaleway TEM offer pay per use. I moved off of resend when my side project went beyond their free tier and now pay <0.5€ a month