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.
/products/_findBody
Response200 OK · 7ms
Where to run it
Cloud, desktop, or self-host
One database, three places it can live. Pick the speed you want and move between them when you outgrow it.
Branching, on request
Database branching is live on 9 engines today, and the same copy-on-write mechanism spans the whole fleet. Want it on CouchDB? Reach out and we will look at switching it on for your account.
Request branchingWhat you get
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.
TLS by default
All connections encrypted. No setup required.
Always-on connections
Pin a database to your always-on pool to prevent hibernation.
Scale to zero
Hibernates when idle. Wakes on the next connection.
Connection pooling
Pooled endpoint for serverless and edge workloads.
Direct connections
Bypass the pooler for migrations and replication.
Native HTTPS endpoint
Engines whose own wire protocol speaks HTTPS. Every database, including this one, is also queryable over the platform's HTTPS query API and web console.
Serverless driver
Drop-in HTTP driver for edge runtimes (Upstash REST, PlanetScale, or the engine-native client).
IP whitelisting
Restrict access to specific IPs or CIDR ranges.
Automatic backups
Scheduled dumps and volume snapshots with one-click restore on paid plans. Free tier includes a manual backup slot.
Why Layerbase
Predictable pricing, no cloud setup
CouchDB on Layerbase Cloud is priced the same way as every other engine: a flat monthly plan with nothing metered behind it.
A fixed monthly price
Plans are flat: Free at $0, then $5/mo Solo and $15/mo Pro. No per-hour compute meter, no per-database line items, and no bill that changes shape when your traffic does.
No bandwidth charges
Reads and writes are not metered. There are no ingress or egress fees, so moving data in and out of your database never adds to the bill.
No cloud account to wire up
You do not need an AWS, GCP, or Azure account. Sign up, create a database, and connect. Layerbase runs the infrastructure, so there is no cloud provider to configure or pay separately.
Side by side
Hosted CouchDB, compared
There is no other self-serve managed Apache CouchDB anywhere. IBM Cloudant is a CouchDB-derived fork, and the remaining CouchDB hosting options are quote-only. Layerbase runs real Apache CouchDB, self-serve, on the Pro plan at $15/mo flat.
Competitor facts as of July 2026, from public pricing pages.
Quick start
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
curl "https://admin:password@your-host.cloud.layerbase.dev/"
More on CouchDB
All articles- June 14, 2026
Branching with any database
Neon branches Postgres. PlanetScale branches MySQL. Layerbase branches all of them, because branching happens at the filesystem, not inside the engine. Here is how it works.
Read - May 18, 2026
IBM Cloudant deprecations in 2025 and 2026: database caps, QuickJS, and removed features
A complete, dated rundown of what IBM Cloudant has changed, deprecated, or removed in the last 18 months, including the new 20-database Lite-plan cap, the SpiderMonkey to QuickJS cutover on October 6, 2026, and the removed CouchApp design-doc handlers. With migration paths if any of these break your app.
Read - May 18, 2026
IBM Cloudant vs Layerbase Cloud: managed CouchDB compared in 2026
A direct head-to-head between IBM Cloudant and Layerbase Cloud for managed Apache CouchDB hosting. Compares entry pricing, database-count caps, the billing model, JavaScript engine, migration path, region coverage, and operational ergonomics, with a recommendation for each common workload.
Read - May 18, 2026
Migrating from IBM Cloudant to managed Apache CouchDB: a zero-downtime guide
Step-by-step migration from IBM Cloudant to a managed Apache CouchDB on Layerbase Cloud, with continuous replication for zero downtime, verification scripts, rollback plan, and notes on what does and does not transfer (design docs, Mango indexes, Cloudant Search, IAM keys, attachments).
Read - May 18, 2026
Serverless CouchDB in 2026: scale-to-zero managed Apache CouchDB
What "serverless CouchDB" actually means in 2026, why the category is small (one long-running hosted option, IBM Cloudant, plus flat-rate managed CouchDB on Layerbase Cloud), and how to ship an offline-first or document-store app without managing the database yourself.
Read
FAQ
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.