TigerBeetle
An open-source financial transactions database built on debit/credit, published under the Apache License 2.0.
TigerBeetle is a database for online transaction processing, designed around accounts and transfers rather than tables. Every transfer debits one account and credits another under strict serializability. Transfers can run in two phases: a pending transfer reserves funds and is then posted, voided or left to expire, and a partial post moves part of the amount and returns the rest. That model fits card authorizations and other holds.
The software is production-ready on Linux, with client libraries for Python, Java, Node.js, .NET, Go and Ruby. TigerBeetle says one query can carry up to 8,189 transactions and that a cluster scales up on six replicated machines rather than partitioning. The code is open source under Apache 2.0 with no contributor license agreements. Applications define their own account structure on top.
- Website
- tigerbeetle.com
- Infrastructure layers
- Ledger infrastructure (open-source database)
- Products (as published)
- TigerBeetle financial transactions database (accounts, transfers, two-phase transfers)
Client libraries for Python, Java, Node.js, .NET, Go and Ruby - Client types
- Engineering teams building payment, ledger and other transaction systems
- Pricing model (only if published)
- Open source, Apache License 2.0
- API documentation
- docs.tigerbeetle.com
- Date checked
- Profile type
- Standard
Questions
Is TigerBeetle a ledger as a service?
What license does TigerBeetle use?
What is a two-phase transfer?
See also
Sources
- TigerBeetle home
- TigerBeetle Docs and Two-Phase Transfers
- TigerBeetle license
- Checked October 4, 2026.
Source: each provider’s own documentation, product pages, official announcements and filings, and official registers for licences, as linked in each profile. Fields a provider does not publish stay empty. How we build profiles: methodology.
