Managed TigerBeetle, in Alpha, on Layerbase Cloud
The only self-serve managed TigerBeetle anywhere. Double-entry accounting baked in, running always-on on a dedicated server of your own, from $35/mo. TigerBeetle reserves roughly 1.4 GB of RAM around the clock and assumes it owns its machine, so we run it only where it does.
JavaScriptCode
Result
Dedicated only
Your own server, from $35/mo
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 DesktopQuick 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 a dedicated server
- 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
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.
Managed TigerBeetle hosting
What managed TigerBeetle costs here, and what Alpha means
Layerbase is the only place selling self-serve managed TigerBeetle, and we label it Alpha on purpose. It runs only on a dedicated server of your own, from $35/mo, because it reserves roughly 1.4 GB of RAM around the clock whether you are using it or not.
Dedicated servers only, from $35/mo
TigerBeetle reserves roughly 1.4 GB of RAM around the clock and assumes it owns its machine, so we do not put it on the shared cloud on any plan. It runs on a dedicated server of your own, a flat monthly price for the whole box, where it sits beside any other engines you run there. We would rather say that plainly than squeeze it into a shared pool.
Always-on, with no sleep state at all
TigerBeetle runs in its own dedicated container and never hibernates or auto-archives. There is no scale-to-zero story here and no wake path to design around: the always-on reservation is exactly why it runs on a dedicated server.
Alpha, and here is what that actually means
The engine is pre-1.0 and its client libraries must match the server release exactly, so upgrades are coordinated rather than seamless. We run it with crash isolation and capacity guards, but treat managed TigerBeetle as suitable for evaluation and development, not yet for production money movement. Evaluating it costs nothing on Layerbase Desktop or through the Layerbase CLI.
Native clients, a Ledger console, and no branching
TigerBeetle speaks its own binary protocol through native clients for Node.js, Go, Python, Java, and .NET, without TLS; access is protected by automatic IP restrictions instead. The dashboard shows the instance address and cluster id with copy-ready snippets, plus a built-in Ledger console for creating and looking up accounts and transfers. Branching is not offered: cluster identity lives inside the data, so a copy would not be an independent database. Automatic backups still run.
TigerBeetle runs on a dedicated server, from $35/mo. Free on Layerbase Desktop if you only want to evaluate it.
FAQ
Common TigerBeetle questions
What is TigerBeetle?
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.
What does TigerBeetle require on Layerbase Cloud?
A dedicated server of your own, from $35/mo. 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, so it is not offered on the shared cloud on any plan. Once you have a server, TigerBeetle is one of the engines you can create on it, and the create flow shows the 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 run it on a dedicated server of your own when you need it managed.
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 to TigerBeetle on Layerbase?
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 runs only on a dedicated server, where the whole machine funds it.
Can I restrict my TigerBeetle instance to specific IP addresses?
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.
Is there a free TigerBeetle tier on Layerbase?
Not in Cloud. Managed TigerBeetle runs only on a dedicated server, from $35/mo, 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.
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 runs only on a dedicated server of your own, from $35/mo, and the create flow says so before you commit. Evaluating first? Run it free on Layerbase Desktop.
Try it free on DesktopWhat you get
Everything a TigerBeetle database should ship with
The same primitives on every TigerBeetle database: TLS, web console, hibernation, and a real dashboard. The rows that need a paid plan say so on the row; nothing here is 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 plan's always-on pool so it never hibernates. Free has no pool, so a free database always sleeps when idle; Solo includes 768 MB of pool and Pro 1.5 GB.
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 (Neon serverless, PlanetScale, Upstash REST, 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 includes 1 manual backup slot you take and restore yourself.
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.
Your own single-tenant server. TigerBeetle runs only there.
Side by side
Hosted TigerBeetle, compared
Layerbase is the only self-serve managed TigerBeetle anywhere; TigerBeetle Cloud publishes plans from $40,960 per year and provisions a cluster only after a kickoff call and a signed MSA. Available in Alpha on your own dedicated server, or run it free on Layerbase Desktop.
Competitor facts verified September 7, 2026 against each vendor's own pricing and documentation pages: TigerBeetle Cloud.
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. Its own managed offering is invitation-only, but self-serve hosting now exists. The honest state of running it 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
Upstream project
TigerBeetle is developed by the TigerBeetle project. Layerbase packages and hosts official releases; the engine itself is built upstream.