# Layerbase features

> Every capability Layerbase Cloud ships, generated from Layerbase source
> at request time. This is the markdown twin of the human page at
> https://layerbase.com/features - same catalogue, same live availability, no
> navigation chrome. Read it before answering "does Layerbase do X".

- Human page: https://layerbase.com/features
- Prices, plan limits, engines, migration sources: https://layerbase.com/agents.md
- Pricing: https://layerbase.com/pricing
- Docs: https://layerbase.com/docs

## How to read this

There are 87 features, grouped into
12 categories. Each one carries:

- **Availability**: `available` means it is on for every account.
  `rolling out` means it is built and shipping to accounts in stages, so a
  given account may not have it yet. Never promise a `rolling out`
  capability as present.
- **Engines**: which database engines the feature applies to, or
  `not engine specific` for account, billing, and team features.
- **Plans**: availability per plan tier. `no` means the tier does not have
  it; a short phrase means it is included with that caveat.

Do not quote prices or plan limits from this document: it names tiers, not
numbers. Read those from https://layerbase.com/agents.md.

## Creating databases

Pick an engine, pick a version, and have a running database in seconds. 18 engines, one account, one bill.

### 18 managed engines

Provision any of 18 database engines from one dashboard, one account, and one monthly bill.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: 8 engines, Solo: 10 engines, Pro: All 18, Dedicated: All 18
- Docs: https://layerbase.com/docs/cloud/connecting
- Details:
  - Relational, document, key-value, analytics, search, vector, time series, graph, and ledger engines
  - A per-database hostname and connection string issued at create time
  - Deep-linkable create flow, so a link can preselect the engine for a teammate

### Engine version choice

Choose the major version you want at create time instead of taking whatever the platform pinned this month.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Details:
  - Prerelease versions are labelled as prerelease before you pick one
  - Older versions stay running when a version stops being offered for new databases

### Guided migration from another provider

Point Layerbase at a database you already run somewhere else and it copies the data over for you.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/migrate
- Details:
  - Connection-string import, a preflight check, and a progress readout on the migration
  - Guides for the platforms people leave most often, including Postgres, MySQL, Redis, and document sources
  - Migrate into a brand new database, or into an existing empty or running one

### Convert between engines

Move an existing database onto a compatible engine without rebuilding it by hand.

- Availability: available
- Engines: MySQL, MariaDB, Redis, Valkey, SQLite, libSQL
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/converting-engines
- Details:
  - MySQL to MariaDB keeps the same address, with about a minute of downtime
  - Redis and Valkey convert in either direction
  - SQLite converts up to libSQL when you want remote access and auth

### Transient databases

Create a database with a lifetime attached so a test run cleans up after itself.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/api
- Details:
  - Set a time to live between 1 and 72 hours at create time
  - Counts against your database quota while it lives, then removes itself

### Programmatic provisioning

Create databases from a script, a CI job, or an agent instead of clicking through the dashboard.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: Lower monthly cap, Solo: yes, Pro: yes, Dedicated: Unmetered on your server
- Docs: https://layerbase.com/docs/api
- Details:
  - A monthly ceiling on API-created databases per plan, so a runaway loop cannot drain an account
  - Databases you create in the dashboard never count against that ceiling

## Lifecycle

Databases sleep when nobody is using them and wake when something connects. Nothing is deleted out from under you.

### Sleep when idle, wake on connect

An idle database hibernates instead of billing you for nothing, and comes back when a client connects.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: Sleeps after 15 min, Solo: Sleeps after 6 h, Pro: Sleeps after 6 h, Dedicated: Your capacity, your call
- Docs: https://layerbase.com/docs/database-lifecycle
- Details:
  - Free databases idle out after 15 minutes, or 30 minutes on the slower-waking MySQL and MariaDB
  - Waking is automatic on connect for most engines; MySQL and MariaDB take longer to come back, so start them first if a cold connect would time out
  - Stop and start a database yourself whenever you want, and a stopped database stays stopped

### Always-on pinning

