Releases, engineering notes and stories from people running immudb in production.
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.
immudb 1.11.2 is a small release with an outsized operational payoff. Versions 1.11.0 and 1.11.1 shipped three distinct ways to take a running server out of service — and this release closes all three.
The release of immudb 1.11.0 marks one of the most significant milestones in the evolution of the project since SQL support was introduced. While immudb has always provided cryptographically
The latest release of immudb introduces a host of improvements designed to enhance performance, expand SQL functionality, improve query handling, and increase compatibility with PostgreSQL. These
When AWS announced the discontinuation of its Quantum Ledger Database (QLDB), financial institutions that relied on its immutable ledger capabilities were forced to find alternative solutions. For
We use Google Analytics cookies to understand how the site is used. Nothing is loaded unless you accept. Privacy policy
