Serverless CouchDB

Document storage with the HTTP API you already know, multi-master replication, and the same client libraries you've always used. Cloud or self-host.

REST API Console
CouchDB
POST/collections/products/points/search

Body

{
"vector": [0.21, 0.07, ...],
"limit": 5
}

Response200 OK · 6ms

{
"result": [
{ id: 412, score: 0.94 },
{ id: 287, score: 0.88 }
]
}

Production features, free tier included

Every CouchDB database ships with the same primitives: TLS, web console, hibernation, and a real dashboard. No tiered features hidden behind a sales call.

Web IDE

Query console in the dashboard, no extra client to install.

Included

TLS by default

All connections encrypted. No setup required.

Included

Always-on connections

Optional keep-alive add-on prevents hibernation.

Included

Scale to zero

Hibernates when idle. Wakes on the next connection.

Included

Connection pooling

Pooled endpoint for serverless and edge workloads.

Not available

Direct connections

Bypass the pooler for migrations and replication.

Included

HTTPS access

HTTP-native engines reachable over port 443.

Included

Serverless driver

Upstash REST or PlanetScale serverless drivers supported.

Not available

IP whitelisting

Restrict access to specific IPs or CIDR ranges.

Included

Automatic backups

Scheduled point-in-time backups with one-click restore.

Included

Connect with any CouchDB client

Offline-first apps that sync via PouchDB, multi-master document workloads, and apps that prefer HTTP-native storage.

  • Sync state between mobile and desktop apps via PouchDB to a hosted CouchDB
  • HTTP-native document storage for serverless and edge runtimes
  • Self-host with SpinDB when on-premise replication is required
  • Local-first apps that bring their CouchDB to the cloud without code changes
  • Long-running document workloads with periodic compaction
bashCouchDB
curl "https://admin:password@your-host.cloud.layerbase.dev/"

Common CouchDB questions

Will PouchDB sync to hosted CouchDB?+

Yes. The endpoint speaks the standard CouchDB HTTP API, so PouchDB syncs to it without configuration changes other than the URL.

TLS and authentication?+

HTTPS by default. The dashboard manages admin credentials and provides per-database keys for app-level auth.

Can I use Fauxton?+

Yes for direct administration via the REST API. The Layerbase dashboard provides a console for everyday use; Fauxton-style operations work against the same endpoint.

Replication?+

CouchDB replication targets the standard /replicate API. Configure source and target URLs through the dashboard or your tooling.

Can I run CouchDB locally?+

Yes. SpinDB and Layerbase Desktop both manage local CouchDB versions with the same UI.