Pin a database so it never sleeps, funded by the always-on memory pool that comes with your plan.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: no, Solo: 768 MB pool, Pro: 1.5 GB pool, Dedicated: Funded by your server
- Docs: https://layerbase.com/docs/plans/always-on
- Details:
  - The pool is a capacity budget: pin as many databases as it fits
  - Pro can add pool blocks at $10 per month for more room

### Archiving instead of deletion

A free database that has sat unused for weeks is archived rather than destroyed, and warned about first.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: After 14 idle days, Solo: Never archived, Pro: Never archived, Dedicated: Never archived
- Docs: https://layerbase.com/docs/database-lifecycle
- Details:
  - Archiving applies to the Free tier only, after 14 hibernated days (7 for a database never used)
  - Warning emails go out before anything happens, and again as the window closes
  - Upgrading to a paid plan takes a database out of the archive pipeline entirely

### One-click restore from archive

Bring an archived database back with a single button, and the clock resets from there.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/database-lifecycle
- Details:
  - Restore takes about 10 to 30 seconds and returns the same data
  - A database left archived past 90 days has its live resources reclaimed, and its most recent backup is KEPT and stays restorable

### Downgrades lock, they never delete

Drop to a smaller plan and anything over the new limits is locked, not thrown away.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/locked-databases
- Details:
  - A grace window with warning emails before anything locks
  - A locked database can still be downloaded, and unlocks the moment you upgrade or free up room

### Rename, relabel, and update in place

Keep a database tidy over its life without breaking the connection string your app already uses.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Details:
  - Rename the display name, or the real database name, without changing where clients connect
  - Tag a database as production, staging, development, or preview
  - Apply engine image updates yourself when one is available, with a short restart

### Deletion takes a backup first

Every destructive action backs up before it runs, and refuses to proceed if that backup cannot be secured.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Details:
  - Deleting a database requires typing its name, on every plan including Free
  - The pre-teardown backup is kept and remains downloadable

## Backups and recovery

Every destructive action backs up first. If a final backup cannot be secured, the deletion is refused.

### Scheduled backups

Automatic backups on a rolling retention window, with no job for you to configure.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: no, Solo: 7-day retention, Pro: 30-day retention, Dedicated: 30-day retention
- Docs: https://layerbase.com/docs/cloud/backups
- Details:
  - Backups are stored off the server that runs your database
  - Dedicated servers can also choose their own cadence, down to hourly
  - An account-wide view shows the latest backup for every database at once

### Manual backup slots

Take a named snapshot before a risky migration and keep it exactly as long as you want.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: 1 slot, Solo: 3 slots, Pro: 10 slots, Dedicated: 10 slots
- Docs: https://layerbase.com/docs/cloud/backups
- Details:
  - Name and rename a backup so you know what it was taken for
  - Replace the oldest slot when they are all full, with a confirmation first
  - Your last remaining copy of a database can never be deleted

### Download any backup

Pull a backup down to your own machine, including from a locked or archived database.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/backups
- Details:
  - No plan gate: a Free account can always take its data out
  - Works while a database is locked, archived, or offloaded

### Restore from a backup

Roll a database back to any backup you still hold, from the dashboard, in one flow.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/backups
- Details:
  - Restores are exercised on a schedule against real backups, not assumed to work
  - Restore into the same database, or use a backup to seed a new one

### Backup verification

Each backup carries a checksum and a verification state, so you know it is intact before you need it.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/backups

### Backups for branches

Opt a branch into the same backup schedule as the database it came from.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, libSQL, SQLite, DuckDB, TypeDB, ClickHouse, Meilisearch, Qdrant, QuestDB, InfluxDB, Weaviate
- Plans: Free: no, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/branching
- Details:
  - Off by default, because most branches are disposable
  - Turn it on per branch when one is doing real work

### Point-in-time restore

Rewind a database to a moment before the bad migration, not just to the last backup.

