libfuse meets immudb to create a versioned and tamperproof filesystem

Adam, one of our fantastic developers at Codenotary wrote a cool proof of concept to mount immudb, the open source immutable database in a filesystem using libfuse.

This Python project enables you to use a normal Linux filesystem mount to store files tamperproof and versioned in immudb.

You can watch a short tutorial video here:


To run the immufs project the first thing you need to start is an immudb instance. You can read more in the documentation page of immudb:

Make sure to install all the dependencies and the libfuse-dev OS packages.

git clone
cd immufs
pip3 install -r requirements.txt

# Debian or Ubuntu
apt install -y libfuse-dev
# lets run a local immudb docker container that listens on the immudb standard port 3322
docker run -p 3322:3322 -d codenotary/immudb:1.3.2

The default credentials are immudb:immudb, but you can change that using the immuadmin command. There is also a database initialized when starting immudb that is called defaultdb.

Start immufs

You can find a script in the repository but its simply a shortcut for the following command:

# when immudb is running on the same host
python3 -m immufs.immufs /immufs -o serverurl=localhost:3322 -o login=immudb -o password=immudb -o database=defaultdb

# when immudb is running on another system
python3 -m immufs.immufs /immufs -o serverurl=<ip or dns name>:3322 -o login=immudb -o password=immudb -o database=defaultdb

Now you can work within the mountpoint /immufs and the backend is immudb.


As this is a proof of concept, don’t expect it to be production ready or without any limitations. You can look into the feature list that is updated on a regular basis:

Feel free to try immufs, share your use cases or issues with us

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.

Subscribe to our newsletter