Skip to main content
Early AccessManaged TigerBeetle · Production-ready

Ship fast
with managed
TigerBeetle®

TigerBeetle's mission-critical double-entry engine — provisioned, replicated, and operated by us. Process one million transfers per second without running a single cluster.

Start Building FreeRead the Docs
Peak Throughput · Single Cluster
1,000,000
Transfers / Second · Hardware-limited
3x
Replicated
By Default
99.99%
Uptime SLA
Guaranteed
<5ms
P99 Commit
Latency
0
External
Dependencies
Strict Serializability
Zero Data Loss
Immutable Audit Log
Explore Platform
01 — Features

Why We Love TigerBeetle

001

One Million Transfers Per Second

TigerBeetle's single-threaded engine with hardware-optimized I/O processes more financial transactions than any general-purpose database. Linear performance, no configuration tuning required.

3 Orders of Magnitude Faster
002

Double-Entry Accounting Native

Debits and credits aren't conventions — they're enforced primitives. Balance limits, two-phase transfers, and atomic batch operations are built into the data model itself. 500 years of accounting correctness, encoded.

No Application-Layer Workarounds
003

Strict Serializability

Built on Viewstamped Replication consensus. Every transfer is strongly serializable — no phantom reads, no dirty writes, no lost updates. Immutable and append-only by design: your audit log is the database.

Formally Verified Consensus
004

Deterministic Simulation Tested

TigerBeetle uses a simulation framework that injects network partitions, disk faults, and clock skew — deterministically. The most rigorous safety methodology in the database industry outside formal verification.

Written in Zig · Zero Dependencies
005

Distributed by Default

Every Parix cluster runs across three replicas in separate failure domains. Automated failover, zero data loss, and consensus-based replication. No single node is ever a point of failure.

Multi-AZ · Automated Failover
006

Every Language, One Protocol

Official clients for Node.js, Go, Python, Java, .NET, and more. Parix manages connection pooling, keepalives, and TLS. Bring your existing stack — no new protocols to learn.

Multi-Language · Batteries Included
02 — Throughput

Every transfer.
Instantly.

Live transfer stream
Live
—
Transfers / sec
0
Committed this session
2.1ms
Avg commit latency
03 — Distribution

No point
of failure.

Replica cluster
Live
us-east-1aLeader
—
Op number
—
Commit latency
Δ 0
Sync lag
us-east-1bReplica
—
Op number
—
Commit latency
Δ 0
Sync lag
us-east-1cReplica
—
Op number
—
Commit latency
Δ 0
Sync lag
04 — Performance

Predictable.
At any load.

Latency distribution
Live
—
P50 Latency
—
P99 Latency
—
P99.9 Latency
05 — The Problem

General-purpose databases
weren't built formoney.

01 / FAILURE MODE

Lock Contention

Row-level locking serializes concurrent balance updates. Hot accounts become bottlenecks. Your Stripe webhook queue backs up. Customers notice.

02 / FAILURE MODE

No Audit Trail

Mutable records mean last-write-wins. Your balance history is a diff of diffs. Compliance audits require reconstructing state from application logs you may not have.

03 / FAILURE MODE

Race Conditions

Read-modify-write patterns create TOCTOU windows. The balance looks fine at read time. By write time, concurrent logic has already spent it twice.

04 / FAILURE MODE

Batch Processing

Billing runs and reconciliation workloads are scheduled because databases can't handle them continuously. You discover errors when the batch job fails at 3am.

05 / FAILURE MODE

Double-Spends

Idempotency logic lives in application code. When it has bugs — and it has bugs — money gets processed twice. Compensating transactions also have bugs.

06 / FAILURE MODE

Operational Complexity

Sharding, replication, failover, backups, observability — none of it purpose-built for financial guarantees. You're running a database operations team instead of building product.

06 — The Foundation

Built on the only database
designed formoney.

TigerBeetle isn't Postgres with extensions. Every design decision was made under the assumption that correctness — not flexibility — is non-negotiable.

// Connect to your managed clusterimport { createClient }from 'hypertransactions';const client =createClient({ cluster:'prod-01.db.hypertransactions.io', replicas:3, });// Create accounts on a USD ledgerawait client.createAccounts([ { id:1n, ledger:840, code:1000 }, { id:2n, ledger:840, code:1000 }, ]);// Transfer $250.00 — atomically enforcedconst result =await client.createTransfers([{ id:1n, debit_account_id:1n, credit_account_id:2n, amount:25000n,// $250.00ledger: 840, code: 5001, }]);// ✓ committed in 2.1ms · replicated · immutable
01

Linked Transfers

Chain multiple transfers into a single atomic unit. All succeed or all fail. No compensating transactions, no rollback logic, no partial states in production.

02

Pending / Posted Semantics

Reserve funds without posting them. Pre-authorizations, escrow, in-flight holds — native to the database, not hacked into your application layer.

03

Strict Serializability

Every transfer is ordered relative to every other. No read anomalies, no phantom reads, no lost updates. The guarantees you need to move money with confidence.

04

Immutable Audit Trail

Records are never updated, only appended. The full history of every transfer exists permanently. Compliance and forensics are not afterthoughts.

05

Zero-Lock Throughput

Purpose-built concurrency eliminates lock contention entirely. One million transfers per second from a single cluster. Hot accounts are no longer bottlenecks.

06

Multi-Ledger Isolation

Model USD, EUR, loyalty points, and game currency in the same cluster with hard isolation. Cross-ledger transfers are atomic. Currency contamination is impossible.

07 — The Platform

TigerBeetle primitives.
Our engineering surface.

TigerBeetle speaks a binary protocol. We built the translation layer, the connection pool, the retry semantics, the auth surface, and the observability stack — and we keep it current through every upstream release.

