Kimberlite

Kimberlite
vs PostgreSQL

From bolt-on compliance to built-in compliance.

Feature Comparison Architecture

PostgreSQL is the world's most advanced open source relational database. Kimberlite is a compliance-first database where every record is immutable, hash-chained, and formally verified. They solve fundamentally different problems.

When to Use Each

PostgreSQL

General-purpose OLTP/OLAP, broad ecosystem, mature tooling, traditional relational workloads

General-purpose applications — Web apps, SaaS platforms, content management
Mature ecosystem — Thousands of extensions, ORMs, and tools
Flexible data modeling — JSON, full-text search, GIS, time-series extensions

Kimberlite

Regulated industries requiring immutable audit trails, formal compliance verification, and cryptographic integrity

Audit-critical data — Healthcare records, financial transactions, legal evidence
Compliance by construction — 23 frameworks formally verified, not bolted on after the fact
Cryptographic integrity — Hash-chained records with dual-hash (SHA-256 + BLAKE3) verification

Feature Comparison

A side-by-side comparison of capabilities relevant to regulated data workloads.

Feature PostgreSQL Kimberlite
Data model Mutable rows (UPDATE/DELETE) Immutable append-only log
Audit trail Bolt-on (pg_audit, triggers) Built-in, hash-chained, immutable
Compliance frameworks Manual configuration per framework 23 frameworks formally verified (92 proofs)
Formal verification None 136+ proofs (TLA+, Coq, Kani, Alloy, Ivy, Flux)
SQL support Full SQL standard + extensions Core SQL (SELECT, JOIN, CTE, aggregates)
Ecosystem Thousands of extensions and tools Rust, Python, TypeScript, Go SDKs
Data integrity Checksums on pages Per-record CRC32 + dual hash chains
Multi-tenancy Schema-based (manual isolation) Built-in tenant isolation with ABAC
Access control Role-based (GRANT/REVOKE) RBAC + ABAC + row-level + field masking
License PostgreSQL License (permissive) Apache 2.0

Architecture

How each database approaches data storage and integrity.

PostgreSQL: Mutable State

PostgreSQL stores mutable rows. An UPDATE overwrites the previous value. History requires triggers, audit tables, or extensions like pg_audit. Compliance is layered on top.

Kimberlite: Immutable Log

Kimberlite stores every event in an immutable, hash-chained log. Current state is derived by replaying the log. History is inherent. Compliance is structural, not optional.

Other Comparisons

Evaluate Kimberlite

Install in under 60 seconds. Start with a compliance-ready template.

Install Documentation