🩺 Vitals
- 🟢 Last active: 2026-07-24
- 📦 Latest release: 2026.5.1 (2026-05-26)
- 🐞 Open issues: 386
- 🌟 Stars: 7.8k
What do these metrics mean?
- Last active: when code was last pushed, as of our last check. The dot is green when that was recent, grey otherwise. A long gap can mean a tool is finished and stable, not only unmaintained.
- Latest release: the most recent tagged, packaged version the maintainers published. Not every healthy project tags releases.
- Open issues: unresolved reports and requests. A high number is normal for a popular project and is not a warning on its own.
- Stars: how many people bookmarked the project on its forge. A rough popularity signal, not a measure of quality.
🏗️ Profile
- Official: cryptpad.org
- Source: github.com/cryptpad/cryptpad
- License: AGPL 3.0
- Deployment: Docker | SaaS
- Data Model: Encrypted blobs: server stores only ciphertext (zero-knowledge)
- Jurisdiction: France 🇫🇷 / EU 🇪🇺 (XWiki SAS)
- Compliance (SaaS): N/A
- Compliance (Self-Hosted): GDPR Ready
- Complexity: Moderate (3/5) - Docker available; the WebSocket and sandbox-domain setup needs care
- Maintenance: Low (2/5) - Standard Node.js app; documented Docker images and upgrade path
- Enterprise Ready: High (4/5) - Open-source SSO (OIDC/LDAP) and team drives; E2EE by default, though it limits server-side content governance
1. The Executive Summary
What is it? CryptPad is a collaborative office suite (real-time documents, spreadsheets, presentations, forms, kanban boards, and a code editor) with one defining property: it is zero-knowledge. All encryption and decryption happen in your browser, so the server only ever stores ciphertext. Unlike a conventional self-hosted suite where the server (and therefore whoever administers it) handles documents in plaintext, a CryptPad operator can host your files without ever being able to read them. It is built by XWiki SAS in France, funded partly by EU research grants, AGPL-licensed, and self-hostable, with a managed offering for teams that would rather not run the infrastructure. The trade is deliberate: CryptPad uses its own editors rather than the LibreOffice or Office engines, exchanging some document fidelity for an encryption model in which the server is mathematically blind to content.
The Strategic Verdict:
- 🔴 For High-Fidelity Microsoft Document Workflows: Caution. CryptPad's editors are its own, not LibreOffice or Office engines, so complex .docx/.xlsx files with heavy formatting may not round-trip perfectly. Teams whose work is precise Office-format fidelity (legal redlining, intricate financial spreadsheets) will find a LibreOffice-based suite such as Collabora a closer fit.
- 🟢 For Privacy-Critical Collaboration: Primary Choice. When the requirement is that no one (not your server admin, not your hosting provider) can read the content, CryptPad's zero-knowledge model is in a different class from "self-hosted but server-readable" suites. Combined with EU jurisdiction and AGPL source, it is the strongest answer for journalism, healthcare, legal, and any team where confidentiality is the product.
2. The "Hidden" Costs (TCO Analysis)
| Cost Component | Google Workspace (SaaS) | CryptPad (Self-Hosted) |
|---|---|---|
| Pricing Model | Per-user monthly subscription | Free, full-featured core; pay only your own hosting |
| Data Privacy | Vendor can read, scan, and index content | Zero-knowledge; server stores only ciphertext |
| Jurisdiction | US CLOUD Act exposure | France/EU (XWiki SAS), GDPR-aligned |
| Vendor Lock-in | Proprietary formats and account graph | AGPL; export to .docx/.xlsx or encrypted blobs |
3. The "Day 2" Reality Check
🚀 Deployment & Operations
- Installation: Self-host via Docker or a manual Node.js install behind a reverse proxy. The configuration that most often trips people up is the WebSocket and separate sandbox-domain setup that the client-side encryption requires; the documentation covers it, but it is not a single-command deploy. The hosted CryptPad service is the zero-ops alternative.
- Scalability: Because the cryptography is offloaded to clients, the server's job is largely storing and relaying encrypted blobs rather than rendering documents. A single Node.js instance serves a team or small organization comfortably; very large deployments scale on storage growth and WebSocket connection limits rather than document-rendering CPU.
🛡️ Security & Governance (Risk Assessment)
- Jurisdiction & Geopolitics (EU Advantage): XWiki SAS is a French company under EU law, so the managed service sits under GDPR and outside US CLOUD Act reach, a real sovereignty advantage for European organizations. Self-host and even that question dissolves: with zero-knowledge encryption the server holds no readable data to compel, in any jurisdiction.
- The Compliance Shift (Encryption Changes the Math): Self-hosting moves infrastructure security and incident response to your team, as always. But the zero-knowledge architecture materially shrinks the blast radius: a breach of the server yields ciphertext, not documents, which softens the usual "self-hosted means you own the breach liability" calculus. The trade-off lands elsewhere: features that need the server to read content (server-side search, content-level audit, administrative eDiscovery) are constrained by design, and compliance teams must weigh that against the confidentiality gain.
- License Risk (AGPL, and Why It Rarely Bites Here): The suite is AGPL-3.0, whose network-copyleft clause requires anyone who modifies CryptPad and offers it as a network service to publish their changes. For the standard cases (self-hosting it as-is, or using the managed service), the clause is inert. It matters only if you fork the code and run a modified public instance, in which case your modifications must be shared. Notably, even the SSO plugin is AGPL rather than a paywalled add-on: the commercial line is drawn purely at managed hosting, SLAs, and installation support, not at features.
4. Market Landscape
🏢 Proprietary Incumbents
- Google Workspace: The benchmark for real-time collaborative editing, but all content lives readable in Google's US cloud and feeds the surrounding account graph, the exact exposure CryptPad's zero-knowledge model removes.
- Microsoft 365: The enterprise office standard, carrying the same EU data-sovereignty and CLOUD Act concerns alongside proprietary file formats and per-seat licensing.
🤝 Open Source Ecosystem
- Collabora Online: The LibreOffice-based sovereign suite. The real contrast is the security model: Collabora processes documents in plaintext on your own server (data stays on your infrastructure), where CryptPad encrypts client-side so the server never sees plaintext. Choose Collabora for Office-format fidelity, CryptPad for zero-knowledge confidentiality.
- LibreOffice: The mature open-source desktop office suite and the de facto standard for offline document work. It is single-user desktop software rather than a real-time collaborative web suite, so it tends to complement CryptPad (author and finalize locally, collaborate and share encrypted online) rather than compete head-on.