Ross ROSS = Recommend OSS · open-source software intelligence for agents

apache/couchdb

Seamless multi-primary syncing database with an intuitive HTTP/JSON API, designed for reliability observed · 2026-08-28

github.com/apache/couchdb · homepage · Erlang · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

77/100

  • Activity 99
  • Release rhythm 35
  • Longevity 100

Flags: no_releases

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 6314
  • days_rel: n/a
  • days_push: 8
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

6942 stars · 1076 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Apache CouchDB is an open-source NoSQL document database written in Erlang that stores data as JSON documents and exposes an intuitive HTTP/JSON API. Its defining feature is seamless multi-primary (master-master) replication, enabling offline-first apps and clustered deployments that scale from servers to mobile devices.

Use cases

  • sync data between multiple servers with multi-master replication
  • build offline-first mobile and web apps that sync when back online
  • store and query JSON documents over a simple HTTP REST API
  • run a clustered database across many nodes for reliability
  • self-host a document database on my own servers or cloud provider
  • store binary attachments alongside JSON documents
  • query documents with MapReduce views

When to choose

  • you need multi-primary replication or offline-first sync out of the box
  • you want a database that speaks HTTP/JSON natively with no driver layer
  • you need a self-hosted, Apache-licensed document store with proven reliability
  • you want to scale from a single node to a cluster without changing your data model

When to avoid

  • you need complex ad-hoc joins or relational constraints - use a SQL database
  • you require heavy analytical or aggregation workloads - use a columnar or OLAP engine
  • you depend on an ecosystem of ORMs and tooling built around SQL or MongoDB
  • you need strict ACID transactions across multiple documents

Facets

service · maturity stable

database http-server search-engine serialization databases backend web-development self-hosted microservices windows cross-platform self-hosted cloud document-database multi-master-replication offline-first -api mapreduce erlang nosql apache-project linux macos web-server docker

4 sources

Member repositories

RepositoryRoleHealth v2
apache/couchdbmain77

For agents

markdown · JSON · MCP: product_card(name="apache/couchdb")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem