The case for Enclessa, and where it falls apart

Because in Enclessa it is a property of the room rather than a setting on the tenant. Direct messages and group direct messages use MLS as specified in RFC 9420, implemented with OpenMLS, with one key per device and no key held by the server — so there is no administrator override, no key escrow and no configuration that quietly turns it off. Where a competitor offers customer-managed keys, the service still processes plaintext; that is a real control and it is a different guarantee. Enclessa is equally clear about the other half: channels are server-managed and readable by the server, because that is what makes search, retention and compliance export possible, and the room says which mode it is in.

You should not, on our word. What replaces the word is published detail: the architecture, the data model and the OpenAPI surface are documented, the confidentiality guarantee rests on an IETF standard and an audited open-source implementation of it, and tenant isolation is proven by a probe suite generated from the API document that drives 286 cross-organisation operations and is refused all 286 times, failing the build if that regresses. The platform control plane our own operators use cannot read content at all, and a continuous-integration check forbids it from importing any code that could.

The hosted service runs in one European Union region and the seller is a company established in Germany, so the processing agreement, the invoice and the jurisdiction all point at the same place instead of at a transfer mechanism. Where a mandate goes further than one shared region — a named country, or no shared tenancy at all — the Enterprise plan buys a dedicated deployment in a region you name, with its own database, object storage and media nodes, still operated and updated by us.

Usually you should not, unless confidentiality is a driver — that is the honest answer, and it is why the comparison pages each name the case for the other product. Where it does change the arithmetic is scope: one price per member covers messaging, video calls, task boards with GitHub sync, time tracking with absence, and personnel records, on one permission model and one invitation list. Teams that were paying for a chat product plus a board plus a time tracker are not adding a line item, they are replacing three.

By checking the exit before you need it. An organisation can export everything the platform holds for it, in open formats, at any time and without a support ticket; the data model is documented and the whole API is described by an OpenAPI document, so the export is something you can read and reload rather than a proprietary archive. Nothing about Enclessa gets more expensive to leave the longer you stay, because there is no marketplace, no macro language and no third-party app estate to unpick.

Yes, and without a payment card or an expiry date. The Free plan carries up to ten members with channels, threads, end-to-end encrypted direct messages, video calls with screen sharing and ninety days of searchable history, permanently. It is a plan rather than a trial, so an evaluation that stalls for a quarter does not end with a deleted workspace, and moving to a paid plan later keeps everything that is already there.