Cloudflare API token permissions, explained
The exact scopes Flowmails needs, the principle of least privilege, and the audit trail you can show your security reviewer.
Journal
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
7 of 22 posts match
The exact scopes Flowmails needs, the principle of least privilege, and the audit trail you can show your security reviewer.
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.
A tour of the runtime: Email Routing, the Worker, the R2 bucket for attachments, and the D1 tables behind a single inbound message.
Cloudflare Email Routing is the world's best front door for inbound mail. It isn't a database, an inbox UI, a REST API, or a send path. Here's what you add — and why the answer is a self-hosted Worker, not another SaaS.
Transactional-email pricing splits into per-email fees (Resend, SendGrid, Mailgun, SES), bundled tiers (Postmark Pro), and flat platform fees (Cloudflare-native stacks like Flowmails). Here's the same-volume comparison.
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.
Run support@, billing@, and abuse@ inboxes across tenants on a single Cloudflare Worker. Per-tenant routing, metadata injection, webhooks, and the D1 schema to back it.