Your Data. Your Keys. Your Control.
MindooDB is an end-to-end encrypted, offline-first sync database for secure collaboration — servers can store and sync, but cannot read. Works client-server, peer-to-peer and local-only. For browsers, NodeJS and React Native.
Keys stay on devices. Servers never see plaintext or hold decryption keys.
Create and edit locally, then sync missing encrypted entries when online.
CRDT-based collaboration so concurrent edits merge automatically.
When to choose MindooDB vs. alternatives
MindooDB is designed for applications where end-to-end encryption, offline operation, and multi-party collaboration are essential. Here's when it fits best.
- 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 regulatory compliance (HIPAA, SOX, GDPR, PCI-DSS)
- 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
| Feature | MindooDB | PostgreSQL/Firebase | Blockchains |
|---|---|---|---|
| End-to-end encryption | ✅ Yes (servers can't decrypt) | ❌ No (server-side keys) | ⚠️ Public by default |
| Offline-first | ✅ Built-in | ❌ Requires custom logic | ❌ Requires network |
| Audit trails | ✅ Append-only, cryptographically chained | ⚠️ Requires custom implementation | ✅ Immutable public records |
| Multi-org collaboration | ✅ Fine-grained access control | ⚠️ Server-side access control | ❌ All-or-nothing visibility |
| Performance | ✅ High (no consensus needed) | ✅ Very high | ❌ Lower (consensus overhead) |
| Data privacy | ✅ Private by default | ⚠️ Depends on server security | ❌ Public by default |
Servers can sync & store — but cannot read
- Sign every change (authorship + integrity)
- Encrypt before leaving the device (confidentiality)
- Append-only storage (audit trail)
- Content-addressed sync (transfer only what’s missing)
- Works client-server and peer-to-peer
Security guarantees without losing UX
Copy-pasteable examples
These snippets are derived from the MindooDB test suite to stay aligned with real usage patterns.
Built for secure, collaborative applications
Production readiness & trust signals
MindooDB is alpha software — APIs may change without notice. Core functionality is stable and tested, but we recommend thorough evaluation before production use.
- Core encryption and sync protocols
- Document CRDT operations
- Virtual Views and indexing
- Attachment storage
- API method names and signatures
- Configuration options
- Internal data structures
- 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
Active development, comprehensive documentation, and growing community. View on GitHub →