Migadu vs Purelymail vs FolioInbox: Real Costs for Multi-Domain Operators

Pricing Arithmetic: Calculating the Real Monthly Bill for 3, 5, and 10 Domains

Calculating the true cost of multi-domain email hosting requires looking past headline rates. Overage fees, storage tiers, and annual commitments shift the math depending on your portfolio size and message volume.

Purelymail Cost Breakdown

According to Purelymail pricing documentation, the service offers a flat fee of $10 per year under its Simple pricing plan. This flat rate covers unlimited domains and mailboxes with standard storage allocations. It functions as an unbundled commodity infrastructure option, provided the operator is comfortable configuring DNS records, constructing SPF strings, and troubleshooting local email client settings without managed assistance.

Migadu Cost Breakdown

According to Migadu Official Pricing Documentation, plans are segmented by storage capacity and daily outgoing limits across all connected domains:

• Micro: Designed for light usage across domains with entry-level daily outbound allowances.
• Mini: Offers expanded daily outbound transmission capacity and shared mailbox storage for growing domain portfolios.

On Migadu, storage limits apply across the entire account rather than per domain, and hitting account ceilings requires upgrading to a higher plan tier.

FolioInbox Cost Breakdown

FolioInbox eliminates variable storage metering and charges flat rates determined by domain count and monthly transmission envelopes. Review detailed plan breakdowns on the FolioInbox pricing page:

• Folio Solo: Published on the FolioInbox Solo tier at $2.99 per month billed annually ($35.88 per year) or $3.50 billed monthly. Supports up to 3 custom domains with an outbound cap of 1,000 sends per month.
• Folio Studio: Published on the FolioInbox Studio tier at $12 per month billed annually ($144 per year) or $15 billed monthly. Supports up to 10 custom domains with an outbound cap of 6,000 sends per month. Priority support included.
• Folio Holding Co.: Published on the FolioInbox Holding Co. tier at $29 per month billed annually ($348 per year) or $39 billed monthly. Supports unlimited custom domains with an outbound cap of 30,000 sends per month. Includes an onboarding configuration review and DNS setup verification with SLA response times.

Folio has no free plan. It offers a 14-day free trial and a no-credit-card preview, then flat paid plans (Solo, Studio, Holding Co.). Storage is included across all tiers without per-gigabyte metering, subject only to a standard 15 MiB per-message attachment cap.

Cost Comparison Across Common Scenarios

If minimizing raw cash outlay is your exclusive operational metric, Purelymail provides the lowest baseline cost. However, infrastructure price is only one component; configuration maintenance and deliverability management account for the rest.

Email Authentication and Deliverability: Per-Domain DKIM, SPF, and DMARC Alignment

When sending transactional or commercial correspondence on behalf of multiple corporate entities, authentication must be mathematically isolated. Major mailbox providers immediately penalize unaligned messages under modern inbox security mandates.

According to IETF RFC 6376, DomainKeys Identified Mail (DKIM) attaches a cryptographic signature to the email header that verifies the message was sent by the authentic owner of the domain name and was not altered in transit. If an email host signs outgoing messages for brand-a.com using an omnibus cryptographic key belonging to a shared system domain or another client domain, strict DMARC alignment breaks. When evaluating options, review the comparison guide at Migadu vs Purelymail.

Authentication Management by Provider

• Purelymail: Requires manual DNS configuration for every domain you onboard. You must log in to your DNS registrar and construct custom MX records, paste SPF include: mechanisms, and create distinct CNAME or TXT records for DKIM public keys. Purelymail generates individual DKIM keys per domain, but verification and syntax integrity rest entirely on the operator. If you misconfigure your SPF string or exceed the 10-DNS-lookup limit, messages fail silently.
• Migadu: Enforces rigorous DNS compliance. Migadu provides dedicated DKIM keys and distinct SPF values for each domain zone. Migadu’s administrative panel continuously checks your DNS zones and alerts you if records deviate from required syntax. However, the process is completely manual: adding 10 domains requires navigating 10 separate DNS dashboards, generating 10 record sets, and pasting distinct records across your registrars.
• FolioInbox: Every custom domain automatically receives its own distinct DKIM private/public keypair and independent outbound signature. To eliminate configuration errors, Folio implements Domain Connect integration. At supported registrars, domain configuration occurs on a single screen without manual copy-pasting; authentication records publish to your zone file automatically with valid SPF, DKIM, and DMARC parameters.

For independent founders and solo founders managing multiple ventures, manually updating DNS records across multiple domains increases the risk of human error. A single misplaced colon in an SPF TXT record can invalidate outbound delivery across your entire customer list.

Daily Operations: Migadu vs Purelymail vs FolioInbox Under Load

