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.
JavaScriptCode
Result
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.
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 DesktopWhat you get
Production features, free tier included
Every TigerBeetle database ships with the same primitives: 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.
TLS by default
All connections encrypted. No setup required.
Always-on connections
Pin a database to your always-on pool to prevent hibernation.
Scale to zero
Hibernates when idle. Wakes on the next connection.
Connection pooling
Pooled endpoint for serverless and edge workloads.
Direct connections
Bypass the pooler for migrations and replication.
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.
Serverless driver
Drop-in HTTP driver for edge runtimes (Upstash REST, PlanetScale, or the engine-native client).
IP whitelisting
Restrict access to specific IPs or CIDR ranges.
Automatic backups
Scheduled dumps and volume snapshots with one-click restore on paid plans. Free tier includes a manual backup slot.
Why Layerbase
Predictable pricing, no cloud setup
TigerBeetle on Layerbase Cloud is priced the same way as every other engine: a flat monthly plan with nothing metered behind it.
A fixed monthly price
Plans are flat: Free at $0, then $5/mo Solo and $15/mo Pro. No per-hour compute meter, no per-database line items, and no bill that changes shape when your traffic does.
No bandwidth charges
Reads and writes are not metered. There are no ingress or egress fees, so moving data in and out of your database never adds to the bill.
No cloud account to wire up
You do not need an AWS, GCP, or Azure account. Sign up, create a database, and connect. Layerbase runs the infrastructure, so there is no cloud provider to configure or pay separately.
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.
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 SpinDB tooling
- Develop a billing engine with audit-grade accuracy on the desktop before moving to a dedicated server
const client = createClient({ cluster_id: 0n, replica_addresses: ['your-host.cloud.layerbase.dev:3000'] })More on TigerBeetle
All articles- May 18, 2026
Managed TigerBeetle: where things actually stand in 2026
TigerBeetle is purpose-built for double-entry financial accounting. There is no general-purpose managed offering yet. The honest state of hosting in 2026.
Read - March 8, 2026
Getting Started with TigerBeetle
Build a multi-party payment system with TigerBeetle and TypeScript using double-entry bookkeeping, two-phase transfers, and balance limits on a pre-1.0 ledger.
Read
Questions
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.