Migadu vs. FolioInbox: What One Operator With Six Domains Actually Pays

The arithmetic: six domains, one person, three ways to pay

When you run six businesses, your email setup usually falls into one of three buckets: enterprise suites like Google Workspace or Microsoft 365, a mailbox-metered host like Migadu, or a portfolio-focused provider like FolioInbox. The table below details what an operator pays and manages across these setups.

The alternative that many solo founders try is purchasing a single Google Workspace seat and attaching the other five domains as secondary alias domains. In practice, this setup frequently breaks. When you use consumer Gmail or a single Workspace seat to "Send As" an external address, the mail transport agent frequently signs the outbound message using the primary domain's DKIM key. When receiving servers inspect the email headers, the address in the From: line does not align with the signing domain in the d= tag. If the secondary domain has an active DMARC policy, the message may be discarded or routed to the spam folder.

To calculate what you are paying, check our email cost calculator to map your domain count against enterprise seat pricing. The break-even arithmetic is straightforward: an operator running six domains on individual Google Workspace Business Starter seats pays $36 per month ($432 per year), according to Google Workspace's published rates, whereas FolioInbox Studio costs $12 per month billed annually ($144 per year) for up to 10 domains, as outlined in the FolioInbox capability specification. The only constraint to watch is your sending volume: Studio caps outbound sends at 6,000 messages per month across your domains. If you send 50 to 100 conversational emails a day across all your brands combined, 6,000 sends per month leaves ample headroom. However, attempting to route a high-volume queue of transactional emails or marketing messages through a personal mailbox risks exceeding provider sending limits. Source: Folioinbox source.

Per-domain DKIM and signatures: the capability that decides this

Email authentication is no longer an optional configuration for custom domains. Major mailbox providers enforce strict verification requirements. If your DNS records do not demonstrate that your mail server has explicit authorization to dispatch mail for your domain, your messages will disappear into junk folders or bounce entirely.

The standard governing this is the IETF RFC 6376 specification, which defines DomainKeys Identified Mail (DKIM). DKIM works by publishing a public cryptographic key in your domain's DNS records via a TXT or CNAME entry. When an outgoing message is prepared, the sending server calculates a digital signature based on the body and select headers, injecting this signature into the DKIM-Signature header. The receiving mail server retrieves the public key from your DNS records and verifies that the message has not been altered in transit.

For an operator running multiple ventures, domain alignment is critical. Under DMARC (Domain-based Message Authentication, Reporting, and Conformance), receiving servers check whether the domain found in the visible From: header matches the domain authenticated by SPF and DKIM. This is known as cryptographic alignment:

• If an email claims to come from billing@storefront.com, but the DKIM signature specifies d=consultingfirm.com, alignment fails unless relaxed organizational policies apply.
• If alignment fails and storefront.com publishes a DMARC policy of p=reject or p=quarantine, the message will fail verification.
• Sharing a single cryptographic key across multiple client entities also exposes the connection between your different businesses inside raw email headers. Anyone inspecting the message source can see that your e-commerce store and your consulting brand share the same sending infrastructure.

This is why multi-domain email hosting requires per-domain keys. FolioInbox generates an isolated DKIM key pair for every single domain you attach. When you compose an email from your consulting address, it is signed using your consulting domain's private key. When you compose from your e-commerce domain, it is signed using that domain's private key. Each brand authenticates cleanly as an independent entity, ensuring full DMARC compliance.

Before modifying your current setup, run our free domain health audit to inspect your current SPF, DKIM, DMARC, and MTA-STS records. The tool evaluates your live DNS records without requiring an email gate, giving you a baseline of your deliverability health before you make changes.

What breaks during the move, and how to avoid it

Migrating email services across half a dozen domains is not fundamentally difficult, but executing steps out of sequence will result in bounced messages or deliverability penalties. According to established FTC phishing guidance, receiving systems increasingly flag unauthenticated or suddenly altered mail flows as potential phishing vectors, which means any disruption in your domain's DNS authentication records can immediately damage inbox placement.

Follow this strict order of operations when moving a domain:

1. Verify the domain and stage authentication records first: Add the domain inside your new email provider's console before touching your primary MX records. Generate your SPF, DKIM, and DMARC TXT entries and publish them to your DNS zone.
2. Wait for DNS propagation: DNS changes take time to propagate across global recursive resolvers. Do not touch your MX records until external DNS lookups confirm that your new DKIM public keys are resolving correctly.
3. Cut over MX records: Once your authentication records are verified, update your MX records to point to the new provider. Because inbound mail transfer agents will now find active SPF and DKIM rules immediately upon delivery, no incoming messages will bounce due to missing cryptographic parameters.
4. Purge redundant legacy records: A common failure mode occurs when an operator adds new MX records but forgets to delete older MX entries pointing to Google Workspace, Microsoft 365, or an old hosting server. Sending servers pick MX targets based on priority weights, but if multiple priorities match or servers cycle through available endpoints, mail delivery becomes intermittent and unpredictable.

The Domain Connect standard simplifies this process. When adding a domain inside FolioInbox, if your registrar supports Domain Connect, authentication and MX records can be published with a single authorization click. If you manage your DNS manually via Cloudflare, Route 53, or Namecheap, you can use our free SPF record generator and AWS WorkMail deadline checker under /tools to verify your record syntax before committing changes. Source: Migadu source.

When migrating historical messages, keep your previous email subscription active for at least one full billing cycle after completing your DNS cutover. Messages sent across the internet can occasionally route based on cached MX records for up to 48 hours. Retaining your old account ensures you capture any trailing deliveries while exporting local archive files (such as .mbox or .pst) for your business records.

