TigerBeetle quickstart
Core TigerBeetle concepts and how Parix packages them as a managed platform.
TigerBeetle is a purpose-built ledger database. Parix does not replace its data model. It packages TigerBeetle behind a managed control plane and gateway.
Core concepts
TigerBeetle centers on a few primitives:
- accounts
- transfers
- integer-based identifiers and amounts
- strongly consistent, append-only ledger operations
Parix keeps those primitives visible so teams can use the official TigerBeetle client model rather than a separate product-specific abstraction.
What Parix adds
TigerBeetle by itself does not provide the full operator experience that this repository targets. Parix adds:
- authentication and org context at the edge
- provider-aware request dispatch
- HTTP gateway translation into native TigerBeetle client calls
- provisioning, upgrade, and backup workflows
- logs, metrics, CDC configuration, and backup history in the dashboard
Operational model
Current product behavior assumes:
- requests reach TigerBeetle through a gateway path
- CDC is handled on a separate transport path from synchronous request routing
- backups, upgrades, and topology changes are orchestrated by control-plane workflows
Best fit
Parix is a good fit when you want TigerBeetle's durability and ledger semantics, but you want the platform to handle:
- cluster lifecycle
- gateway deployment
- observability surfaces
- CDC transport integration
- backup artifact tracking
For the system layout, continue with Parix architecture.