Deep Dive
7 min readSelf-hosting your email data in Cloudflare D1 (no vendor lock-in)
The architectural case for putting inbox and outbox in your own D1 database, and what that means in practice for compliance, exports, and exit plans.
Self-hosted · CFFlowmails
Runtime v0.1
Journal
Operator notes on Cloudflare-native email.
Long-form writing about self-hosted email in D1, Workers-native routing, the REST API, and the parts of the platform that show up in the security review.
Categories
Tags
alternativeamazon-sesapiauditautomationcatch-allcloudflarecloudflare-apicloudflare-email-routingcloudflare-workerscompliancecostcustom-domaincutoverd1data-residencydata-sovereigntydeep-divedeliverabilitydkimdmarcemail-routingemail-servicesemail-webhookhelpdeskhmacinboundleast-privilegelimitationsliteral-matchersmail-servermailgunmigrationmulti-tenantpostfixpostmarkpricingproduct-overviewr2resendrest-apiretryroute-tablesruntimescoped-tokenssecurityself-hostedsendsendgridspfsupportsupport-inboxtcotickettransactional-emailtutorialvendor-lock-inwebhookwebhooks
3 of 22 posts match
Deep Dive
8 min readHow Workers-native email routing actually processes your inbound mail
A tour of the runtime: Email Routing, the Worker, the R2 bucket for attachments, and the D1 tables behind a single inbound message.
Deep Dive
13 min readCloudflare Workers email cost — Workers + Email Services + D1 + R2
Cloudflare's email path runs through four primitives that each bill separately. Here's how Workers per-request, Email Services per-email, D1 read/write/storage, and R2 storage / operations stack up — and how to keep the bill predictable.