Any kind of key-value. Clients can choose how to structure data.
No data mutation APIs are provided.
Data is never overwritten, so multiple versions of the same key co-exist and are verifiable.
Tamper-evident history system.
Clients and auditors want cryptographic proof of data inclusion and historical consistency in real time.
If tampered, clients and auditors will notice that and take actions.
Data ownership is verifiable by clients and auditors.
Sign your data using Public-Key Cryptography.
Keys additions and revocations is immutably stored into the database
docker run -it -d -p 3322:3322 -p 9497:9497 --name immudb codenotary/immudb:latest
sequential write --- Concurrency: 128 Iterations: 1000000 Elapsed t.: 3.06 sec Throughput: 326626 tx/sec
batch write (async commit) --- Concurrency: 16 Iterations: 1000000 Elapsed t.: 0.36 sec Throughput: 2772181 tx/sec
- 4 cores
- 16GB memory
- single SSD drive
immudb is a ledger database that has been developed with performance, scalability and versatility in mind. The user feedback has shown that they love the very high throughput and being able to store hashes as well as data. They see it as a great alternative to using a blockchain or ledger service.
- Easy setup
- Fast and reliable immutable database
- Secure REST API gateway
- Powerful, easy to use admin
- Open source
Very high throughput, immutable database with cryptographic verification
immudb is an indispensable asset when it comes to tamper-proof data:
- Store every update to sensitive database fields (credit card or bank account data) of an existing application database
- Store CI/CD recipes to build and deployment pipelines
- Store public certificates
- Store tamper-proof log streams (i. e. audit logs)
- Transactional integrity
- ACID compliance
- SDKs for Python, Node.js, Java, Go