An open-source NoSQL document database with an HTTP/JSON API, built for reliability and for multi-primary sync that scales from large clusters down to mobile and browser clients. Any CouchDB database, on a server or a device, can replicate with any other over the documented CouchDB Replication Protocol, which synchronises JSON documents between two peers over HTTP/1.1 using the public REST API and the project's multi-version concurrency control (MVCC) model; conflicting edits are detected through revision trees rather than merged automatically. CouchDB is the reference implementation of that protocol, which PouchDB and other tools reuse. It is a project of the Apache Software Foundation .
LicenciaPermissive (Apache-2.0). https://github.com/apache/couchdb (Erlang, with C, C++ and JavaScript components; Fauxton web console in a separate repository)
Estado de Desarrollo 🟢 Activo
PropietarioApache Software Foundation (top-level project: Apache CouchDB PMC)
Órgano de GobiernoApache CouchDB Project Management Committee at the Apache Software Foundation
PaísUnited States (the Apache Software Foundation is a US charity; the project's committers are international)
Año de Inicio 2008
StackErlang/OTP core, with C, C++ and JavaScript components; HTTP/JSON REST API; Mango queries and map/reduce views; clustering in the 3.x series; packages for Windows, macOS, Debian/Ubuntu and RHEL/CentOS
FinanciamientoASF project supported by volunteer and employer-sponsored committers and ASF sponsorship; no project-level funding stated
Última Investigación 29 oct 2026
Vista de topología
Esta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.
Almacenamiento local-first Portabilidad de datos Autoalojable
Protocolo de Datos Descentralizado Atributos
OrígenesA reliable, always-available document database that can be replicated between servers and, increasingly, mobile and browser clients, with a plain HTTP/JSON interface any language can use
Base de DatosCouchDB: this entry is the database. A document store with MVCC revision trees and, in the 3.x series, clustering (the documentation has a Cluster Management guide)
Lenguaje de ConsultaHTTP/JSON API; Mango selector queries and map/reduce views (the documentation has a Query Server and API reference)
Formatos de DatosJSON documents with revision identifiers and binary attachments; JSON over HTTP
Edición Colaborativa en VivoPartial: documents replicate between peers and conflicting edits are surfaced as revision conflicts for the application or the deterministic winner rule to resolve; there is no automatic character-level merge
Edición de Texto Enriquecido Not stated by the project.
Soporte MóvilThrough sync: the home page says CouchDB scales down to mobile; PouchDB and other clients provide the on-device database
Soporte WebYes: the Fauxton web console and an HTTP/JSON API usable directly from browsers
Aplicaciones NativasServer packages for Windows, macOS and Linux; no native client library of its own
TérminosFree and open source (Apache-2.0)
Fondos Not stated by the project.
Basado EnIts own MVCC and replication model; the replication protocol is the shared standard that PouchDB and other tools implement
Arquitectura P2PPeer-to-peer replication between servers and clients: any two CouchDB databases (or compatible stores) replicate with each other over HTTP, in either direction or both, without a coordinator; the project presents this as multi-primary sync. It is not an overlay network, and discovery is manual
Red de SuperposiciónNone: replication endpoints are addressed by URL; the cluster mode is a data-centre feature, not an overlay
Direccionamiento por ContenidoNo: documents are addressed by identifier and revision (revision ids are hashes of content), not by content hash
Local-FirstEnabling: the replication model underpins local-first clients such as PouchDB; the server itself is a conventional database that can run anywhere, including on a user's own hardware
Cifrado de Extremo a Extremo (E2EE)No: the database stores documents as submitted; transport security is TLS and encryption at rest is left to the platform
Biblioteca de CRDTsNo: conflicts are tracked with revision trees rather than CRDTs
Tolerancia a Fallos BizantinosNo: replication trusts the authenticated peer; the project designs for crash and partition tolerance, not malicious replicas
FirmaN/A: documents are not signed; authentication is cookie, basic or proxy-based on the server
PermisosServer-side: per-database admin and member roles with validate_doc_update functions; no end-to-end document permissions
Compatibilidad con la Web SemánticaN/A: JSON document store with no RDF layer
Contrato InteligenteN/A: no ledger or contract component
Posición en la Pila del ProtocoloApplication-layer: HTTP/1.1 REST API and replication protocol
Incorporación de Activos/ValorNone: no token or value-transfer mechanism
Madurez del Protocolo / EstandarizaciónMature: the CouchDB Replication Protocol is written down as a normative specification using RFC 2119 language and is implemented by several independent projects, though it is an ASF project specification rather than an IETF or W3C standard
Relaciones
Cómo se conecta esta herramienta con otras herramientas y organizaciones, según relaciones revisadas por el responsable de datos de OpenHaven. Describen cómo se conectan los proyectos, no su calidad.