The CodeNotary team is excited to announce the release of version 1.0 of its immutable database immudb, now with support for SQL and the new TimeTravel(™) feature.

immudb is the first database to provide tamper-evident data management, immutable history and client-cryptographic proof. Every change is preserved and can’t be changed without clients noticing. Clients do not need to trust the server and every new client adds trust to the deployment. Licensed under the Apache 2.0 license, immudb is open source and free for all to use.

Prior to release v1.0, immudb already offered a high speed key-value database paradigm, which is extremely popular and used in hundreds of different projects, both of proprietary and open source nature. This new version being released today introduces the first open-source immutable SQL database that extends the already known highly-secure client verification technology to SQL queries.

This leap forward enables businesses to take advantage of the tamper-proof capabilities while modeling their data as they were used to without changing application logic.

Not happy with the major new feature of SQL support, the team at Codenotary went and overdid itself and also announced TimeTravel(™). This new functionality allows travel back in time through the data change history, and even compares these values in the same query! Of course, all results are client-verifiable and returned tamper-evident. That enables insights into data never seen before, while enabling users to continue to use the well-known SQL language.

Also in today’s release of immudb v1.0, we are announcing the availability of the Postgres wire protocol compatibility with immudb. Any application using the Postgres pgsql protocol is automatically compatible with immudb as today, and allows users to get tamper-evident cryptographic verification without changing your app!

One more thing, however. Listening to the needs of our amazing user base, we worked hard, to embed a web console that allows for easy monitoring, basic administrative tasks and SQL based data query, all from the comfort of your browser.

Major new features:

  • Relational (SQL) Support
    immudb can be used both as a key-value store and as a relational database (SQL), making it the first immutable database with relational capabilities. immudb also expands tampering verification capabilities to rows.
  • TimeTravel(™)
    immudb is the first database which allows you to do queries across time. You can pin a table into a point in time inside a query or subquery, allowing for powerful comparisons.
  • immudb Web Console
    immudb includes an embedded web console with administration and query capabilities. Create users, manage databases, and query relational data with no additional downloads or tools.
    immudb webconsole

  • PostgreSQL wire protocol Compatibility
    immudb SQL features can be used with libraries compatible with the pgsql protocol. This means popular database access frameworks already available in Ruby, C, Java JDBC, PHP, etc., can be used to perform operations on immudb.

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.