immudb v1.1.0 is officially released and you will love it!

Many of the features included in this release were requested and discussed by community members, to whom we’re grateful for all the interaction and contributions!

Today’s release includes a more matured and robust SQL engine, built-in replication, stable cloud storage capabilities, among many minor improvements and fixes.

What makes immudb so unique?

immudb layered design makes it a great fit for a wide range of use cases; immudb’s heart consists of an embeddable, verifiable key-value store and as such, it can be used as an embedded cryptographically verifiable log or as a full-blown key-value store.

The pluggable SQL Engine converts it into a relational database, similar to SQLite but tamper-proof!

If that weren’t enough, immudb is released as a stand-alone server with user management and multi-database support, making it super easy to integrate with any application. Now with built-in replication and cloud storage capabilities!

Major new features:

  • SQL improvements
    immudb can be used both as a key-value store and as a relational database (SQL), making it the first embeddable/client-server immutable database with relational capabilities. immudb also expands tampering verification capabilities to rows.

    The following features were added to the SQL Engine:

    • AUTO_INCREMENT primary key
    • Unique indexes
    • Multi-column indexes
    • Multi-column primary keys
    • Support for negative values in INTEGER columns and calculations using negative values
    • Huge improvements of query optimization with indexes
    • Explicit index selection
    • Un-restricted joins (joins involving sub-queries)

    All these features together with queries across time and tampering verification capabilities make immudb unique.

  • Replication
    immudb built-in replication makes it possible to replicate databases for backup and distributing query workloads.

  • S3 storage backend
    ​Remote storage is now marked stable. With the S3 backend, immudb automatically uploads the data into an S3-compatible server reducing the amount of data stored locally.

  • Reproducible databases
    By default, ingesting the same data into different databases may produce different and incomparable cryptographic proofs. This release includes the possibility to have a deterministic state by ingesting the same data.

  • Improved docker images
    New release comes with changes to how our docker images are built.

    The main codenotary/immudb image is now built using a scratch base to reduce the image size and increase its security.

    There are two more versions of the immudb image – one based on debian (codenotary/immudb:1.1.0-bulllseye-small) and one based on almalinux (codenotary/immudb:1.1.0-almalinux-8-minimal).

Important notes

  • Breaking changes on the SQL layer
    This release is using completely new format for storing SQL data. This change was necessary to support new features but it is not compatible with the old format.

    After upgrading to immudb 1.1.0, the old data will not be available through the SQL interface even though immudb still contains the low-level KV representation of those entries. If you need to migrate the old data to the new format, please contact us on our discord channel.

  • Go version support
    Starting with the next release our official builds and docker images will be compiled and tested using go 1.17. In order to support older systems where go 1.17 is not easily available, we are providing statically-linked binaries. We also ensure that binaries can be manually compiled with older go versions down to 1.13 (excluding tests).

Downloads for all major platforms are available on Github. Documentation and a getting started guide are available on the website.

Contact Us

For any question contact us on Discord.

Codenotary Inc.
6750 West Loop South, Suite 845
Bellaire, TX 77401, United States



Open Source and easy to use in new applications and easy to integrate into existing application.

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.