There's a particular kind of person who reads "we never store your email" and thinks: I'd rather not have to take your word for it. If that's you, self-hosting is the honest answer to a trust problem. Instead of believing a company's privacy promise, you run the software yourself and the promise becomes a fact you can verify.
This guide is about what self-hosting an email dashboard actually means when you're managing several accounts or businesses, what it does and doesn't protect, and how to think about running your own rather than handing your mail to someone else's server.
It's worth drawing a line carefully here, because "self-hosted email" gets used for two very different things.
Running your own mail server means operating the actual infrastructure that receives and stores mail: the SMTP and IMAP servers, spam filtering, the works. This is famously hard. Deliverability alone, getting the big providers to trust mail from your server rather than dumping it in spam, is a part-time job, and most people who try it eventually go back to a host.
Self-hosting an email dashboard is a different and much lighter thing. Your mail still lives at whatever provider you already use, Fastmail, Workspace, a hosted domain mailbox. What you self-host is the client layer: the application that connects to those mailboxes, organizes them, and shows them to you. You get control over the tool that touches your mail without taking on the misery of running a mail server.
This guide is about the second one. It gives you most of the control people actually want, without the deliverability nightmare.
For managing multiple accounts, self-hosting the client layer buys you a few specific things.
The privacy claim becomes auditable. A hosted email tool asks you to trust that it does what it says with your mail. Self-hosted, open-source software lets you read the code and run it yourself, so "email bodies are never stored" stops being a promise and becomes something you can confirm. The claim is only as good as your ability to check it, and self-hosting is how you check it.
Your mail doesn't transit a third party's server. With a hosted dashboard, your mail passes through their infrastructure to be fetched and displayed. Self-hosted, it passes through yours. For people handling sensitive client work or who simply don't want a startup in the path of their email, that's the whole point.
No dependency on a company's survival or pricing. Hosted tools get acquired, shut down, or change their plans. Software you run yourself keeps working regardless. For something as load-bearing as email, that durability has real value.
Not all "open source" is equal, and for multi-account use the bar is specific.
A real license, not a look. Check that it's genuinely open source under a recognized license like AGPL or MIT, and that the self-hostable version is the full product, not a hollowed-out version with the useful parts held back for the paid tier.
Organizes by business, not just by account. The reason you have multiple accounts is usually multiple businesses. The dashboard should let you keep those genuinely separate, with the right sending identity per business, not just list your accounts in a sidebar.
Works with standard mail providers. It should connect over IMAP and SMTP to whatever you already use, so self-hosting the client doesn't force you to also migrate your mailboxes.
Reasonable to actually run. A self-hostable tool that takes a weekend to stand up isn't self-hostable in practice. Look for a straightforward path: a container, a clear database requirement, plain setup docs.
Cereal is open source under AGPL, and the self-hosted build is the full product, not a stripped demo. You run it against any Postgres database, point it at the mailboxes you already own over IMAP and SMTP, and it organizes them the same way the hosted version does: each business in its own bowl, mail routed by the address it was sent to, the right identity set by which bowl you're in.
Because the source is public, the privacy posture is auditable rather than asserted: email bodies are processed in memory and never stored, credentials are encrypted at rest, and you can read exactly what the code does before you trust it with your mail. One honest caveat worth stating plainly, the same one that applies to any dashboard of this kind: when the app fetches and renders your mail, it passes through the server running it. Self-host it and that server is yours, which is the entire reason to self-host. If you'd rather not run anything, the hosted version exists; if you'd rather own the whole path, the code is there. Our roundup of open source email clients for multiple accounts covers how the broader landscape compares.
Self-hosting isn't about distrust for its own sake. It's about turning a privacy promise into something you can verify, and keeping your mail on infrastructure you control. For multi-business email, that's an option worth having.