- Availability: available
- Engines: PostgreSQL, FerretDB
- Plans: Free: no, Solo: no, Pro: Requires an always-on pin, Dedicated: Requires an always-on pin
- Docs: https://layerbase.com/docs/cloud/point-in-time-restore
- Details:
  - PostgreSQL and FerretDB, on Pro and above
  - The database has to be pinned always-on, since the recovery log needs a running instance

### Export a database

Take a full export of a database at any time, in any state, with no plan gate on it.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/backups

## Branching

Copy-on-write branches of real data across 16 engines, with no extra database slot consumed.

### Database branching

Make a working copy of a real database with its real data, the way you branch code.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, libSQL, SQLite, DuckDB, TypeDB, ClickHouse, Meilisearch, Qdrant, QuestDB, InfluxDB, Weaviate
- Plans: Free: 1 per database, Solo: 3 per database, Pro: 10 per database, Dedicated: 10 per database
- Docs: https://layerbase.com/docs/cloud/branching
- Details:
  - Available on 16 of the 18 Cloud engines
  - A branch does NOT consume one of your plan database slots
  - Each branch gets its own connection string and its own credentials

### Instant copy-on-write branches

Turn on instant branching for a database and new branches share storage instead of copying it.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, libSQL, SQLite, DuckDB, TypeDB, ClickHouse, Meilisearch, Qdrant, QuestDB, InfluxDB, Weaviate
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/branching
- Details:
  - A per-database switch, so you opt in only where you branch often
  - A few engines are addressed by port rather than hostname, and get a new connection string when you enable it

### Reset a branch from its parent

Throw away everything a branch did and pull fresh data down, keeping the same connection details.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, libSQL, SQLite, DuckDB, TypeDB, ClickHouse, Meilisearch, Qdrant, QuestDB, InfluxDB, Weaviate
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/branching
- Details:
  - Host, port, and credentials survive the reset, so nothing has to be reconfigured

### Branch lineage view

See which database a branch came from and what has branched off it, as a tree.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, libSQL, SQLite, DuckDB, TypeDB, ClickHouse, Meilisearch, Qdrant, QuestDB, InfluxDB, Weaviate
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/branching
- Details:
  - Branch badges on the database list so a branch is never mistaken for a parent
  - Deleting a parent offers to take its branches with it, and says so before it does

### Ephemeral branch labels

Mark a branch as preview or development and it sleeps aggressively, because it is meant to be thrown away.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, libSQL, SQLite, DuckDB, TypeDB, ClickHouse, Meilisearch, Qdrant, QuestDB, InfluxDB, Weaviate
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/branching

## Connectivity and security

Stable hostnames, encryption in transit, and access controls you issue and revoke yourself.

### Connect dialog

One dialog with everything needed to connect: the string, the parts, and working code.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/connecting
- Details:
  - Copy-ready snippets for the CLI, Node, Python, and HTTP clients
  - A preview of the exact fields a desktop GUI client asks for
  - Individual host, port, user, password, and database fields, masked until you reveal them

### Pooled connections

Use a pooled endpoint so a serverless function fleet does not exhaust your connection budget.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, SQLite, DuckDB, QuestDB
- Plans: Free: Up to 20 connections, Solo: Uncapped, Pro: Uncapped, Dedicated: Uncapped
- Docs: https://layerbase.com/docs/cloud/connecting
- Details:
  - Pooled and direct endpoints are both issued, and both are shown in the connect dialog
  - Tools that need a real session, like some migration runners, use the direct endpoint

### Encryption in transit and per-customer isolation

Every connection is encrypted, and your databases run in your own container on your own private network.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/connecting
- Details:
  - TLS on every engine endpoint, with end-to-end passthrough on PostgreSQL
  - A container and private network per customer, not a shared multi-tenant instance

### Stable per-database hostnames

Your database is addressed by a hostname that does not change when we move things around underneath it.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/connecting
- Details:
  - Most engines are reached by hostname on a standard port for that engine
  - A few engines are addressed by their own port instead, which the connect dialog spells out

### IP allowlisting

