Email and messaging for your people and your AI agents, inside your own cluster.
Not another mail service. Every message lives on your Semurg cluster and becomes part of what your agents know. People and agents get addresses of the same form, and write to each other the same way.
Two promises
What Semurg communications is built to do. The sections below say what works on the current release and what is coming.
Private
Your messages stay on your own cluster. No outside mail provider stores or reads them, and only the people and agents in a conversation can open it.
Encryption at rest with a key for each user: coming soon.
Ready for your agents the moment it arrives
Every email and message becomes part of your agents' memory as it is stored, its text searchable by meaning at once, with no export and no pipeline to build. Searching by who said what to whom follows.
Coming soon, with sending.
One address for people and agents
Every person and every agent gets an address of the same form, name@ your cluster's domain. An agent can
hold its own address and talk to people, and to other agents, the way a person does.
Works today: give a person or an agent an address. On the current release, anyone with an API token for the
node binds an address on the cluster, as a person or as an agent, for themselves or for an end user of their app, with
one and the same call: the MCP tool comms_bind_address, which the node serves beside the memory tools, or
POST /v1/comms/bind_address over HTTP. A fresh node answers for the domain semurg.mesh, so an
address reads alice@semurg.mesh.
- An address belongs to one person or agent. Binding one you already hold answers that it is already yours, so a script can repeat it safely.
- An address someone else holds, an address on a domain the cluster does not answer for, or one that is not a valid address is refused, and the refusal says which and what to send instead.
- The fields and every refusal are in the API reference, generated from the release itself.
That is the whole list today: addresses. Nothing can be sent on the current release yet.
Coming soon
Each of these moves to "works today" when it passes, from outside, on a published release.
- Sending and receiving messages, one to one and in groups.
- An inbox and conversations for every person and every agent: newest first, page by page.
- Every message in your agents' memory, open only to the conversation's members.
- Searching messages by who said what to whom, beside searching them by meaning.
- Your own domain for addresses.
- The same messaging on every way in: MCP, the HTTP API, the binary protocol and the client libraries.
- Messages between the nodes of a cluster, then between two Semurg clusters.
- Encryption at rest with a key for each user.
What your agents will be able to do
Coming soon, with sending.
Answer from the conversation
"What did the supplier promise in last week's thread?" answered from the messages themselves, with the messages cited.
Work beside the people
An agent with its own address reports to its owner, and asks a person to approve before anything it drafts goes further.
Questions
- Is this a mail server for the internet? No. Semurg email is native to your cluster: the people and agents on it write to each other directly.
- Does a message leave my cluster? Messages between addresses on your cluster stay on your cluster.
- Is there an app or an inbox screen? Not yet. Communications works from your agents and your code first.
- What does it need? A Semurg node. A single free node has all of it, with no licence key.