FAQ

Cloudflare’s Email Service is for transactional email, like receipts and password resets, so it doesn’t allow newsletters or announcements. SES does, and it’s about as cheap as sending gets: $0.10 per thousand emails.

Rendering an email takes about 30 ms of CPU when a Worker starts cold, and the free plan allows 10 ms per request. Sendoff renders each issue once and fills in each person’s unsubscribe link, so sending stays cheap, but the render itself needs the headroom.

Mostly no, on purpose. There’s no admin dashboard: you draft, send and manage subscribers by talking to Claude or Codex. Any MCP client works, and the REST API covers signups and imports from your own code.

Sendoff makes it hard to send by accident. A send needs a test of the exact version, then a prepare step that returns a summary and a confirmation that expires in 15 minutes, and the agent is told to confirm only after you explicitly say to send. Keep the MCP token private: anyone with it can do what your agent can.

Clicks, yes: links go through your own Sendoff domain, and clicks from email security scanners are filtered out. Opens are off by default, because Apple Mail loads every image automatically, but you can turn them on. Ask your agent “how’s my latest send doing?” See Issue stats.

Only for commercial email, like launches and promotions: US and Canadian law require one there. It’s optional in Sendoff. Without one, each issue is checked before it’s sent, and any that reads as commercial is blocked until you add an address or rework it. See When you need a postal address.

You set the name or logo, the accent color, the footer links and the postal address. The layout itself is fixed and built to render consistently across Gmail, Apple Mail, Outlook and dark mode, so there’s no template to maintain.

One deployment sends to one list. There are no segments or tags.

In a D1 database in your Cloudflare account. Nothing goes to a third party except what SES needs to deliver each email. To leave, ask the agent to list your subscribers, or export the database with wrangler d1 export.

Not yet; a web archive, RSS and image uploads are planned. In the meantime, you can import past issues from another provider, so nothing you’ve sent is lost.