ChatGPT answers, unedited

For a tech-savvy solo developer, I’d narrow it to Fastmail, Purelymail, and Migadu. All three let you keep your domain at your own registrar/DNS provider rather than locking DNS into the mail host.

1. Fastmail — polished managed choice

Fastmail is probably the most conventional choice if you want good email infrastructure without having to administer mail infrastructure.

You can keep DNS at your registrar and add Fastmail's MX, SPF, DKIM, and DMARC records yourself. Fastmail explicitly supports this "MX only" configuration, and its documentation provides the exact records. Fastmail Fastmail

It also has domain/user administration in its own control panel, plus routing and subdomain controls. Fastmail

Why I'd consider it: you get substantial DNS/domain control while outsourcing the unpleasant parts of running an email server.

2. Purelymail — very developer-friendly

Purelymail is particularly interesting if you don't care about a big productivity-suite ecosystem.

Its custom-domain setup explicitly has you manage DNS at your registrar, with records for ownership verification, MX, SPF, DKIM, and DMARC. Once the domain is verified, you can create users from the administration portal. Purelymail

Purelymail also doesn't sell domains, so your domain and DNS remain independently managed—which is a nice property for someone who thinks of the domain as infrastructure rather than an account belonging to the email vendor. Purelymail

Its September 2026 update also added automatic client configuration support (AutoConfig/AutoDiscover). PurelyMail News

3. Migadu — especially good for lots of addresses/domains

Migadu is worth looking at if your "solo developer" setup means lots of project addresses, aliases, or domains.

Migadu supports external DNS as well as its own nameservers, provides DNS diagnostics, and supports DKIM/SPF/DMARC. It explicitly describes its service as standards-based SMTP/IMAP/POP3/webmail rather than requiring a proprietary client. Migadu Migadu

That's appealing if you have things like:

• me@example.com
• billing@example.com
• alerts@project-a.dev
• hello@project-b.com
• several development/project domains

My practical shortlist

For your stated requirements, I'd investigate them in this order:

1. Fastmail — if you want the least operational friction.
2. Purelymail — if you're comfortable with a more utilitarian service and want your domain/DNS setup to remain very independent.
3. Migadu — if multiple domains and many addresses are a major consideration.

One architectural recommendation: keep the domain registered separately from the email provider, and keep authoritative DNS somewhere you control (e.g. your existing DNS provider). Then the mail provider is essentially just an MX/DKIM/SPF/DMARC dependency. That makes switching providers much less painful. Fastmail explicitly supports this arrangement, as do Purelymail and Migadu. Fastmail Purelymail Migadu

If you tell me roughly how many domains, mailboxes, aliases, and outbound transactional emails you expect, I can narrow this down further and compare the current pricing/limits.

Purelymail is particularly interesting if you don't care about a big productivity-suite ecosystem.

Its custom-domain setup explicitly has you manage DNS at your registrar, with records for ownership verification, MX, SPF, DKIM, and DMARC. Once the domain is verified, you can create users from the administration portal. Purelymail

Purelymail also doesn't sell domains, so your domain and DNS remain independently managed—which is a nice property for someone who thinks of the domain as infrastructure rather than an account belonging to the email vendor. Purelymail

Its September 2026 update also added automatic client configuration support (AutoConfig/AutoDiscover). news.purelymail.com

3. Migadu — especially good for lots of addresses/domains

Migadu is worth looking at if your "solo developer" setup means lots of project addresses, aliases, or domains.

Migadu supports external DNS as well as its own nameservers, provides DNS diagnostics, and supports DKIM/SPF/DMARC. It explicitly describes its service as standards-based SMTP/IMAP/POP3/webmail rather than requiring a proprietary client.

That's appealing if you have things like:

For your requirements, I’d shortlist:

• Fastmail — polished, excellent custom-domain support, full DNS can remain at your registrar, and explicit SPF/DKIM/DMARC setup. Fastmail Fastmail
• Migadu — particularly attractive if you want multiple domains/addresses and don’t mind a more technical admin experience; DNS records are managed manually. digitalhosting.com
• MXroute — worth considering if you expect heavier business mail or multiple mailboxes/domains. digitalhosting.com

My practical pick: Fastmail if you want “set it up once, retain DNS control, and get on with development.” If minimizing cost and maximizing domain/mailbox flexibility matter more, look closely at Migadu. Fastmail digitalhosting.com

For a tech-savvy solo developer, I’d shortlist these:

🥇 My pick: MXroute

MXroute is probably the closest match to what you're describing.

You keep authoritative DNS wherever you want—Cloudflare, your registrar, etc.—and MXroute gives you the MX/SPF/DKIM values to publish yourself. Its control panel lets you add domains, create mailboxes, aliases, catch-alls, and test DNS configuration. docs.mxroute.com docs.mxroute.com

It also exposes per-domain DKIM keys, and its documentation explicitly covers SPF, DKIM, and DMARC rather than trying to hide those details behind an opaque setup wizard.

For a tech-savvy solo developer, I’d shortlist these:

1. purelymail.com — best value / maximum DIY control

• Designed around bringing your own domain.
• You keep DNS at your registrar/DNS provider and manually control MX, SPF, DKIM, and DMARC.
• Supports three DKIM CNAMEs with rotating keys and a DMARC record. Purelymail Purelymail
• Particularly attractive if you have multiple aliases/domains and don't need a polished business suite.
• My pick if you enjoy managing DNS yourself.
• migadu.com — best for lots of addresses/domains

• Very developer-friendly, standards-based SMTP/IMAP/POP3/webmail rather than locking you into proprietary clients. Migadu
• Flat account pricing rather than charging per mailbox, with unlimited addresses and domains subject to plan limits. Migadu
• Good admin tooling for creating mailboxes, aliases, and multiple domains.
• My pick if your "solo developer" setup includes lots of project domains/aliases.
• fastmail.com — best polished option

• Excellent UX and mature custom-domain support.
• You can leave DNS with your existing provider and add the required MX/SPF/DKIM/DMARC records yourself. Fastmail Fastmail
• Its domain setup also supports more advanced DNS configurations. Fastmail
• My pick if you want "it just works" while retaining proper domain/DNS control.

My ranking for your requirements

I'd start with Purelymail unless you care strongly about polished UX. If you're going to host email for several domains or generate lots of addresses like hello@, billing@, dev@, etc., Migadu becomes especially compelling. If email is infrastructure you don't want to think about, choose Fastmail.

One thing I'd specifically look for regardless of provider: keep your registrar/DNS independent from your mail provider. That makes switching providers as simple as changing MX/SPF/DKIM/DMARC records rather than migrating your entire DNS setup. Purelymail's documentation explicitly follows this model. support.purelymail.com

For a tech-savvy solo developer, I’d shortlist these:

My pick: Migadu

Migadu is particularly well suited if you're comfortable managing DNS yourself. It is standards-oriented—SMTP, IMAP, POP3 and webmail—with unlimited addresses on your domains and a domain-oriented admin model. Migadu Migadu

That's attractive for a developer who might have:

• me@example.com
• hello@example.com
• billing@example.com
• alerts@example.com
• throwaway addresses for side projects

without wanting every address to become a separately priced mailbox.

Best overall: Fastmail

Fastmail is what I'd choose if you value a really polished product over squeezing out maximum flexibility.

You can keep DNS at your existing registrar/DNS provider and manually configure MX, SPF, DKIM and DMARC. Fastmail explicitly documents the required records, including three DKIM CNAMEs and a DMARC record. Fastmail Fastmail

It also has a surprisingly capable DNS interface if you want Fastmail to host DNS: custom A, AAAA, CNAME, MX, NS, SRV, SSHFP, TXT and other records are supported. Fastmail

Verdict: probably the best balance of developer control and "I don't want to babysit my mail server."

Budget/developer choice: Purelymail

Purelymail is worth considering if your priority is cheap, straightforward domain email rather than a fancy ecosystem.

Its documentation exposes the DNS setup directly, including MX, TXT, three DKIM CNAMEs and DMARC, and it provides a DNS zone-record management interface. Purelymail

Privacy-first: Proton Mail

Proton Mail supports custom domains on paid plans and lets you manage the necessary DNS records at your own DNS provider. Its custom-domain setup explicitly covers SPF, DKIM and DMARC, including automatic DKIM key rotation. Proton Proton

I'd pick Proton primarily if privacy is a major requirement. For a developer whose main requirement is DNS/domain administration, I think Migadu or Fastmail is a better fit.

What I'd choose

1. Migadu — if you want maximum domain/address flexibility.
2. Fastmail — if you want the nicest overall service.
3. Purelymail — if keeping costs extremely low matters.
4. Proton — if privacy is the deciding factor.

One important distinction: "full DNS control" should ideally mean keeping DNS at Cloudflare, Route 53, your registrar, etc., rather than delegating your nameservers to the mail provider. Fastmail and Proton both support setups where DNS remains elsewhere. Fastmail Proton

For your particular requirements, I'd start with Migadu vs. Fastmail.

For a tech-savvy solo developer who wants full DNS control, DKIM/DMARC, and self-service domain provisioning, I would avoid bundled “website hosting email” and focus on providers that treat email as infrastructure.

My shortlist:

framekit.aidigitalhosting.com

My recommendations by developer profile

1. “I own a few domains, want aliases, and never want to think about mail”

Pick: Fastmail

Why:

• Excellent custom-domain support
• Easy DNS setup (MX/SPF/DKIM/DMARC)
• Strong IMAP/JMAP support
• Great for me@domain.com, github@domain.com, billing@domain.com, etc.
• Good fit if you are the only user but have many identities

The downside: you pay per user, so it is not the cheapest if you accumulate many mailboxes. thesoftwarescout.comframekit.ai

2. “I have 5–20 domains and want to manage them like infrastructure”

Pick: Migadu

This is probably the most developer-oriented option.

Good for:

• Side projects
• Startup experiments
• Multiple domains
• Lots of aliases
• Keeping costs low

You manage your DNS yourself and get the records you expect:

• MX
• SPF
• DKIM
• DMARC

The tradeoff is that it feels more like email infrastructure than a polished consumer mailbox. framekit.ai

3. “I want maximum control and don't mind being the mail admin”

Pick: MXroute

Good if you:

• Understand DNS
• Want many domains/mailboxes
• Prefer a traditional hosting model
• Do not need Gmail-style UX

It is closer to “rent a reliable mail server platform” than “use a productivity suite.” framekit.aidigitalhosting.com

What I would not do

Self-host Postfix/Dovecot unless it is a hobby project

You can absolutely run:

• Mailcow
• Mailu
• Postfix + Dovecot
• Stalwart Mail Server

…but the hard part is not receiving mail. The hard part is:

• IP reputation
• Gmail/Outlook deliverability
• spam filtering
• backups
• abuse handling
• monitoring

For a solo developer, the operational cost usually exceeds the savings. thesoftwarescout.comframekit.ai

DNS checklist I would require from any provider

Before committing, verify you can configure:

MX
SPF
DKIM
DMARC
MTA-STS
TLS-RPT

Recommended DMARC starting point:

_dmarc.example.com TXT

v=DMARC1; p=none; rua=mailto:dmarc@example.com

Then move toward:

p=quarantine

or eventually:

p=reject

once you know all legitimate senders are authenticated.

My ranking for your exact description

1. Fastmail — best daily driver
2. Migadu — best for developer-style multi-domain ownership
3. MXroute — best if you enjoy managing infrastructure
4. Zoho Mail — best cheap conventional business option
5. Google Workspace — best only if you specifically want Gmail/Docs integration

For a solo developer with one main domain plus side projects, I would probably choose Fastmail + Cloudflare DNS. For someone running many project domains, I would lean Migadu. thesoftwarescout.comframekit.ai

For a tech-savvy solo developer who wants full DNS control, DKIM/DMARC, and self-service provisioning, I would avoid bundled web-host email and focus on providers that treat your domain as infrastructure. The best fits are usually the ones with strong alias support, good APIs/admin tooling, and clean DNS workflows. The Software Scout

My shortlist:

digitalhosting.com The Software Scout## My picks by developer profile

1. "I want email to just work" → Fastmail

This is my default recommendation for a solo developer.

Good fit if you want:

• you@yourdomain.com
• unlimited aliases like github@domain.com, aws@domain.com
• catch-all addresses
• normal SMTP/IMAP/JMAP access
• easy DNS setup
• no advertising ecosystem

It feels like infrastructure rather than a productivity suite. The Software Scout

2. "I own lots of domains/projects" → Migadu

Great if you have:

• project1.dev
• project2.io
• client domains
• many forwarding addresses

The model is closer to "host my domain email" than "buy one mailbox per human". Framekit

3. "I want maximum control and don't mind tinkering" → MXroute

Good for someone comfortable with:

• DNS records
• mail clients
• migration tools
• managing their own aliases

It is closer to traditional mail hosting than SaaS email. digitalhosting.com

