Company email on a custom domain, built twice
Once as a mail server I administer, once as a serverless pipeline. Same result, opposite cost structures.
A small business wanted addresses on its own domain without paying per seat for a suite it would barely open. Mail punishes carelessness quietly: authentication that is almost right sends invoices to spam, and storage that is almost right loses one of them. The requirement was never "send email" — it was email that is trusted, delivered, and recoverable.
Two builds
A hosted stack I administer end to end, for a client who wants full control of storage and routing.
Inbound and outbound mail through managed functions and an email API. Nothing to patch, nothing idling.
The path a message takes
What went wrong first
Early sends passed every test I had written and still landed in spam. The fix was not code, it was DNS discipline: SPF, DKIM, and a DMARC policy that starts at none, gets read for a fortnight, then tightens. Deliverability is now a number I watch rather than a box I ticked, and the reverse-DNS and warm-up notes live in the runbook so nobody rediscovers them at midnight.