Derived state is never the sole authority
Search indexes, caches and renditions may be stale. What they produce is confirmed against PostgreSQL before it reaches a caller.
Enclave · in development
One policy boundary around all of it.
Enclave is a self-hostable enterprise content and collaboration platform — SharePoint-class in purpose, built around modern APIs, Rust performance, a React interface, strong security governance, customer-controlled infrastructure, hybrid vector search and MCP-native AI access.
It is not a file server. It is an information boundary combining content, identity, permissions, governance, search, collaboration, DLP, retention, audit and AI access — so that every way in obeys the same rules.
Apache-2.0. In development — the specification phase is complete and implementation is underway across a Rust workspace and a React SPA. There is no hosted demo yet, and nothing here is ready for production.
Status
in development
Stack
Rust · Axum · React
Authoritative store
PostgreSQL
License
Apache-2.0
The invariant Every entry point runs the same chain,
Every entry point runs the same chain,
in the same order.
Web, desktop sync, mobile, REST, MCP, agent, preview, download, search, external editor, webhook or admin utility — every operation passes through this, in this order. It is implemented once, in one function, and every entry point calls it. A code path that needs a different order is a design defect, not a special case.
Tenant Isolation
-> Authentication
-> Conditional Access
-> Authorization (RBAC / ACL)
-> Information Barriers
-> Classification Policy
-> DLP
-> Retention / Records / Legal Hold
-> Execute
-> AuditThe client is hostile
Identity attributes, IDs, paths and headers arriving from a client are inputs to policy, never conclusions of it.
What it does
Content, identity, governance, search, AI.
Content
Workspaces, libraries, folders, files, immutable versions, lists, pages, metadata and content types, and 16 view types.
Identity
Local, LDAP/AD, OIDC, SAML, SCIM, WebAuthn/passkeys, guests and service accounts — with JWT access tokens and rotating refresh tokens.
Authorization
Granular per-action permissions — preview ≠ download ≠ print ≠ export ≠ sync — with hierarchical ACL inheritance, explicit break, and deny-wins resolution.
Governance
DLP with simulation, classification, information barriers, retention, records, legal hold, antivirus, security incidents, and a tamper-evident audit trail.
Conditional access
IP/CIDR, country, ASN, network zone, device posture, authentication strength, and client type — evaluated before authorization, not after.
Search
Milvus hybrid retrieval — dense, sparse and BM25 — with permission-aware results confirmed against the authoritative database before they reach a caller.
AI under the same chain
An MCP gateway that obeys the same policy chain as every other entry point. RAG answers with citations, plus bring-your-own embedding and LLM providers with classification-aware routing.
BYO infrastructure
Object storage, secrets, KMS, SMTP, vector store, embeddings, LLM, antivirus and identity — all behind provider traits, so the deployment is yours rather than ours.
Workflows & signing
Approval and review pipelines, and document signing from click-through acknowledgement up to PAdES digital signatures with long-term validation.
How it fits
The boundary the editors run inside.
Editors stay editors
Casual Sheets, Casual Docs and the engines (OpenCalc, OpenDoc) do one job: open a file, edit it, save it back. Enclave is where identity, permissions, retention and audit live — the things an editor should not be inventing for itself.
External editing, by design
Desktop and mobile sync and external document editing are part of the spec rather than bolted on, so an editor opening a document out of Enclave is still inside the policy chain rather than beside it.
Enterprise delivery
White-labeling, custom domains, i18n with full RTL, WCAG 2.2 AA, and HA/DR are scoped in the specification rather than deferred to a later “enterprise edition”.
Honest status
Specification complete, implementation underway.
Done
The specification phase — a 16-document pack covering PRD, HLD, LLD, data model, API, security, search, BYO infrastructure, UX, sync, operations, testing, identity, i18n and signing — is complete and public in the repo.
In progress
Implementation is live across a Rust workspace and a React SPA, tracked item
by item in TRACKER.md with milestones and exit criteria in
ROADMAP.md. Priority is re-assessed only at phase boundaries.
Not yet
No hosted demo, no release, no version to pin, and no compliance certification. If you need enterprise governance in production today, this is not yet it — follow the roadmap instead.
Read the spec before the code. Enclave is designed in the open —
the PRD, architecture, data model, API surface and security model are all in the
repository, and the tracker says exactly what is built and what is not.