Cloudflare Email Service

Post by jedberg » Thu, Apr 16, 2026, 6:39 PM UTC

written-beyond wrote: post #124

jedberg wrote: post #117

Earlier quoted context omitted.

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.

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 gla…

Post by stewartjarod » Thu, Apr 16, 2026, 6:50 PM UTC

STRiDEX wrote: post #53

bdangubic wrote: post #31

Earlier quoted context omitted.

Resend will change the pricing - guaranteed. Not sure how soon but I'd expect very soon.

I guess if they're big enough they should be working on moving off of amazon SES for emails and warming up ip addresses? Otherwise they need to keep a markup on top of amazon. Edit: didn't realize people were paying resend $20. AWS already exists at a low price and people pick them anyway, i'm sure they're fine.

Post by chinathrow » Thu, Apr 16, 2026, 6:58 PM UTC

thomas_gauvin wrote: post #70

embedding-shape wrote: post #49

Earlier quoted context omitted.

> But getting back to the consensus in the comments here: I'm not sure why people think that they'll be worse about policing spam than AWS SES, Azure Email, etc. Cloudflare is (in)famous for not acting against spammers, fraud, piracy and other less savory groups that are hosting their stuff at/behind Cloudflare, so reasonably, people who've been affected by that are now afraid the same thing will happen with email.

Blog author chiming in here: We have reserved IPs for Email Service and will be protecting the reputation and fighting spam from originating on Email Service. If we did not do so, our IPs would get flagged and then emails end up in spam or not delivered. That defeats the purpose of having a transactional Email Service. We're well aware of this.

Post by purrcat259 » Thu, Apr 16, 2026, 7:05 PM UTC

written-beyond wrote: post #91

nope1000 wrote: post #29

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.

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.

Post by karimf » Thu, Apr 16, 2026, 7:17 PM UTC

tracker1 wrote: post #133

karimf wrote: post #82

Ok I just tried the service since I want to migrate from Resend. Seems like you can only send email via the worker or REST API for now? Can I send via SMTP? I'm using Supabase and it needs the SMTP credentials. I can't find anything on the dashboard or on the docs, even though last year they said it supports SMTP [0] [0] https://blog.cloudflare.com/email-service/

Not to oversimplify the issue... but you could probably run a small VPS and SMTP relay service that requires tls+auth and just relays all email from your domain through to API calls. You could probably get something operational in a couple hours with Claude Code. My first thought in reading this would be using this service and the default mail app's structure to back end typical email protocols so you can still use a…