DNS checklist I would expect any provider to support

For a serious domain, configure:

• MX records — mail delivery
• SPF TXT record — authorized senders
• DKIM TXT record — cryptographic signing
• DMARC TXT record — policy/reporting
• Autodiscover/client config where applicable
• Reverse DNS if you ever send directly from your own infrastructure

A good starting DMARC policy:

_dmarc.example.com TXT

v=DMARC1; p=none; rua=mailto:dmarc@example.com

Then move toward:

v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com

or eventually:

v=DMARC1; p=reject; rua=mailto:dmarc@example.com

once you know all legitimate senders are aligned.

What I would avoid

• Self-hosting your primary mailbox on a VPS unless it is a learning project. Running Postfix/Dovecot is easy; maintaining reputation, spam filtering, backups, and deliverability is the hard part. The Software Scout
• Cheap "free email with hosting" bundles unless price is the only concern.
• Providers that hide DKIM keys or force you into their DNS hosting.

My final ranking for your exact use case

1. Fastmail — best balance of control, reliability, and developer ergonomics
2. Migadu — best if you have many domains/aliases
3. MXroute — best value if you enjoy managing things
4. Zoho Mail — good cheap business option
5. Proton Mail — choose mainly for privacy reasons

For a solo developer with one or a few domains, I would probably choose Fastmail + Cloudflare DNS and keep all DNS ownership independent.

For a tech-savvy solo developer, I’d optimize for:

• Full control of DNS records (MX, SPF, DKIM, DMARC, MTA-STS/TLS-RPT if desired)
• Reliable deliverability to Gmail/Outlook
• API or automation options where useful
• Easy mailbox/alias provisioning
• No forced productivity suite unless you want one

I would not self-host primary email unless the goal is learning mail infrastructure. The hard part is not running Postfix; it is reputation, deliverability, spam filtering, abuse handling, and uptime. The Software Scout

My shortlist

Rost Glukhov The Software Scout## 1. Fastmail — my default recommendation

Best if you want: “I want my domain email to just work, but I still care about technical control.”

Strengths:

• Custom domains
• Clean SPF/DKIM setup
• Strong IMAP/SMTP support
• JMAP support (nice for developers building integrations)
• Excellent aliases and masked addresses
• Good admin UI without enterprise clutter

Trade-offs:

• More expensive than bare-bones hosts
• Less suitable if you need hundreds of mailboxes

For a solo developer with you@domain.com, billing@domain.com, github@domain.com, etc., this is usually the sweet spot. The Software Scout

2. Migadu — best if you own many domains

Best if you have:

• Personal domain
• Side-project domains
• Startup experiments
• Many aliases

Strengths:

• Multiple domains
• Lots of aliases
• Developer-friendly DNS model
• Avoids paying per mailbox for every identity

Trade-offs:

• More utilitarian UI
• Sending limits on lower tiers

This is attractive for developers who think in terms of “domains and identities” rather than “one mailbox.” Framekit

3. Purelymail — hacker-friendly budget option

Best if you want:

• Cheap
• Simple
• Full DNS ownership
• Minimal hand-holding

Strengths:

• Very inexpensive
• Supports custom domains
• Good for technically comfortable users

Trade-offs:

• Less polished
• You are expected to know what MX/SPF/DKIM/DMARC mean

A good fit if you enjoy managing infrastructure but do not want to run your own mail server.

4. Google Workspace — if Gmail is non-negotiable

Best if you want:

• Gmail UI
• Google Calendar/Drive integration
• Business-standard ecosystem

Strengths:

• Excellent deliverability
• Mature admin tooling
• Strong APIs

Trade-offs:

• You pay for a suite, not just email
• More account-management overhead

For a solo developer who lives in Gmail all day, it can be worth it. Rost Glukhov

5. Zoho Mail — value pick

Best if cost matters.

Strengths:

• Custom domains
• DKIM/SPF support
• Business-oriented admin controls
• Low cost

Trade-offs:

• UX is less polished than Fastmail/Gmail
• Developer experience is not its main focus

Rost Glukhov TechRadar## What I would avoid

Self-hosted mail as your main inbox

Mailcow/Mailu/Postfix setups are great learning projects, but for a primary address you depend on, you inherit:

• IP reputation problems
• Spam filtering
• Security patching
• Backup responsibility
• Deliverability debugging

The Software Scout### Domain registrar email bundles

Convenient, but usually weaker on:

• migration
• admin controls
• authentication visibility
• long-term portability

My picks by scenario

• One developer, one main domain: Fastmail
• Developer with 5–20 side-project domains: Migadu
• Lowest-cost technical setup: Purelymail
• Already living in Gmail: Google Workspace
• Privacy is the priority: Proton Mail
• Need email for a SaaS product: use a mailbox provider plus a separate transactional sender (for example Amazon SES/Postmark/etc.) rather than sending app mail from your personal mailbox. SendX

For your stated requirements, I’d rank them:

1. Fastmail
2. Migadu
3. Purelymail
4. Google Workspace
5. Zoho Mail

A setup I’d personally consider “developer-grade” is:

• registrar/DNS: Cloudflare or your preferred DNS host
• mailbox: Fastmail or Migadu
• transactional mail: SES/Postmark/Resend
• DMARC policy: start p=none, monitor reports, then move toward enforcement (quarantine/reject) once confident

That gives you control without making email operations your hobby.

For a tech-savvy solo developer who owns a domain and cares about full DNS control, DKIM/DMARC, and self-service provisioning, I’d optimize for:

• Ability to manage your own MX/SPF/DKIM/DMARC records (not a “contact support” workflow)
• Clean IMAP/SMTP (or JMAP) access
• Aliases and catch-all support
• API or automation friendliness (if you add domains later)
• Good deliverability without becoming a mail administrator

My shortlist:

Rost Glukhov The Software Scout## My recommendations by scenario

1. “I want email that just works, but I still control DNS”

Pick: Fastmail

This is probably the sweet spot. You keep your DNS at your registrar/DNS provider, publish the MX/SPF/DKIM/DMARC records yourself, and you get a clean mail platform. It is especially good if you want:

• you@domain.com
• github@domain.com
• billing@domain.com
• random-service-123@domain.com

all without creating lots of paid mailboxes. Framekit

2. “I own 20 domains and want automation”

Pick: Migadu or a similar multi-domain-focused host

Good for developers with:

• side projects
• startup experiments
• parked domains
• client/demo domains

The ability to avoid paying per mailbox/domain can matter more than fancy UI. Folio

3. “I want maximum control and don’t mind tinkering”

Self-hosting is possible, but I usually wouldn’t recommend it

A Postfix/Dovecot stack gives ultimate control, but the hard parts are not the mailbox—they are:

• reputation management
• spam filtering
• IP reputation
• reverse DNS
• bounce handling
• DKIM key rotation
• DMARC reporting
• keeping up with Gmail/Yahoo/Microsoft requirements

For a solo developer, renting a good mail platform and keeping DNS ownership is usually the better engineering tradeoff.

DNS checklist I would require from any provider

Before signing up, verify you can publish:

• MX — inbound mail routing
• SPF — authorized senders
• DKIM — cryptographic signing
• DMARC — enforcement/reporting policy
• Optional but nice: - MTA-STS
• TLS-RPT
• BIMI

A solid setup would look like:

DNS: Cloudflare / Route53 / your registrar
        |
        +-- MX -> mail provider
        +-- TXT SPF
        +-- TXT DKIM
        +-- TXT DMARC

My ranking for your exact profile

1. Fastmail — best balance of control, simplicity, and developer friendliness
2. Migadu — best if you manage many domains
3. Zoho Mail — best low-cost business option
4. Google Workspace — only if you actually want Google apps
5. Self-hosted Postfix/Dovecot — only if email infrastructure itself is the hobby

I would avoid registrar-bundled email (GoDaddy-style offerings, etc.) for this use case; they tend to hide the pieces developers usually want access to. digitalhosting.com

A setup I’d personally choose for a solo developer: domain DNS on Cloudflare + Fastmail for mail + strict DMARC policy after monitoring reports for a few weeks.

For a tech-savvy solo developer, I’d shortlist these three:

1. Fastmail — my default recommendation

fastmail.com

Fastmail is probably the best fit if you want professional email without giving up control. You can keep DNS at your registrar/DNS provider and manually configure the required records, including DKIM and SPF. Fastmail also has a DNS customization interface if you choose to host DNS with them. Fastmail Fastmail

It's particularly nice for a developer because you can have:

• you@example.com
• hello@example.com
• billing@example.com
• catch-all/aliases
• multiple domains
• standard IMAP/SMTP
• DKIM signing
• your own DMARC policy

You aren't forced to move your nameservers to Fastmail; their documentation explicitly supports keeping DNS elsewhere. Fastmail

Pick this if: you want something polished and boring that you won't have to think about.

2. Migadu — best hacker-friendly option

migadu.com

Migadu is unusually attractive for a solo developer. It's designed around domains and addresses rather than traditional mailbox-per-user pricing, and explicitly supports hosting many domains and unlimited addresses within its usage limits. Migadu Migadu

It supports standard SMTP/IMAP/POP3, has an admin panel, DNS diagnostics, and can either work with your registrar's DNS or provide its own nameservers. Migadu Migadu

Pick this if: you're likely to have lots of aliases, project domains, or side projects and enjoy having more knobs to turn.

3. Purelymail — best value/minimalism

purelymail.com

Purelymail is compelling if your priority is "just give me standards-based email on my domain and don't charge me much."

Its custom-domain setup explicitly supports MX, SPF, multiple DKIM CNAMEs, and DMARC. You manage the DNS records at your own registrar. Purelymail Purelymail

The interface and ecosystem aren't as polished as Fastmail, but for a developer who is comfortable editing DNS records, that's not necessarily a disadvantage.

Pick this if: price and simplicity matter more than premium UX.

My ranking for your requirements

1. Fastmail — best overall balance of control, reliability, UX, and self-service.
2. Migadu — best if you're going to operate multiple domains/aliases or want a more postmaster-ish experience.
3. Purelymail — best if you want extremely inexpensive, no-nonsense domain email.

One important distinction: "full DNS control" doesn't require the mail provider to host your DNS. For a developer, I'd actually keep the authoritative DNS at something like Cloudflare and give the mail host only the MX/SPF/DKIM records it needs. That keeps your web/DNS infrastructure independent of your email provider.

If this were my personal developer domain, I'd choose Fastmail + independently hosted DNS + a deliberate DMARC policy. Fastmail

It supports standard SMTP/IMAP/POP3, has an admin panel, DNS diagnostics, and can either work with your registrar's DNS or provide its own nameservers.

Pick this if: you're likely to have lots of aliases, project domains, or side projects and enjoy having more knobs to turn.

3. Purelymail — best value/minimalism

For a tech-savvy solo developer who owns a domain and wants full DNS control, proper DKIM/DMARC, and self-service provisioning, I’d avoid bundled “business suites” unless you need their docs/calendar/chat features. Look for a provider that treats email as infrastructure: custom domains, aliases, API-friendly management, transparent DNS records, and good deliverability.

My shortlist:

The Software Scout digitalhosting.com## My ranking for your exact profile

1. Fastmail — my default recommendation

fastmail.com

This is probably the sweet spot for a solo developer:

• Bring your own domain
• Full control of MX/SPF/DKIM/DMARC records
• Unlimited aliases (very useful for github@, aws@, newsletters@, etc.)
• Good IMAP support and native JMAP support
• Excellent web UI without forcing an ecosystem
• Simple migration/export story

It feels like a “Unix philosophy” email provider: do one thing well, expose standards, stay out of your way. The Software Scout

2. Migadu — best if you own lots of domains

migadu.com

Great if you have:

• firstname.dev
• sideproject.io
• familyname.net
• test domains
• lots of aliases

You can manage many domains without paying the “one mailbox per user” pricing model. The downside is that lower tiers have sending limits, so it’s better for personal/project mail than high-volume transactional sending. digitalhosting.com

3. MXroute — best value if you enjoy managing email

mxroute.com

Good match if you think:

“I understand DNS. Give me a reliable mail server and let me configure it.”

Pros:

• Multiple domains
• Many mailboxes/aliases
• Low cost
• Traditional email protocols

Cons:

• Less hand-holding
• Less polished than Fastmail
• You need to be comfortable debugging DNS/mail issues

digitalhosting.com

4. Self-hosting (Mailcow/Mailu) — only if email infrastructure is a hobby

A developer’s instinct is often “I’ll just run Postfix.” For a learning project, great. For your primary identity email, I’d usually avoid it.

You inherit:

• IP reputation
• spam filtering
• backups
• DKIM rotation
• DMARC reporting
• abuse handling
• uptime responsibility

Modern self-hosted stacks such as Mailcow make it much easier, but the hard part is not installing the software — it is staying trusted by Gmail, Outlook, and Yahoo. SecureSMTP

DNS checklist I would require

