HOSTING & DATABASES · SOURCE-BASED PROFILE

Layerbase pricing
and database limits

What the shared and dedicated plans include, where databases run, and what to check before using them in production.

Public sources checked 2026-11-11. Prices are in USD per month.

Updated November 11, 2026, after Layerbase revised pages that disagreed when this profile was first checked on November 10, 2026. Its current pricing, documentation and product pages now agree on paid connection limits, dedicated cancellation, backup frequency on the shared plans, the shared-cloud allowance that comes with a dedicated server and whether a branch takes a database slot, so each is shown once. Three details are still described differently between its pages, so both descriptions are shown below: the branch limit and default backup frequency of dedicated servers, and the storage a new branch uses.

Visit Layerbase ↗

Shared plans: account-level quotas

Storage quotas are summed across every database on the account, not allotted per database. Source: Storage Quota, checked 2026-11-11 Branches use that storage too, but a branch does not take one of the plan's database slots: each database has its own branch allowance, shown as branches per database on the plan cards. Source: Plans and availability, checked 2026-11-11 Source: Plans and availability, checked 2026-11-11 Layerbase's pages describe the storage a new branch uses differently (see the qualified claims below).

Free is meant for development, testing, evaluation, CI, personal projects and early-stage products; once a product runs in production and earns recurring revenue, Layerbase says it belongs on Solo or Pro. Source: Is the free tier okay for commercial work?, checked 2026-11-11

The Pro trial lasts 7 days Source: The Pro free trial, checked 2026-11-11, requires a card, charges $0 up front and automatically converts to 15 USD/month Source: The Pro free trial, checked 2026-11-11. It is limited to one per customer, and canceling during the trial ends Pro access immediately. Source: The Pro free trial, checked 2026-11-11

Pro pool blocks add 1 GB RAM Source: Pool blocks, checked 2026-11-11, 1 vCPU Source: Pool blocks, checked 2026-11-11 and 25 GB storage Source: Pool blocks, checked 2026-11-11 for 10 USD/month Source: Pool blocks, checked 2026-11-11 each, up to 20 blocks Source: Pool blocks, checked 2026-11-11.

Engine minimums: MySQL and FerretDB start on Solo; Meilisearch, CouchDB and the Performance engines (ClickHouse, QuestDB, Qdrant, Weaviate, InfluxDB) need Pro; TigerBeetle (Alpha) runs only on a dedicated server. Source: Every cloud engine, classed honestly, checked 2026-11-11
Bandwidth policy: Never billed; measured across every database on the account per 24 hours, 7 days and 30 days. Going over starts a 24-hour grace period (skipped above 5x the allowance); after that, databases are stopped and cannot be restarted until you upgrade or the traffic is fixed. Data and backups are untouched. Source: Bandwidth and acceptable use, checked 2026-11-11
Plan terms during beta: Beta period June 2026 to July 2027: plans and limits may change; paid-plan changes are announced at least 60 days in advance; Free plan features may change without notice. Source: Database plan beta terms, checked 2026-11-11

Claims that need qualification

Layerbase's public pages state these details differently as of the check date. Confirm the applicable terms before depending on them.

Branch limit on dedicated servers

The dedicated docs, the dedicated pricing page, the pricing page's Dedicated card and details, the plan table in the pricing page's Markdown version and the branching page say a dedicated server has no branch cap beyond its memory and storage. The features page and its Markdown version list Dedicated at 10 branches per database. Confirm the branch limit that applies to your server before planning more than 10 branches of one database.

/docs/dedicated /pricing/dedicated /pricing /pricing.md /branching /features /features.md

Dedicated backup frequency

Layerbase's pages for people (the dedicated and backup docs, the pricing page and its Markdown version, and the security page) say a dedicated server is backed up hourly by default. The machine-readable capability document at /agents.md lists the dedicated ("Custom") plan with "backups every 12 hours, 30-day rolling retention". Check the schedule set on each database before relying on hourly restore points.

