We’re absolutely thrilled to announce our new release of CodeNotary that went online today.

The update includes a ton of smaller and larger changes and improvements of the look and feel. It’s much better structured, on-boarding is even easier as before and you can use all features for free.

We worked very hard to cover most of the amazing community and users feedback we received over the last couple of months.

Before we share what’s new, we also want to present our new Mascot, that guides your through our Open Source projects:


What’s New in CodeNotary

Sign Up for CodeNotary

While you can find most information required during on-boarding or on our new documentation page we want to share you some new dashboard screenshots, to get you a better idea about our new design.


Start your journey your Top Assets and your activity timeline. That way you can always follow through the digital assets you or your pipeline service (i. e. Jenkins) notarized or authenticated.

CodeNotary My Assets


This view helps you in checking asset details based on your notarization. Unlike digital certificate signing, you can notarize digital objects without changing them, but all information is notarized in an immutable way including details.

Asset details

You can remove Trust from any digital asset at any point in time. That feature is amazingly powerful, in case you don’t want to use these assets anymore. In combination with our docker watchdog or Kube-Notary, you can track any running untrusted container image within seconds.

Check out our latest blog posts that cover Microsoft Azure DevOps, but can be adopted to any Jenkins and/or Kubernetes environment:

Securing your Azure DevOps Ecosystem, Jenkins and Kubernetes (AKS) using CodeNotary – Part 1

Securing your Azure DevOps Ecosystem – Part 2

Digital Asset Details

Let’s take the highly popular cloud native edge router Traefik, that our friends at Containous are developing and maintaining

Traefik notarize CodeNotary

You can simply Trust the latest version of Traefik and Unsupport all older versions you don’t want to use anymore. If you use Kube-Notary, you’ll can check your runtime in realtime immediately like in this example here of our demo environment:

Kube-Notary status dashboard

Of course we would love to get your feedback and would be thrilled if you show us your support on GitHub or Dockerhub! Highly appreciated!

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

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.