Why do my LLCs need separate email setups instead of just aliases?

An LLC's value as a liability shield depends on courts (and the IRS) seeing the entity as genuinely separate. Sending mail for two LLCs from the same DKIM key, the same SPF record, and the same envelope From muddies that line. Per-entity DKIM and SPF keep the cryptographic record of who signed what cleanly aligned with the LLC that owns the activity.

Will my CPA be able to tell which LLC sent which email?

Yes. Each bound domain gets its own RSA-2048 DKIM key generated at provisioning. The DKIM-Signature header in every outbound message names the signing LLC's domain explicitly, so the audit trail matches the bookkeeping.

Do I have to buy a separate plan for each LLC?

No. Emcognito charges per operator, not per LLC. The Studio plan ($12/month annual) covers unlimited domains — bind every LLC you own to the same account. Most multi-LLC operators expense the subscription against the parent or operating entity.

What if I sell one of the LLCs?

Unbind the LLC's domain from your account. The buyer's team can bind the same domain to their own Emcognito (or any other provider's) account using fresh DNS records. There is no data migration to negotiate — DNS is the boundary, and the unbound domain leaves nothing behind in your inbox.

Can I keep using my existing accountant's portal and just move email?

Yes. Email is the only thing Emcognito touches. Your accounting software, bank feeds, payroll, and tax-filing tools are unchanged. The migration is a DNS cutover per LLC's domain, walked through one entity at a time at /migrate/google-workspace if you're leaving Workspace.

Is this also compliant if one LLC operates in a regulated industry?

Per-domain DKIM, per-domain DMARC enforcement, and Amazon SES backed sending give each LLC its own deliverability posture — the same building blocks the regulated provider would expect. We're not a HIPAA-BAA provider today; if one entity requires that, keep that LLC on a HIPAA-capable provider and bind the rest into Emcognito.

For the owner of more than one LLC

Three LLCs, three sets of books.
One inbox.

An owner of multiple LLCs needs each entity's email to stay legally and reputationally separate — separate DKIM keys, separate SPF/DMARC, separate reply-From — while only one human sits at the keyboard. Emcognito WebMail keeps every LLC cryptographically isolated under one operator account and one flat price, instead of one Workspace seat (and one admin console, and one bill) per LLC.

You filed the second LLC because your CPA told you to. Then the third, because the next venture needed clean separation from the first two. The bank accounts are separate. The K-1s are separate. The IRS treats every entity on its own line.

Emcognito WebMail is the inbox that respects that line. Each LLC's domain has its own DKIM key, its own SPF posture, its own reply-From — so a letter to one entity never goes out signed by another.

Updated 24 May 2026 (2026-05-24)

Start free — no card See the price

Android app live on Google Play

I · The problem with one Workspace seat per LLC

Per-user pricing, paid per entity.

Most multi-LLC owners end up running one Google Workspace tenant per entity. It's the path of least resistance: each LLC gets its own admin console, its own billing portal, its own per-user license. At $7 per user per month per entity, three LLCs is $252 a year and four admin URLs on five laptops to keep straight.

The single-tenant alternative — running every entity through aliases on one Workspace seat — collapses sending reputations into one pool and makes DKIM-per-entity fiddly to configure. The cheap setup undermines the corporate boundary the LLCs exist to draw.

What you actually want is the opposite multiplication: one operator, paying one flat price, while every entity stays cryptographically and reputationally separate downstream.

Your CPA tracks each LLC separately. Your bank tracks each LLC separately. Your inbox shouldn't be the place where the entities collapse into one signature.

II · A morning across three entities

Three filings, one reader.

Not a screenshot — a live render in the same editorial design system the app uses. Each row's stripe is the domain the letter was sent to. Hover (or read quickly, by eye): which self is each one addressed to?

WED 14 MAY · 8:02 AM·The Correspondence4 letters

7:51 AM
Wells Fargo
owner@cobalt-properties-llc.com
via cobalt
Wire received · $84,300 — Unit 4B closing
A wire transfer of $84,300.00 has been received into your Cobalt Properties LLC checking account from Stewart Title…
7:38 AM
Square
hello@field-and-flour-llc.com
via field-and-flour
Weekly sales summary · Field & Flour Bakehouse
Field & Flour Bakehouse processed 412 transactions this week totalling $9,841. Top item: sourdough miche. One refund pending review…
yesterday
M. Patel, CPA
owner@northstar-consulting-llc.com
via northstar
Northstar Q1 estimated tax — confirmation needed
Confirming the Q1 estimated payment for Northstar Consulting LLC of $11,420. K-1 separation looks clean against last year's filing; one note on the deductible…
May 11
Counsel
owner@cobalt-properties-llc.com
via cobalt
Operating agreement amendment — Unit 4B
Per our call, the amendment to the Cobalt operating agreement is attached for signature. Note the schedule change on page 4 reflects the new member percentages…

III · How the entities stay separate

Per-LLC cryptography, one reading surface.

Each LLC's domain becomes a first-class identity inside the inbox: its own colour stripe in the margin, its own RSA-2048 DKIM key, its own SPF and DMARC posture, its own reply-From. The corporate veil stays intact at the protocol level — but you only sit in one editor.

·
One subscription, every LLC. You're one person reading mail for three entities. You pay for one seat — not three. The Studio plan covers unlimited LLCs at $12/month annual.
·
Per-entity DKIM, per-entity reputation. Each LLC gets its own DKIM key generated at bind. A bounce problem on the rental-property LLC's list cannot leak onto the consulting LLC's sending reputation.
·
Compliance-clean replies. When the title company writes to the rental LLC's owner@ address, the reply goes out from the rental LLC — DKIM-signed by the rental LLC's key. Never the consulting LLC. Never the bakery.
·
No console proliferation. One sign-in. One billing page. One suppression list. Three LLCs, zero admin sprawl across multiple Workspace tenants.

IV · What your CPA and counsel will ask about

Boringly auditable, entity by entity.

When you sit down for an audit, your CPA will want to know your mail trail respects the boundaries your entities exist to draw. These are the answers.

Per-LLC DKIM: Each LLC's domain has its own RSA-2048 DKIM key. An auditor tracing a disputed email can verify which LLC signed it — never an aggregate identity.
Entity data segregation: Messages are stored per identity. There is no shared 'all entities' bucket; retention rules apply per domain.
PITR backup: DynamoDB point-in-time recovery is on by default. An accidental delete on the consulting LLC's mail is recoverable to the second, without touching the bakery's mail.
Magic-link auth: Sign-in is a one-time, fifteen-minute link issued to your address. No password to rotate across three tenants, no 2FA codes per entity.

V · Common questions

Questions readers ask.

Why do my LLCs need separate email setups instead of just aliases?: An LLC's value as a liability shield depends on courts (and the IRS) seeing the entity as genuinely separate. Sending mail for two LLCs from the same DKIM key, the same SPF record, and the same envelope From muddies that line. Per-entity DKIM and SPF keep the cryptographic record of who signed what cleanly aligned with the LLC that owns the activity.
Will my CPA be able to tell which LLC sent which email?: Yes. Each bound domain gets its own RSA-2048 DKIM key generated at provisioning. The DKIM-Signature header in every outbound message names the signing LLC's domain explicitly, so the audit trail matches the bookkeeping.
Do I have to buy a separate plan for each LLC?: No. Emcognito charges per operator, not per LLC. The Studio plan ($12/month annual) covers unlimited domains — bind every LLC you own to the same account. Most multi-LLC operators expense the subscription against the parent or operating entity.
What if I sell one of the LLCs?: Unbind the LLC's domain from your account. The buyer's team can bind the same domain to their own Emcognito (or any other provider's) account using fresh DNS records. There is no data migration to negotiate — DNS is the boundary, and the unbound domain leaves nothing behind in your inbox.
Can I keep using my existing accountant's portal and just move email?: Yes. Email is the only thing Emcognito touches. Your accounting software, bank feeds, payroll, and tax-filing tools are unchanged. The migration is a DNS cutover per LLC's domain, walked through one entity at a time at /migrate/google-workspace if you're leaving Workspace.
Is this also compliant if one LLC operates in a regulated industry?: Per-domain DKIM, per-domain DMARC enforcement, and Amazon SES backed sending give each LLC its own deliverability posture — the same building blocks the regulated provider would expect. We're not a HIPAA-BAA provider today; if one entity requires that, keep that LLC on a HIPAA-capable provider and bind the rest into Emcognito.

VI · Adjacent readers

Where the claims come from.

Open the first letter

Three LLCs. One reader.

Start free, no card. Bind your first LLC's domain; route its inbound mail through Emcognito and see how the per-entity colour stripe and per-domain reply-From actually read in your morning. Add the other entities when the model proves out.

Start free — no card Read the manual