← ← Back to all products
Apache CouchDB
Active
DatabasesLatest Version: 3.5.2Latest Release: May 14, 2026
Apache CouchDB is a document-oriented NoSQL database with an HTTP API and built-in conflict resolution.
Support summary
Apache CouchDB currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
2
0 lts
Versions
4
Latest Version
3.5.2
Active Support
2
EOL
2
Lifecycle Timeline
Today ↓
3.5
3.5
3.4
3.4
3.3
3.3
3.2
3.2
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 3.5 | May 5, 2025 | Yes | No | 3.5.2 | No | Active |
| 3.4 | Sep 20, 2024 | Yes | No | 3.4.3 | No | Active |
| 3.3 | Dec 28, 2022 | No | May 5, 2025 | 3.3.3 | No | EOL |
| 3.2 | Oct 8, 2021 | No | Sep 20, 2024 | 3.2.3 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Apache CouchDB have reached end of life?
The following Apache CouchDB versions have reached end of life and no longer receive security updates: 3.3, 3.2. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache CouchDB 3.3?
Apache CouchDB 3.3 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache CouchDB?
The latest version of Apache CouchDB is 3.5.2, released in the 3.5 release cycle.
How many versions of Apache CouchDB are currently supported?
Apache CouchDB currently has 2 actively supported version(s): 3.5, 3.4.
When does Apache CouchDB 3.5 reach end of life?
Apache CouchDB 3.5 does not have a specific end-of-life date announced yet.
What should I do when Apache CouchDB reaches end of life?
When a Apache CouchDB version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.