# The publication is the product: archive, feed, and inbox

> A newsletter platform with RSS, a public web archive, hosted subscribe pages, and signed view-in-browser links. Paid subscriptions arm at launch.

Canonical: https://emailfast.dev/features/newsletters

## More than a blast tool

Email Fast is a newsletter platform with RSS and a public web presence built in:
every publication gets a hosted subscribe page, a search-indexable archive at
`/n/:pub`, a page per issue, an RSS feed, and signed view-in-browser links. Under it
sits a pricing posture worth naming: contacts and subscribers are never billed — we price sending, not the size of your audience.

## How it works

1. Create a publication and set up its template once.
2. Write and send issues. Each one reaches subscriber inboxes and, at the same time, lands on the public archive and the RSS feed.
3. Readers find back-issues through search or the feed, and subscribe through the hosted page or an [embedded form](/features/forms).
4. Every issue carries a signed view-in-browser link — usable without a login, not guessable.

Two pieces arm at launch: paid subscriptions (reader billing through Stripe) and
RSS-to-email, which turns a feed you already publish into issues automatically.

## The evidence

:::panel What every publication ships with
- A hosted subscribe page — zero frontend work
- A public, search-indexable archive at `/n/:pub`, with a page per issue
- An RSS feed of the archive
- Signed view-in-browser links on every send
- Paid subscriptions via Stripe — arms at launch
:::

Who carries the mail matters more here than anywhere: every newsletter platform we surveyed rents its delivery: beehiiv's status page lists SendGrid components; Buttondown's subprocessor list names Mailgun and Postmark; Substack sends through Mailgun (verified on their own public pages, July 2026). Email
Fast is the other kind of company — Email Fast runs its own mail transfer agent, warmup engine, reputation breaker, and per-tenant fair queue — the pipes are ours, not resold.

## Honest limits

:::tradeoffs Public by design, and two things that wait
The archive is the point: issues are public and search-indexable, which is how new
readers find you — so don't publish what shouldn't be on the open web. Paid
subscriptions and RSS-to-email both arm at launch, with billing. And subscribers
acquired through our forms carry double opt-in confirmation, which costs some
signups; a list you can defend is the trade we've picked.
:::

## Where to go next

The [creator door](/creators) has the whole story — audience ownership, exports,
honest metrics. Pair publications with [signup forms](/features/forms) and
[automations](/features/automation). Leaving a hosted newsletter platform? The
[comparison](/compare/substack-alternative) is honest in both directions.

## Do you charge per subscriber?

No: contacts and subscribers are never billed — we price sending, not the size of your audience. Your list can grow to any size without raising your bill — only sending is priced.

## Is there a public archive and RSS feed?

Yes — every publication gets a search-indexable archive at /n/:pub , a page per issue, a hosted subscribe page, and an RSS feed. Readers can find and follow you outside the inbox.

## Can readers pay for subscriptions?

Paid subscriptions are built in, with card processing through Stripe. Reader billing arms at launch, alongside RSS-to-email.

## What is a signed view-in-browser link?

A per-issue web link that works without a login and can't be enumerated or guessed — safe for recipients to forward, safe for you to publish.

## Who actually delivers my issues?

We do — the same company hosting your archive runs the mail servers your issues leave from: Email Fast runs its own mail transfer agent, warmup engine, reputation breaker, and per-tenant fair queue — the pipes are ours, not resold.