# Managed TigerBeetle, in Alpha, on Layerbase Cloud

> The only self-serve managed TigerBeetle. Always-on on your own dedicated server from $35/mo, or run it free on Layerbase Desktop.

Canonical: https://layerbase.com/db/tigerbeetle
Last updated: 2026-11-09

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.

## Key facts

| Fact | Value |
| --- | --- |
| Engine | TigerBeetle |
| Category | Ledger |
| Upstream project | [TigerBeetle](https://tigerbeetle.com/) |
| Layerbase Cloud | Yes |
| Free tier | No |
| Pricing | Dedicated servers only, from $35/mo flat, no meters |
| Default version | 0.16 |
| Versions for new databases | 0.16 |
| Layerbase Desktop | Yes |
| SpinDB (local CLI) | Yes |
| Best for | Ledger systems, payment processors, billing engines, in-game economies, and any workload that needs double-entry accounting with strict consistency. |

## Use cases

- 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

## Cloud features

| Feature | Available |
| --- | --- |
| Always-on option | Yes |
| TLS encryption | No |
| HTTP access | No |
| IP allowlisting | Yes |
| Web query console | Yes |
| Sleeps when idle, wakes on connect | No |
| Automatic backups | Yes |
| Pooled connections | No |
| Direct connections | Yes |
| Serverless HTTP driver | No |

## 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.

## Links

- [TigerBeetle on Layerbase](https://layerbase.com/db/tigerbeetle)
- [Create a TigerBeetle database](https://layerbase.com/create/tigerbeetle)
- [Connecting to TigerBeetle](https://layerbase.com/docs/cloud/connecting/tigerbeetle)
- [Pricing](https://layerbase.com/pricing) (markdown: https://layerbase.com/pricing.md)