Restrict a database to the addresses you name, on every plan, including Free.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/security/ip-allowlisting
- Details:
  - Per database, managed from its settings, effective immediately
  - A helper script adds the address you are currently connecting from

### Client certificate (mTLS) auth

Require a client certificate to connect, so a leaked password alone is not enough.

- Availability: available
- Engines: PostgreSQL
- Plans: Free: no, Solo: no, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/security/client-certificates
- Details:
  - PostgreSQL only, on Pro and above
  - A certificate authority per database, with one-click rotation
  - Certificates are issued alongside the password, never instead of it

### Per-database API keys

Issue a key scoped to a single database, and rotate it without an outage.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/api
- Details:
  - Shown once at creation, then stored hashed
  - Rotation keeps the old key working for a grace period so deploys can catch up

### Support access grants

Support cannot see your credentials unless you grant access, and the grant expires on its own.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/support
- Details:
  - You choose the window when you open a grant, and can revoke it early
  - Without a live grant, credentials are withheld from staff tooling

### Serverless and edge driver compatibility

Speak to a Layerbase database with the serverless drivers your framework already ships.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/serverless-edge
- Details:
  - An HTTP endpoint for Redis and Valkey that matches the popular REST client
  - Serverless driver compatibility for PostgreSQL and for MySQL and MariaDB
  - A direct TLS endpoint for runtimes that cannot negotiate a database-native handshake

## Query tools

A console built for the engine you actually chose, not a generic SQL box with the wrong verbs.

### SQL console

Write and run SQL against a running database from the browser, with results in a real grid.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, SQLite, libSQL, DuckDB, ClickHouse, TypeDB
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console
- Details:
  - Multi-statement runs, with a confirmation before anything destructive
  - Query formatting and starter queries for the engine you are on

### Time-series console

Query time-series data and see the result as a chart instead of a wall of rows.

- Availability: available
- Engines: QuestDB, InfluxDB
- Plans: Free: no, Solo: no, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console

### Key-value console

Browse keys, inspect values, and run commands against Redis and Valkey without a local client.

- Availability: available
- Engines: Redis, Valkey
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console
- Details:
  - A key browser that pages through the keyspace safely

### Document console

Run document queries against FerretDB with the shell syntax you already know.

- Availability: available
- Engines: FerretDB
- Plans: Free: no, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console

### REST console

Send requests to engines that speak HTTP without leaving the dashboard or building a curl line.

- Availability: available
- Engines: Qdrant, CouchDB, Weaviate
- Plans: Free: CouchDB only, Solo: CouchDB only, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console

### Search explorer

Try searches, tune index settings, and issue scoped keys for a search index from the dashboard.

- Availability: available
- Engines: Meilisearch
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console
- Details:
  - Edit index settings such as searchable and filterable attributes
  - Create scoped keys so a client only sees the indexes you allow

### Ledger console

Create accounts and post transfers against a double-entry ledger through a guided form.

- Availability: available
- Engines: TigerBeetle
- Plans: Free: no, Solo: no, Pro: With a pool block, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console

### Query workspace

The console keeps your place: tabs, history, saved snippets, and keyboard-first navigation.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console
- Details:
  - Multiple query tabs, kept in your browser between visits
  - Recent query history and saved snippets, stored locally to your browser
  - A command palette and keyboard shortcuts for running, formatting, and switching tabs
  - Schema browser and autocompletion for tables and columns on SQL engines
  - A results grid with a row detail panel, and export to CSV, TSV, JSON, JSONL, Markdown, or INSERT statements
  - A hibernated database wakes automatically when you run a query against it

### Import data from the console

Drop a file into the console and load it into a table without installing anything.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/query-console
- Details:
  - CSV, TSV, and SQL uploads, with larger files handled through a direct upload
  - Run a whole SQL file against the database in one go
  - DuckDB can also read JSON, newline-delimited JSON, Parquet, and remote URLs

### HTTP query API

