TigerBeetle on Desktop and SpinDB

A financial transactions database with double-entry accounting baked in. Strict consistency, deterministic execution, native clients for accounts and transfers.

Layerbase Desktop / TigerBeetle / ledger_prod

Database

ledger_prod

Ledger

  • accounts
  • transfers
  • queries
  • pending
TigerBeetle Client (Node.js)Cmd+R to run
import { createClient } from 'tigerbeetle-node'
 
const client = createClient({
cluster_id: 0n,
replica_addresses: ['127.0.0.1:3000'],
})
 
await client.createTransfers([
{
id: 1n, debit_account_id: 1n, credit_account_id: 2n,
amount: 100n, code: 1, ledger: 1, flags: 0,
},
])
[] // empty array = success (no per-row errors)
1 transfer - 0.3ms

TigerBeetle's strict-consistency cluster model needs operational primitives we have not built yet for multi-tenant managed hosting. We would rather wait and ship it right than ship a half-managed financial database.

If you're with TigerBeetle and would like to help us host a managed offering, we would love to hear from you.

Contact us

Cloud, desktop, or self-host

One database, three places it can live. Pick the speed you want and move between them when you outgrow it.

Desktop app or self-host with SpinDB

TigerBeetle runs on your laptop with the Layerbase Desktop app, or anywhere else with SpinDB, our open-source CLI for managing local and self-hosted databases.

Native dashboard

Same dashboard chrome, query console, and connection manager as the Layerbase Cloud experience, running on your own machine.

Runs the upstream binary

No license substitution. You are running the engine maintainers ship, with the configuration knobs they document.

Your machine, your data

Data stays on disk. No managed-host TLS to terminate, no IP allowlist to maintain, no third party to trust.

Free for personal use

Layerbase Desktop is free for personal projects. Team and commercial use is covered under the standard license.

Common TigerBeetle questions

Why is TigerBeetle desktop-only on Layerbase?+

TigerBeetle is a strict-consistency cluster designed to be operated by a single team. Layerbase Cloud will add managed TigerBeetle once the client-snippet flow and operational primitives are in place. For now, desktop and SpinDB are the supported paths.

How do I connect?+

TigerBeetle uses native client libraries (Node.js, Go, Java, Python) over a binary protocol. The dashboard exposes the connection settings; your code uses createClient with the cluster id and addresses.

Why no web query console?+

TigerBeetle has a domain-specific data model (accounts and transfers, not arbitrary rows). The dashboard surfaces account and transfer browsers and code snippets rather than an ad-hoc query box.

IP whitelisting?+

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.

When will Cloud TigerBeetle ship?+

When the client-snippet workflow and managed-operations primitives are ready. Follow the status page or the public roadmap for updates.