/docs/dedicated /docs/cloud/backups /pricing /pricing.md /security /agents.md

Branch storage

The branching docs say "On standard storage, a branch is a full copy of the data" and that a branch shares data with its parent only after Branching is turned on for the database; the features page says "Turn on instant branching for a database and new branches share storage instead of copying it." The branching page describes branches as copy-on-write clones and, without stating that condition, answers "Does a branch double my storage cost?" with "No. A fresh branch shares its parent blocks and writes nothing new until you change something." Check whether Branching is turned on for a database before estimating how much storage its branches use.

/docs/cloud/branching /features /branching

Sleep, archive and recovery

Sleep, archive and manual stop are different states. A manually stopped database does not wake just because a client connects. Source: The states, checked 2026-11-11

Free idle sleep: 15 minutes Source: The states, checked 2026-11-11
MariaDB idle sleep on Free: 30 minutes Source: What does "sleeps and wakes on connect" mean?, checked 2026-11-11
Unpinned Solo and Pro idle sleep: 6 hours Source: The states, checked 2026-11-11
Free sleep requirement: Asleep at least 25% of any rolling 7-day window (about 6 hours a day). A database held awake around the clock by a poller, uptime monitor or keep-alive ping is put to sleep and paused after a warning and grace period. Source: Free databases must sleep, checked 2026-11-11
Free archive after inactivity, approximately: 14 days Source: The states, checked 2026-11-11
Never-connected Free database archive, approximately: 7 days Source: The states, checked 2026-11-11
Archive recovery: Restore from the dashboard before connecting, typically in 10 to 30 seconds; data and backups are kept. Source: Archiving and restoring (Free tier), checked 2026-11-11
Free archived database removal, approximately: 90 days Source: Long-archived free databases (90 days), checked 2026-11-11
After removal: Live resources are removed, but the most recent backup is kept for a one-click restore or download. Source: Long-archived free databases (90 days), checked 2026-11-11
Automatic archive on paid plans: No Source: The states, checked 2026-11-11

Backups and point-in-time restore

Shared paid-plan dump interval while running: 12 hours Source: Automatic backups, checked 2026-11-11
Sleeping and stopped databases: A final dump when the database goes to sleep; per-database dumps pause while it sleeps. Volume snapshots, checked every 6 hours and refreshed at least weekly, also cover sleeping and stopped databases. Source: Sleeping databases, checked 2026-11-11
Automatic backups on branches by default: No Source: Branches, checked 2026-11-11
Restoring a dump: Overwrites the live database and cannot be undone; take a fresh backup first. Source: Restoring from a backup, checked 2026-11-11
PITR minimum shared plan: Pro Source: Turning it on, checked 2026-11-11
PITR engines: PostgreSQL, FerretDB Source: What it covers, checked 2026-11-11
PITR requires an always-on pin: Yes Source: Turning it on, checked 2026-11-11
PITR on by default: No Source: Turning it on, checked 2026-11-11
PITR restore target: A new database; the original is untouched, and the restored copy counts toward your plan. Source: How a restore behaves, checked 2026-11-11
PITR window: A rolling window measured in days, anchored by daily base snapshots Source: Common questions, checked 2026-11-11

The docs give no exact number of days for the PITR window; once PITR is on, the database's Backups tab shows how far back it reaches. Source: Turning it on, checked 2026-11-11 Test a restore before relying on it.

Branches and plan limits

Branching is available on Free. Each database has its own branch allowance (see the plan cards), and branches do not count toward the plan's database limit, though they use storage. Source: Plans and availability, checked 2026-11-11 Source: Plans and availability, checked 2026-11-11 Supported-engine count: 17 Source: Supported engines, checked 2026-11-11. Excluded engines: CouchDB, TigerBeetle Source: Supported engines, checked 2026-11-11.

