# codenotary/immudb

immudb - immutable database based on zero trust, SQL/Key-Value/Document model, tamperproof, data change history

Repository: https://github.com/codenotary/immudb
Canonical: https://ross.abutalabs.com/products/immudb
Homepage: https://immudb.io
Language: Go
License: NOASSERTION
License Family: other
Topics: key-value, immutable, merkle-tree, go, database, tamperproof, verification, immutable-database, compliance, pci-dss, gdpr, cryptographic, tamper-evident, verify, auditable, performance, sql, timetravel, zero-trust
Last push: 2026-08-24T21:17:00+00:00

## Health v2 (maintenance only)
Score: 88/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 66, longevity 100
- inputs: {"age_days": 2491, "days_push": 9, "days_rel": 68, "gap_med": 144, "n_releases_24m": 6}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 9023, forks 378 (observed 2026-08-28T04:10:27.904115+00:00)

## What it is
immudb is an open-source immutable database written in Go that stores data in SQL, key-value, or document models while guaranteeing tamper-evidence through cryptographic proofs and Merkle-tree verification. It can run as a standalone server, in Docker, or embedded as a library, handling millions of transactions per second.

## Use cases
- store tamper-proof audit logs for compliance
- track changes to sensitive data with cryptographic verification
- replace blockchain or ledger services for data integrity
- keep an immutable history of record changes for auditors
- store sensor or IoT data that cannot be altered
- embed a lightweight verifiable database in a Go application

## When to choose
- you need provable data integrity and tamper-evidence without trusting the database server
- you need SQL, key-value, and document models in one immutable store
- you need high throughput (millions of tx/s) unlike blockchain solutions
- compliance requirements like GDPR, PCI-DSS, or audit trails apply
- you want time-travel queries and data change reports

## When to avoid
- you need to update or delete records in place - immudb only allows adding new versions
- you need a general-purpose operational database with rich ecosystem tooling like PostgreSQL
- you need heavy analytical or full-text search workloads
- your stack lacks an immudb SDK and you cannot use JDBC/ODBC

## Facets
- artifact type: application
- maturity: stable
- function: database, cryptography, search-engine, sdk
- domain: databases, security, legal, developer-tools, fintech
- platform: windows, go, cross-platform, self-hosted, cloud
- tags: immutable-database, tamperproof, merkle-tree, audit-log, zero-trust, ledger, sql, key-value-store, document-database, data-integrity, gdpr, time-travel, linux, macos, docker

## Member repositories
- codenotary/immudb (main) score 88

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:27.904115+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:24:19.682564+00:00, confidence not recorded.
  - readme: https://github.com/codenotary/immudb (fetched 2026-08-28T04:10:27.904115+00:00, sha a31cc5542485)
  - homepage: https://immudb.io (fetched 2026-08-29T08:24:14.868259+00:00, sha 4b08190e9fe0)
  - site_page: https://docs.immudb.io/master (fetched 2026-08-29T08:24:14.877332+00:00, sha 86e69900fb46)
  - site_page: https://docs.immudb.io/1.2.1/quickstart.html (fetched 2026-08-29T08:24:14.879279+00:00, sha f179ffa3cea5)
  - site_page: https://docs.immudb.io/ (fetched 2026-08-29T08:24:14.881298+00:00, sha 14b8f83d6f0e)
- Data as of 2026-08-30T08:39:29.467469+00:00.