MLS, or Messaging Layer Security, is the IETF standard published as RFC 9420 for end-to-end encrypted group messaging, designed so that adding or removing a member costs work proportional to the logarithm of the group size rather than to the group size itself.
Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.
Also called
Messaging Layer Security
What MLS (RFC 9420) means
Before MLS, group encryption was usually built by encrypting each message separately for every recipient device — the approach the Signal protocol takes when extended to groups. That works, and it is what most encrypted messengers do, but the cost of every key change grows with the number of devices, which is why encrypted group chat has historically been small and slow. MLS replaces the pairwise fan-out with a binary tree of keys, so a change touches a path through the tree instead of every leaf.
The unit of membership in MLS is a device, not a person. Each device holds its own leaf, so a group of ten people with three devices each is a group of thirty members. Adding a device is a visible operation, and removing one changes the group key so that the removed device cannot decrypt anything sent afterwards. The state of a group at any moment is called an epoch, and every membership change advances it.
MLS became RFC 9420 in July 2023 after several years of work in the IETF working group of the same name, with contributions from the people behind Signal, Wire, Cisco, Google and Mozilla. Being a published standard rather than a proprietary design matters for a buyer: the protocol can be reviewed by anybody, has been analysed formally, and does not depend on any one vendor continuing to exist.
How Enclessa uses it
Enclessa uses MLS for direct messages and group direct messages. The implementation is OpenMLS, compiled once in Rust and shipped to every client, so the web client and the desktop client run identical cryptographic code rather than two implementations that agree until they do not. The Enclessa server implements only the MLS delivery service — it orders and forwards handshake messages and performs no cryptography of its own.
Where MLS (RFC 9420) is specified
Related terms
Read further
The security page explains how Enclessa protects data and which certifications it does not hold. The trust centre covers the processing agreement, the subprocessors and the residency position. The FAQ answers the questions buyers ask most often.
Encrypted collaboration, hosted in Europe.
Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.
Open beta. Free plan, no payment card to start.