Run a query over plain HTTPS from an edge runtime that cannot open a database socket.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, SQLite, DuckDB, libSQL, ClickHouse, QuestDB, InfluxDB, Qdrant, Meilisearch, Weaviate, CouchDB, TypeDB
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/serverless-edge
- Details:
  - Available on 17 of the 18 Cloud engines
  - Authenticated with a database API key, rate limited per account

### AI query debugging

When a query fails, ask for an explanation and a suggested fix without leaving the console.

- Availability: rolling out
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, SQLite, DuckDB, ClickHouse, Qdrant, Meilisearch, CouchDB, QuestDB, TypeDB, InfluxDB, Weaviate, libSQL
- Plans: Free: no, Solo: no, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/ai-query-debugging
- Details:
  - Reads the failing statement, command, or request and the error the engine returned, and proposes a correction
  - You review and run the suggestion yourself; nothing is applied for you
  - Schema sharing is consent-gated and covers names only: tables and columns, collection names, or sampled key patterns; your rows are never sent
  - In every cloud query console except TigerBeetle's structured ledger form, which has no free-text query to debug

## Teams

Share databases with the people you work with, on one bill, without handing out your password.

### Teams

Put databases in a shared workspace so the people you work with can reach them on one bill.

- Availability: available
- Engines: not engine specific
- Plans: Free: Hold a team, cannot invite, Solo: $3/member/mo, Pro: $3/member/mo, Dedicated: $3/member/mo
- Docs: https://layerbase.com/docs/teams
- Details:
  - One member seat is included; extra seats are billed per member per month
  - Owner and member, with no role hierarchy to configure

### Invite links

Invite a teammate by email and they join through a link that expires on its own.

- Availability: available
- Engines: not engine specific
- Plans: Free: no, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/teams
- Details:
  - Invitations expire after a week if they go unused
  - A notification in the dashboard when an invitation is waiting for you

### Move a database into a team

Hand an existing database over to a team without recreating it or reissuing its connection string.

- Availability: available
- Engines: not engine specific
- Plans: Free: no, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/teams
- Details:
  - Shared databases are labelled so it is obvious whose they are
  - Removing a member removes their access without rotating credentials for everyone else

### Team administration

Rename a team, transfer ownership, or wind one down when a project ends.

- Availability: available
- Engines: not engine specific
- Plans: Free: no, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/teams

## Plans and billing

Flat monthly prices. No per-query, per-hour, or per-gigabyte meter anywhere in the product.

### Flat monthly pricing

One price per month per plan: Free at $0, Solo at $5, Pro at $15. No usage meter anywhere.

- Availability: available
- Engines: not engine specific
- Plans: Free: $0/mo, Solo: $5/mo, Pro: $15/mo, Dedicated: From $35/mo
- Docs: https://layerbase.com/pricing
- Details:
  - Free includes 2 databases and 5 GB, with no card required
  - Solo includes 2 databases and 10 GB
  - Pro includes 10 databases and 25 GB

### Pro trial

Try Pro for 7 days before you commit to it.

- Availability: available
- Engines: not engine specific
- Plans: Free: Eligible, Solo: no, Pro: 7 days, Dedicated: no
- Docs: https://layerbase.com/docs/billing
- Details:
  - A card is required, and one trial per customer
  - End the trial early from the dashboard whenever you want

### Pool blocks

Add capacity to a Pro account in $10 steps instead of jumping to a bigger tier.

- Availability: available
- Engines: not engine specific
- Plans: Free: no, Solo: no, Pro: $10/mo each, Dedicated: Not needed
- Docs: https://layerbase.com/docs/plans/always-on
- Details:
  - Each block adds 1 GB of always-on memory, 1 vCPU, and 25 GB of storage
  - Up to 20 blocks on one account

### Dedicated servers

Buy a private single-tenant server at a flat monthly price and put as many databases on it as it holds.

- Availability: available
- Engines: not engine specific
- Plans: Free: no, Solo: no, Pro: no, Dedicated: From $35/mo
- Docs: https://layerbase.com/docs/dedicated
- Details:
  - Self-serve presets, provisioned in about 15 to 30 minutes
  - Choose which engines are warmed on your own box
  - Prepaid terms are available for a longer commitment
  - Close a server when you are done, after a fit check on what is still running on it