Outbound message limits dictate how effectively a service handles operational bursts. Solo operators frequently encounter situations where invoices, customer notifications, or proposal follow-ups cluster into short time windows.

Outbound Sending Limits

Migadu structures outbound limits around daily message volume pooled across the entire account rather than per mailbox. Lower tiers enforce modest daily outgoing message caps across all connected domains, with a temporary tolerance buffer before further outbound mail is delayed or queued. If an operator conducts heavy morning communications on one brand, remaining outbound capacity for other domains is reduced for the rest of that daily cycle. Migadu also applies automated burst protection on shared servers to prevent rapid transmission spikes.

Purelymail enforces anti-abuse sending caps that scale dynamically based on account age and transmission patterns. While the service provides general capacity for standard correspondence, newer accounts face burst throttles to prevent spam generation. Sudden bursts of customer notifications can trip internal rate limiters, requiring support intervention to unblock queues.

Because limits are metered over a monthly billing cycle rather than a rigid 24-hour window, you can execute short-term outbound campaigns or deliver sudden bursts of client correspondence without tripping daily rate limiters.

Day-to-Day Email Management Workflow

The daily experience of managing multiple brands reveals the starkest divide among these platforms:

With Migadu and Purelymail, the provider operates purely as a protocol host. To check your email, you must link each domain's mailboxes into a local client like Apple Mail, Outlook, or Thunderbird using individual IMAP/SMTP credentials. Managing five domains with distinct addresses means managing five separate account trees in your sidebar. If you need to switch devices or set up a new laptop, you must re-enter credentials, port assignments, and SSL settings five times over.

With FolioInbox, your domains converge into a unified web application. Outbound identities are toggled directly within the composer interface. Selecting billing@agency.com automatically loads that domain's isolated DKIM key and specific HTML signature; switching to founder@ecommerce.store instantly switches the outbound signature, cryptographic envelope, and reply-to path within the exact same view. Authentication uses modern passwordless workflows: access is granted via cryptographic passkeys or secure magic links, removing stored IMAP account passwords from your security footprint.

Security, Encryption, and Data Handling Across All Three Services

Email security for multi-entity founders encompasses identity validation, secure transit, and access controls. Because business email accounts serve as the master password recovery mechanism for banking, registrar, and cloud infrastructure, authentication hygiene is paramount.

For foundational context on digital personal security, FTC phishing guidance emphasizes treating unexpected correspondence and requests for personal details with caution, while FTC guidance on how websites and apps collect and use information outlines why operators must maintain strict boundaries around how contact credentials are authenticated and shared.

Data handling and security architectures differ significantly across the three providers:

Storage and Encryption Standards

• 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. This server-side architecture is what allows cross-domain searching and server-level spam analysis without local client indexing.
• Migadu provides transport encryption (TLS) across all incoming and outgoing connections, storing data on infrastructure hosted in Switzerland and European datacenters. Migadu does not provide zero-knowledge encryption; mail is stored in standard formats to allow server-side IMAP indexing.
• Purelymail stores user mail on standard redundant cloud clusters with data encrypted at rest. It does not provide zero-knowledge encryption, ensuring standard search and anti-spam models operate without local client processing bottlenecks.

Authentication Credentials and Attack Surfaces

Both Migadu and Purelymail rely on traditional username-and-password pairs for IMAP/SMTP client authentication. While both platforms support multi-factor authentication (MFA/TOTP) for their administrative web portals, your local email clients authenticate over legacy protocols using raw passwords or generated "app passwords." If an app password is compromised from a local device, unauthorized actors can query your mail streams directly via IMAP.

Folio eliminates legacy mail application passwords entirely. Account access relies on FIDO2 WebAuthn passkeys (biometric facial scan, fingerprint, or hardware security key) or time-sensitive cryptographic magic links delivered to your recovery address. There are no static passwords stored in plain text or hashed form on Folio servers to be brute-forced or compromised in third-party credential stuffing attacks.

When to Choose Purelymail, When to Choose Migadu, and When Folio Fits Best

Every multi-domain operator operates under specific budget limitations, technical tolerances, and interface requirements. No single service fits every scenario.

Choose Purelymail If:

• Your primary objective is minimizing cash expenses, and you want to spend minimal amounts across multiple domains.
• You require raw infrastructure flexibility: creating distinct inboxes, forwarding hooks, and distribution lists across your domains.
• You prefer using third-party desktop mail applications (Apple Mail, Thunderbird) and do not mind manually configuring server settings, ports, and DNS records.
• Your daily send volumes are low to moderate and predictable, avoiding sudden bursts that might trip automated anti-abuse filters.

Choose Migadu If:

