Your Data. Your Keys. Your Control.

Keys stay on devices. Three independent encryption layers: AES-256-GCM at rest, per-user RSA in transit, TLS on the wire. Servers never see plaintext.

Create and edit locally. Metadata-first reconciliation syncs only what changed — bandwidth proportional to delta, not total size.

Automerge CRDTs ensure concurrent edits converge automatically. Order-independent sync — entries can arrive in any sequence.

• You need end-to-end encryption and cannot trust your hosting provider
• You require complete audit trails with cryptographic integrity
• You need offline-first operation for field or remote operations
• You collaborate across organizations and need fine-grained access control
• You need technical controls for compliance — encryption, signed audit trails, and coordinated data erasure that support HIPAA, SOX, GDPR, PCI-DSS programs
• You want simple backups without key exposure
• You need multi-party collaboration with different access levels

• You only need simple CRUD operations without collaboration
• You always have reliable network connectivity and don't need offline-first
• You don't need end-to-end encryption and can trust your hosting provider
• You have simple access control needs that don't require document-level encryption
• You need complex relational queries that don't fit document model
• You have very high write throughput that may challenge append-only stores

• Completeness — after a full sync cycle, the client has metadata awareness of every remote entry
• Idempotency — every endpoint can be called repeatedly with the same input without side effects
• Order independence — entries can arrive in any sequence; CRDTs handle causal ordering
• Deduplication — entries identified by id, deduplicated by contentHash
• Immediate revocation — enforced at challenge generation and token validation; no stale-token window

• Baseline sync — send known IDs, receive missing metadata; works for any dataset size
• Cursor scanning — page through remote metadata incrementally; constant request size regardless of total entries
• Bloom filter pre-check — probabilistic set summary eliminates 90–99% of exact existence checks
• Capability negotiation — start simple, enable optimizations later without protocol changes
• Snapshots — periodic CRDT snapshots prevent performance degradation from long histories

Standard sync with a central server. Simplest deployment. Start here and scale later.

Two devices sync directly over LAN, WebRTC, or Bluetooth. No server dependency. Same pullChangesFrom/pushChangesTo API.

Data flows through nodes that cannot decrypt it. Sync operates on encrypted metadata — relay nodes never need keys.

A node forwards sync requests to another remote store for edge caching, access control boundaries, or multi-hop distribution.

Multiple peers sync with each other. Entries deduplicate automatically. CRDT convergence guarantees consistency.

Different participants hold different keys. A hospital server syncs patient records it cannot read — trust is at the key level, not the network level.

MindooDB is alpha software — APIs may change without notice. Core functionality is stable and tested, but we recommend thorough evaluation before production use.

• Open source — Full codebase on GitHub
• Security audit — Documented in security audit docs
• Threat model — Assumes servers are compromised
• Cryptographic guarantees — Ed25519 signatures, AES-256-GCM encryption