Cloudsteading
Submit

Use the existing project

This idea now points to a reviewed repository. The original build proposal is preserved below.

EmailFlare’s original admin template library and Welcome email preview, captured locally with synthetic variables and its Ocean theme. Template workflows were reviewed; actual email delivery and the separate team Inbox were not tested.
Existing project · Paid hosting baseline

EmailFlare

By 0xdps

Requires fixes before production use · see runtime findings on the project page

Editorial workflow alternative for transactional email APIs, templates, delivery records and suppressions. Local review verified admin/template workflows only, found the Worker Test Mailbox API missing, and did not test real email delivery, provider operations, SLAs or full integration parity.

EmailFlare has a documented low-volume paid Cloudflare path beginning with Workers Paid ($5 USD/account/month), with separately metered usage. Arbitrary-recipient email requires Paid; database, storage and email usage above included allowances add charges.

Explore EmailFlare →
MailySend dashboard overview showing 1,839 sent, 99.3% delivered and an hourly send curve
Existing project · Paid hosting baseline

MailySend

By gagndeep

Transactional send APIs, queued delivery and delivery-event management; upstream Resend API-compatibility claims have not been runtime-verified, and no full platform parity is asserted.

The Cloudflare Email Service path requires Workers Paid from $5 USD/account/month, includes 3,000 sends/month, then bills $0.35/1,000. Storage, queues and DO overages are additional. Analytics Engine is currently not billed, per its primary pricing page. SES, Resend and SMTP are alternative transports with separate provider fees; SMTP ingress requires an optional external shim.

Explore MailySend →
Original build proposal

The concept below is preserved for reference. Use the linked project above for its actual features, README and infrastructure.

Browse existing projects and remaining proposals →
Existing project selected
Original concept

Transactional Email Console on Cloudflare

Email templates, provider routing, event logs, webhooks, and suppression lists around Postmark or Resend.

replaces Postmarkreplaces ResendD1Email WorkersQueuesR2Workers
Postmark logo
would replace
Postmark· email

Transactional email delivery and email activity tracking.

How it would work

A URL goes in, an API-ready result comes out. These are the stages the request flows through.

  1. map01

    Map the rented workflow

    Identify the small-team job that actually needs replacing.

  2. build02

    Assemble the Cloudflare loadout

    Pick the primitives that cover the core data, compute, auth, and delivery path.

  3. ship03

    Publish the useful version

    Release a deployable build with limits, setup notes, and maintenance tradeoffs.

Concrete jobs it does

If you're paying Postmark for any of these, the proposed build would let you stop.

  • →Cover the small-team workflow people actually rent the SaaS for
  • →Expose a simple, deployable API
  • →Persist the right data in D1 and the right artefacts in R2
  • →Stay maintainable by one or two engineers

Config knobs

What you'll be able to tune from day one.

Workflow scope
core team workflow only
Deployment target
Cloudflare Workers + supporting primitives
Access model
simple auth and admin controls
Limits
documented scale and maintenance boundaries
proposed architecture

The Cloudflare loadout, wired together.

Architecture

Overview inferred from the listed Cloudflare services. Routes and connections have not been verified.

Public interface
Surfaces1
client / caller
interface not yet reviewed
↓
App
Workers
entry
request handler
↓
what each tool does
Cloudflare feature
D1tool 01
D1

Track crawl jobs, pages, status, users, limits, and API keys.

Email Workerstool 02
Email Workers

Use Email Workers for the part of the owned app that needs this platform capability.

Queuestool 03
Queues

Fan out background jobs so crawls can retry and continue after the first request.

R2tool 04
R2

Store raw HTML, screenshots, markdown output, and crawl artefacts.

Workerstool 05
Workers

Public API, routing, auth checks, rate limits, and orchestration glue.

will build
  • +The core workflow small teams actually use every week.
  • +A deployable Cloudflare-native version with clear setup steps.
  • +Basic auth, data storage, admin screens, and operational visibility.
  • +A writeup that explains the useful limits and maintenance burden.
will not build
  • -A pixel-perfect clone of the SaaS being replaced.
  • -Enterprise governance, compliance guarantees, or managed support.
  • -Every advanced feature that only large teams need.
  • -A promise that replacing the rented tool is always the right call.
readme

Transactional Email Console on Cloudflare

This candidate asks whether Postmark, Resend can be replaced by a smaller owned workflow on Cloudflare without pretending to cover the whole enterprise product.

What this is

The hard part of email is delivery, but the app layer around templates, logs, suppression, routing, and webhooks is very buildable.

How we would build it

Use D1, Email Workers, Queues, R2, Workers to cover the core workflow without adding rented infrastructure.

The honest limit

This should wrap existing email providers rather than become an SMTP network. It replaces the dashboard/workflow layer, not deliverability infrastructure.

Discussion · 0

sign in to comment →
No comments yet — be the first.