Every hosted email assistant works the same way: you grant it standing access to your mailbox, it reads everything, and it drafts, summarises and sorts on somebody else’s computer. For a lot of people that is a fair trade. For a law firm, a hospital, a bank or a defence unit it is not a trade at all, because handing a third party continuous read access to correspondence is the thing they are specifically not permitted to do. Those are the people we built OpenMailBot for. It runs on your server, with a private language model if it must, inside the mail client you already use.
Why the usual answer is not available
The sectors that would benefit most from help with email are the ones that can least use the products on offer.
- Legal. Privileged correspondence cannot be disclosed to a vendor, and a mailbox is where privilege lives. An assistant that has read the thread has been told the secret.
- Healthcare. Patient information moves through email whether the policy says it should or not. An assistant with standing access to a clinician’s inbox has standing access to patient data.
- Defence and government. Outbound access to a commercial AI service is not a risk to be managed. It is not permitted.
- Finance. Pricing, deal flow and client instructions sit in threads, and the retention policy of a vendor is not something the firm controls.
None of these organisations has less email than anyone else. Most have more, with higher stakes per message, and the same problem everyone has: the detail needed to reply is in a different thread from four months ago, or in one a colleague was on.
What the assistant does
It does the work that eats a professional’s day, and it does it where the mail already is.
- Summarises a long thread into what was decided, what was promised, and what is still open.
- Drafts a reply with context — it retrieves the related correspondence first, so the draft reflects what was agreed elsewhere and not only what is on screen.
- Labels and sorts, and adjusts the register of a draft to the person it is going to.
- Never sends. Every draft is a suggestion for a person to read and send. Nothing leaves the building on the assistant’s own authority.
It appears as an add-in inside Gmail, Thunderbird or Outlook, so nothing about anyone’s day changes. There is no new inbox and no migration.
Where it runs, and why that is the whole point
The server is yours. The per-user mail data lives on storage you own. The model credentials are yours, and where the environment is strict enough, the model itself is installed locally, which means there is no external network call anywhere in the path. That is a system with nowhere to send your correspondence, which is a stronger guarantee than a policy promising not to.
For a legal practice that means privilege is not disclosed, because nothing is disclosed. For a hospital, patient data stays inside the network it was already inside. For a defence unit, the assistant works with the outbound connection turned off, because it never needed one.
What it costs you
A hosted assistant is an afternoon to set up. This is a deployment: a server, an integration with your mail system, and a policy conversation about who may see what. The strongest hosted models are also, on some tasks, a step ahead of the strongest models you can run yourself — for summarising and drafting correspondence the gap is rarely the deciding factor, but it exists and we would rather say so.
The same approach — your server, your model, an assistant that reads context and drafts but never acts alone — is how we build every communication tool, and the email assistant is the one that is ready today. If your organisation is one of the ones that cannot use the public products, the first conversation is about your mail system and your rules, not ours.