The LAST free Semurg nodes EVER: the first 1,000 are free, for a limited time. After that, every node is US$139, paid once.
Communications

Email and messaging for your people and your AI agents, inside your own machines.

Not another mail service. Every message lives on your Semurg machines 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 machines. 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.

Works today for messages between addresses on your machines: each member's memory finds them (below). Mail from the internet, searching messages by meaning, and by who said what to whom: coming soon.

One address for people and agents

Every person and every agent gets an address of the same form, name@ your machines' 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 key for the machine binds an address on the machines, 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 (the standard that lets your agent connect to tools) tool comms_bind_address, which the machine serves beside the memory tools, or POST /v1/comms/bind_address over HTTP. A fresh machine 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 machines 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.

Works today: send a message and read it. On the current release, tested from outside on a fresh machine: a person or an agent with an address sends a message to another address with POST /v1/comms/send; the recipient sees the conversation in POST /v1/comms/inbox with its unread count, and reads it with POST /v1/comms/thread or POST /v1/comms/read. Someone who is not in the conversation is refused by name and finds nothing of it in their own inbox. The machine serves the same calls as MCP tools beside the memory tools (comms_send, comms_inbox, comms_thread, comms_read); their fields are in llms.txt.

Works today: group conversations. On the current release, tested from outside on a fresh machine: one message goes to several people and agents at once, and every one of them sees the same conversation in their inbox with its members and their own unread count. A reply to the same people, from a person or from an agent over MCP, continues that conversation. Adding someone starts a new conversation: they do not see the earlier messages.

Works today: every message in its members' memory, and no one else's. On the current release, tested from outside on a fresh machine: a member's ordinary memory question, asked on their own scope with no conversation named, finds the message through the conversations they are in and cites it; it searches their 64 most recent conversations. Someone who is not in the conversation finds nothing of it, is refused by name if they ask for it, and nobody can write into it except by sending a message.

Works today: your own domain. The operator names the machines' domains when installing (for example SEMURG_COMMS_DOMAINS=acme.com,mail.acme.com); on the current release, tested from outside on a fresh machine, addresses on them bind (case does not matter), message each other and still resolve after a restart, and an address on any other domain is refused with the domains the machines answers for. Receiving mail from the internet for your domain is part of "Mail to and from the internet" below.

Our own mail

Every email semurg.io sends, licence keys included, goes out from our own Semurg install, signed for our own domain, with no outside mail provider in between.

Coming soon

Each of these moves to "works today" when it passes, from outside, on a published release.

  • Searching messages by who said what to whom, beside searching them by meaning.
  • Mail to and from the internet: sending to and receiving from addresses outside your machines, signed.
  • The same messaging on every way in: MCP, the HTTP API, the binary protocol and the client libraries.
  • Messages between machines in one set, then between two sets of machines.
  • Encryption at rest with a key for each user.

What your agents will be able to do

Coming soon.

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

  • Does it send and receive internet mail? Not on the current release: Semurg email is native to your machines, and the people and agents on it write to each other directly. Mail to and from addresses outside your machines is coming soon.
  • Does a message leave my machines? On the current release, no: messages between addresses on your machines stay on your machines.
  • 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 install. A single free machine has all of it, with no licence key.