25 sections
What the product does
Does Enclessa do the job at all?
- Features18 pages
One page per capability, each ending with what it does not do.
- Use cases9 pages
What teams do in Enclessa, described as work.
- Integrations6 pages
What connects, what does not, and the API behind it.
- Solutions4 pages
Public sector, healthcare, legal and advisory, engineering.
Deciding between options
Each names where Enclessa is the wrong answer.
- Comparisons3 comparisons
Including the cases where the other tool wins.
European options: who runs them, where, what they encrypt.
- Migrating to Enclessa5 guides
What moving involves, and what does not come across.
Per-member pricing, monthly or yearly.
Up to ten members, no card, no expiry.
A dedicated deployment in a region you name, operated by us.
The argument, including who should not buy it.
Reference
Look-up material, written to be quoted.
The common questions, answered briefly.
- Glossary28 terms
Encryption, platform and compliance terms, defined.
28 pages
- End-to-end encryption
- MLS (RFC 9420)
- OpenMLS
- Forward secrecy
- Post-compromise security
- Safety numbers
- Cross-signing
- Room mode
- Managed channel
- Multi-tenancy
- Tenant isolation
- Data residency
- GDPR
- DSGVO
- Data processing agreement (DPA)
- Subprocessor
- Data subject access request (DSAR)
- Retention policy
- Legal hold
- Audit log
- Compliance export
- SCIM
- Single sign-on (SSO)
- WebRTC
- SFU (Selective Forwarding Unit)
- LiveKit
- Seat-based pricing
- Zero-knowledge
How RFC 9420 scales group encryption, compared with Signal and Megolm.
- Changelog97 entries · to 2026-11-07
What shipped, newest first.
- Roadmap7 things ruled out
What is coming, and what is ruled out.
Security and procurement
What security and legal reviews ask for, including what rules Enclessa out.
How data is protected, and the certifications not held.
The DPA, subprocessors, residency, data rights and breach notice.
How incidents are communicated, and why no uptime figure is published.
As published.
As published.
As published.
As published.
The company
Who builds this, and how to reach us.
Who builds Enclessa and why.
Sales, security reports and data protection.
Not here, on purpose
FAQ
About what Enclessa publishes
- The security page first — it leads with the certifications Enclessa does not hold — then the trust centre for the DPA, subprocessors and residency.
- Every feature page ends with what it does not do, the security page leads with what is missing, and the roadmap lists what is ruled out and why.
- The API is described by an OpenAPI document. Documentation for outside developers and client libraries are on the roadmap.