Whatever you choose, configure:

• SPF — authorize your mail provider
• DKIM — provider signs outgoing mail
• DMARC — start with monitoring: ```

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

 Then move toward `quarantine` or `reject` after validating
- **MTA-STS/TLS reporting** if supported
- Separate sending identities for apps: - `me@domain.com` → human mail
- `notifications@domain.com` → app mail
- `support@domain.com` → support workflows

---

## One setup I’d choose

For a solo developer:

- Registrar/DNS: Cloudflare DNS
- Mail: Fastmail
- Transactional email: separate provider (e.g., Postmark/SES/Mailgun)
- DMARC: start `p=none`, review reports, tighten later

That keeps your personal mailbox reliable while avoiding the common mistake of sending application mail through your personal inbox provider.

If you manage **multiple domains and want API-driven mailbox provisioning**, the recommendation changes slightly toward infrastructure-oriented providers.

For a tech-savvy solo developer, I’d shortlist these:

My pick: Migadu

Migadu is probably the closest match to what you're describing.

Its API can manage domains, mailboxes, identities, aliases, forwardings, rewrites, etc., so you can script provisioning rather than clicking around an admin panel. Migadu Migadu

That's particularly attractive if your workflow is something like:

terraform / script
      ↓
create domain
      ↓
create mailbox + aliases
      ↓
configure DNS
      ↓
DKIM/SPF/DMARC validation

You can keep authoritative DNS with something like Cloudflare and have Migadu handle mail, rather than surrendering your entire DNS zone to the mail provider.

Fastmail: best if you value polish

Fastmail is my choice if email quality and a polished client matter more than API-driven provisioning.

It explicitly supports keeping your nameservers/DNS elsewhere while pointing MX at Fastmail, and provides DKIM, SPF and DMARC configuration. Fastmail Fastmail

Its DNS tooling is unusually good: Fastmail documents the complete DNS configuration and lets you manage arbitrary DNS records when it hosts your DNS. Fastmail

The downside for your particular requirements is that it isn't as compelling as Migadu if you want to treat mailboxes as infrastructure.

Purelymail: excellent minimalist option

Purelymail is worth considering if you want very inexpensive custom-domain email without unnecessary enterprise features.

It supports external DNS and explicitly documents MX, SPF, three DKIM records, and DMARC. Purelymail Purelymail

I'd rank it below Migadu for a developer who wants to automate provisioning, though.

Bottom line

I'd choose Migadu for your stated requirements.

If your priorities shift toward:

• Best UX / reliability: Fastmail
• Best developer automation: Migadu
• Lowest-cost straightforward hosting: Purelymail

One architectural recommendation: keep your domain registration and authoritative DNS independent of your mail provider. Then your mail provider is essentially a replaceable MX/DKIM/SPF/DMARC backend, which is exactly the kind of setup a developer is likely to appreciate long-term.

Migadu is probably the closest match to what you're describing.

Its API can manage domains, mailboxes, identities, aliases, forwardings, rewrites, etc., so you can script provisioning rather than clicking around an admin panel. Migadu Migadu

That's particularly attractive if your workflow is something like:

terraform / script
      ↓
create domain
      ↓
create mailbox + aliases
      ↓
configure DNS
      ↓
DKIM/SPF/DMARC validation

You can keep authoritative DNS with something like Cloudflare and have Migadu handle mail, rather than surrendering your entire DNS zone to the mail provider.

Fastmail: best if you value polish

Fastmail is my choice if email quality and a polished client matter more than API-driven provisioning.

It explicitly supports keeping your nameservers/DNS elsewhere while pointing MX at Fastmail, and provides DKIM, SPF and DMARC configuration. Fastmail Fastmail

Its DNS tooling is unusually good: Fastmail documents the complete DNS configuration and lets you manage arbitrary DNS records when it hosts your DNS. Fastmail

The downside for your particular requirements is that it isn't as compelling as Migadu if you want to treat mailboxes as infrastructure.

Purelymail: excellent minimalist option

Purelymail is worth considering if you want very inexpensive custom-domain email without unnecessary enterprise features.

It supports external DNS and explicitly documents MX, SPF, three DKIM records, and DMARC.

I'd rank it below Migadu for a developer who wants to automate provisioning, though.

Bottom line

For a tech-savvy solo developer, I’d prioritize API/admin automation, external DNS control, DKIM/DMARC, aliases, and standards-based IMAP/SMTP over bundled office-suite features.

My picks

1. Migadu — my recommendation

migadu.com is unusually well suited to a developer who wants to treat email hosting almost like infrastructure.

Its API can create/manage domains, mailboxes, identities, forwarding rules, aliases and rewrites. It can also return the exact DNS records needed for a domain, including MX, SPF, DKIM and DMARC, and provides DNS diagnostics/activation endpoints. Migadu Migadu

That's a major advantage if your ideal workflow is something like:

terraform/app script
       ↓
create domain
       ↓
retrieve DNS requirements
       ↓
Cloudflare DNS API
       ↓
verify/activate domain
       ↓
create mailbox + aliases

Migadu explicitly supports external DNS, rather than requiring you to move authoritative DNS to them. Migadu

It also supports unlimited addresses/domains within plan usage limits, making it attractive if your "solo developer" setup includes lots of project-specific addresses such as github@, billing@, alerts@, etc. Migadu Migadu

Downside: the API is described as still being in beta, so I'd test the specific provisioning operations you intend to automate before building your whole infrastructure around it. Migadu

2. Purelymail — excellent value

purelymail.com is compelling if you don't need a sophisticated provisioning API.

It supports custom domains without an additional per-domain charge, custom routing/catchalls, IMAP/SMTP, and multiple domains/users. Purelymail

You retain control of DNS at your registrar: Purelymail's setup explicitly has you configure MX, SPF, three DKIM CNAME records and DMARC yourself. Purelymail Purelymail

The catch for your use case is automation: Migadu is considerably more interesting if "self-service provisioning" means API-driven provisioning rather than clicking around an admin console.

3. Fastmail — best if you value polish

fastmail.com is probably the nicest general-purpose option of the three.

It supports custom domains, DKIM, customizable DNS, aliases and multi-user administration. Its documentation specifically covers manual DNS configuration for technically sophisticated users, and you can keep your DNS elsewhere rather than handing your zone over to Fastmail. Fastmail Fastmail

Its admin interface makes user and alias management straightforward. Fastmail Fastmail

But if "self-service provisioning" means "I want an API that my own tooling can call to create mailboxes/domains", I'd choose Migadu instead.

Bottom line

I'd rank them for your stated requirements:

1. Migadu — best combination of external DNS + authentication records + API provisioning.
2. Purelymail — fantastic if low cost and simple infrastructure matter more than API automation.
3. Fastmail — best polished email experience, but less compelling as an infrastructure/provisioning platform.

If you're already using Cloudflare DNS + Terraform, Migadu is the one I'd investigate first. Its API's ability to expose the DNS requirements and provision domains/mailboxes makes it the closest match to an "email as infrastructure" setup. Migadu

1. Migadu — my recommendation

migadu.com is unusually well suited to a developer who wants to treat email hosting almost like infrastructure.

Its API can create/manage domains, mailboxes, identities, forwarding rules, aliases and rewrites. It can also return the exact DNS records needed for a domain, including MX, SPF, DKIM and DMARC, and provides DNS diagnostics/activation endpoints. Migadu Migadu

That's a major advantage if your ideal workflow is something like:

terraform/app script
       ↓
create domain
       ↓
retrieve DNS requirements
       ↓
Cloudflare DNS API
       ↓
verify/activate domain
       ↓
create mailbox + aliases

Migadu explicitly supports external DNS, rather than requiring you to move authoritative DNS to them. Migadu

It also supports unlimited addresses/domains within plan usage limits, making it attractive if your "solo developer" setup includes lots of project-specific addresses such as github@, billing@, alerts@, etc. Migadu Migadu

Downside: the API is described as still being in beta, so I'd test the specific provisioning operations you intend to automate before building your whole infrastructure around it. Migadu

2. Purelymail — excellent value

purelymail.com is compelling if you don't need a sophisticated provisioning API.

It supports custom domains without an additional per-domain charge, custom routing/catchalls, IMAP/SMTP, and multiple domains/users. mailserver.purelymail.com

You retain control of DNS at your registrar: Purelymail's setup explicitly has you configure MX, SPF, three DKIM CNAME records and DMARC yourself. support.purelymail.com Purelymail

The catch for your use case is automation: Migadu is considerably more interesting if "self-service provisioning" means API-driven provisioning rather than clicking around an admin console.

3. Fastmail — best if you value polish

fastmail.com is probably the nicest general-purpose option of the three.

It supports custom domains, DKIM, customizable DNS, aliases and multi-user administration. Its documentation specifically covers manual DNS configuration for technically sophisticated users, and you can keep your DNS elsewhere rather than handing your zone over to Fastmail.

For a tech-savvy solo developer, I’d prioritize providers that let you keep DNS at your registrar/Cloudflare, expose normal SMTP/IMAP, and give you straightforward control over SPF, DKIM, and DMARC.

My shortlist

1. fastmail.com — best overall

I'd pick this if you want "I want email infrastructure, but I don't want to babysit it."

You can keep your DNS elsewhere and simply add Fastmail's MX/SPF/DKIM/DMARC records yourself. Fastmail explicitly supports an MX-only setup for domains whose DNS remains with your registrar. Fastmail Fastmail

It's particularly good for a solo developer because aliases are first-class: you can have hello@, billing@, dev@, etc. without turning each into another paid human account.

Choose it if: polish, reliability, good clients, and low maintenance matter more than squeezing out the last few dollars.

2. migadu.com — best for a tinkerer

Migadu is probably the most interesting choice if "full control" is the overriding criterion.

It's designed around people managing their own domains and DNS rather than hiding infrastructure behind a corporate abstraction. You manually configure MX, SPF, DKIM, etc., and can have multiple domains/mailboxes without conventional per-user pricing. Framekit

That makes it especially attractive if your eventual setup is something like:

example.com
├── you@
├── hello@
├── billing@
└── alerts@

sideproject.dev
├── you@
└── noreply@

Choose it if: you enjoy managing DNS and expect to have multiple domains/identities.

3. purelymail.com — best cheap option

Purelymail is the minimalist/developer-budget choice.

Custom domains have no additional charge, and its documentation explicitly expects you to add the DNS records yourself. Purelymail

It's much less "ecosystem" than Fastmail, but that's arguably the appeal: email hosting rather than a giant productivity suite.

Choose it if: you want standards-based email at extremely low cost and don't care about fancy UX.

4. mxroute.com — good for lots of mailboxes

MXroute is worth considering if you anticipate many addresses or domains. Current comparisons put its entry offering around $59/year with unlimited domains/mailboxes, though storage and other plan limits matter. digitalhosting.com

Choose it if: you want traditional hosted email and expect your number of addresses/domains to grow.

What I'd choose

For your exact requirements, my ranking would be:

1. Fastmail — best balance of control + usability.
2. Migadu — best if you're genuinely a DNS/infrastructure nerd.
3. Purelymail — best if cost is the primary consideration.
4. MXroute — best if you're going to accumulate lots of domains/mailboxes.
5. Zoho Mail — competent low-cost alternative, but I'd choose the above first for a developer.

One important distinction: DNS control doesn't require your email provider to host your DNS. I'd personally keep the authoritative DNS with something like Cloudflare and give the mail provider only the DNS records it needs. That keeps your website, email, verification records, and future services decoupled.

For a solo developer, my concrete setup would be Cloudflare DNS + Fastmail + SPF/DKIM/DMARC managed in your DNS, with a separate transactional-email provider for application-generated mail rather than sending production app mail through your personal mailbox host.

You can keep your DNS elsewhere and simply add Fastmail's MX/SPF/DKIM/DMARC records yourself. Fastmail explicitly supports an MX-only setup for domains whose DNS remains with your registrar. Fastmail Fastmail

It's particularly good for a solo developer because aliases are first-class: you can have hello@, billing@, dev@, etc. without turning each into another paid human account.

Choose it if: polish, reliability, good clients, and low maintenance matter more than squeezing out the last few dollars.

2. migadu.com — best for a tinkerer

Migadu is probably the most interesting choice if "full control" is the overriding criterion.

It's designed around people managing their own domains and DNS rather than hiding infrastructure behind a corporate abstraction. You manually configure MX, SPF, DKIM, etc., and can have multiple domains/mailboxes without conventional per-user pricing. Framekit

That makes it especially attractive if your eventual setup is something like:

For your requirements, I’d prioritize email-only providers that let you keep DNS at your registrar rather than Google/Microsoft-style suites.

My shortlist

• Fastmail — best overall

• Excellent custom-domain support.
• You publish the provider’s MX/SPF/DKIM records yourself, so DNS remains yours.
• Strong alias/catch-all tooling and IMAP/SMTP plus JMAP.
• Polished enough that you don't spend your evenings administering mail.
• Current developer-oriented comparisons consistently put it near the top for custom-domain users. The Software Scout
• Pick this if: you want maximum control over your domain without actually running a mail server.
• Migadu — best for multiple domains

• Particularly attractive if you expect to have several side-project/client domains.
• Technical DNS setup and mailbox/domain management suit someone comfortable with DNS.
• Less polished than Fastmail, but more oriented toward hands-on domain administration. The Software Scout Digital Hosting
• Pick this if: "I have five domains and don't want five separate subscriptions" sounds familiar.
• MXroute — best value for lots of mailboxes

• Flat-fee model rather than the usual per-user pricing.
• Especially interesting if you want lots of aliases/mailboxes across multiple domains.
• More utilitarian than Fastmail, but that's arguably appropriate for a developer who cares about infrastructure rather than a productivity suite. Digital Hosting
• Pick this if: you want cheap, conventional hosted SMTP/IMAP and don't mind a less polished UI.
• Zoho Mail — budget choice

• Custom domains, SPF/DKIM/DMARC and self-managed DNS are supported.
• Good if keeping the monthly bill very low matters more than having the nicest developer experience. Current comparisons put it among the cheapest mainstream options.
• Pick this if: "under $2/month" matters more than JMAP, polish, or privacy.

What I'd actually choose

Fastmail would be my default recommendation for a solo developer.

The architecture I'd use is:

yourdomain.com
      │
      ├── DNS stays at your registrar / Cloudflare
      │      ├── MX → Fastmail
      │      ├── SPF → Fastmail
      │      ├── DKIM → Fastmail
      │      ├── DMARC → your policy/reporting address
      │      └── optional MTA-STS / TLS-RPT
      │
      └── Fastmail
             ├── me@
             ├── hello@
             ├── billing@
             └── arbitrary aliases

That gives you ownership of the DNS identity while outsourcing the annoying parts—mail storage, spam filtering, SMTP reputation, backups, and uptime.

I would not self-host primary business email unless the operational aspect itself is the hobby. Running Postfix/mailcow is straightforward compared with maintaining good deliverability; SPF, DKIM, DMARC, reverse DNS, reputation, spam filtering, patching and backups become your problem. The Software Scout

One distinction worth making: "full DNS control" doesn't mean the email provider needs API access to your DNS. In fact, for your use case, I'd prefer the opposite: keep authoritative DNS entirely separate and have the mail provider tell you exactly which records to publish.

If you tell me how many domains/mailboxes you expect (e.g. 1 domain/1 inbox vs. 10 domains/50 aliases), I can narrow this to the best 2–3 options and compare pricing, API/provisioning capabilities, aliases, catch-all, and DKIM/DMARC handling.

For a tech-savvy solo developer, I’d shortlist these:

1. Fastmail — my default recommendation

Fastmail is probably the sweet spot if you want professional email without surrendering control.

You can keep DNS at Cloudflare, Route 53, your registrar, etc., and simply publish Fastmail's MX/DKIM/SPF records yourself. Their documentation explicitly supports manual DNS configuration, including three DKIM CNAMEs and your own DMARC TXT policy. Fastmail Fastmail

It's particularly nice for a developer because you can have something like:

example.dev
├── me@example.dev
├── hello@example.dev
├── billing@example.dev
└── github@example.dev

…and manage addresses/domains from the Fastmail UI rather than maintaining Postfix/Dovecot yourself.

fastmail.com

Why I'd pick it: excellent UX + standards-based mail + granular DNS control + mature custom-domain support.

2. Migadu — best for a domain-heavy developer

Migadu is especially interesting if you expect to have several domains or lots of aliases. It explicitly supports unlimited email addresses and domains subject to plan usage quotas, and exposes standard SMTP/IMAP/POP3 rather than locking you into proprietary clients. Migadu Migadu

Their positioning is unusually close to "self-hosted email, minus the sysadmin"—which sounds aligned with what you're asking for. Migadu

migadu.com

Why I'd pick it: you're a developer who might accumulate project-a.dev, project-b.com, client domains, etc.

3. MXroute — best if quantity matters

MXroute is worth considering if you want lots of domains/accounts without traditional per-user pricing. Its current offering emphasizes unlimited domains and accounts on its plans, with SMTP/IMAP/POP3 and SPF/DKIM/DMARC support. MXroute

mxroute.com

Why I'd pick it: you're more interested in mail infrastructure than a polished consumer-mail experience.

My ranking for your requirements

1. Fastmail — best overall solo-developer choice
2. Migadu — best if you're going to operate multiple domains
3. MXroute — best value for lots of mailboxes/domains
4. Purelymail — compelling if minimizing cost is the priority

One important distinction: "full DNS control" doesn't mean the mail provider needs to host your DNS. I'd actually recommend keeping DNS at a provider you already trust (e.g. Cloudflare) and using MX + SPF + DKIM + DMARC records to delegate only email to the host. Fastmail explicitly supports this MX-only arrangement. Fastmail

For a solo developer, I'd therefore choose Fastmail + your existing DNS provider, rather than letting the email company become your authoritative DNS host.

It's particularly nice for a developer because you can have something like:

example.dev
├── me@example.dev
├── hello@example.dev
├── billing@example.dev
└── github@example.dev

…and manage addresses/domains from the Fastmail UI rather than maintaining Postfix/Dovecot yourself.

fastmail.com

Why I'd pick it: excellent UX + standards-based mail + granular DNS control + mature custom-domain support.

2. Migadu — best for a domain-heavy developer

Migadu is especially interesting if you expect to have several domains or lots of aliases. It explicitly supports unlimited email addresses and domains subject to plan usage quotas, and exposes standard SMTP/IMAP/POP3 rather than locking you into proprietary clients. Migadu Migadu

Their positioning is unusually close to "self-hosted email, minus the sysadmin"—which sounds aligned with what you're asking for. Migadu

migadu.com

Why I'd pick it: you're a developer who might accumulate project-a.dev, project-b.com, client domains, etc.

3. MXroute — best if quantity matters

MXroute is worth considering if you want lots of domains/accounts without traditional per-user pricing. Its current offering emphasizes unlimited domains and accounts on its plans, with SMTP/IMAP/POP3 and SPF/DKIM/DMARC support.

For a tech-savvy solo developer, I’d prioritize providers that let you keep the domain/DNS under your control rather than hiding email configuration behind a simplified wizard.

My picks

1. Migadu — best overall for power users

• Built specifically around hosting your domains, with unlimited addresses and multiple domains depending on plan.
• Standard IMAP/SMTP/POP3 rather than a proprietary ecosystem.
• Gives you an admin panel for domains, users, aliases and mail configuration.
• Supports DKIM and DMARC, with domain diagnostics in the admin panel. Migadu Migadu
• Particularly attractive if you expect to have several project domains or lots of aliases.
• Current entry-level pricing is $19/year for Micro, with higher-capacity plans at $9/month and up. Migadu

migadu.com

2. Purelymail — best minimalist/cheap option

• Very developer-friendly philosophy: you bring your own domain and explicitly manage the DNS records.
• Custom domains cost nothing extra, and you can have multiple users/domains. Purelymail Purelymail
• Explicitly supports SPF, DKIM and DMARC; DKIM keys are rotated automatically. Purelymail Support Purelymail
• Catchalls, routing rules, subaddressing and 2FA are useful for a developer's domain.
• Less polished than Fastmail, but arguably more aligned with someone who actually wants to understand and control the plumbing.

purelymail.com

3. Fastmail — best polished experience

• Excellent if you want the technical control without spending your weekends administering mail.
• Custom domains, multiple users/aliases, catchalls and strong domain administration. Fastmail
• If you use Fastmail's DNS, its control panel lets you customize DNS records rather than imposing arbitrary restrictions. Fastmail Fastmail
• DKIM is automatically generated for added domains; if DNS stays with your registrar, Fastmail gives you the DKIM record to publish yourself. Fastmail
• More expensive than Purelymail/Migadu, but probably the nicest "set it and forget it" choice.

fastmail.com

What I'd choose

My personal recommendation for your requirements: Migadu. It sits unusually close to the "managed mail server for people who could run their own mail server" sweet spot. Its own positioning is essentially that: full control without the sysadmin burden. Migadu

One architectural suggestion: keep authoritative DNS at your existing DNS provider (e.g. Cloudflare or another provider you already use), and let the mail host provide the MX/SPF/DKIM values. That gives you maximum portability: changing mail hosts later becomes a DNS migration rather than a domain-management migration.

If you tell me whether you care more about privacy, deliverability, aliases/catchalls, or lowest cost, I can narrow this to one choice.

For a tech-savvy solo developer, I’d shortlist these three:

1. Migadu — my pick for you

migadu.com

Migadu is particularly interesting if by "self-service provisioning" you mean "I want to script this." Its API can manage domains and identities, and it exposes domain/mailbox administration programmatically. Migadu Migadu

You can keep authoritative DNS wherever you like, while configuring the MX/SPF/DKIM/DMARC records yourself. Migadu also provides domain diagnostics for authentication problems. Migadu

Why I'd choose it: it's closer to an email infrastructure service than a consumer-oriented mailbox product.

2. Purelymail — excellent minimalist choice

purelymail.com

Purelymail gives you custom domains without an additional per-domain charge and explicitly supports SPF, DKIM and DMARC. Its documentation has you put the records directly into your registrar's DNS, so you retain complete DNS authority. Purelymail Purelymail

It's especially attractive if you're running one person + lots of aliases/domains rather than building elaborate provisioning infrastructure.

The downside for your particular requirement is that its automation story isn't as strong as Migadu's API.

3. Fastmail — best polished option

fastmail.com

Fastmail supports external DNS, including manually configured MX/DKIM/SPF records, and has very good domain-management tooling. Fastmail Fastmail

Its developer API is excellent for mail itself: JMAP, IMAP, SMTP, CardDAV, etc., with API tokens available for personal integrations. Fastmail

But if your priority is automatically creating domains/mailboxes/users, I'd put Migadu ahead of it.

My ranking for your requirements

1. Migadu — best combination of DNS independence + authentication + provisioning automation.
2. Purelymail — best if low cost and straightforward administration matter more than API automation.
3. Fastmail — best if you want a highly polished mailbox experience and powerful mail APIs.

One architectural recommendation: keep DNS at your registrar/DNS provider rather than letting the mail host become authoritative. Then your setup is essentially:

Registrar/DNS → MX + SPF + DKIM + DMARC → mail provider

That makes changing mail hosts later dramatically easier and keeps your domain infrastructure under your control. Fastmail explicitly supports this arrangement, for example. Fastmail

If "self-service provisioning" means you want a POST /users-style API that you can put behind your own admin panel, I'd go Migadu without much hesitation.

2. Purelymail — excellent minimalist choice

purelymail.com

Purelymail gives you custom domains without an additional per-domain charge and explicitly supports SPF, DKIM and DMARC. Its documentation has you put the records directly into your registrar's DNS, so you retain complete DNS authority. purelymail.com mailserver.purelymail.com

It's especially attractive if you're running one person + lots of aliases/domains rather than building elaborate provisioning infrastructure.

The downside for your particular requirement is that its automation story isn't as strong as Migadu's API.

3. Fastmail — best polished option

fastmail.com

Fastmail supports external DNS, including manually configured MX/DKIM/SPF records, and has very good domain-management tooling.

For a tech-savvy solo developer, I’d prioritize: custom-domain support, transparent DNS configuration, good DKIM/DMARC handling, aliases/catch-alls, IMAP/SMTP, and an admin UI that doesn’t get in your way.

My picks

1. fastmail.com — best overall

• Excellent fit if you want a polished service without giving up technical control.
• Supports custom domains, DKIM, SPF, and flexible DNS configurations. You can keep DNS at your registrar rather than handing nameservers to Fastmail. Fastmail Fastmail
• Admins can create/remove users and manage domains and aliases themselves. Fastmail
• My choice if this is your primary professional email and you value reliability and a clean UI.
• migadu.com — best for developer-style domain/alias sprawl

• Particularly attractive if you expect to have multiple domains, lots of aliases, project addresses, or catch-alls.
• Migadu explicitly supports unlimited email addresses and multiple domains, with usage-based plans rather than charging per address. Migadu Migadu
• It has a substantial admin panel and supports standard IMAP/SMTP rather than locking you into proprietary clients. Migadu Migadu
• My choice if you're likely to run hello@, billing@, security@, dev@, aliases for projects, etc.
• purelymail.com — best value / minimalist option

• Custom domains are included without an additional domain fee, and you can have multiple users/domains. Purelymail Purelymail
• Very explicit about the DNS records: MX, SPF, three DKIM records, and DMARC. It expects you to manage DNS yourself—which sounds like a feature rather than a drawback for your use case. Purelymail Purelymail
• Supports IMAP/SMTP plus calendar/contact protocols.
• My choice if you enjoy managing the plumbing and want to spend very little.
• proton.me — best if privacy is the priority

• Custom domains are available on paid plans.
• Supports SPF, DKIM, and DMARC, with Proton generating the records you publish at your DNS provider. Proton Proton
• The tradeoff is that it's more opinionated around its ecosystem than Fastmail/Migadu/Purelymail.
• My choice if privacy/security matters more than maximum interoperability and admin flexibility.

What I'd choose

For your exact description, I'd start with Fastmail, unless you're planning to operate several domains or dozens of project identities—in that case I'd seriously consider Migadu.

One important distinction: email hosting doesn't have to mean DNS hosting. I'd personally keep authoritative DNS with a provider such as Cloudflare and have the mail host give you the MX/SPF/DKIM/DMARC records to publish. Fastmail explicitly supports this setup. Fastmail

If you tell me your approximate monthly budget and whether you need catch-all/aliases, I can narrow this to a single recommendation.

For a tech-savvy solo developer, I’d optimize for standards, DNS independence, aliases/routing, and easy account administration—not for bundled office apps.

My shortlist

1. Fastmail — best default

fastmail.com

I'd choose this if you have one or a few domains and want email to simply work.

You retain control of your registrar/DNS provider: MX, SPF, DKIM and DMARC are records you configure at your DNS host, rather than handing your domain management over to the mail provider. Fastmail also supports IMAP, SMTP and JMAP, which is particularly nice if you like building tooling around your own mail. Current 2026 comparisons consistently put it near the top for developer-oriented custom-domain hosting. The Software Scout Zapier

Why I like it for you: polished enough that you won't resent using it every day, while still being standards-friendly enough for a developer.

2. Migadu — best if you're DNS/infra-oriented

migadu.com

Migadu is especially interesting if you expect to have multiple domains, lots of aliases, or several identities. Its pricing model is based more around usage than charging you for every mailbox, which makes it unusually attractive for a developer managing several domains. The Software Scout Sekin

I'd pick Migadu over Fastmail if your mental model is:

"I want an email infrastructure service I can configure."

rather than:

"I want the nicest email product."

3. Purelymail — absurdly good value

purelymail.com

Worth serious consideration if you enjoy technical configuration and don't need a fancy UI. A recent 2026 comparison puts its basic plan at roughly $10/year, with support for multiple domains and standard email functionality including DKIM and routing. Folio

The tradeoff is product polish and maturity compared with Fastmail. For a developer who spends most of the day in an email client anyway, that may not matter.

What I'd actually choose

Single primary domain → Fastmail.

Several domains / lots of aliases → Migadu.

"I want this to cost almost nothing" → Purelymail.

Privacy/encryption is the overriding concern → Proton Mail. Proton explicitly supports custom domains and has documented configuration for MX, SPF, DKIM and DMARC. Proton Proton

One other recommendation: keep your domain registrar/DNS completely separate from your email provider. Put the domain at something like Cloudflare/Porkbun/Namecheap, manage DNS yourself, and point MX records at whichever mail host you select. That gives you a clean migration path if you ever switch providers.

For your stated requirements, Fastmail is the one I'd start with; Migadu is the one I'd investigate if you're the kind of developer who expects to accumulate domains and aliases.

For a tech-savvy solo developer, I’d optimize for domain/DNS independence + API-driven administration, rather than Google Workspace-style productivity features.

My picks

1. Migadu — my recommendation

migadu.com is unusually well suited to your requirements.

You can keep DNS entirely at your registrar/DNS provider rather than handing nameservers to the mail host. Migadu's API can create domains, retrieve the exact DNS records required, run diagnostics, activate domains, and manage mailboxes, identities, aliases, and rewrites. Migadu Migadu

That means you can build something like:

Terraform/CLI → your DNS provider + Migadu API → new domain/mailboxes

Their domain API even exposes the DKIM, SPF, DMARC and MX records programmatically. Migadu

Why I'd pick it: it feels like infrastructure rather than a SaaS admin console. It's particularly attractive if you have several project domains or want hello@, billing@, security@, etc. without treating every address as a separate paid user. Migadu explicitly prices around usage rather than address count. Migadu

2. Fastmail — best polished alternative

fastmail.com is my choice if you care more about having an excellent daily email product than automating the mail infrastructure.

Fastmail supports external DNS, and its custom-domain documentation explicitly covers DKIM/SPF and other security records. Fastmail It also has strong standards-based APIs, including JMAP, plus IMAP/SMTP. Fastmail

The catch is that its API story isn't as infrastructure/provisioning-centric as Migadu's. For a single developer mailbox, though, Fastmail is arguably the nicest overall experience.

3. Zoho Mail — good if provisioning automation matters

zoho.com has a surprisingly capable administration API. Its domain API can add and verify domains, enable mail hosting, manage domain aliases, verify SPF/MX, and configure DKIM. Zoho Zoho

Its admin console also exposes MX, SPF, DKIM, DMARC and BIMI status/configuration. Zoho

I'd put it behind Migadu for a developer-centric setup because Zoho's ecosystem and admin model are more business-suite oriented.

What I'd actually use

Migadu + Cloudflare DNS (or another DNS provider you already control).

Keep the authoritative DNS completely separate from your mail provider. Then automate:

1. Create domain in Migadu API.
2. Read required MX/SPF/DKIM/DMARC records from the API.
3. Create those records through your DNS provider's API.
4. Run Migadu's domain diagnostics.
5. Activate the domain.
6. Create mailboxes/aliases through the Migadu API.

That gives you reproducible email infrastructure without self-hosting SMTP, while retaining control of the DNS layer.

One important distinction: DKIM and DMARC don't require your mail provider to host your DNS. In fact, for your stated goals, I'd deliberately avoid providers that require you to delegate the whole DNS zone to them.

Bottom line: Migadu > Fastmail > Zoho for your particular requirements. If "I want to be able to automate this like infrastructure" is the dominant requirement, Migadu is the clear first place I'd test.

That means you can build something like:

Terraform/CLI → your DNS provider + Migadu API → new domain/mailboxes

Their domain API even exposes the DKIM, SPF, DMARC and MX records programmatically. Migadu

Why I'd pick it: it feels like infrastructure rather than a SaaS admin console. It's particularly attractive if you have several project domains or want hello@, billing@, security@, etc. without treating every address as a separate paid user. Migadu explicitly prices around usage rather than address count. Migadu

2. Fastmail — best polished alternative

fastmail.com is my choice if you care more about having an excellent daily email product than automating the mail infrastructure.

Fastmail supports external DNS, and its custom-domain documentation explicitly covers DKIM/SPF and other security records. Fastmail It also has strong standards-based APIs, including JMAP, plus IMAP/SMTP. Fastmail

The catch is that its API story isn't as infrastructure/provisioning-centric as Migadu's. For a single developer mailbox, though, Fastmail is arguably the nicest overall experience.

3. Zoho Mail — good if provisioning automation matters

zoho.com has a surprisingly capable administration API. Its domain API can add and verify domains, enable mail hosting, manage domain aliases, verify SPF/MX, and configure DKIM.

Its admin console also exposes MX, SPF, DKIM, DMARC and BIMI status/configuration.

I'd put it behind Migadu for a developer-centric setup because Zoho's ecosystem and admin model are more business-suite oriented.

What I'd actually use

Migadu + Cloudflare DNS (or another DNS provider you already control).

For a tech-savvy solo developer, I’d shortlist these three:

1. Fastmail — my default recommendation

Fastmail is probably the sweet spot if you want real control without becoming your own mail administrator.

You can keep DNS at your existing registrar/Cloudflare and just publish Fastmail's MX, SPF, DKIM and DMARC records. Fastmail documents the exact DKIM CNAMEs and supports custom DMARC policies. Fastmail Fastmail

Particularly nice for a developer:

• Custom domains and addresses are managed from the account UI.
• You can manage DNS yourself rather than handing your entire zone to Fastmail.
• DKIM signing is automatic.
• You can choose and manage your own DMARC policy.
• Standard IMAP/SMTP plus JMAP/API support.
• Good web UI without forcing you into an enterprise suite.

fastmail.help is unusually useful if you want to understand exactly what it's doing.

Verdict: ⭐ Best overall for one-person businesses/projects.

2. Migadu — best if you think like a postmaster

Migadu is more infrastructure-oriented. Its philosophy is essentially "your domains, our mail infrastructure." It supports standard SMTP/IMAP/POP3, unlimited addresses, multiple domains, and built-in DNS. Migadu

It's especially attractive if your definition of "solo developer" includes:

"I might eventually have me@, support@, billing@, dev@, and three separate project domains."

Migadu explicitly supports multiple domains under one account and provides an admin panel for managing them. Migadu Migadu

You can either retain your own DNS or use Migadu's nameservers; its documentation specifically covers DKIM setup and DNS diagnostics. Migadu

Verdict: ⭐ Best for a developer who wants lots of domains/addresses and a more mail-infrastructure-centric service.

3. Purelymail — best if cost/minimalism dominates

Purelymail is worth considering if you want email hosting as cheap infrastructure rather than a polished productivity suite.

I'd put it behind Fastmail for the "set it and forget it" experience, but ahead of conventional business suites if your priority is simply:

domain → DNS → authenticated mailboxes/aliases → IMAP/SMTP.

What I'd actually choose

For your requirements, I'd rank them:

1. Fastmail — best balance of control, reliability, UI, and developer-friendly configuration.
2. Migadu — choose this if you're likely to operate multiple domains or a large collection of aliases.
3. Purelymail — choose this if minimizing cost is more important than polish.

I would not pick Google Workspace or Microsoft 365 for this particular requirement unless you specifically want their office/collaboration ecosystems. They certainly support custom domains and authentication, but you're paying for considerably more than "give me a well-run mail server attached to my domain."

One important architectural point: keep your authoritative DNS somewhere you control, such as Cloudflare or your registrar, and use the mail provider only for MX/DKIM-related records. Fastmail explicitly supports an MX-only setup where your existing DNS remains authoritative. Fastmail

For a developer, that separation makes migration much easier later: changing mail providers becomes a DNS change rather than a wholesale nameserver migration.

Migadu explicitly supports multiple domains under one account and provides an admin panel for managing them. Migadu Migadu

You can either retain your own DNS or use Migadu's nameservers; its documentation specifically covers DKIM setup and DNS diagnostics. Migadu

Verdict: ⭐ Best for a developer who wants lots of domains/addresses and a more mail-infrastructure-centric service.

3. Purelymail — best if cost/minimalism dominates

Purelymail is worth considering if you want email hosting as cheap infrastructure rather than a polished productivity suite.

I'd put it behind Fastmail for the "set it and forget it" experience, but ahead of conventional business suites if your priority is simply:

domain → DNS → authenticated mailboxes/aliases → IMAP/SMTP.

What I'd actually choose

For your requirements, I'd rank them:

For your priorities, I’d shortlist Fastmail, Purelymail, and Migadu, with Fastmail as the default recommendation.

1. Fastmail — best overall

fastmail.com is probably what I'd choose for a solo developer who wants to own the domain and keep DNS under their own control.

You can leave your domain's DNS at your registrar/Cloudflare and manually configure MX, SPF, DKIM and DMARC. Fastmail explicitly documents this mode, including three DKIM CNAMEs and a DMARC record. Fastmail Fastmail

It also has unusually good support for a developer-ish workflow:

• Multiple custom domains
• Lots of aliases
• Catch-all addresses
• IMAP/SMTP plus JMAP
• Easy creation/deletion of addresses from the UI
• Good webmail without forcing you into Google's ecosystem

Fastmail supports up to 100 domains on an account and lets you create users and aliases across them. Fastmail

Caveat: if by "self-service provisioning" you mean automate mailbox creation/deletion from scripts or Terraform, I'd investigate the API capabilities specifically before choosing it. Its UI is excellent, but that's a different requirement from API-first provisioning.

2. Purelymail — my pick if you're very cost-conscious

purelymail.com is particularly attractive for a technically sophisticated solo operator.

It supports custom domains at no additional charge, multiple users/domains, custom routing and catch-alls. Purelymail

Its DNS model is exactly what you're describing: you control the DNS, while Purelymail tells you what MX/SPF/DKIM/DMARC records to publish. It uses three DKIM records and rotates the keys. Purelymail

The downside is that it feels more like a lean technical service than a polished business-email suite. For someone who actually enjoys managing DNS and mail configuration, that's arguably a feature.

3. Migadu — worth considering for lots of domains

migadu.com is another strong fit if you expect to operate several domains or many addresses rather than just me@example.com.

Its model is more infrastructure-oriented than Google Workspace/Microsoft 365, so it's worth considering when your mental model is "I own the domain and this provider supplies the mail infrastructure."

What I'd actually do

For a solo developer:

Fastmail → if you want the best combination of reliability, UX, aliases, protocols and low maintenance.

Purelymail → if you want maximum flexibility per dollar and don't mind a less polished interface.

Migadu → if you're likely to accumulate domains/projects and want to manage them centrally.

I would not self-host SMTP/mail delivery unless running mail infrastructure itself sounds like an enjoyable hobby. Receiving mail is relatively straightforward; maintaining reputation, spam filtering, IP reputation, DKIM rotation, backups, abuse handling and reliable outbound delivery is where the time sink appears.

One important distinction: keep DNS at Cloudflare/your registrar rather than transferring nameserver control to the mail provider if "full DNS control" is a hard requirement. Fastmail supports exactly this arrangement. Fastmail

If you tell me whether API/Terraform-based mailbox provisioning is a hard requirement, I can narrow this to the providers that actually expose the right automation surface rather than merely having a good admin UI.

For your profile, I’d prioritize API-driven mailbox management + external DNS + strong authentication controls, rather than a consumer-oriented mail host.

My picks

1. Migadu — my recommendation

Migadu is unusually well aligned with a developer-centric setup. You can keep authoritative DNS at Cloudflare, Route 53, etc., while Migadu provides the mail infrastructure. Its API exposes domains, mailboxes, identities, aliases, forwardings, and rewrites, so you can automate things like:

create domain
    ↓
provision mailbox
    ↓
create aliases
    ↓
configure DNS
    ↓
verify DKIM/SPF/DMARC

Its API can also return the DNS records required for a domain, including DKIM, DMARC, SPF and MX records. migadu.com

Migadu API documentation

2. Fastmail — best if you value polish

Fastmail is probably the nicest option if you're willing to do some provisioning manually. It supports custom domains, external DNS, DKIM, SPF and DMARC, and gives you detailed control over DNS records when it hosts DNS. www.fastmail.help

The important bit for you is that you don't have to delegate DNS to Fastmail. You can leave your DNS at your existing provider and publish Fastmail's MX/DKIM/SPF/DMARC records yourself. www.fastmail.help

Fastmail custom-domain/DNS documentation

Its weakness for your use case is automation: Migadu's API is much more explicitly designed around programmatic domain/mailbox provisioning.

3. Purelymail — excellent if cost is the main consideration

I'd look at Purelymail if you're running a handful of personal/dev domains and don't need the richer ecosystem of Fastmail. It's particularly attractive when the goal is essentially "give me reliable IMAP/SMTP for my domains without paying for a business suite."

What I'd actually deploy

For a solo developer, I'd do:

Domain registrar → Cloudflare DNS → Migadu

and manage DNS declaratively alongside your infrastructure:

example.com
├── MX       → Migadu
├── TXT SPF  → Migadu
├── CNAME    → DKIM selectors
├── TXT      → _dmarc
├── A/AAAA   → your infrastructure
└── CNAMEs   → whatever else you're running

That keeps mail hosting and DNS ownership separate, which is exactly what I'd want for a technical setup. Migadu explicitly supports external DNS and exposes the records through its API. migadu.com

I'd choose Fastmail instead if this is primarily your personal mailbox and you care more about excellent mail UX, calendar/contact integration, and low operational fuss than automated provisioning.

Bottom line: Migadu for developer-first automation; Fastmail for developer-friendly-but-polished personal email.

For your requirements, I’d shortlist Migadu, Fastmail, and MXroute, with Migadu as the strongest fit if self-service provisioning/API access matters most.

1. Migadu — my pick

Migadu is unusually well suited to a developer who wants to treat email infrastructure almost like another service.

Its API exposes domains, mailboxes, identities, forwarding, aliases, and rewrites, including create/update/delete operations. It can also return the DNS records required for a domain—including DKIM, DMARC, SPF and MX—and has a domain diagnostics endpoint. migadu.com

Crucially, you can keep DNS at your own provider rather than handing nameservers to Migadu. Their API explicitly supports creating domains with external DNS. migadu.com

That makes something like this quite practical:

Terraform/CLI → Migadu API → domain/mailbox/alias provisioning

while:

Cloudflare/Route 53/etc. → authoritative DNS → MX/SPF/DKIM/DMARC

Migadu also supports unlimited addresses and multiple domains under its paid plans, which is attractive if you're running several projects. migadu.com

Downside: the API is still described as being in early beta, so I wouldn't choose it if you need a rock-solid enterprise provisioning API. migadu.com

2. Fastmail — best polished option

Fastmail is probably the better choice if you are the primary mailbox user and don't need to automate dozens of accounts.

You can keep DNS elsewhere and manually publish the required records; Fastmail supports DKIM and lets you customize DNS records. www.fastmail.help It also has a good developer API based around JMAP and supports IMAP/SMTP. www.fastmail.com

Its admin interface also lets an account administrator add, remove, and update users and manage domains and aliases. www.fastmail.help

But: its API isn't nearly as compelling as Migadu's for mail infrastructure provisioning. Fastmail's strength is a polished mail product rather than acting like an email-hosting control plane.

3. MXroute — worth considering

MXroute is another strong option if your priority is inexpensive hosting for lots of domains/mailboxes rather than the slickest end-user experience.

I'd put it behind Migadu for your particular requirements because API-driven provisioning and developer ergonomics sound like unusually important criteria for you.

My recommendation

If I were building this as a solo developer:

Migadu + Cloudflare DNS

I'd keep authoritative DNS completely under my control and automate:

• domain creation
• mailbox creation
• aliases
• forwarding
• DKIM record retrieval
• SPF
• DMARC
• DNS verification/diagnostics

Migadu's API is particularly compelling because it exposes both the mail objects and the DNS configuration/diagnostics needed to turn a new domain into a working mail domain. migadu.com

If you tell me roughly how many domains/mailboxes you expect (e.g. 1 domain/5 addresses vs. 20 domains/100 addresses), I can narrow this down further and compare pricing, API capabilities, catch-all behavior, outbound limits, and portability.

For a tech-savvy solo developer, I’d prioritize providers that let you keep DNS at your preferred registrar/DNS host, expose proper DKIM/DMARC configuration, and don’t force you into a productivity suite.

My picks

1. migadu.com — best match for your requirements

This is probably my #1 recommendation for you.

Migadu is unusually developer-friendly: its API can create/manage domains, mailboxes, aliases, identities and forwarding rules. It can also return the exact DNS records required for a domain—including DKIM, SPF and DMARC—and provides a DNS diagnostics endpoint before activation. Migadu Migadu

The particularly nice part is that you can tell the API to use external DNS, rather than having Migadu manage your DNS. Migadu

That makes a workflow like this practical:

terraform/domain creation → Migadu API → DNS provider API → DNS verification → mailbox/alias provisioning

Choose Migadu if: you want to script everything and potentially have several domains/addresses.

2. fastmail.com — best overall email experience

I'd choose Fastmail if your priority is excellent email rather than infrastructure automation.

You can keep DNS elsewhere and simply publish Fastmail's MX, SPF, DKIM and DMARC records yourself. Fastmail explicitly supports this configuration. Fastmail Fastmail

Its DNS setup is also unusually flexible if you do let Fastmail host DNS: it supports arbitrary record types and doesn't impose the sort of restrictive DNS controls you sometimes see in bundled email services. Fastmail Fastmail

One caveat for your use case: Migadu wins decisively on API-driven provisioning.

3. purelymail.com — minimalist/cheap option

Worth considering if you mostly want basic custom-domain email without paying for a bunch of collaboration software.

I'd put it behind Migadu and Fastmail for a developer building an automated provisioning workflow, though.

4. Self-hosted mailcow — maximum control

If by "full control" you literally mean I want the mail server to be mine, mailcow is the interesting option.

You control the VPS, SMTP/IMAP stack, DKIM keys, DNS, retention, filtering, backups, etc. The tradeoff is substantial operational responsibility: reputation, IP reputation, spam handling, TLS, backups, monitoring, upgrades and deliverability become your problems.

For a solo developer, I'd only choose this if running mail infrastructure itself sounds fun.

What I'd actually use

Migadu + Cloudflare DNS (or another DNS provider with a good API).

Keep the authoritative DNS completely separate from the mail provider:

• Registrar → your registrar
• Authoritative DNS → Cloudflare/another DNS provider
• Email hosting → Migadu
• DKIM → CNAMEs published in your DNS
• SPF → TXT
• DMARC → TXT
• Provisioning → Migadu API + DNS API
• Your infrastructure → Terraform/scripts

That gives you a clean separation of concerns and makes moving away from Migadu relatively painless.

If you don't need automated provisioning: pick Fastmail instead. It's the better "set it up once and forget about it" choice, while Migadu is the better "email is another service I want to automate" choice.

For a tech-savvy solo developer, I’d optimize for DNS independence + standards access + easy provisioning, rather than a productivity suite.

My shortlist

1. Fastmail — my default recommendation

Fastmail is probably the nicest balance for a solo developer.

You can keep your authoritative DNS wherever you want and simply publish Fastmail's MX/SPF/DKIM/DMARC records. Fastmail explicitly supports an MX-only configuration, so it doesn't require handing your nameservers over to them. www.fastmail.help

Its DNS documentation exposes the actual records rather than hiding everything behind an opaque wizard, including three DKIM CNAMEs and a DMARC TXT record. www.fastmail.helpwww.fastmail.help

Why I'd choose it: excellent deliverability, polished clients, IMAP/SMTP/JMAP, aliases, custom domains, and very little operational hassle.

Downside: if your priority is programmatically creating domains/mailboxes as infrastructure, Fastmail isn't the standout.

Fastmail custom-domain documentation

2. Migadu — best if you're going to automate everything

Migadu is the interesting choice for a developer who thinks of email accounts as infrastructure.

Its API directly supports management of domains hosted by your organization, authenticated with an API key. www.migadu.com

That makes it particularly attractive if you want something like:

Terraform/script → create domain → provision mailbox/aliases → configure DNS → done

It also has a pricing model aimed at multiple domains/mailboxes rather than charging you separately for every address.

My pick over Fastmail if: you're likely to own several domains, create/delete addresses programmatically, or want email to behave more like an infrastructure service.

Migadu API documentation

3. Purelymail — ridiculously good value

Purelymail is worth a serious look if you don't care about fancy UX.

It supports your own domains, multiple users/domains without additional per-user charges, IMAP/POP3/SMTP, routing rules and Sieve filtering. purelymail.com

It's particularly appealing for a developer who wants "give me standards-compliant email and get out of my way."

Downside: less polished ecosystem and tooling than Fastmail, and I'd choose Migadu first if sophisticated provisioning automation is central.

4. Self-hosting — only if you actually want the job

Stalwart or Mailcow can give you essentially complete control over the mail stack, including DNS, DKIM signing, DMARC policy, users, routing and automation. But the hard part isn't running SMTP; it's reputation, spam handling, reverse DNS, IP reputation, backups and maintaining reliable delivery to Gmail/Outlook/Yahoo. www.itechguides.com

For a domain you actually depend on, I'd pay someone else $1–10/month rather than turn email administration into a second hobby.

What I'd choose

One domain, one developer, normal personal/business email → Fastmail.

Several domains + programmatic mailbox provisioning → Migadu.

Cheapest possible standards-based hosting → Purelymail.

"I want to own every layer and don't mind operating mail infrastructure" → Stalwart/Mailcow.

One architectural point: don't let the mail host become your DNS host unless you have a reason to. Keep DNS at Cloudflare, Route 53, your registrar, etc., and delegate only the mail records. That gives you clean separation between your web/infrastructure DNS and your email provider, and makes migration much easier. Fastmail explicitly supports this model. www.fastmail.helpwww.fastmail.help

For your stated requirements, Migadu is the one I'd investigate first if “self-service provisioning” means actual API-driven provisioning; Fastmail if it means a great admin UI with minimal operational fuss.

For a tech-savvy solo developer who wants full DNS control, DKIM/DMARC, and self-service provisioning, I would avoid traditional “domain email bundled with hosting” providers and pick something that treats email infrastructure as a first-class service.

My shortlist:

thesoftwarescout.com

My ranking for your specific requirements

1. Fastmail — probably the default choice

I would pick this for most solo developers.

Good fit because:

• Bring-your-own-domain DNS
• You control MX, SPF, DKIM, DMARC records
• Great alias support (github@, aws@, billing@, etc.)
• Works with normal clients via IMAP/SMTP
• Supports JMAP for modern integrations
• Very little operational overhead

It feels like “Unix philosophy for email”: standards-based, fast, minimal ceremony. thesoftwarescout.com

2. Migadu — if you own many domains

If you have:

• firstname.dev
• sideproject1.com
• startup2.io
• lots of catch-alls and aliases

Migadu is attractive because it is designed around domains and addresses rather than charging you per mailbox. thesoftwarescout.com

3. Zoho Mail — if cost matters

A good pragmatic choice:

• custom domains
• admin console
• DKIM/SPF/DMARC tooling
• inexpensive paid tiers

I would choose it over cheap cPanel email because deliverability and administration matter more than saving a dollar.

4. Google Workspace — if email is mission critical

If this is your professional identity and you already live in Gmail/Calendar/Docs, it is hard to beat.

The downside: you are paying mostly for the ecosystem, not just mail.

What I would avoid

Running Postfix/Dovecot yourself unless the goal is learning.

A modern mail stack is not hard to deploy. The hard parts are:

• getting Gmail/Microsoft to trust your IP
• monitoring reputation
• spam filtering
• backups
• patching
• avoiding compromised accounts

Self-hosting is excellent as a lab project; it is usually a poor choice for your primary identity. thesoftwarescout.com

Cheap shared hosting email is also usually a bad match:

• weak reputation
• limited DKIM controls
• poor automation
• noisy neighbors

If you also mean “programmatic provisioning”

If by self-service provisioning you mean:

“I want an API/CLI where I can create domains, mailboxes, aliases, rotate DKIM keys, etc.”

then the ranking changes. Look at more infrastructure-oriented platforms such as:

• Atriomail — API-driven provisioning, DNS automation, mailbox/domain management atriomail.com
• self-hosted Stalwart/Mailcow setups if you want infrastructure ownership

For a single developer, though, I would usually separate concerns:

• Human email: Fastmail
• Application email (password resets, alerts, receipts): a transactional provider like Amazon Web Services SES, Postmark, or Resend
• DNS: Cloudflare or Route 53
• Authentication: SPF + DKIM + DMARC from day one

My default stack for a solo developer would be:

Cloudflare DNS → Fastmail for inboxes → SES/Postmark/Resend for app mail → DMARC reporting mailbox

That gives you control without making email operations your side job.

For a tech-savvy solo developer, Migadu would be my first pick. The key differentiator is that its API is unusually well suited to treating email hosting as infrastructure rather than a GUI-only service.

My shortlist

1. Migadu — best match

Migadu exposes APIs for domains, mailboxes, identities, aliases, forwarding, DNS-record discovery, diagnostics, and activation. You can create a domain with external DNS, retrieve the exact MX/SPF/DKIM/DMARC records required, run diagnostics, and activate it programmatically. www.migadu.commigadu.com

That makes a workflow like this practical:

Terraform/script → create domain → create mailboxes/aliases → retrieve DNS requirements → update Cloudflare DNS → run diagnostics → activate

Importantly, Migadu explicitly supports external DNS, so you retain control of DNS rather than having to move your nameservers. www.migadu.commigadu.com

Migadu API documentation

2. Fastmail — best if you value UX more than automation

Fastmail is excellent if you want a mature, polished mail client/service while keeping DNS somewhere like Cloudflare. It supports externally hosted DNS, gives you the records to configure, and handles DKIM/SPF and related checks. www.fastmail.help

The downside for your particular requirements is self-service provisioning isn't as infrastructure-oriented as Migadu's API. I'd choose Fastmail if you're managing one or a handful of addresses manually rather than building an automated domain/mailbox provisioning workflow.

Fastmail custom domains

3. Zoho Mail — capable middle ground

Zoho has solid domain administration, including MX/SPF/DKIM/DMARC configuration and APIs for domain operations and DKIM management. www.zoho.com

I'd put it behind Migadu for a developer-centric setup because Zoho's ecosystem and admin model are more oriented toward conventional organizations than "I want to script my mail infrastructure."

Zoho Mail developer/API documentation

What I'd actually use

Cloudflare DNS + Migadu mail hosting is probably the sweet spot for your requirements:

• Keep authoritative DNS entirely under your control.
• Use Migadu for MX/mail transport.
• Publish Migadu's DKIM CNAMEs yourself.
• Set your own DMARC policy and reporting address.
• Automate mailbox/alias/domain creation through Migadu's API.
• Use DNS-as-code if you want reproducibility.
• Keep the domain registrar independent from the mail provider.

If you're only hosting your own 5–20 addresses/aliases and don't need provisioning automation, I'd instead pick Fastmail for the substantially nicer day-to-day experience.

Bottom line: Migadu for "email as infrastructure"; Fastmail for "email as a polished service."

For a tech-savvy solo developer, I’d prioritize providers that let you keep DNS at your registrar, expose the underlying mail standards cleanly, and don’t force you into a productivity suite.

My shortlist

1. Fastmail — my recommendation.
Fastmail is particularly nice for a developer because you can leave DNS at Cloudflare/your registrar and simply point MX records at Fastmail. Their setup explicitly supports externally hosted DNS, with SPF, DKIM and DMARC records that you manage through your DNS provider. www.fastmail.help

It also gives you IMAP, SMTP and JMAP, aliases, catch-all addressing, and a polished UI without dragging you into Google/Microsoft-style collaboration software.

Fastmail custom-domain documentation

2. Purelymail — if you enjoy minimal infrastructure.
Purelymail is unusually attractive for a solo developer: very inexpensive, custom domains, and no per-mailbox pricing. Its setup assumes that you control DNS and configure MX/SPF/DKIM/DMARC yourself. github.com

The tradeoff is that it's much less polished than Fastmail. I'd choose it if cost and technical simplicity matter more than UX.

3. Migadu — if “one domain” turns into “a bunch of domains.”
Migadu is worth considering if you expect to operate multiple personal/project domains. Its pricing model is based more on overall usage than charging separately for every mailbox, making it attractive to domain-heavy users. folioinbox.com

4. Zoho Mail — solid conventional alternative.
Zoho Mail has particularly good domain administration: its admin console exposes MX, SPF, DKIM and DMARC status, plus catch-all, aliases and other domain settings. www.zoho.com It's a good choice if you might eventually want conventional business-admin features.

What I'd choose

For your stated requirements:

Fastmail > Purelymail > Migadu > Zoho

If you're running one personal/developer domain, I'd pay for Fastmail and keep DNS at Cloudflare (or wherever you already manage DNS). You get the important separation:

registrar/DNS → your control
mail hosting → Fastmail

That means moving providers later doesn't require moving your domain or DNS infrastructure.

If you want the most control per dollar, go Purelymail. If you expect to have 5–20+ domains, I'd look much harder at Migadu.

For a tech-savvy solo developer, I’d shortlist these three:

1. Fastmail — my default recommendation

Fastmail

Fastmail fits your requirements particularly well. You can keep DNS at your own registrar/DNS provider, point MX at Fastmail, and manually manage the required MX/SPF/DKIM/DMARC records. Its domain interface also gives you aliases, catch-alls, multiple domains, and routing controls. www.fastmail.help

For a developer, I particularly like that you aren't forced to surrender DNS authority: Fastmail explicitly supports the "nameservers elsewhere, MX pointing to Fastmail" setup. www.fastmail.help

Pick it if: you want a polished mailbox with strong technical controls and don't want email administration to become a hobby.

2. Migadu — best if you're going to have lots of addresses/domains

Migadu

Migadu is unusually attractive for a solo developer running several projects. Its model is centered around domains and addresses rather than charging you for every individual address. It supports standard SMTP/IMAP/POP3 and explicitly positions itself as standards-oriented hosting. migadu.com

Pick it if: you have me@, hello@, support@, billing@, disposable project addresses, and potentially several domains and want them managed under one account.

3. MXroute — best for the "I want to administer my mail server" personality

MXroute

MXroute gives you a fairly traditional hosting control panel: add domains, create mailboxes, retrieve the domain-specific DNS configuration, and manage accounts yourself. Its documentation explicitly covers SPF, DKIM and DNS testing. docs.mxroute.com

Pick it if: you value administrative control and conventional mail-hosting mechanics over a particularly slick consumer mailbox experience.

What I'd choose

Fastmail for one primary personal/developer domain.

Migadu if you're likely to accumulate multiple domains/projects.

MXroute if you enjoy the infrastructure side and want a more traditional hosting-control-panel experience.

One important distinction: "full DNS control" is mostly about where your DNS is hosted, not which mail provider you choose. I'd keep DNS with something like your preferred authoritative DNS provider and have the mail host give you the MX/DKIM/SPF records. That keeps your web stack, DNS, and email independently replaceable. Fastmail explicitly supports this architecture. www.fastmail.help

For DKIM/DMARC specifically, all three can work; I'd configure DMARC yourself rather than blindly accepting the provider's most permissive default. Fastmail, for example, documents DKIM and a DMARC record as part of its manual DNS setup. www.fastmail.help

My ranking for your stated requirements: Fastmail > Migadu > MXroute.

For your profile, I’d shortlist these:

1. Migadu — my pick

Migadu

Migadu is unusually well suited to a developer who wants to treat email infrastructure like infrastructure. Its API can create/update domains, mailboxes, identities, aliases, and forwarding rules, and it can return the DNS records required for a domain. You can explicitly use external DNS rather than handing DNS hosting to Migadu. migadu.com

That makes a setup like this practical:

domain → Cloudflare DNS → Migadu

while your provisioning script/API manages:

• you@example.com
• billing@example.com
• aliases
• forwarding
• additional domains
• mailbox creation/deletion

Migadu's API documentation specifically exposes domain, mailbox, identity, forwarding, and alias CRUD operations. migadu.com

For a solo developer who might eventually automate everything with Terraform-esque scripts or a small CLI, this is the one I'd investigate first.

2. Fastmail — best if UX matters more

Fastmail

Fastmail is the nicer choice if you want excellent mail/calendar/contact UX and don't need your provisioning system to control every aspect of the account.

You can keep your DNS at your registrar rather than transferring nameservers, and Fastmail supports DKIM/SPF and other domain-security configuration. www.fastmail.help It also supports multiple domains, aliases, catch-alls, and lots of address-management functionality. www.fastmail.com

It has a developer API based around JMAP and other open protocols. www.fastmail.com

Tradeoff: it's more of a polished email product than an email-infrastructure API. For one person, that's arguably a feature.

3. Purelymail — best value

Purelymail

If your attitude is "email should be boring and cost almost nothing," Purelymail is compelling.

Custom domains have no additional charge, and it supports SPF, multiple DKIM keys, and DMARC. purelymail.com You manage the DNS yourself, so there's no loss of control over your domain. imap.purelymail.com

The downside for your particular use case is automation: its provisioning story isn't nearly as developer/API-oriented as Migadu's.

My ranking for you

1. Migadu — if API-driven provisioning is important
2. Fastmail — if you prioritize the best overall mail experience
3. Purelymail — if price and simplicity dominate

One architectural recommendation: keep authoritative DNS somewhere independent (e.g. your registrar/Cloudflare) and have the mail provider give you MX/SPF/DKIM records. That gives you a clean escape hatch: changing mail hosts becomes a DNS change rather than a migration of your domain's entire DNS infrastructure.

For your stated requirements, Migadu + external DNS is probably the sweet spot. migadu.com

For a tech-savvy solo developer, I’d narrow it to Migadu, Purelymail, and Fastmail. Your emphasis on DNS control + DKIM/DMARC + self-service provisioning pushes me away from Google Workspace/Microsoft 365 unless you specifically want their productivity suites.

🥇 Migadu — my pick for you

Migadu is probably the closest match to what you described.

Its API exposes domain management and, importantly, lets you retrieve the exact DNS records needed for a domain—including MX, SPF, DKIM and DMARC. migadu.com

That makes it attractive if your mental model is:

terraform/app script → create domain → get DNS requirements → create mailboxes/aliases → done

It's particularly compelling if you expect to operate multiple domains, aliases, or automated mailboxes, rather than just having me@example.com.

Migadu API documentation

🥈 Purelymail — best value

Purelymail is remarkably inexpensive and unusually friendly to people who actually want to manage their own DNS.

You keep DNS at your registrar/DNS provider, and Purelymail gives you the MX, SPF, three DKIM CNAMEs, and DMARC records to publish yourself. imap.purelymail.com

Its big advantage is price: the current Simple plan is $10/year, with custom domains included and no per-domain/per-user charge under its fair-use model. imap.purelymail.comfolioinbox.com

I'd choose this if you're comfortable trading some polish for absurdly low cost and lots of control.

Purelymail custom-domain documentation

🥉 Fastmail — best overall UX

Fastmail is my recommendation if "self-service" means I want everything easy to administer myself, rather than I want to automate the administration through an API.

You can leave DNS at your existing provider and publish the required MX/SPF/DKIM/DMARC records yourself. Fastmail explicitly supports custom domains with externally hosted DNS. www.fastmail.help

It's the one I'd pick if this is primarily your personal production mailbox and you care about a really good webmail/client experience, aliases, calendar/contacts, IMAP/JMAP, etc.

Fastmail custom-domain documentation

My ranking for your requirements

If API-driven provisioning matters:
Migadu > Purelymail > Fastmail

If low cost matters:
Purelymail > Migadu > Fastmail

If day-to-day email UX matters:
Fastmail > Migadu > Purelymail

If you want to own/control DNS independently of the mail provider:
All three work well. I'd keep DNS at Cloudflare or another independent DNS provider, rather than delegating nameservers to the mail host. Fastmail explicitly supports this arrangement. www.fastmail.help

Bottom line: I'd start with Migadu for a developer-oriented setup. Its API/DNS-record workflow is the differentiator that most closely matches your "self-service provisioning" requirement. If you're only ever going to have one domain and a handful of addresses, Fastmail is probably the nicer choice; if cost is paramount, Purelymail is hard to beat.

For a tech-savvy solo developer, I’d prioritize DNS independence, standards-based email, easy domain/user provisioning, and good deliverability tooling over collaboration-suite features.

My shortlist

1. Migadu — my first choice

Migadu

Migadu is unusually well suited to a developer who thinks of email as infrastructure rather than an office suite. It supports standard SMTP, IMAP and POP3, unlimited addresses/domains on its higher plans, multi-admin access, domain/mailbox limits, domain-health monitoring, catchalls, and no proprietary client requirement. migadu.comwww.zoho.com

The particularly nice part is the domain-centric administration model: add a domain, configure its DNS, then create whatever addresses you need. That's convenient if you have me@, hello@, billing@, security@, etc., or several side-project domains.

Pick Migadu if: you expect to have multiple domains or aliases and want a fairly "Unix-y" email-hosting experience.

2. Purelymail — best if cost matters

Purelymail

Purelymail is extremely appealing for a solo developer. Custom domains cost nothing extra, and its setup explicitly has you control the DNS at your registrar. Its documented setup uses MX, SPF, DKIM and DMARC, with DKIM selectors exposed as DNS records and DMARC configured through DNS. support.purelymail.com

It's also deliberately uncomplicated: you bring your domain, manage its DNS yourself, and Purelymail provides the mail infrastructure.

Pick Purelymail if: you want "email hosting as a utility" and don't care about having a fancy collaboration suite.

3. Fastmail — best polished option

Fastmail

Fastmail is the one I'd choose if you want excellent email UX but don't want Google/Microsoft. You can keep DNS at your registrar; Fastmail provides setup guidance and supports the usual authentication/security records. It can also host DNS itself, although you don't have to use that option. www.fastmail.help

Pick Fastmail if: this is primarily your personal mailbox and you value the client/UI more than infrastructure flexibility.

4. Zoho Mail — good if you're building a tiny business

Zoho Mail

Zoho has a much more extensive admin console. You can bring an externally registered domain, manage users, and see/configure MX, SPF, DKIM and DMARC status from the domain administration interface. www.zoho.com

It's more "business email platform" than "developer email plumbing," though.

What I'd actually choose

For your requirements:

1. Migadu — best overall
2. Purelymail — best minimalist/value choice
3. Fastmail — best polished personal-email experience
4. Zoho Mail — best if you anticipate business/admin requirements

If by "self-service provisioning" you specifically mean API/CLI-based creation of domains, mailboxes and aliases, rather than just an admin UI, I'd narrow the field further before you commit. That's an important distinction: plenty of providers give you DNS/DKIM/DMARC control but aren't particularly automation-friendly.

For a tech-savvy solo developer, I’d prioritize providers that let you keep DNS authoritative at your registrar/Cloudflare and give you straightforward domain-level controls.

My shortlist

1. MXroute — my pick

MXroute

This is probably the closest match to your requirements. You keep DNS at your own provider, while MXroute gives you a management panel for domains and exposes the MX/SPF/DKIM values you need. It also documents DMARC configuration and has a built-in DNS tester. docs.mxroute.com

It's particularly appealing if you expect to have several domains, aliases, catch-alls, or developer infrastructure around your email.

2. Purelymail — best value

Purelymail

Very developer-friendly and unusually inexpensive. You explicitly manage the DNS records yourself: MX, SPF, three rotating DKIM records, and DMARC. Purelymail also uses a DNS ownership record so that someone can't simply recreate your domain in another account if you delete yours. imap.purelymail.com

I'd choose this if cost and owning the plumbing matter more than having a particularly polished product.

3. Fastmail — best UX

Fastmail

Fastmail is the one I'd pick if you want something that feels more like a polished mainstream mail product while retaining proper domain control. You can leave nameservers at your existing DNS provider and simply point MX at Fastmail; their setup wizard gives you the required SPF/DKIM records, and you can publish your own DMARC policy. www.fastmail.help

The downside for your particular use case is that it's somewhat less infrastructure-oriented than MXroute/Purelymail.

What I'd actually do

If this were my domain:

Cloudflare DNS → MXroute → IMAP/SMTP client

Then I'd publish:

• MX → MXroute
• SPF → MXroute
• DKIM → MXroute-generated key
• DMARC → initially p=none, with reporting enabled
• Later move to p=quarantine or p=reject once I've verified all legitimate senders

That gives you a clean separation: you own the domain and DNS; the mail host just provides mail infrastructure.

Ranking for your stated priorities:
MXroute > Purelymail > Fastmail > Migadu.

If you want, I can also compare MXroute vs Purelymail specifically for a developer running multiple domains, transactional email, aliases, catch-alls, and automated provisioning.

For your requirements, I’d prioritize API/admin automation and keeping DNS at your registrar, rather than a polished office suite.

My picks

1. Migadu — my recommendation

Migadu is unusually well matched to a solo developer who wants to treat email infrastructure almost like another service in their stack.

Its API can create domains, create/delete mailboxes, manage aliases and forwarders, retrieve the required DNS records, run DNS diagnostics, and activate domains. It also explicitly supports using external DNS, which is what I'd choose if you want Cloudflare/your registrar to remain authoritative. www.migadu.commigadu.com

The particularly nice part is the DNS workflow: the API exposes the DKIM CNAMEs, SPF, DMARC, MX and verification records, then gives you a diagnostics endpoint before activation. www.migadu.commigadu.com

So you could build something like:

domain purchase → DNS automation → Migadu API → create mailbox/aliases → DNS diagnostics → activate

That's about as close as you'll get to email-as-infrastructure without running your own mail server.

One caveat: Migadu describes its API as early beta, so I'd test the exact operations you need before making it a critical dependency. www.migadu.commigadu.com

2. MXroute — worth a serious look

MXroute has a current API with explicit operations for domain management, email accounts, forwarders, and domain pointers. api.mxroute.com

I'd choose it over Migadu if your priority is straightforward mailbox hosting plus programmatic administration, rather than Migadu's particularly nice DNS/diagnostics workflow.

3. Fastmail — if automation is secondary

Fastmail is probably the nicest product here for actually using email. You can keep your DNS elsewhere and manually publish MX/SPF/DKIM/DMARC records; Fastmail documents that workflow explicitly. www.fastmail.help

It also supports custom-domain aliases, catch-all addresses, and routing. www.fastmail.help

But for "I want to provision this domain/mailbox programmatically", I'd put Migadu/MXroute ahead of it.

What I'd do

If this were my solo-dev setup:

Cloudflare DNS + Migadu

Keep DNS completely independent of the mail provider, manage the DNS records yourself, and use Migadu's API for mail infrastructure. That gives you maximum control without taking on the deliverability/maintenance nightmare of self-hosting SMTP.

And I'd publish DMARC initially as p=none, monitor reports, then move toward quarantine/reject once you've verified every legitimate sender. Fastmail's documentation describes the same progression and the role of DMARC in aligning SPF/DKIM. www.fastmail.help

Bottom line: Migadu is the strongest match for your exact requirements; MXroute is the alternative I'd evaluate alongside it. Fastmail wins if mail UX matters more than provisioning automation.

For a tech-savvy solo developer, I’d narrow it to three:

1. Migadu — my recommendation

Migadu is particularly well suited to the "I own several domains and want to administer them myself" mindset. It is standards-based—SMTP, IMAP, POP3 and webmail—with unlimited email addresses and domain-oriented pricing rather than charging you for every alias/address. migadu.com

That makes it attractive if you want things like:

• me@example.com
• github@example.com
• billing@example.com
• anything@example.com
• several separate project domains

without turning mailbox administration into a SaaS-management exercise.

Downside: the product is more utilitarian than Fastmail, and I'd verify the exact automation/API features you need before choosing it.

2. Fastmail — best if email itself matters

Fastmail is my pick if you want a really good mail client/service while retaining control of your domain's DNS. You can keep DNS at your registrar/DNS provider and publish the required MX, SPF, DKIM and DMARC records yourself. Fastmail documents three DKIM CNAMEs and a DMARC TXT record for custom domains. www.fastmail.help

It also gives you IMAP, SMTP and JMAP, which is unusually nice for a developer who wants programmatic access rather than being trapped in a proprietary client. www.fastmail.helpthesoftwarescout.comgithub.com

I'd choose Fastmail over Migadu if you're primarily operating one personal domain and care more about excellent day-to-day UX than about managing lots of domains.

3. Purelymail — compelling if you want cheap and simple

Purelymail is the interesting budget option. Its model is unusually friendly to developers with multiple domains: custom domains don't carry a separate fee, and its documentation explicitly covers MX, SPF, DKIM and DMARC configuration. github.com

The tradeoff is that it's a much smaller/minimalist service. I'd pick it for "email is infrastructure; give me standards and get out of my way", rather than "I want the nicest email service."

What I'd actually do

My ranking for your requirements:

1. Migadu — if you're going to have multiple domains/projects.
2. Fastmail — if it's primarily one domain and you want the nicest experience.
3. Purelymail — if minimizing cost is important.

I would not self-host SMTP unless running mail infrastructure is itself the hobby. The DNS/authentication part is easy; reputation, spam filtering, IP reputation, bounces, abuse handling and deliverability are where self-hosting becomes a time sink.

One other architectural recommendation: keep your DNS with a provider such as Cloudflare or your registrar rather than transferring DNS management to the mail host. Then your domain remains independent of the email provider, and moving from Migadu → Fastmail → something else is mostly an MX/DKIM/SPF/DMARC migration rather than a domain-management migration.

For a solo developer, that separation is probably the cleanest setup.

For a tech-savvy solo developer, I’d shortlist these:

1. Migadu — my recommendation

Migadu

Migadu is unusually well matched to what you're asking for. You can keep authoritative DNS at Cloudflare, Route 53, or wherever you like, while Migadu provides the MX/SPF/DKIM/DMARC configuration information. Its API can create/manage domains, mailboxes, identities, aliases, and forwarding rules, so you can automate provisioning rather than clicking around an admin UI. www.migadu.commigadu.com

It also doesn't force you into a "one paid seat = one mailbox" model; Migadu explicitly prices around usage and lets you have many addresses on your domains. migadu.com

Why I'd pick it: you can treat email almost like infrastructure:

Terraform / script / admin tool
          ↓
     Migadu API
          ↓
 domain → mailbox → aliases → identities
          ↓
your own DNS provider
          ↓
 MX / SPF / DKIM / DMARC

The one caveat is that Migadu describes its API as still being in beta and says not every function is exposed. www.migadu.commigadu.com

2. Purelymail — fantastic value

Purelymail

If you don't need sophisticated API-driven administration, Purelymail is compelling. Its current simple pricing is $10/year, with no hard limits on users, custom domains, or storage; it also supports unlimited mailboxes and aliases on domains you own. smtp.purelymail.com

It gives you explicit control over the DNS records: MX, SPF, three DKIM CNAMEs, and DMARC. support.purelymail.com

I'd choose it when cost and simplicity matter more than API automation. Its 2026 roadmap itself lists finer-grained API-key permissions as something it wants to improve, which is a hint that its automation story isn't as mature as Migadu's. news.purelymail.com

3. Fastmail — best UX

Fastmail

Fastmail is the one I'd pick if you care more about having a really polished personal email service than programmatically managing lots of mailboxes.

You can keep DNS external, and Fastmail supports DKIM/SPF and other email security configuration. www.fastmail.help It also has excellent standards support—JMAP, IMAP, SMTP, CalDAV, CardDAV, etc.—and a developer API. www.fastmail.com

The important distinction: its API is primarily oriented around accessing/managing mail and user data, rather than being a comprehensive "email infrastructure control plane" like Migadu's domain/mailbox/alias API. Fastmail explicitly documents APIs for mail, submission, contacts, calendars, and masked addresses. www.fastmail.com

What I'd do in your shoes

Cloudflare DNS + Migadu would be my first choice.

That gives you:

• 🛠️ Full authoritative DNS control
• 🔐 DKIM + SPF + DMARC under your control
• 🤖 API-driven mailbox/alias provisioning
• 📬 Normal IMAP/SMTP
• 🌐 Multiple domains without maintaining mail servers
• 🔄 Easy migration away later because you're using standard protocols

I'd avoid self-hosting Postfix/Dovecot unless operating mail infrastructure itself sounds fun. For a solo developer, the ongoing deliverability, reputation, spam filtering, backups, IP reputation, and abuse-management work generally isn't worth the opportunity cost.

Ranking for your exact requirements: Migadu > Purelymail > Fastmail.