Preview and Development branches sleep after 20 idle minutes Source: Create a branch, checked 2026-11-11 and cannot be pinned always-on on shared hosting. Source: Create a branch, checked 2026-11-11 On standard storage a branch is a full copy and the source is briefly paused; turning on Branching for a database makes new branches share data with the parent until the two diverge. Source: Why some branches are instant and others take a moment, checked 2026-11-11 The branching page does not state this condition (see the qualified claims above).

Dedicated servers: billed per server

A dedicated server is a single-tenant VM that stays on and is billed at one flat monthly price per server. Source: What you get, checked 2026-11-11 Source: How a server is billed, checked 2026-11-11 Layerbase's dedicated docs and pricing pages say there is no database or branch cap on the server, only its RAM and disk, but its features page gives Dedicated a per-database branch limit (see the qualified claims above). Source: What you get, checked 2026-11-11 On the shared cloud, a server on its own includes the Free plan's allowance: up to 2 databases with 5 GB storage and no always-on pool or pool blocks; more shared cloud needs Pro at $15/month. Source: What you get, checked 2026-11-11 If Pro ends, up to 2 shared-cloud databases keep running, and any beyond that are paused 72 hours after a warning email, never deleted. Source: Can I keep a Dedicated server and cancel Pro?, checked 2026-11-11

Monthly USD prices and resources from dedicated documentation
Location / server	USD/month	vCPU	RAM GB	Disk GB	Outbound transfer
United States · Dedicated 4GB	35 Source: The sizes, checked 2026-11-11	2 Source: The sizes, checked 2026-11-11	4 Source: The sizes, checked 2026-11-11	25 Source: The sizes, checked 2026-11-11	Included, not metered Source: What you get, checked 2026-11-11
United States · Dedicated 8GB	65 Source: The sizes, checked 2026-11-11	4 Source: The sizes, checked 2026-11-11	8 Source: The sizes, checked 2026-11-11	50 Source: The sizes, checked 2026-11-11	Included, not metered Source: What you get, checked 2026-11-11
United States · Dedicated 16GB	120 Source: The sizes, checked 2026-11-11	2 (memory-optimized) Source: The sizes, checked 2026-11-11	16 Source: The sizes, checked 2026-11-11	100 Source: The sizes, checked 2026-11-11	Included, not metered Source: What you get, checked 2026-11-11
Brazil · Dedicated 4GB	45 Source: The sizes, checked 2026-11-11	2 Source: The sizes, checked 2026-11-11	4 Source: The sizes, checked 2026-11-11	100 Source: The sizes, checked 2026-11-11	5 TB / month included Source: The sizes, checked 2026-11-11
Brazil · Dedicated 8GB	95 Source: The sizes, checked 2026-11-11	4 Source: The sizes, checked 2026-11-11	8 Source: The sizes, checked 2026-11-11	180 Source: The sizes, checked 2026-11-11	6 TB / month included Source: The sizes, checked 2026-11-11
Brazil · Dedicated 16GB	155 Source: The sizes, checked 2026-11-11	2 (memory-optimized) Source: The sizes, checked 2026-11-11	16 Source: The sizes, checked 2026-11-11	100 Source: The sizes, checked 2026-11-11	6 TB / month included Source: The sizes, checked 2026-11-11

Default dedicated backup interval (see the qualified claims): 1 hour Source: What you get, checked 2026-11-11
Per-database schedule options: hourly, every 6 hours, every 12 hours, daily Source: What you get, checked 2026-11-11
Dedicated backup retention: 30 days Source: What you get, checked 2026-11-11
Month-to-month cancellation: Takes effect at the end of the period you paid for: the server keeps running, you are not billed again, and a Keep server button undoes the cancel until then. Then every database gets a final backup, kept for 30 days, and the server is destroyed, so export data before that date. A server with no successful payment behind it is canceled at once. Source: Canceling a server, checked 2026-11-11
Prepaid terms: Prepaying is US-only (standing offer: 12 months for the price of 10); canceling during a prepaid term takes effect when the term ends. Source: Prepaying a server, checked 2026-11-11
TigerBeetle (Alpha) runs only on dedicated servers: Yes Source: What you get, checked 2026-11-11