• You manage several domains that require distinct mailboxes used by different contractors, personal assistants, or family members.
• You want predictable outbound sending allocations without unexpected monthly charges.
• You are a technical user who wants compliant European hosting and is fully capable of manually maintaining DKIM, SPF, and DMARC TXT records across registrars.

Choose FolioInbox If:

• You are a solo operator running multiple LLCs, client projects, or eCommerce brands and want a single, consolidated inbox rather than switching between IMAP profiles.
• You need each domain to have its own independent cryptographic DKIM signature and distinct visual footer without managing local client aliases.
• You want automated DNS provisioning via Domain Connect to eliminate manual DNS entry errors.
• You prefer modern passwordless security using biometric passkeys over storing legacy IMAP credentials in local email apps.

Operators handling complex entity structures can explore how this operational model streamlines communication in our guide for multi-LLC owners.

Making the Switch: Migration Checklists and Technical Pitfalls

Transitioning production domains between email providers requires careful execution to avoid dropped messages, delivery failures, or broken authentication. Complete this operational checklist before altering active records:

1. Audit Existing DNS Time-to-Live (TTL): At least 48 hours prior to migrating, log into your DNS registrar or nameserver host. Locate your current MX records and lower the TTL value from 86400 seconds (24 hours) or 14400 seconds (4 hours) down to 300 seconds (5 minutes). This ensures that when you point your domain to a new mail host, the change propagates worldwide in minutes rather than days.
2. Catalog Active Outbound Services: Review all external platforms that send email on behalf of your domains. This includes payment gateways (Stripe), transactional engines (Postmark, SendGrid), website contact forms (WordPress, Webflow), and store platforms (Shopify). Make sure their authorization strings are preserved when you construct your new SPF record.
3. Export Historical Archives: If your previous host used IMAP, run an offline backup or export your data to .mbox or .eml files. Services like Purelymail and Migadu allow direct IMAP synchronization, while web-native services require local archival if you plan to retire the older hosting account.
4. Update MX Records First: Point your MX records to your new host's ingestion endpoints. Because you lowered your TTL in step one, incoming mail will rapidly divert to the new mailboxes without downtime.
5. Provision Dedicated DKIM and SPF Records: Immediately publish your new host's SPF parameters and DKIM public keys. Do not combine multiple SPF v=spf1 TXT records into separate lines; combine them into a single record to prevent total validation failures under RFC standards.
6. Audit Domain Deliverability: Before routing live customer inquiries or marketing updates, run a complete deliverability audit to confirm that DKIM signatures, reverse DNS, and DMARC alignment resolve cleanly.

Frequently Asked Questions

Can I send from multiple custom domains without exposing my personal email address?

Yes, provided your email host handles domain-level routing natively. When using FolioInbox, every domain you attach operates with its own isolated outbound identity, return-path envelope, and distinct DKIM signature; your personal address or master recovery email is never exposed in headers. With Migadu and Purelymail, you can avoid exposing your personal address by creating distinct, dedicated mailboxes for each domain and configuring separate outbound SMTP accounts in your email client, rather than using consumer Gmail "Send As" forwarders.

Do Migadu, Purelymail, and FolioInbox support per-domain DKIM signatures?

Yes, all three providers support per-domain DKIM keys to ensure messages pass DMARC alignment checks. Purelymail generates distinct DKIM records that you must paste manually into your registrar's DNS editor. Migadu generates distinct DKIM keys per domain and validates their syntax within its management portal. FolioInbox automatically generates distinct cryptographic keys for every connected domain and can publish them automatically to supported registrars via Domain Connect.

Can I use traditional IMAP desktop clients like Apple Mail or Thunderbird with FolioInbox?

No. FolioInbox does not expose legacy IMAP or POP3 endpoints and cannot be connected to third-party desktop mail applications. Folio is built exclusively as a unified web and mobile application accessed via browser or native Android app on Google Play. If your core operational workflow requires managing mail through desktop clients like Apple Mail, Thunderbird, or Outlook via traditional IMAP ports, Migadu or Purelymail is the appropriate choice.

What happens if I exceed my monthly outbound send limit on FolioInbox or Migadu?

On Migadu, sending limits are calculated on a daily basis across all connected domains. If an account exceeds its daily outgoing allocation, Migadu provides an operational buffer before rejecting or delaying subsequent outbound messages until the daily window resets or the plan is upgraded. On FolioInbox, outbound allowances operate on a predictable monthly cycle (1,000 sends on Solo, 6,000 on Studio, 30,000 on Holding Co.). If you approach or reach your monthly allocation, you can upgrade your plan directly from your billing dashboard to immediately restore sending headroom.

Calculate your multi-domain email costs with our free email cost calculator, or audit your current SPF and DKIM setup at folioinbox.com/tools/domain-health before migrating.