tigerbeetle/tigerbeetle

Health v2 · maintenance only

Adoption not part of the score

16908 stars · 886 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

TigerBeetle is a purpose-built financial transactions database written in Zig, designed for mission-critical safety and performance in online transaction processing (OLTP). It uses a replicated consensus protocol and a purpose-built storage engine to process debits and credits across accounts and transfers at very high throughput.

Use cases

• store double-entry ledger transactions for a payments platform
• track account balances with debits and credits at scale
• build a mission-critical OLTP backend for financial products
• replace a general-purpose database for high-throughput transaction processing
• run a replicated fault-tolerant transactions database cluster
• implement two-phase transfers with pending and posted amounts

When to choose

• your workload is financial transactions: accounts, transfers, and balances
• you need strict correctness, durability, and auditability for money movement
• you need very high transaction throughput with predictable latency
• you want a replicated database with strong consistency via consensus

When to avoid

• you need general-purpose queries, joins, or ad-hoc analytics
• your data model is not account-and-transfer based
• you need rich secondary indexes or document/relational flexibility
• you want a mature ecosystem of ORMs and tooling for a mainstream database

Facets

service · maturity active

database concurrency cryptography developer-tools fintech databases microservices backend performance windows self-hosted cloud oltp financial-transactions ledger double-entry-accounting consensus zig replication safety-critical linux macos docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="tigerbeetle/tigerbeetle")