We've run TigerBeetle through failure scenarios most teams will never simulate. The production hardening we've done isn't in any public documentation.

HTTP/JSON Gateway

Full REST API over TigerBeetle's binary protocol. Works from any language. No custom client required.

API Key Auth

Project-scoped API keys with fine-grained permissions. Rotate credentials without downtime. Audit log of every access.

CDC Streaming

Change data capture webhooks and Kafka-compatible streams. React to every transfer in real time, without polling.

Metrics & Alerting

P50/P99/P999 latency, throughput, error rates. PagerDuty and Slack integrations. SLA dashboard always on.

Multi-Region Replication

Clusters in US, EU, and APAC with sub-100ms cross-region sync. Geographic distribution without distributed systems complexity.

Compliance Exports

SOC 2 Type II certified. PCI-DSS ready. Immutable audit exports for financial regulators. Certifications already done for you.

Zero-Downtime Upgrades

Every TigerBeetle release ships correctness improvements and performance gains. Staying current on a live consensus cluster without dropping your SLA is a solved problem — for us. For self-hosters, it's a quarterly incident risk.

Client SDKs

TypeScript, Python, Go, Java, Ruby. Idiomatic clients with built-in retry logic, connection pooling, and type safety.

08 — Use Cases

Six industries.
One ledger.

Every company that moves money at scale faces the same underlying problem. The primitives are universal, even if your domain isn't.

01 / USE CASE

Digital Wallets & Fintech

Multi-currency wallets with instant settlement, P2P transfers, and real-time balance updates at 10M+ user scale. No reconciliation jobs.

≤0.5ms P99 balance read
02 / USE CASE

Gaming Economies

In-game currency, item trading, loot drops, and tournament payouts. Atomic transfers prevent duplication exploits that destroy game economies.

1M+ transactions/event
03 / USE CASE

SaaS Subscription Billing

Usage metering, proration, credit wallets, and billing runs for 100K+ subscriptions. Replace your nightly Stripe batch with continuous streaming updates.

100K subs in 40 seconds
04 / USE CASE

AI Platforms & Usage Metering

Token consumption tracking, credit-based billing, team spend limits, and real-time cost attribution at inference scale.

<1ms per token event
05 / USE CASE

Ride-Sharing & Marketplaces

Driver earnings, rider payments, platform fees, and promotional credits with multi-party atomic splits. Settlement in real time, not T+1.

Multi-party splits, atomic
06 / USE CASE

Digital Banking

Core banking ledger for neobanks and BaaS providers. Strict serializability for compliance, immutable audit trail for regulators.

Full regulatory audit trail
09 — Getting Started

Up and running in
three steps.

1

Create your cluster

Provision a managed TigerBeetle cluster in your chosen region. Pick your tier. Get credentials. Done in under two minutes.

POST /v1/clusters
{"name":"prod-payments","region":"us-east-1","tier":"starter"}// → cluster ready in ~90s
2

Define accounts & ledgers

Create ledgers per currency or product, then accounts for each entity in your system. The model is simple and extremely flexible.

POST /v1/accounts
{"id":"acc_user_4821","ledger":840,// USD"flags": ["debits_must_not_exceed_credits"] }
3

Post transfers

Start posting transfers. The API is idempotent, atomic, and returns in under a millisecond. Link multiple for complex operations.

POST /v1/transfers
[{"id":"<uuid>","debit_account_id":"acc_u","credit_account_id":"acc_m","amount":9900}]// ✓ Processed in <1ms// ✓ Immutably recorded
10 — Comparison

Self-hosting TigerBeetle
is an engineering project.

TigerBeetle has no managed cloud offering. No hosted option. No ops playbook. Consensus tuning, replica recovery, zero-downtime version upgrades across a Viewstamped Replication cluster — this is not a weekend project. Teams who've done it don't talk about it lightly. We've done it. Here's what you get.

CapabilitySelf-hostedParix
TigerBeetle core primitives
HTTP/JSON API (no client SDK needed)
Managed replication & failover
Zero-downtime version upgrades
Upstream version managementQuarterly incident risk
Replica recovery automation
CDC / Kafka streamingCustom build
SLA with financial penalties
SOC 2 Type II certificationYour burden
Metrics, dashboards, alertingBuild it
Time to first transferDays to weeksUnder 2 minutes
11 — In Production

Teams that made
theswitch.

"

We replaced three separate services — a Postgres ledger, a Redis balance cache, and a Kafka deduplication layer — with a single Parix cluster. The architecture got simpler and the correctness guarantees got stronger.

Engineering Lead — Series B fintech, 4M active wallets
"

Our billing run used to be a daily prayer that nothing deadlocked. Now it's a cron job we don't think about. A hundred thousand subscriptions in forty seconds, zero reconciliation errors in six months.

Head of Infrastructure — $40M ARR SaaS platform
12 — Enterprise

Built for teams
movingserious
money.

Dedicated clusters, contractual SLAs, compliance documentation, and a direct line to the engineering team. For organizations where a billing error has seven-figure consequences.

Talk to SalesCompliance Docs
Dedicated single-tenant clusters
99.995% uptime SLA with financial credits
SOC 2 Type II + PCI-DSS documentation
Custom data residency & regional isolation
Direct engineering team Slack channel
Custom retention & compliance exports
SAML SSO & role-based access control
Architecture review & migration support
Get started today

Infrastructure your
finance stack deserves
is one API call away.

Free tier includes 1M transfers/month, one cluster, and all primitives. No credit card required.

Start Building FreeRead Documentation
Free Tier · 1M Transfers/Month · No Credit Card · All Primitives Included