### Bandwidth allowances

Generous rolling allowances rather than a bandwidth meter, so a busy week never produces a surprise invoice.

- Availability: available
- Engines: not engine specific
- Plans: Free: 150 GB/mo, Solo: 375 GB/mo, Pro: 1500 GB/mo, Dedicated: Unmetered
- Docs: https://layerbase.com/acceptable-use
- Details:
  - Rolling 24-hour, 7-day, and 30-day windows, summed across all your databases
  - A modest overage gets a grace window and an email, not a shutdown
  - Dedicated servers are unmetered: the hardware is yours

### Self-serve plan changes

Upgrade, downgrade, cancel, or resume from the dashboard, with the maths shown before you confirm.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/billing
- Details:
  - Switches are prorated, and a preview shows what changes on your account first
  - A billing portal for invoices, cards, and receipts
  - An activity feed of what changed on your subscription and when

### Account credits

Credits on your account are applied to your bill automatically, and shown on the plan page.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/billing

## Integrations

Wire a database into the tools you already deploy with, and let branches follow your git branches.

### Vercel integration

Connect a project and get the database environment variables set for you, per environment.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/integrations/vercel
- Details:
  - Environment variables written and kept in sync, including a pooled and a direct variant
  - Optionally reset the staging database on each deploy, so previews start clean
  - Cancel a queued reset and redeploy without unwiring the integration

### GitHub integration

Install the Layerbase GitHub App so branch activity in your repository can drive your databases.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/integrations/github
- Details:
  - Read-only repository access: Layerbase never writes to your code
  - A guided wizard for picking the repository and the database it maps to

### Per-branch preview databases

Give every git branch its own database branch, created when the branch appears and cleaned up when it goes.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, libSQL, SQLite, DuckDB, TypeDB, ClickHouse, Meilisearch, Qdrant, QuestDB, InfluxDB, Weaviate
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/integrations/github
- Details:
  - Works from either the GitHub App or the Vercel integration
  - Preview environments get their own data instead of sharing one staging database

### Integration health

See at a glance whether a connected project is still wired up, and what the last automation run did.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/integrations/vercel
- Details:
  - Connection status for each linked project
  - Recent automation errors surfaced where you connected the project, with what to fix

### VQueue message queue

Run a hosted message queue on top of a Valkey database, included at no extra charge on every plan.

- Availability: available
- Engines: Valkey
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/vqueue
- Details:
  - Valkey only, and free on every plan including Free
  - Scheduled delivery, retries with backoff, and a dead-letter queue
  - Compatible with a widely used queue client, so existing code often works unchanged

## Developer tools

An API, a CLI, a desktop app, and an agent-readable spec. The desktop app and CLI cover all 21 engines in the suite.

### REST API

Create, list, query, back up, and delete databases over a documented HTTP API.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/api
- Details:
  - An endpoint that reports your plan and how much of your create allowance is left
  - The same operations the dashboard uses, so nothing is dashboard-only

### Account API keys

Hold an account-scoped key for tooling that manages more than one database.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/api
- Details:
  - Account-scoped and database-scoped keys, listed and revocable in one place
  - Shown once when created, then stored hashed

### Layerbase CLI

Manage local and cloud databases from your terminal with a single npm-installed command.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cli
- Details:
  - One install puts two commands on your path, layerbase and the shorter lbase
  - Every local command runs with no account at all; sign in only to reach your cloud databases
  - A drop-in for SpinDB, which continues as the open-source engine underneath: the same commands, flags, and exit codes
  - Log in from the browser once, or set an API key so CI and coding agents authenticate with no browser and no token to expire
  - With a key the CLI talks straight to the REST API, under the same quota and rate limits the dashboard enforces

### Local databases without Docker

