Layerbase: 18 databases
one cloud
no meters
Run Postgres, MySQL, Redis, SQLite, FerretDB, and more. Branch for isolated previews. Always-on production from $5/month. No usage meters.
8 engines free. No card required.
Connection
postgresql://layerbase:•••••@postgresql-prod.cloud.layerbase.dev:5432Used in production by the team building it.
Branch your data like you branch your code.
Create an isolated, writable copy for previews, migration rehearsals, or experiments. Works across 16 engines, including Postgres, MySQL, and MongoDB-compatible FerretDB.
accounts-prod
PostgreSQL
2 branches
orders-prod
MySQL
2 branches
catalog-main
FerretDBMongoDB-compatible
1 branch
Give your agent a database to work with.
With the CLI installed and authenticated, your agent can create Postgres and create an isolated preview for your next change.
Set up your agentlbase cloud create accounts --engine postgresql
lbase cloud branch accounts accounts-previewAvailable on PostgreSQL, MySQL, MariaDB, Redis, Valkey, FerretDB, libSQL, SQLite, DuckDB, TypeDB, ClickHouse, Meilisearch, Qdrant, QuestDB, InfluxDB, and Weaviate. See how branching works.
The database your app needs.
Choose an engine for your project, or combine SQL, documents, vectors, and time-series data on one platform.
QuestDB, CouchDB, and FerretDB run self-serve and scale to zero, and TigerBeetle is in alpha and coming to cloud plans. All four are hard to find managed anywhere else.
Migrate
Now accepting database refugees.
Paste a connection string or API key. Layerbase provisions your destination and copies the data in one read-only pass.
Your source stays untouched. Keep your app and integrations pointed at it until you’re ready to switch.
Find your migration pathChoose your source
We discover the database for you.
Paste once
postgresql://user:••••@source.example/appOld database untouched
Read once
New database ready
Also migrate from your own Postgres, MySQL, MariaDB, Redis, or Valkey database. Start with a connection string.
More ways to work with your data.
Always there when you connect.
Free databases sleep when idle and wake on connection. Paid plans add always-on capacity.
Query over HTTPS from anywhere.
Use compatible Neon, Upstash, Vercel KV, or PlanetScale drivers, or native HTTP APIs, from serverless and edge runtimes.
psql, for things that aren't Postgres.
Use Postgres clients with SQLite, DuckDB, and QuestDB, or Mongo drivers with Apache-licensed FerretDB.
One flat monthly bill.
No per-query, request, or bandwidth charges.
6 Web IDEs, matched to the data.
Explore SQL, document, key-value, REST, graph, and ledger data from the browser. Included with every database.
When a query fails, ask the console to explain it and propose a fix.
Tables
- users
- events
- orders
- sessions
| id | name | created_at |
|---|---|---|
| 1247 | signup | 2026-03-12 14:21 |
| 1246 | purchase | 2026-03-12 14:08 |
| 1245 | login | 2026-03-12 13:55 |
| 1244 | signup | 2026-03-12 13:44 |
| 1243 | purchase | 2026-03-12 13:30 |
SQL Web IDE: Postgres, MySQL, ClickHouse, DuckDB, and more, syntax-highlighted and ready.
The multi-database tax.
Postgres, cache, vector search, and text search usually mean four vendors. On Layerbase, they share one plan.
A typical production stack, priced separately (July 2026)
Postgres on Neon
metered by compute-hours
Redis on Upstash
metered per command
Vector search on Pinecone
minimum
Text search on Algolia
metered per search - ours is Meilisearch, open source, with a real console
On Layerbase
The same four databases are 4 of your 10 on Pro.
One bill. Zero meters.
Competitor pricing as of July 2026, from public pricing pages.
More engines, one operating model.
Compare engine choice, workflows, and included features.
Compare Layerbase against
| Feature | Supabase | Neon | PlanetScale | Railway |   Layerbase |
|---|---|---|---|---|---|
| Database engines | 1 (Postgres) | 1 (Postgres) | 2 (MySQL, Postgres) | Templates, unmanaged | 18 managed |
| Database branching | Postgres | Postgres | MySQL, Postgres | Not offered | 16 engines |
| HTTP query API | PostgREST | Postgres | Serverless driver | No | 17 engines |
| Client cert (mTLS) auth | No | No | No | No | Pro, per-database CA |
| IP allowlist scope | Project, not its APIs | Project, Scale plan | Per database | Not offered | Per database, every plan |
| Free tier | 500 MB, pauses after 1 week | 0.5 GB, scale-to-zero | None since April 2024 | $1/mo of usage credit | 5 GB, wakes on connect |
| Pricing model | $25 base + meters | Usage meters | From $5 + usage | Metered per second | $0 / $5 / $15, no meters |
| Self-hostable companion | Full platform, Docker | Source only | Not offered | Not offered | CLI + Desktop |
Database engines
- Supabase
- 1 (Postgres)
- Neon
- 1 (Postgres)
- PlanetScale
- 2 (MySQL, Postgres)
- Railway
- Templates, unmanaged
- Layerbase
- 18 managed
Database branching
- Supabase
- Postgres
- Neon
- Postgres
- PlanetScale
- MySQL, Postgres
- Railway
- Not offered
- Layerbase
- 16 engines
HTTP query API
- Supabase
- PostgREST
- Neon
- Postgres
- PlanetScale
- Serverless driver
- Railway
- No
- Layerbase
- 17 engines
Client cert (mTLS) auth
- Supabase
- No
- Neon
- No
- PlanetScale
- No
- Railway
- No
- Layerbase
- Pro, per-database CA
IP allowlist scope
- Supabase
- Project, not its APIs
- Neon
- Project, Scale plan
- PlanetScale
- Per database
- Railway
- Not offered
- Layerbase
- Per database, every plan
Free tier
- Supabase
- 500 MB, pauses after 1 week
- Neon
- 0.5 GB, scale-to-zero
- PlanetScale
- None since April 2024
- Railway
- $1/mo of usage credit
- Layerbase
- 5 GB, wakes on connect
Pricing model
- Supabase
- $25 base + meters
- Neon
- Usage meters
- PlanetScale
- From $5 + usage
- Railway
- Metered per second
- Layerbase
- $0 / $5 / $15, no meters
Self-hostable companion
- Supabase
- Full platform, Docker
- Neon
- Source only
- PlanetScale
- Not offered
- Railway
- Not offered
- Layerbase
- CLI + Desktop
Capabilities verified September 7, 2026. Vendor sources: Supabase, Neon, PlanetScale, Railway, Turso, Upstash, Render, MongoDB Atlas.
One engine across every environment.
Preview, ship, or work locally without swapping database products.
Production without a product swap.
Add always-on capacity and backups. Keep your engine and connection model.
TLS, generated credentials, and IP allowlists included on every tier.
Security
Read the full security overview, including what we do not have yet, or jump to the IP allowlisting and client certificate guides.
FAQ
Questions, answered.
What is Layerbase?
Layerbase Cloud is the easy way to run a database in production: 18 engines, a free tier with no credit card, and flat monthly plans. Layerbase Desktop brings the full engine suite and admin UI to your laptop as a local runner and multi-database IDE, and the Layerbase CLI runs the same engine runtime from the terminal with native binaries, no containers required.
See plans and pricingIs there really a free tier?
Yes. PostgreSQL, MariaDB, SQLite, DuckDB, libSQL, Valkey, Redis, and TypeDB are free at the base configuration: cloud-hosted, real connection string, HTTPS endpoint. The free tier includes 2 databases, with instant branching on one, on a single signup, and it does not expire.
See what free includesHow does billing work?
Free needs no credit card. Solo is $5/mo for 2 Standard databases, one of which you pin always-on. Pro is $15/mo for up to 10 databases, every engine, and an allocatable always-on pool. Dedicated starts at $35/mo per server. Every price is flat, with no usage meters: the price is a number, not a formula.
See full pricingIs Layerbase serverless?
Yes, in the way that changes your infrastructure: there is no server to size or provision, idle Standard-class databases scale to zero, and the next connection wakes them in about one to five seconds. The few engines that are better off awake run always-on from your pool instead. It is not serverless in the billing sense, and that part is deliberate. There are no compute units, request counts, or per-row charges on any plan.
How serverless works hereWhat does Layerbase Cloud replace?
Neon, PlanetScale, Supabase, Railway, Render, Aiven, Upstash, DigitalOcean Managed Databases, Turso, Vercel KV, Algolia (we host Meilisearch, the open-source alternative, with a real console), and MongoDB Atlas (with branching, which Atlas does not offer, via FerretDB). More engines than any single one of them.
Find your migration pathWhen should I NOT use Layerbase Cloud?
High availability and multi-region replication are on the roadmap, not shipped. If your workload requires synchronous multi-region writes today, use the upstream cloud for that engine. Everything else (single-region production, dev/staging, side projects) we are ready for.