Cloud Platform
21 database engines. One platform.
The only managed database platform with scale-to-zero across every engine, an HTTP query API for edge platforms, and per-database firewalls. PostgreSQL, Redis, MongoDB, ClickHouse, DuckDB, and 16 more - all with the same API, dashboard, and connection experience.
Early Access Program
Layerbase Cloud is in public beta. Core infrastructure - scale-to-zero, pooling, HTTP queries, backups, and firewalls - is production-ready and battle-tested across all 21 engines. We are actively building toward GA with additional features like built-in auth, branching, and read replicas on the roadmap. Early adopters get direct access to the founding team and influence over what ships next.
Compare
How Layerbase stacks up
Every managed database platform specializes in one engine. Layerbase runs 21 - with features the specialists don't offer.
| Feature | Neon | Supabase | PlanetScale | Upstash | Layerbase |
|---|---|---|---|---|---|
| Database engines | 1 (PostgreSQL) | 1 (PostgreSQL) | 1 (MySQL) | 2 (Redis, Kafka) | 21 |
| Scale-to-zero | Yes | Pause only | Yes | Yes | Yes (all engines) |
| HTTP query API | No | PostgREST | No | Yes (Redis) | 20 engines, ~5ms |
| Transparent TCP wake | PG only | No | MySQL only | N/A | PG family |
| Connection pooling | PgBouncer | PgBouncer | Vitess | N/A | PgBouncer + ProxySQL |
| Per-database firewall | No | No | No | No | IP allowlist |
| Backup & restore | Point-in-time | Daily | Automated | Daily | Scheduled + manual |
| Self-hostable companion | No | Yes (complex) | No | No | SpinDB CLI + Desktop |
| Built-in auth | No | Yes | No | No | Roadmap |
Platform
Built for modern infrastructure
Every feature works across all 21 engines. No engine-specific caveats, no partial support.
HTTP query API for edge
Query any of 20 supported engines over HTTPS with ~5ms overhead. Works on Cloudflare Workers, Vercel Edge Functions, and any platform that speaks HTTP but not raw TCP or TLS.
Scale-to-zero, every engine
Idle databases hibernate automatically. PostgreSQL wakes transparently on TCP connect. All engines wake on HTTP query or explicit /wake call. Cold starts from 1 to 5 seconds for most engines.
Per-database firewall
Allowlist specific IP addresses per database. Block all traffic except approved sources. Essential for engines like TigerBeetle that lack built-in authentication.
TLS on every connection
SNI-routed engines share canonical ports (5432, 27017, 6379, 443) with wildcard certificates. Dedicated-port engines get native TLS or HAProxy termination. No unencrypted connections.
Container isolation
Each user gets their own Docker container on an isolated bridge network. Databases cannot reach each other. Unique credentials per database, generated with URL-safe characters.
Connection pooling
PgBouncer for PostgreSQL-family engines (7 engines). ProxySQL for MySQL and MariaDB. Both pooled and direct connection strings provided so you choose the right path.
Drop-in Compatible
Upstash and Vercel KV compatible
Every Redis and Valkey database includes a built-in REST API that is fully compatible with the Upstash Redis protocol. Use @upstash/redis, @vercel/kv, or plain HTTP as drop-in replacements with zero code changes.
Both connection methods reach the same database: the REST API for serverless and edge environments, and the standard Redis wire protocol for traditional clients like ioredis and redis-cli.
// @upstash/redis - zero code changes
import { Redis } from '@upstash/redis'
const redis = new Redis({
url: process.env.UPSTASH_REDIS_REST_URL,
token: process.env.UPSTASH_REDIS_REST_TOKEN,
}
// @vercel/kv - also works
import { kv } from '@vercel/kv'
await kv.set('key', 'value')
// @planetscale/database - drop-in
import { connect } from '@planetscale/database'
const conn = connect({
host: process.env.DATABASE_HOST,
username: process.env.DATABASE_USERNAME,
password: process.env.DATABASE_PASSWORD,
}
// Drizzle ORM - also works
import { drizzle } from 'drizzle-orm/planetscale-serverless'
Drop-in Compatible
PlanetScale compatible
Every MySQL and MariaDB database includes a built-in HTTP API compatible with PlanetScale's serverless driver. Use @planetscale/database, drizzle-orm/planetscale-serverless, or plain HTTP as drop-in replacements with zero code changes.
Ideal for Vercel Edge Functions, Cloudflare Workers, and serverless environments where persistent TCP connections aren't practical. Both the HTTP API and the standard MySQL wire protocol reach the same database.
PostgreSQL Protocol
5 engines, one familiar protocol
These engines all speak the PostgreSQL wire protocol. Connect with psql, any SQL IDE, or your existing PG client libraries. PgBouncer pooling and transparent TCP wake included.
PostgreSQL
The original
Versions 15-18
CockroachDB
Distributed SQL
PG-compatible
SQLite
Embedded SQL via PG proxy
~1s cold start
DuckDB
Analytics via PG proxy
~1s cold start
QuestDB
Time-series SQL
PG-compatible
All PG-family engines connect on port 5432 via SNI routing with TLS. No port in the connection string, no firewall rules to configure. Works with every PostgreSQL client, ORM, and migration tool.
Security
Secure by default, not by upgrade
Every database on every plan gets the full security stack. No premium tier required for encryption or isolation.
TLS on every connection
All 21 engines use encrypted connections. SNI-routed engines share canonical ports (5432, 27017, 6379, 443) with wildcard certificates. Dedicated-port engines get native TLS or HAProxy termination. There is no way to connect without encryption.
Per-database IP firewall
Allowlist specific IP addresses per database. Block all traffic except approved sources. Essential for engines like TigerBeetle that lack built-in authentication, and a strong defense-in-depth layer for everything else.
Container isolation
Each user gets their own Docker container running on an isolated bridge network. Databases cannot reach each other across containers. No shared processes, no shared memory, no noisy-neighbor access.
Credential isolation
Every database gets a unique username and password generated with URL-safe characters. No shared credentials between databases. Passwords are never stored in plaintext in the control plane.
Encrypted backups
All backups are stored on Cloudflare R2 with server-side encryption. Scheduled backups run every 12 hours for running databases. Manual backups and point-in-time downloads available via the dashboard and API.
HTTPS query API
The HTTP query API runs over HTTPS exclusively. Bearer token authentication on every request. No API keys in URLs, no unencrypted query traffic. Works on edge runtimes that block raw TCP.
Exclusive
Serverless databases you can't get anywhere else
These engines have no managed serverless offering from any other provider. Layerbase is the only platform that runs them with scale-to-zero, HTTP queries, backups, and TLS.
FerretDB
MongoDB-compatible on PostgreSQL
Cold start: ~5s
TypeDB
Graph database
Cold start: ~5s
TigerBeetle
Financial ledger
Cold start: ~2s
CouchDB
Document database
Cold start: ~3s
Valkey
Redis-compatible key-value
Cold start: ~1s
QuestDB
Time-series database
Cold start: ~30s
DuckDB
In-process analytics
Cold start: ~1s
SurrealDB
Multi-model database
Cold start: ~2s
Edge-Compatible
Query from anywhere over HTTPS
Cloudflare Workers, Vercel Edge Functions, Deno Deploy - many edge runtimes don't support raw TCP or TLS connections. Layerbase's HTTP query API gives you direct database access over standard HTTPS with ~5ms overhead.
19 of 21 engines are queryable over HTTP. Send SQL, MongoDB queries, Redis commands, REST calls, or SurrealQL - the API normalizes the response format across all engines.
Try It Now// From a Cloudflare Worker
const res = await fetch(url, {
method: 'POST',
headers: { 'Authorization': `Bearer ${key}` },
body: JSON.stringify({
query: 'SELECT NOW()'
})
}
)
// ~5ms overhead, any edge runtime
Layerbase Desktop
macOS, Windows, Linux
Desktop
A cross-platform companion app
Layerbase Desktop puts every supported database engine on your local machine with a native GUI. Install databases, manage versions, start and stop instances - no Docker, no terminal required.
Develop locally with the same engines you deploy to Layerbase Cloud. Move from laptop to production with identical database configurations and zero compatibility surprises.
Download DesktopWhat's Next
Growing fast, building in the open
The core platform - 21 engines, scale-to-zero, HTTP queries, pooling, backups, firewalls - is stable and production-ready. Here's what's coming next:
Start building with any database
Pick an engine, get a connection string in seconds. No infrastructure to configure, no Docker to install, no cold starts to worry about.