CodeNotary - Blockchain-Based Code Authentication


In DevOps, where teams can constantly be rearranged and sorted for different purposes, the ability to form groups or change their member status is important. Up until recently, CodeNotary strictly offered the easy visualization and verification of containers and all other existing code/digital assets signed by an individual. Now, enterprises can guarantee the trust of all of their DevOps assets, deployed or in development, with the immutability of the blockchain.


What is an Organization in CodeNotary?

An organization is actually an alias of a group of public keys belonging to its authorized members. Each member has their own unique pubkey that is then connected to the organization.


Just as individual code signers have to go through a KYC (Know Your Customer) authentication process, organizations have to go through a similar certification in order to prove they are who they say they are.


How Organizations Work in CodeNotary

Organization names are created based on the email domain of the registered user who sets up the organization. (Within the command line, an organization name is known as an ‘organization ID’). Once created, the blockchain then stores the new organization’s ID and enables 100% verification transparency of all signed digital assets associated with the ID from that point forward.

Any enterprise user (i.e. a user with an enterprise license) can create an organization for their company. Once the organization is created, any user a part of the new organization can start signing assets under the organization’s name. By becoming the designated organizational admin and can add new users directly from their dashboard as shown below:


CodeNotary Organizational Dashboard View


Verifying a Digital Asset Against an Organization

Verification of a digital asset’s signature against a specific organization’s name extends globally. From within the registered organization to beyond its walls, vcn users anywhere can verify a digital asset’s signature against a specific organization’s name. This way, when a digital asset indicates it was signed by, for example, Oracle, users outside of Oracle can know with confidence that Oracle indeed signed the digital asset they want to use.


Let’s look at an example.


Say is member of and uses his pubkey, that has been associated with the organization, to sign an asset.

A user can verify an asset against an organization by using the command:


vcn verify –org=


People can also verify the asset’s integrity by using the pubkey of with the command vcn verify --key. Alternatively, by users can verify an asset simply by using the organization’s name, i.e. its domain name, with the command:


vcn verify –org=


The benefits here of grouping public keys together and connecting them to a domain are huge. For instance, would you rather remember a long alpha-numeric string of random characters like the following:




…or something much simpler like


Verifying Against a Group of Signers (Keys)

Organizations and users are also able to internally verify against groups of signers or organizations such as several vendors like,, and This is particularly helpful when several contractors need to sign off on an asset before it is allowed to be used internally within the hiring organization or before passing the asset off to another contractor. (In the future, admins will be able to invite new users by email to join their organizations.)


Get a free trial account and try out CodeNotary for yourself.



Start Free Trial

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.