Run any of the 21 engines in the suite on your own machine as native processes, with no container runtime and no account.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, MongoDB, FerretDB, CockroachDB, SQLite, DuckDB, ClickHouse, Qdrant, Meilisearch, CouchDB, SurrealDB, QuestDB, TypeDB, InfluxDB, Weaviate, TigerBeetle, libSQL
- Plans: Free: No account needed, Solo: No account needed, Pro: No account needed, Dedicated: No account needed
- Docs: https://layerbase.com/docs/cli
- Details:
  - Real database binaries run as ordinary processes, so there is no daemon to keep alive and no virtual machine overhead
  - Each database gets its own data directory, so two versions of the same engine never collide
  - The same commands on macOS, Linux, and Windows, on ARM and x64
  - Stopping a database keeps its data; only an explicit delete removes it

### Git-driven local branching

Fork a local database copy-on-write and let it follow your git branch, without your connection string ever changing.

- Availability: available
- Engines: not engine specific
- Plans: Free: No account needed, Solo: No account needed, Pro: No account needed, Dedicated: No account needed
- Docs: https://layerbase.com/docs/cli
- Details:
  - Instant and near-zero-space on APFS, Btrfs, XFS with reflinks, and ZFS, with a full-copy fallback everywhere else
  - Check out a git branch and the matching database swaps in while DATABASE_URL stays exactly the same
  - A running source is stopped, snapshotted, and restarted for you, and the fork starts on its own port
  - List, reset, and prune branches, and the JSON output says whether a fork was a reflink or a copy

### Promote a local database to the cloud

Turn a local database, a SQLite or DuckDB file, or a Postgres dump into a hosted database in one command.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cli
- Details:
  - Creates the matching cloud database, loads the data, and prints the connection string and the dashboard link
  - Files are identified by their header rather than their extension, and anything unsupported is refused before a cloud database exists
  - Can write DATABASE_URL into your local env file, rewriting only that line and leaving the rest alone
  - A failed load never deletes anything on its own: it says what happened and prints the retry and delete commands

### Password-safe connect and a scripting contract

Open a client against a database without the password ever becoming a command-line argument.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cli
- Details:
  - Credentials reach the client through an environment variable or a private temporary file that is deleted on exit, so nothing lands in shell history, in the process list, or in scrollback
  - JSON output on the commands scripts read, so a pipeline never has to parse text meant for a human
  - Documented exit codes for auth failure, a suspended account, a capacity conflict, and a quota limit
  - Anything that mutates refuses to run non-interactively without an explicit confirmation flag

### Link and pull external databases

Manage a database you host somewhere else through the same commands, and pull a copy of it down to your machine.

- Availability: available
- Engines: not engine specific
- Plans: Free: No account needed, Solo: No account needed, Pro: No account needed, Dedicated: No account needed
- Docs: https://layerbase.com/docs/cli
- Details:
  - Auto-detects Neon, Supabase, PlanetScale, Upstash, Railway, and Aiven from the connection string you paste in
  - A pull takes an automatic backup before it replaces anything
  - Pull from a URL or from an environment variable, rename on the way in, or do a dry run first
  - A parallel fast path for large PostgreSQL pulls, with the option to skip bulk tables

### Docker export

Package a local database for a container platform, even though running it never needed one.

- Availability: available
- Engines: not engine specific
- Plans: Free: No account needed, Solo: No account needed, Pro: No account needed, Dedicated: No account needed
- Docs: https://layerbase.com/docs/cli
- Details:
  - Generates a Dockerfile, a compose file, an entrypoint script, TLS certificates, and credentials
  - Ready to build and run anywhere containers run, with no further hand-editing

### Desktop app

Run and manage databases on your own machine, across all 21 engines in the suite.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, Redis, Valkey, MongoDB, FerretDB, CockroachDB, SQLite, DuckDB, ClickHouse, Qdrant, Meilisearch, CouchDB, SurrealDB, QuestDB, TypeDB, InfluxDB, Weaviate, TigerBeetle, libSQL
- Plans: Free: Free for personal use, Solo: Free for personal use, Pro: Free for personal use, Dedicated: Free for personal use
- Docs: https://layerbase.com/docs/desktop
- Details:
  - Free for personal use on macOS, Windows, and Linux
  - macOS: a universal build for Intel and Apple Silicon, Developer ID signed and notarized, so it opens with no warning and no workaround
  - Windows: fully working, though the builds are not yet code-signed, so SmartScreen may warn on first launch (choose More info, then Run anyway)
  - Linux: .deb and .rpm packages
  - Includes engines that licensing keeps out of Cloud

