Managed TigerBeetle, in Alpha, on Layerbase Cloud

TigerBeetle is a financial accounting database. Instead of generic tables it stores accounts and transfers with double-entry semantics and strict consistency, which is what ledgers, payment processors, billing engines, and in-game economies actually need. It speaks a binary protocol through native client libraries rather than SQL. Layerbase runs it always-on in a dedicated container with a built-in Ledger console, and labels it Alpha because the engine is pre-1.0.

The Pro plan with at least one $10/mo pool block. TigerBeetle is pre-1.0 and built for dedicated always-on deployments, not casual serverless use: it reserves roughly 1.4 GB of RAM around the clock and never sleeps, which is more than the base Pro pool can absorb on its own. The create flow shows the same requirement before you commit to anything.

For most projects, honestly, no. If you need a general-purpose database, PostgreSQL or MariaDB will serve you better and cheaper. TigerBeetle earns its footprint when you need a real double-entry ledger with strict consistency. The two paths that make sense: evaluate it free on Layerbase Desktop, or talk to us about a dedicated server (Custom plan) for production ledger workloads.

TigerBeetle is a pre-1.0 engine and its client libraries must exactly match the server release, so upgrades are coordinated rather than seamless. We run it with crash isolation and capacity guards, but you should treat managed TigerBeetle as suitable for evaluation and development, not yet for production money movement.

TigerBeetle uses native client libraries (Node.js, Go, Python, Java, .NET) over a binary protocol. Your dashboard shows the instance address and cluster id with copy-ready client snippets, and the built-in Ledger console lets you create and look up accounts and transfers without writing code.

No. TigerBeetle runs always-on in its own dedicated container and never hibernates or auto-archives. That always-on reservation is exactly why it draws from your Pro pool and requires a pool block.

TigerBeetle has no built-in authentication, so IP restrictions are enforced automatically: any TigerBeetle instance you run is locked down to specific IPs by default.

Not in Cloud. Managed TigerBeetle needs the $15/mo Pro plan plus at least one $10/mo pool block, $25/mo in total, because it reserves roughly 1.4 GB of RAM around the clock. It is free to run on Layerbase Desktop and through the Layerbase CLI, which is the cheapest way to evaluate it before committing.