Mailbase
Start free
DeliverabilityUpdated · 7 min read

Email Infrastructure for Indie Hackers

A practical email infrastructure guide for indie hackers: the layers you actually need, build vs buy, cheap stacks, the deliverability work you can't skip, and where to keep it simple.

MT
Mailbase Team
email infrastructure for indie hackers
Archived guide. Mailbase is now a prospecting agent built on the French company register, and sends through Amazon SES. This guide was written for an earlier version of the product and may describe options (useSend, self-hosted sending, the AI task drawer) that are no longer available. It is kept for reference. See what Mailbase does today.
On this page · 8 sections

Overview

"Email infrastructure" sounds heavy, but for an indie hacker it's really three layers: a way to send (API/SMTP), the deliverability foundation (domain, DNS, reputation), and a workflow layer (templates, campaigns, replies, analytics). The trap is overbuilding too early or, worse, treating email as plug-and-play and getting filtered. This is how to set up something cheap, reliable, and not over-engineered.

The layers you actually need

Sending layer: a provider that delivers your mail — a hosted API (Resend, Postmark) for zero ops, or a self-hosted/owned option (useSend, backed by AWS SES) if you want control and near-cost pricing. Deliverability foundation: a sending domain with SPF, DKIM, DMARC, bounce/complaint handling, and suppression — this part is non-negotiable regardless of provider. Workflow layer: templates, campaigns, a reply inbox, and analytics, which you either stitch together or get from a tool.

Keep transactional (signups, receipts) and marketing (newsletters) conceptually separate, ideally on separate domains or subdomains, so a marketing misstep can't take down your password resets.

  • Sending: hosted API (no ops) or self-hosted useSend/SES (control)
  • Foundation: SPF/DKIM/DMARC + bounce/complaint handling + suppression
  • Workflow: templates, campaigns, reply inbox, analytics
  • Separate transactional from marketing streams

Build vs buy, and keeping it cheap

Don't run your own mail servers — IP reputation and the maintenance burden aren't worth it for an indie hacker. "Self-hosted" sensibly means running an app like useSend on a cheap box (Coolify, Railway, a VPS) that relays through SES, so you pay near-cost for volume while a provider handles IP reputation. A fully hosted API is the zero-ops alternative if you'd rather not touch infrastructure at all.

Start simple: one provider, an authenticated domain, verified lists, and suppression. Add the workflow layer when you actually need campaigns and replies. Mailbase fits here as that workflow layer — free for 200 emails/month, or €5/month bringing your own useSend — so you get the inbox, campaigns, and analytics without stitching tools together. See email infrastructure costs and cheap tools for developers.

  • Never run your own mail servers — relay through SES/a provider
  • Cheap self-host: useSend on Coolify/Railway/VPS + SES
  • Or a hosted API for zero ops
  • Start with one provider + auth + verified lists + suppression

Common mistakes

  • Skipping SPF, DKIM, and DMARC, or assuming they're a one-time setup.
  • Sending real volume from a brand-new, un-warmed domain.
  • Reusing a stale list without re-verifying, so bounces spike.
  • Ignoring complaint rate until a single bad campaign sinks the domain.

Sources and further reading

Official docs for current setup details, pricing, and API behavior — verify specifics there, since they change.

Amazon SES docsSupabase custom SMTP docs

Related guides

More on email infrastructure for indie hackers and the surrounding deliverability workflow:

free domain checkSPF, DKIM, and DMARCdeliverability and honest warm-upbounce managementsuppression listsunsubscribe best practicessender domain docs
Questions

About this page.

What email infrastructure does an indie hacker need?
Three layers: a sending provider (hosted API or self-hosted useSend/SES), a deliverability foundation (domain with SPF/DKIM/DMARC, bounce/complaint handling, suppression), and a workflow layer (templates, campaigns, replies, analytics). Keep transactional and marketing email separate.
Should I self-host my email?
Not your own mail servers — IP reputation and maintenance aren't worth it solo. Sensible "self-hosting" is running an app like useSend on a cheap box that relays through AWS SES, so you pay near-cost while a provider handles IP reputation. A hosted API is the zero-ops alternative.
What's the cheapest reliable email setup?
Either a hosted API's free/cheap tier, or self-hosted useSend on a low-cost host (Coolify, Railway, a VPS) relaying through AWS SES, which is near-cost at volume. Add a workflow layer like Mailbase (free for 200/month, or €5/month BYO useSend) only when you need campaigns and replies.
How do I keep indie email simple?
Start with one provider, an authenticated domain, verified lists, and automatic suppression — that covers reliable sending. Don't build a campaign system, reply inbox, or analytics yourself until you actually need them; add a workflow layer at that point rather than over-engineering up front.