# Custom-domain email for indie SaaS

> One to three people shipping a product need mail on their own domain, a way for the app to send, and somewhere replies land. What it costs and how to set it up.

- Published: 2026-09-29
- Author: Koltrix Team
- Category: Startups
- Source: https://koltrix.com/blog/custom-domain-email-for-indie-saas

The email setup for a small SaaS ends up the same way almost every time. You start with a personal Gmail. You add Workspace when you need `you@yourproduct.com`. You add a transactional API when the app has to send a password reset. You add a newsletter tool when you want to tell people what you shipped. Three vendors, three bills, three sets of DNS records, and no two of them know anything about each other.

## What you actually need

1. **A mailbox on your own domain** that you and your co-founder can both read, plus shared addresses like `support@` and `hello@`.
2. **A way for the application to send** — an HTTP API or SMTP, with delivery webhooks so you know what happened.
3. **Somewhere replies can land.** This is the one everybody skips, and then discovers a year later that customers have been replying to `noreply@` the whole time.
4. **Deliverability that is somebody's job.** SPF, DKIM, DMARC, bounce suppression and complaint handling.

Note what is not on that list: a campaign builder, an audience segmentation engine, landing pages, or a CRM. Those are real products for real problems, but they are not the problem you have in year one.

## Which addresses should a one-to-three person SaaS create?

Start with few and add when something needs its own owner. Every address is a thing someone has to read.

| Address | Purpose | Who reads it |
|---|---|---|
| `you@yourproduct.com` | Your own mail, replacing the personal Gmail | You |
| `support@` | Customer questions, shared | Whoever is on support that week |
| `hello@` | General inquiries and press | A founder |
| `billing@` | Receipts, invoices, payment questions | A founder |
| `security@` | Vulnerability reports and customer questionnaires | A founder |
| An address for app mail, such as `notifications@` | The From address for transactional mail, with replies routed to the team | Nobody directly; replies go to the inbox |

Role addresses like `info@` and `admin@` attract spam and bounce differently from personal ones; [role addresses](/blog/role-addresses-like-info-and-admin-why-they-bounce-and-what-to-do) covers the details. For the app address, resist `noreply@`: there is a [case against it](/blog/noreply-address-case-against), and replies to it are a free source of customer feedback.

## What DNS records does the setup need?

Four kinds of records: MX for receiving, plus SPF, DKIM and DMARC for proving the mail is yours. SPF lists who may send for the domain, DKIM signs each message so receivers can check it was not altered, and DMARC tells receivers what to do when both fail. The [plain-English guide to all three](/blog/spf-dkim-dmarc-in-plain-english) explains each one, and the [DNS records reference](/blog/dns-records-for-email-reference) lists every record a sending domain needs in a single table.

| Record | Where it lives | Safe to publish before the switch? |
|---|---|---|
| SPF (TXT) | Domain root | Yes, as long as it still includes your current sender |
| DKIM (TXT) | A selector under `_domainkey` | Yes, it does not affect anything already in place |
| DMARC (TXT) | `_dmarc` | Yes; start at `p=none` and read the reports |
| MX | Domain root | No; this is the step that moves inbound mail |

## What does it cost?

Plans and prices are on the [pricing page](/pricing), which shows the current figures in your local currency, so we do not repeat numbers here that would go stale. What matters for an indie team is the shape of the bill: one vendor covering the mailbox, the sending API and the shared inbox, instead of three subscriptions that each charge per seat or per message.

## Should the app send from the main domain or a subdomain?

For a team this small, the main domain is fine at first, as long as you keep the volume modest and the content honest. Once you add newsletters or product-announcement mail alongside password resets, move the bulk mail to its own subdomain so a complaint spike cannot touch the mail your customers must receive. The [subdomain strategy post](/blog/sending-subdomain-strategy) walks through when to make that split.

## The setup, start to finish

1. **Add your domain.** You get an SPF record, a DKIM record and a DMARC record to publish, plus MX records when you are ready to receive.
2. **Publish the records** at your registrar. Verification is usually minutes, occasionally an hour.
3. **Create your addresses.** One for you, one for each person, and the shared ones.
4. **Send a test message** and check it lands in an inbox, not a spam folder.
5. **Point the app at the API**, or at SMTP if it already speaks SMTP.
6. **Switch MX over** when you are ready for mail to arrive. This is the only irreversible-feeling step, and it is the one to do on a quiet morning.

If you are moving from Google Workspace, the cut-over has a specific order — there is a [checklist for it](/blog/moving-from-google-workspace).

## What goes wrong most often?

- **Publishing a second SPF record** instead of editing the first. A domain can have only one; two make SPF fail.
- **Switching MX before the addresses exist.** Mail bounces for any address you have not created yet.
- **Forgetting the sender nobody remembers**: the invoicing tool, the status page, the form on your marketing site. Each one needs to authenticate as your domain or be replaced.
- **Skipping the test from an outside address.** A message sent from one address to another on your own domain proves very little.
- **Leaving DMARC at `p=none` forever.** It is the right place to start and the wrong place to stay; the [rollout guide](/blog/dmarc-none-to-reject-rollout) shows how to tighten safely.

## Where agents actually help

A two-person team does not need AI to write its email. It needs AI to stop reading email it did not want. The two jobs that pay for themselves are screening cold outreach — a founder with a public address gets a startling amount of it — and remembering what was promised, in both directions, without a spreadsheet.

Anything beyond that should be a proposal you approve rather than an action taken for you. We do not let agents send.

## The honest limits

If you need Docs, Sheets, Calendar and Meet, you need Workspace, and Koltrix is not a replacement for it. If your team lives in Apple Mail or Outlook, we have no IMAP access yet. If your enterprise customer's security questionnaire requires SOC 2, we do not have it. Those are the three reasons a small team should not move to us yet, and it is better to say so here than to find out during onboarding.
