immudb is a database with built-in cryptographic proof and verification. It tracks changes to sensitive data, and the integrity of that history is verified by the clients — without having to trust the server.
immudb is a ledger database built for performance, scalability and versatility. Store records, text, images or JSON — a practical alternative to a blockchain or a hosted ledger service.
Performance
Lightweight and fast enough to keep up with billions of transactions a day, and millions of transactions per second on high-end hardware.
Tamper protection
Data can only be added, never changed or deleted, and every read can be answered with a cryptographic proof.
Resilience
Built to stay up for months at a time, with synchronous or asynchronous replication for high availability.
Flexibility
Insert with SQL or key/value. Connect over JDBC, ODBC, the PostgreSQL wire protocol, or an SDK for your language.
Multi-platform
Run it in the cloud or on-premises, embedded or standalone — Linux, macOS, Windows, FreeBSD and z/OS.
Immutable by construction
History is preserved. You can add new versions of a record, but nothing rewrites or removes what came before, so a silent change is not possible.
How immutability is ensuredConsistency checking built in
The server continuously checks disk and memory consistency, the gateway checks integrity, and the client verifies proofs of ownership on its own.
AuditorVerification without the cost
Cryptographically coherent and verifiable, at a price that still allows millions of transactions per second — as a service or embedded as a library.
Performance guideOfficial SDKs, plus the PostgreSQL wire protocol and a REST gateway.
A patch report says that a vulnerability was fixed. Six months later, can your team show which devices received the patch, what the follow-up checks found, and whether those records have changed?
A code diff shows what changed. It rarely shows every instruction, tool result, and approval that led to the change. For software that handles money or health data, that missing history matters.
Oracle AI Database can hold append-only, cryptographically chained rows next to your normal transactional tables. The architectural question is whether immutability belongs inside the transactional database at all — or in a database built for it.
Used by
Government of India
We use Google Analytics cookies to understand how the site is used. Nothing is loaded unless you accept. Privacy policy
