Encryption
OpenMLS, explained
A protocol specification is not a working system. Between RFC 9420 and a message somebody can read there is a state machine, a key schedule, a credential system and a storage layer, each of which can be got wrong in ways that silently remove the guarantee. Using a shared implementation means that review effort concentrates in one place instead of being spread thinly across every vendor writing their own.
How Enclessa uses it
Enclessa builds its cryptographic core as a thin Rust wrapper around OpenMLS, compiled to WebAssembly for the web client and linked natively elsewhere. Enclessa writes no cryptographic primitives of its own. The library is audited; Enclessa’s own integration of it has not been through a third-party audit, which is stated plainly on the security page rather than left to be discovered.