immudb

OPEN SOURCE
IMMUTABLE DATABASE

High performance and easy to integrate and use in both new and existing applications. Supports Key-Value, SQL, data time travel and query functionality with client-verifiable proof.
				
					docker run -it -d -p 3322:3322 --name immudb codenotary/immudb:latest
				
			

Tamper Protection

  • Data is never overwritten, so multiple versions of the same key co-exist and are verifiable.
  • Any kind of key-value.
  • Clients can choose how to structure data.
  • No data mutation APIs are provided.

Time Travel

  • Tamper-evident history system.
  • Clients and auditors want cryptographic proof of data inclusion and historical consistency in real time.
  • If tampered, clients and auditors will notice that and take actions.

Performance & Security

  • Data ownership is verifiable by clients and auditors.
  • ease of integration
  • everything encrypted
  • scalability and resiliency
  • auto-tuning
  • on-premises or cloud

WHY IMMUDB?

immudb is a ledger database that has been developed with performance, scalability and versatility in mind. The user feedback has shown that they love the very high throughput and being able to store hashes as well as data. They see it as a great alternative to using a blockchain or ledger service.
Easy setup
Fast and reliable immutable database

Secure REST API
gateway

Powerful,
easy to use admin

Open source

USE CASES

DevOps Evidence

Financial Data Processing

IoT Sensor Data

Tamper-resistant Clinical Trials

eCommerce and NFT marketplace

Very high throughput, immutable database with cryptographic verification

immudb is an indispensable asset when it comes to tamper-proof data:
				
					// Store any key, value auditproof and tamperproof
key2, value2 := []byte("myClient"), []byte("Visa 6679499384784022 11/23")
verifiedIndex, err := client.SafeSet(ctx, key2, value2)

if err != nil {
	exit(err)
}

fmt.Println("   SafeSet - add and verify entry:")
printItem(key2, value2, verifiedIndex)
				
			

Intuitive setup

immudb is built with simplicity in mind:
				
					# install immudb service
./immuadmin service immudb install

# check current immudb service status
./immuadmin service immudb status

# install immugw service
./immuadmin service immugw install

# check immugw service
./immuadmin service immugw status
				
			

Consistency check built-in

immudb architecture has built-in verification and audit functionality:
				
					// built-in verification for every entry
verifiedItem, err := client.SafeGet(ctx, key2)

if err != nil {
		exit(err)
}

fmt.Println("   SafeGet - fetch and verify entry:")
printItem(nil, nil, verifiedItem)
				
			
Previous
Next

FEATURES

A super-fast, immutable, and cryptographically verifiable ledger database that provides:

Transactional Integrity, Multi-Node

ACID Compliance

SQL and K/V

SDKs for Python, Node.js, Java, Go

RUNS ON

Our Support Plans

immudb is available in:

IMMUDB WEB CONSOLE

UNMATCHED PERFORMANCE

immudb can handle millions of writes per second. The following table shows performance of the embedded store inserting 1M entries on a 4-core Intel® Xeon® E3-1275v6 CPU and SSD disk with 20-100 parallel workers:
Entries Workers Batch Batches Time(s) Entries/s
1M 20 1000 50 1.061 1.2M /s
1M 50 1000 20 0.543 1.8M /s
1M 100 1000 10 0.615 1.6M /s
4-core Intel® Xeon® E3-1275v6 CPU
SSD disk

THE OPEN-SOURCE IMMUTABLE DATABASE

Run immudb easily on Linux, FreeBSD, Microsoft Windows, and macOS, along with other systems derived from them, such as Kubernetes and Docker.

White Paper — Registration

We will also send you the research paper
via email.

Use Case - DevOps Evidence

Goal:

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.

Implementation:

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.

Use Case - Finance

Goal:

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.

Implementation:

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 - IoT Sensor Data

Goal:

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.

Implementation:

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 - Tamper-resistant Clinical Trials

Goal:

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.).

Implementation:

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 - eCommerce and NFT marketplace

Goal:

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, …)


Implementation:

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.

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.

Subscribe to our newsletter