An immutable database with built-in cryptographic proof and verification, supporting SQL, Key-Value, and Document models.
immudb is an immutable database that provides cryptographic proof and verification for data changes, ensuring a tamperproof history. It supports SQL, key-value, and document models, allowing developers to store critical data without fear of compromise. Unlike traditional mutable databases, immudb's immutable nature guarantees that once data is written, it cannot be altered or deleted.
Developers and organizations needing to secure sensitive data, audit logs, transactions, or any information where tamper-evidence and integrity are critical, such as in financial, legal, or compliance applications.
immudb offers a unique combination of high performance, cryptographic integrity, and multi-model flexibility, enabling trustless verification of data history. Its zero-trust architecture ensures clients can independently verify data without relying on the database's security, making it ideal for high-stakes environments.
immudb - immutable database based on zero trust, SQL/Key-Value/Document model, tamperproof, data change history
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides built-in proof and verification mechanisms, allowing clients to independently verify data without trusting the database, as per its zero-trust architecture.
Capable of millions of transactions per second, optimized for SSD storage, with benchmarks showing over 1.8M entries per second in tests.
Supports key-value, document, and SQL models in a single database, enabling diverse use cases from audit logs to relational data.
Can be embedded as a library, run on IoT devices, servers, or in the cloud, with options for external storage like Amazon S3 and MinIO.
Data cannot be altered or deleted, which can lead to storage bloat and challenges in complying with data deletion requirements like GDPR.
Configuring external storage (e.g., S3) requires multiple environment variables and steps, increasing initial deployment complexity.
Has fewer third-party tools and integrations compared to established databases, which might increase development effort for custom solutions.