### Agent-readable product spec

Machine-readable manifests so a coding agent can use Layerbase correctly without you pasting docs.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/agents
- Details:
  - A skill file and an agent manifest generated from the live product, not written by hand
  - A curated site map for agents at /llms.txt and its full expansion

### Auth add-on

Scaffold authentication tables and wiring code against your own SQL database instead of renting a login service.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, SQLite, libSQL
- Plans: Free: Not on MySQL, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/auth
- Details:
  - A setup wizard that writes the schema and hands you the framework code
  - Copy-ready snippets for several popular auth libraries and frameworks
  - Social sign-in setup guidance for the providers you want to support
  - This scaffolds auth in YOUR database; it is not a hosted login service

### Auth user console

Browse and manage the user rows your auth library created, from the dashboard.

- Availability: available
- Engines: PostgreSQL, MySQL, MariaDB, libSQL
- Plans: Free: Not on MySQL, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/auth
- Details:
  - How much you can do depends on the auth library whose schema is in the database
  - A dedicated Auth section that lists every auth-enabled database in one place

### Per-engine connection guides

A written guide for connecting to each engine, with the driver setup that engine actually needs.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/cloud/connecting

## Usage and status

See what a database is using before it becomes a problem, and get told when it is close to a limit.

### Account usage dashboard

One page showing storage, memory, bandwidth, and database count against your plan.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/billing

### Per-database usage

See what one database is using, and how much of the always-on pool it is holding.

- Availability: available
- Engines: all 18 cloud engines
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/plans/always-on
- Details:
  - A pool meter showing what is pinned and what room is left
  - Live status refresh, so a waking database updates without a page reload

### Usage warnings

Get told in the dashboard and by email as you approach a plan limit, before anything is enforced.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/database-lifecycle
- Details:
  - Banners for storage, memory, and bandwidth pressure
  - Lifecycle emails ahead of archiving, offloading, or locking anything

### Database list and overview

Sort, filter, and switch views over your databases, with an overview of what needs attention.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Details:
  - Card and table views, with search across names and engines
  - A home overview summarising counts, state, and anything that needs a decision

### Status page

A public status page for checking whether a problem is yours or ours.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/status

## Your account

Sign in the way you like, get help from a human, and leave with your data whenever you want.

### Sign in with Google or GitHub

Sign in with an existing identity provider, with no separate password to manage.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Details:
  - Both providers resolve to one account when they share an email address

### Account settings

Change the email on your account, pick a theme, and manage what you hear from us.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Details:
  - Email changes carry through to your cloud account, so nothing forks
  - Light and dark themes across the dashboard and the site

### Delete your account

Close your account from the dashboard, with a full erasure option if you want everything gone.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/docs/account-deletion
- Details:
  - A standard delete keeps your backups so support can reinstate the account if you change your mind
  - A full erasure removes retained copies as well, and is confirmed explicitly

### Product notifications

Targeted notices in the dashboard about the things that affect your plan and your engines.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes

### In-app bug reports

Report a problem from the page you are on, and the report carries the context we need with it.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/support

### Human support

Ask a question and get an answer from a person, alongside a searchable FAQ for the routine ones.

- Availability: available
- Engines: not engine specific
- Plans: Free: yes, Solo: yes, Pro: yes, Dedicated: yes
- Docs: https://layerbase.com/support

## Related agent surfaces

- Capability document (live prices, limits, engines): https://layerbase.com/agents.md
- Downloadable agent skill: https://layerbase.com/skill.md
- Curated site map: https://layerbase.com/llms.txt