When Migadu is the better choice for you

Migadu is an established, dependable platform that serves specific hosting requirements effectively. You should select Migadu if:

• You want traditional, decentralized mailbox architecture: If you prefer to configure unique IMAP and SMTP endpoints for every individual project inside dedicated desktop email clients, Migadu's system supports standard server protocols.
• You require traditional webmail access: If your workflow relies on webmail clients like Roundcube, Migadu provides them directly.
• You have a single primary domain with minor alias requirements: If your secondary domains exist solely to forward inbound mail to a main inbox and you rarely initiate new outbound conversations from those secondary entities, an aggregate resource plan on Migadu functions reliably.

Conversely, remember the functional limits. Folio is a single-operator inbox, not a team or shared mailbox — there are no per-user seats and no team collaboration features. If you manage a team where multiple employees need assigned conversations, private internal notes, and collective ownership of an info@ or support@ address, neither product is designed for your workflow. In that scenario, you should evaluate dedicated team software instead.

If your architecture requires custom server builds, keep in mind that Folio is a proprietary, hosted service; its source code is not public. Folio is a fully hosted service and cannot be self-hosted or run on your own servers or infrastructure. If running Postfix and Dovecot on your own hardware is your requirement, Migadu or a private server build is the appropriate path.

Finally, consider message privacy boundaries. Folio encrypts mail in transit (TLS) and at rest, but is not end-to-end or zero-knowledge encrypted: mail is stored server-side and readable by Folio for spam filtering and search. If your operational guidelines require zero-knowledge or PGP-encrypted mail storage where the infrastructure provider cannot parse server-side content, look toward specialized zero-knowledge encryption platforms.

When FolioInbox is the better choice for you

FolioInbox is engineered specifically for the portfolio operator who is exhausted by the administrative overhead of juggling multiple accounts. You should choose FolioInbox if:

• You operate multiple distinct brands alone: You own between 2 and 12 domains—such as a consulting business, an e-commerce shop, a side project, and a family investment LLC—and you need to dispatch and receive email from all of them without switching browser tabs or managing separate mail clients.
• You need clean, per-domain cryptographic authentication: Each of your businesses must pass DMARC checks under its own distinct domain name, with unique DKIM keys and separate custom signatures for every address.
• You are running against a concrete migration deadline: You are facing a Workspace annual renewal, the AWS WorkMail end-of-support timeline, or you need to launch a credible address for a formed LLC today.
• You want streamlined DNS management: You want a single-screen setup that automates record configuration via Domain Connect rather than copying and pasting records across multiple control panels.
• You manage communications from an Android mobile device: You want mobile access through the native Android app available on Google Play alongside modern, passwordless authentication using passkeys or magic links.

Independent business operators rely heavily on continuous, authenticated communication across client entities. Maintaining strict administrative boundaries between those entities protects your professional reputation. As highlighted in FTC guidance on how websites and apps collect and use information, keeping business identities authenticated and isolated prevents cross-contamination and credential leaks across auxiliary ventures.

Frequently Asked Questions

Is Migadu or FolioInbox cheaper for six domains owned by one person?

For one operator managing six domains, FolioInbox Studio costs $12 per month billed annually ($144 per year) and includes up to 10 domains and 6,000 monthly sends, as documented on FolioInbox's pricing page. On Migadu, pricing depends on your aggregate daily sending volume and storage tier across your mailboxes (as detailed on Migadu's pricing page). If your volume requires Migadu's higher-tier plans to support multiple mailboxes or heavier traffic, FolioInbox is often more predictable because it does not bill by mailbox count.

Does FolioInbox give each domain its own DKIM key?

Yes. FolioInbox automatically generates an isolated DKIM key pair and custom selector for every domain you connect. When an email is dispatched from an address on that domain, it is signed using its specific private key, ensuring full cryptographic alignment under strict DMARC policies.

Is there a free trial or preview available?

It offers a 14-day free trial and a no-credit-card preview, then flat paid plans (Solo, Studio, Holding Co.).

What happens to my mail if I move a domain and get the DNS order wrong?

If you cut over your MX records before your SPF, DKIM, and DMARC TXT records are fully published and propagated, receiving mail servers will reject or quarantine incoming messages because your domain fails cryptographic authentication. often publish and verify your authentication records before pointing your MX records to a new provider.

Can an account be used as a collaborative team setup?

No. Folio is a single-operator inbox, not a team or shared mailbox — there are no per-user seats and no team collaboration features. It is built strictly for individual operators who manage multiple entities, domains, or brands by themselves.

Conclusion: pick the pricing unit that matches your life

Choosing between migadu vs folioinbox comes down to identifying the unit of measurement that fits your workload. Per-mailbox pricing makes sense if you have a single domain and want conventional IMAP endpoints. Flat domain pricing makes sense if you are one human steering a portfolio of corporate assets and you want each entity to project an independent, credible image without enterprise costs.

The numbers remain consistent: six domains on Google Workspace Business Starter cost $432 each year in seat licenses (based on Google Workspace's published rates of $6 per user per month). On FolioInbox Studio, those same six domains cost $144 per year, with per-domain DKIM keys, distinct signatures, and 6,000 sends per month across your consolidated account (documented in the FolioInbox capability contract).

Run our free domain health audit to see your current SPF, DKIM, DMARC, and MTA-STS state with no email gate, then start the no-credit-card preview on one domain and connect it in a single screen.