Region and compatibility limits

Shared hosting regions: US East (Ashburn, Virginia) or EU West (France), chosen when each database is created; existing databases do not move between regions. Source: Current Summary, checked 2026-11-11
Dedicated locations: US East (Virginia), US West (Oregon), South America (São Paulo) Source: Current Summary, checked 2026-11-11
EU data residency: Not offered. EU West keeps databases and their backups in the EU, but account records, team records and logs stay in the United States. Source: Not Supported Yet, checked 2026-11-11
Multi-region replication or failover: No Source: Not Supported Yet, checked 2026-11-11
Backup storage: Cloudflare R2. EU West backups stay in an EU-jurisdiction bucket; US East and dedicated-server backups may be processed outside the server location. Source: Backups, checked 2026-11-11
Contractual residency guarantee: No Source: Current Summary, checked 2026-11-11
Compliance programs: Not supported: HIPAA, SOC 2, PCI DSS or similar programs, and custom data processing agreements. Source: Not Supported Yet, checked 2026-11-11
MongoDB selection: Selecting MongoDB opens a chooser for compatible engines (DocumentDB or FerretDB); test your queries against the chosen engine's compatibility documentation. Source: Which engines run on Cloud, checked 2026-11-11
Desktop-only engines: CockroachDB, SurrealDB Source: Which engines run on Cloud, checked 2026-11-11

Direct connections have a separate rate limit: 20 new connections per source IP Source: Pooled vs direct connections, checked 2026-11-11 per 10 seconds Source: Pooled vs direct connections, checked 2026-11-11. This is not an account concurrency allowance.

Not recommended for

Each item restates a limit that Layerbase publishes and links to the page that states it.

Running a production product that earns recurring revenue on the Free plan; Layerbase says it belongs on Solo or Pro. Source: Is the free tier okay for commercial work?, checked 2026-11-11
Keeping a Free database awake around the clock with a poller, uptime monitor or keep-alive ping; Free databases must sleep. Source: Free Databases Must Sleep, checked 2026-11-11
Workloads that need EU-only data residency, a contractual residency guarantee or a custom data processing agreement. Source: Not Supported Yet, checked 2026-11-11
Regulated data that needs HIPAA, SOC 2, PCI DSS or similar compliance programs. Source: Not Supported Yet, checked 2026-11-11
Multi-region replication or failover. Source: Not Supported Yet, checked 2026-11-11
High availability on a dedicated server: each server is one node with no standby or replica. Source: Compared to Supabase, on one bill, checked 2026-11-11

Check the primary sources

Each figure links to its source and identifies its section and check date. This is a dated snapshot; vendor terms can change. Not covered: measured performance, uptime or SLA terms, an exact PITR retention window and ratings.

/pricingChecked 2026-11-11
/pricing/dedicatedChecked 2026-11-11
/docs/billingChecked 2026-11-11
/docs/cloud/backupsChecked 2026-11-11
/docs/cloud/point-in-time-restoreChecked 2026-11-11
/docs/database-lifecycleChecked 2026-11-11
/docs/cloud/branchingChecked 2026-11-11
/docs/plans/always-onChecked 2026-11-11
/docs/dedicatedChecked 2026-11-11
/data-residencyChecked 2026-11-11
/docs/cloud/connectingChecked 2026-11-11
/acceptable-useChecked 2026-11-11
/pricing.mdChecked 2026-11-11
/featuresChecked 2026-11-11
/branchingChecked 2026-11-11
/securityChecked 2026-11-11
/agents.mdChecked 2026-11-11
/features.mdChecked 2026-11-11

ToolPick methodology · Browse the tool directory