Couchbase Server 7.6 End of Life: Full Maintenance Ends March 2027
Couchbase Server 7.6 receives Full Maintenance until the end of March 2027, and reaches End of Life in the same month. Couchbase's own Software Lifecycle Schedules print both dates as months, and say the Software receives Full Maintenance up to the last day of the month shown. After that, Couchbase no longer supports 7.6: no more Maintenance releases, no break-fix help, and no security fixes. The upgrade target is Couchbase Server 8.0, which Couchbase lists with Full Maintenance until October 2028.
Couchbase Server versions and their dates
| Version | End of Full Maintenance | End of Life |
|---|---|---|
| 8.0 | October 2028 | October 2028 |
| 7.6 | March 2027 | March 2027 |
| 7.2 | July 2026 | July 2026 |
Couchbase prints these dates as months, so we do too. Couchbase Server 7.2 has already passed its End of Life. Every earlier version, and its dates, is on the Couchbase Server page. The current risk score for 7.6 is 18 (live value).
What stops at the end of Full Maintenance
The Enterprise Software Support Policy describes Full Maintenance as break-fix assistance with issues related to the use of the Software within the documented specifications, workarounds, and Maintenance releases to resolve product issues. When Full Maintenance for 7.6 ends in March 2027, all three stop:
- No more 7.6 Maintenance releases. A defect or vulnerability found later is fixed in supported versions, not in a new 7.6.x release.
- No break-fix help or workarounds for 7.6. The policy says Support is provided only for versions Couchbase currently supports, and that Couchbase has no obligation to provide Support to a customer who is not running a supported version.
- No fallback phase. Older Couchbase Server lines moved into Limited Support (best effort help, but still no code fixes or security updates). 7.6 goes straight to End of Life, which the policy defines as no longer supported by Couchbase.
The policy also allows Couchbase to direct a customer to upgrade to a more current release before it provides Support, so a support case that starts on 7.6 near the end date may end with that request anyway.
Moving to Couchbase Server 8.0
Couchbase's upgrade documentation lists a direct path from any 7.6.x release to any 8.0.x release, for both Enterprise and Community Edition, so there is no stepping-stone version. Upgrading means upgrading each node in turn. Couchbase supports a cluster running more than one version (mixed mode) only while an upgrade is in progress. Before you start, the same page lists these changes in 8.0:
- Check your CPUs. On x86-64, Couchbase Server 8.0 and later requires the AVX2 instruction set. On a CPU without it the server exits with an error.
- Replace Memcached buckets. Memcached buckets have been removed in 8.0. The upgrade exits with an error if the cluster still has them; Couchbase says to replace them with ephemeral buckets first.
- Review scripts that create buckets. After a full upgrade to 8.0, a new bucket created without a storage backend uses Magma with 128 vBuckets instead of Couchstore with 1024. Magma does not support MapReduce Views, and versions before 8.0 cannot replicate with XDCR between buckets with different vBucket counts. Set the backend explicitly where either matters.
- Pause client-certificate authentication if you use node-to-node encryption. Couchbase says to disable client-certificate authentication before a rolling upgrade, because the first upgraded Index Service node otherwise fails to rebalance in, and to turn it back on once every node runs 8.0.
Clusters still on 7.0 or 7.1 cannot take the same shortcut: the documented path goes through 7.2.3 before 8.0.
Paid support after End of Life
Couchbase's support policy lists no paid extension for Couchbase Server 7.6 beyond its End of Life in March 2027, and a current Enterprise subscription does not change the dates: it covers versions Couchbase still supports. If your clusters cannot reach 8.0 by then, plan for running a database with no vendor fixes, and keep the exposure in your risk register until the upgrade is done.
What to do
- Find every Couchbase Server 7.6 cluster, including container images and Kubernetes deployments pinned to a 7.6 tag.
- Run the 8.0 checks above (AVX2, Memcached buckets, bucket-creation scripts, client-certificate authentication) on a test cluster first.
- Check your SDK and connector versions against 8.0 before the production upgrade.
- Schedule the upgrade well before March 2027, so the last weeks of Full Maintenance are a safety margin, not the plan.
Frequently Asked Questions
When is Couchbase Server 7.6 end of life?
Couchbase's Software Lifecycle Schedules list Couchbase Server 7.6 with End of Full Maintenance and End of Life both in March 2027. Full Maintenance runs up to the last day of that month. After that Couchbase no longer supports 7.6.
Does Couchbase Server 7.6 get Limited Support after Full Maintenance ends?
No. Couchbase's Enterprise Software Support Policy gives Couchbase Server 7.2 and later versions two periods only, Full Maintenance and End of Life, each 36 months from General Availability. The Limited Support phase, which the policy defines as best effort support without any code fixes or security updates, applies to older lines such as Couchbase Server 5.0 to 7.1.
What stops when Full Maintenance ends?
Full Maintenance covers break-fix assistance, workarounds and Maintenance releases that resolve product issues. When it ends for 7.6 those stop, and because 7.6 reaches End of Life in the same month, Couchbase support for 7.6 ends with them. The policy also says Couchbase has no obligation to provide Support to a customer who is not running a supported version.
What should I upgrade Couchbase Server 7.6 to?
Couchbase Server 8.0, which Couchbase lists with End of Full Maintenance in October 2028. Couchbase's upgrade documentation lists a direct path from any 7.6.x release to any 8.0.x release for both Enterprise and Community Edition.
Related
- Couchbase Server — every version and its dates
- Couchbase Server 7.6 — the version page with its live risk score
- Couchbase Server 8.0 — the upgrade target
- MongoDB — version dates for another document database
- Redis — version dates for an in-memory data store