Install immudb with Homebrew, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• immuadmin
• immuclient
• immudb

Project history

The public repository was created in 2019 and the project reached public 0.6.x releases in 2020. The README frames the core problem as mutable database transactions and logs: immudb instead appends versions and makes the resulting history cryptographically verifiable.

The project evolved from a key-value store into a broader database surface. Its documentation describes key-value, SQL, and document-database modes, plus server, replica, and embedded-library deployments.

Adoption history

immudb's adoption has been strongest in audit-log, compliance, artifact, sensor-data, transaction, and software-supply-chain use cases, all called out by the project README. The official repository also advertises large Docker Hub pull counts, which is a useful signal for a service-oriented database distributed as containers as well as packages.

Homebrew and Nix package metadata expose immudb as a CLI/server package with immudb, immuadmin, and immuclient commands. That makes it easy to experiment with a tamper-evident database from a developer laptop without adopting a hosted service.

How it is used

Typical usage is to run immudb as a server, administer it with immuadmin, and connect with immuclient or application SDKs. Developers use it when they want an append-preserving history, verifiable reads, or an embedded immutable store without operating a blockchain network.

The project is often evaluated beside ledgers and append-only audit systems rather than general OLTP databases, because its package identity is about proof of history as much as data storage.

Why package nerds care

For package nerds, immudb is interesting because it compresses a heavy idea, verifiable data history, into ordinary package-manager install shapes: a daemon, an admin CLI, and a client CLI. It is also a Go database that can be used as either a standalone service or an embedded dependency.

Timeline

• 2019: Public GitHub repository created.
• 2020: v0.6.0 release series published on GitHub.
• 2021: v1.2 release line added rollback and expiration-oriented features in the project's release communications.
• 2025: v1.9.x release line emphasized SQL compatibility, security hardening, and performance work.

Related projects

• AWS QLDB, Trillian-style transparency logs, append-only audit stores, and blockchain ledgers are adjacent systems in the tamper-evident data-history space.
• immuadmin and immuclient are companion commands distributed with the immudb package.

Sources

• https://api.github.com/repos/codenotary/immudb/releases
• https://docs.immudb.io/master/
• https://formulae.brew.sh/formula/immudb
• https://github.com/codenotary/immudb
• https://immudb.io/
• input.json source_facts.package-manager