What a 24-hour Cloudflare sign-in guarantees you
What the OAuth grant actually gives Flowmails, when it expires, and why the platform keeps no long-lived credential for your account.
Journal
Long-form writing about provider-connected email, provider-native routing, the REST API, and the parts of the platform that show up in the security review.
Categories
Tags
9 of 25 posts match
What the OAuth grant actually gives Flowmails, when it expires, and why the platform keeps no long-lived credential for your account.
How to hand an AI agent a mailbox it can call on your own domain: a contract it cannot misremember (the skill), a key it cannot overspend, and an inbox it can verify — without inventing the API.
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 one email platform, not another SaaS.
Transactional-email pricing splits into per-email fees (Resend, SendGrid, Mailgun, SES), bundled tiers (Postmark Pro), and flat platform fees (provider-connected 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 one shared worker. Per-tenant routing, metadata injection, webhooks, and the schema to back it.
An email API starts with where the data lives: one hosted worker scoped by domain id, and what that means in practice for compliance, exports, and exit plans.
A tour of the runtime behind Flowmails: Email Routing, the shared worker, the per-domain routing address, and the tables behind a single inbound message.
The exact permissions Flowmails needs, the principle of least privilege, and the audit trail you can show your security reviewer.