Guide

Dedicated servers

A dedicated server is a single-tenant VM that runs only your databases. It is billed at one flat monthly price per server with no usage meters. Buying one puts you on the Custom plan, which is the Pro plan running on hardware that is yours alone. This page covers the sizes, how a server is provisioned, how your databases land on it, and exactly what happens when you cancel.

What you get

Custom includes everything the Pro plan includes, plus the embedded apps (Session Replay and Secret Store), client-certificate (mTLS) authentication, connection pooling, and 30-day rolling backups. Egress is included, so there is no bandwidth metering. The server is region-pinned and always on: it is never hibernated or paused.

There is no database cap and no branch cap. Run as many databases as fit the server's memory and storage - the only limits are the box's RAM and disk. All engines are available, and embedded apps need no separate setup. TigerBeetle stays Alpha, but on a dedicated box it does not require a pool block.

The sizes

Three presets are self-serve. Each is a flat monthly price added to your one Layerbase bill.

Need a region or size outside this catalog, or far more memory or storage? That is what a bespoke Custom configuration is for. See the dedicated servers page to get in touch.

Buying and provisioning

You buy a dedicated server from the plan page under Dedicated servers. Pick a size and region, then pay at checkout. The server is added as a line on your existing Layerbase subscription rather than as a separate bill, and it is charged today.

You do not need Pro first. If you already have a paid plan the server is added to it; if you are on Free, buying a server runs a quick checkout that starts your Custom plan.

Provisioning is automatic. Your server is usually ready in 15 to 30 minutes and always within the hour. A banner across the dashboard shows while a server is being prepared, and we email you the moment it is live. You do not have to do anything while it builds.

How your databases land on the box

Once the server is live, you create databases on it the same way you create any Layerbase database. In the create flow, a server picker lets you place the new database on your dedicated box instead of the shared pool. Everything after that works exactly like a normal cloud database: connect strings, the query console, backups, and branching all behave the same.

You can run more than one dedicated server. Each is a separate single-tenant VM, all managed from the same dashboard and invoiced together on your one bill.

Canceling a server

Cancellation is per server and lives next to each server on the plan page. It is a two-step, type-to-confirm dialog: you type the server's name, then confirm on a final screen. Only an active server can be canceled. A server that is still being prepared, or already winding down, shows the control grayed out with a reason.

The dedicated cancel policy is stricter than the reversible Solo and Pro cancel. It is immediate, with no proration or refund for the remainder of the month, and it cannot be undone. Before the server is torn down, every database on it gets a final backup. Then the box is destroyed.

After you confirm, the server moves to Winding down while the backups run and teardown proceeds, then it is gone. Your subscription is adjusted down right away. If that server was the only paid item on a Custom account, the subscription is canceled outright so you are not left paying for nothing.

Because this is irreversible and there is no grace window, export or download any data you want to keep before you cancel. The final backup is captured for safety, but the live databases and the box itself do not come back.