Skip to content
LayerbaseLayerbase
TigerBeetle

Managed TigerBeetle, in Alpha, on Layerbase Cloud

The only self-serve managed TigerBeetle anywhere. Double-entry accounting baked in, running always-on in a dedicated container. Pro plan with at least one $10/mo pool block: TigerBeetle reserves roughly 1.4 GB of RAM around the clock, and we price that honestly instead of hiding it.

Create TigerBeetleCreate an account
Native Client
TigerBeetle
NATIVE CLIENTJavaScript

Code

import { createClient } from 'tigerbeetle-node'
 
const client = createClient({
cluster_id: 0n,
replica_addresses: ['cloud.layerbase.host:3000'],
})
 
await client.createTransfers([
{
id: 1n, debit_account_id: 1n, credit_account_id: 2n,
amount: 100n, code: 1, ledger: 1, flags: 0,
},
])

Result

[] // empty array means success (no per-row errors)

  • Always-on floor

    Pro plus a $10/mo pool block

  • Locked down

    IP allowlist enforced

  • Layerbase Cloud

    Managed, in seconds

  • Desktop and CLI

    Run it locally or self-host

Always-on

Managed TigerBeetle, priced honestly

TigerBeetle runs always-on in its own dedicated container: it reserves roughly 1.4 GB of RAM around the clock, never sleeps, and never branches. On Layerbase Cloud that means the Pro plan plus at least one $10/mo pool block, and the create flow says so before you commit to anything. Native client libraries for Node.js, Go, Python, Java, and .NET connect over its binary protocol, and the built-in Ledger console creates and looks up accounts and transfers without writing code.

Try it free on Desktop

Quick start

Connect with any TigerBeetle client

Ledger systems, payment processors, billing engines, in-game economies, and any workload that needs double-entry accounting with strict consistency.

  • Run a managed ledger that records accounts and transfers without rolling your own consistency logic
  • Validate a payment-processor design against a real TigerBeetle, free on Desktop or managed on Pro
  • Prototype an in-game economy with deterministic transfer semantics
  • Self-host TigerBeetle on your own infra with the Layerbase CLI
  • Develop a billing engine with audit-grade accuracy on the desktop before moving to a dedicated server
Full TigerBeetle connection guide
ts
TigerBeetle
const client = createClient({ cluster_id: 0n, replica_addresses: ['your-host.cloud.layerbase.dev:3000'] })

Where to run it

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.

Layerbase Cloud

TigerBeetle provisioned on managed infrastructure.

Create database

Layerbase Desktop

Run TigerBeetle locally with the same dashboard and query console.

Download

Layerbase CLI

Run TigerBeetle from the terminal, locally or on your own infra.

View the CLI docs

Alpha, always-on, and priced honestly

TigerBeetle is pre-1.0 and built for dedicated, always-on deployments: it reserves roughly 1.4 GB of RAM around the clock, never sleeps, and never branches. On Layerbase Cloud it needs the Pro plan plus at least one $10/mo pool block, and the create flow says so before you commit. Evaluating first? Run it free on Layerbase Desktop.

Try it free on Desktop

What you get

Everything a TigerBeetle database should ship with

The same primitives on every TigerBeetle database: TLS, web console, hibernation, and a real dashboard. No tiered features hidden behind a sales call.

Web IDE

Query console in the dashboard, no extra client to install.

Included

TLS by default

All connections encrypted. No setup required.

Not available

Always-on connections

Pin a database to your always-on pool to prevent hibernation.

Included

Scale to zero

Hibernates when idle. Wakes on the next connection.

Not available

Connection pooling

Pooled endpoint for serverless and edge workloads.

Not available

Direct connections

Bypass the pooler for migrations and replication.

Included

Native HTTPS endpoint

Engines whose own wire protocol speaks HTTPS. Every database, including this one, is also queryable over the platform's HTTPS query API and web console.

Not available

Serverless driver

Drop-in HTTP driver for edge runtimes (Neon serverless, PlanetScale, Upstash REST, or the engine-native client).

Not available

IP whitelisting

Restrict access to specific IPs or CIDR ranges.

Included

Automatic backups

Scheduled dumps and volume snapshots with one-click restore on paid plans. Free tier includes a manual backup slot.

Included

What it costs

What TigerBeetle costs on Layerbase

Plans are flat. There is no per-hour compute meter, no per-database line item, and no ingress or egress fee, so the bill does not change shape when your traffic does. You do not need an AWS, GCP, or Azure account either: Layerbase runs the infrastructure.

Pro$15/mo

Plus a $10/mo pool block (always-on).

Compare every plan

Side by side

Hosted TigerBeetle, compared

Layerbase is the only self-serve managed TigerBeetle anywhere; TigerBeetle's own managed offering is invite-only enterprise. Available in Alpha on the Pro plan with a pool block, or run it free on Layerbase Desktop.

Competitor facts as of July 2026, from public pricing pages.

More on TigerBeetle

All articles

FAQ

Common TigerBeetle questions

What does TigerBeetle require on Layerbase Cloud?

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.

Is TigerBeetle the practical choice for my project?

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.

Why is it labeled Alpha?

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.

How do I connect?

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.

Does it hibernate like other Layerbase databases?

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.

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.