UIID Mail Is Now Available to Trusted Testers

LINKSPREED has released UIID Mail to Trusted Testers. UIID Mail is an email provider built from the ground up on the UIID identity infrastructure. It looks and feels like the email you already know. Underneath, it works in a fundamentally different way.

This is one of the most consequential things we have built, and not because the world needs another inbox. It is consequential because email is the last universal identifier on the internet — and for UIID to become a global identity layer, it has to be able to carry that role itself.

What UIID Mail is

UIID Mail is a complete email service. You have an address, an inbox, folders, search, attachments, contacts and the ability to send and receive messages. If you have used Gmail, Outlook or any modern webmail client, you already know how to use it. We consider that a design requirement, not a compromise. An identity layer that demands users relearn a daily habit will not be adopted, no matter how good the architecture behind it is.

The difference is what sits behind the interface. UIID Mail is not a classic mail server with a UIID login bolted on top. The mailbox, the addressing, the access control and the message storage are all built on the UIID platform’s own primitives: the decentralised identity, the encrypted key-value storage layer and the UIID API.

Why classic email works the way it does

To understand what is different, it helps to be precise about what conventional email actually is.

Classic email is not one system. It is a set of protocols, most of them designed in an era when the network was small, largely academic and broadly trusting:

SMTP (Simple Mail Transfer Protocol) moves a message from a sender’s server to a recipient’s server. It is the transport layer of email and it dates, in its original form, to the early 1980s.
IMAP (Internet Message Access Protocol) lets a client read and manage messages that remain stored on the server, which is how most people use email today across multiple devices.
POP (Post Office Protocol) downloads messages to a single device, historically removing them from the server.

Around this core, decades of additional layers have been added to compensate for what the original design did not include: authentication of the sender’s domain, protection against forgery, transport encryption, spam filtering, and reputation systems that decide whether a message is delivered at all. Each of these was a patch on an architecture that never assumed the sender might be lying.

The consequence is that in classic email, your identity is your address, your address is controlled by whoever operates the mail server, and the trustworthiness of a message is inferred from domain-level signals rather than from any property of the person who sent it. Change providers and you change identity. Lose access to the domain and you lose the identifier that every other service on the internet uses to recognise you.

How UIID Mail is built differently

UIID is a DID — a decentralised identity. The identity is the primary object. It exists independently of any single service, it is controlled by the person who holds it, and it can be presented to any system that speaks the UIID protocol.

That changes the starting point for building a mail service. Instead of beginning with a mail server and attaching accounts to it, UIID Mail begins with an identity that already exists and gives it the ability to send and receive messages.

The building blocks are already part of the platform:

The decentralised identity provides the account itself. There is no separate mail account to create, no separate password to manage and no separate recovery path to maintain. The identity that authenticates you everywhere else in the UIID ecosystem is the identity that owns the mailbox. Authentication is passwordless and handled by the identity layer.
The encrypted key-value storage provides the mailbox. UIID’s storage layer was built to hold structured, encrypted, identity-scoped data with a clear ownership model and a clear lifecycle. Messages, metadata, folder structure and settings sit in that layer, bound to the identity that owns them. Because the storage is identity-scoped by design, the boundaries of who can access what are enforced at the platform level rather than by the mail application’s own logic.
The API provides everything else. This is the point we want to emphasise, because it is the one with the largest implications: the UIID API surface is complete enough that an entire mail provider can be built on top of it. Identity, authentication, authorisation, encrypted storage, aliases, audit and webhooks — the components required to run a real messaging service are already there. UIID Mail is, in one sense, a proof of that.
Aliases fit the model naturally. UIID’s identity model already distinguishes between a Core ID and context-specific aliases. Email addresses are exactly the kind of thing users want compartmentalised — one context for work, one for shopping, one for a service you are not sure you trust yet — and an alias-based identity model supports that structurally rather than as an add-on feature.

Interoperability: UIID Mail still talks to the rest of the world

An email service that can only reach other users of the same service is not an email service. UIID Mail sends to and receives from conventional email addresses. A message from a UIID Mail user arrives in a recipient’s Gmail, Outlook or corporate inbox normally, and a reply comes back normally.

What changes is the internal architecture and what becomes possible between identities that both use UIID. Where both parties hold a UIID, the identity of the sender is established by the identity layer rather than inferred from domain reputation. That is a structurally stronger position than anything the classic protocol stack can offer, and it is the property that makes the long-term case for this product.

Why this matters for UIID globally

We are direct about the ambition here: UIID Mail should be as good to use as Gmail, and it should be a core piece of backbone infrastructure for the global rollout of UIID.

Those two goals are connected. Email remains the connective tissue of the internet. It is the recovery channel for nearly every account a person holds, the notification channel for nearly every service, and the de facto identifier that ties a person’s digital life together. Any identity system that wants to be genuinely independent has to be able to provide that channel itself rather than depend on a third party for it.

Three things follow from UIID Mail existing:

Identity-native communication. A UIID holder gets a working communication channel from the identity itself, without registering for a separate service from a separate company under separate terms.
Reduced dependency. An identity whose recovery and notification channel is operated by an unrelated provider is not fully self-sovereign. Closing that gap is a prerequisite for the claim UIID makes.
A demonstration of the platform. UIID Mail shows that the UIID API and storage layer are capable of carrying a full consumer-grade product. That is an argument to developers and partners that no architecture diagram can make on its own.

Where UIID Mail is being tested

UIID Mail is currently in testing in several Asian countries, the United States and Germany. This spread is deliberate. Email behaviour, deliverability conditions, network characteristics, device mixes and user expectations differ substantially between these markets, and a service that only works well in one of them is not ready to be described as global infrastructure.

Testing across these regions lets us validate performance, deliverability and usability under genuinely different conditions before broadening availability.

How to get access

UIID Mail is available to Trusted Testers under our beta program.

To apply, email [email protected], state that you are interested in UIID Mail, and include your UIID. Applications without a UIID are not evaluated. Accepted testers sign a non-disclosure agreement covering unreleased functionality.

If you do not yet have a UIID, create one at uiid.me.

Full details on the Trusted Tester Program, and the current list of projects in beta, are available at blog.linkspreed.com and help.linkspreed.com.

What we want from testers

Specifically, and in this order of usefulness:

Does it feel like email? If anything about the daily experience makes you stop and think, we want to know exactly where.
Does it deliver? Send and receive across providers, across countries, with attachments, from mobile and desktop. Deliverability is the hardest problem any new mail service faces and it is where external testing is irreplaceable.
Does the identity model make sense to you? Aliases, passwordless access and identity-bound mailboxes are a different mental model. We want to know whether it is intuitive or whether we are asking too much.
What is missing? Tell us what you reached for and could not find.

UIID Mail — email, rebuilt on identity.

Learn more about UIID at uiid.me · Apply to test at [email protected]