Couchbase Server End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 8.0.3

Couchbase Server end of life (EOL) and end of support (EOS) dates: 20 Couchbase Server versions have reached EOL, including Couchbase Server 7.2 (EOL date: Jul 31, 2026) — no longer receiving security updates or patches. Couchbase Server 8.0.3 is the current supported release, with support through Oct 31, 2028 — 2 versions in active support. Also see ArangoDB lifecycle dates for related end-of-life information.

Couchbase Server end of life dates timeline — release schedule chart of the 8 most recent Couchbase Server versions, mapping security support windows against their EOL dates
Couchbase Server end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Couchbase Server releases of 22 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Couchbase Server EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Couchbase Server Releases - Active EOS/EOSL Support (2)

Release Released Full Maintenance Latest
8.0 (1 year and 1 month ago) (in 1 year and 11 months) 8.0.3 (2 months ago)
7.6 (2 years and 7 months ago) (in 4 months) 7.6.12 (4 months ago)

Couchbase Server End of Life (EOL) Releases - No Longer Supported (20)

Release Released Full Maintenance Latest
7.2 (3 years and 5 months ago) (3 months ago) 7.2.9 (10 months ago)
7.1 (4 years and 6 months ago) (2 years and 9 months ago) 7.1.6 (3 years ago)
7.0 (5 years and 3 months ago) (3 years and 9 months ago) 7.0.5 (3 years and 11 months ago)
6.6 (6 years and 3 months ago) (3 years and 9 months ago) 6.6.6 (3 years and 10 months ago)
6.5 (6 years and 10 months ago) (5 years and 8 months ago) 6.5.2 (5 years and 9 months ago)
6.0 (8 years ago) (6 years and 3 months ago) 6.0.5 (4 years and 6 months ago)
5.5 (8 years and 3 months ago) (6 years and 3 months ago) 5.5.6 (7 years ago)
5.1 (8 years and 8 months ago) (7 years and 9 months ago) 5.1.3 (8 years ago)
5.0 (9 years ago) (8 years and 2 months ago) 5.0.1 (8 years and 11 months ago)
4.6 (9 years and 9 months ago) (8 years and 2 months ago) 5.0.1 (8 years and 11 months ago)
4.5 (10 years and 4 months ago) (8 years and 6 months ago) 4.5.1 (10 years and 1 month ago)
4.1 (10 years and 11 months ago) (8 years and 6 months ago) 4.1.2 (10 years and 3 months ago)
4.0 (11 years and 1 month ago) (9 years and 6 months ago) 4.0.0 (11 years and 1 month ago)
3.1 (11 years and 2 months ago) (9 years and 8 months ago) 3.1.3 (10 years and 6 months ago)
3.0 (11 years and 11 months ago) (10 years and 6 months ago) 3.0.3 (11 years and 7 months ago)
2.5 (12 years and 8 months ago) (10 years and 10 months ago) 2.5.0 (12 years and 8 months ago)
2.2 (13 years and 1 month ago) (11 years and 7 months ago) 2.2.0 (13 years and 1 month ago)
2.1 (13 years and 4 months ago) (11 years and 10 months ago) 2.1.0 (13 years and 4 months ago)
2.0 (13 years and 10 months ago) (12 years and 4 months ago) 2.0.0 (13 years and 10 months ago)
1.8 (14 years and 3 months ago) (12 years and 9 months ago) 1.8.0 (14 years and 3 months ago)

If your cluster still runs an older release, the Couchbase Server end of life schedule tells you how long that release keeps getting fixes. Couchbase is a cloud-native, distributed database that blends relational SQL, ACID transactions and JSON flexibility in one NoSQL platform, and the software runs in hybrid and private cloud setups. Each version moves through full maintenance, then a reduced stage, and the support policy sets the dates for both.

Couchbase Server End of Life Dates by Release

This table follows Couchbase's published schedule as of October 2026. Each Couchbase Server release lists its general availability month, the month end of full maintenance arrives, and the month the version reaches end of life. Look up your Couchbase Server version, then read the status column to see where it stands today.

ReleaseGeneral availabilityEnd of full maintenanceEnd of lifeStatus in October 2026
Couchbase Server 8.0Oct 2025Oct 2028Oct 2028Full maintenance
Couchbase Server 7.6Mar 2024Mar 2027Mar 2027Full maintenance
Couchbase Server 7.2Jun 2023Jul 2026Jul 2026End of life reached
Couchbase Server 7.1May 2022Jan 2024Jul 2025End of life reached
Couchbase Server 7.0Jul 2021Jan 2023Jul 2025End of life reached
Couchbase Server 6.6Aug 2020Jan 2023Oct 2023End of life reached
Couchbase Server 6.5Jan 2020Feb 2021Oct 2022End of life reached

Only 8.0 and 7.6 are still inside full maintenance. A version becomes end of life the day after the date in the table, so 7.2 left support in July 2026 and 7.6 follows in March 2027. Releases before 6.5 ended even earlier.

Read the general availability column first, because every other date follows from the general availability date. For 7.6, general availability in March 2024 plus three years lands the end of full maintenance and the end of life in March 2027, so the end of full maintenance and the end of life coincide for current releases.

Security updates after full maintenance ends

For 7.2 and later, the table shows no reduced stage, so fixes stop the month full maintenance ends. On older releases the reduced stage is best effort support without any code fixes or security patches. Limited support is also available only as a courtesy, so treat the end of full maintenance, not the end of life date, as your real deadline.

Couchbase Software Lifecycle: Full Maintenance Rules

Under this model, which the lifecycle schedules on the support site spell out, full maintenance means break-fix help with issues inside the documented specifications, workarounds, and maintenance releases that resolve product issues. End of life means the software is no longer supported at all. The length of each stage depends on the release type, as the table shows.

Release typeFull maintenanceLimited supportEnd of life
Couchbase Server 7.2 and later36 months from general availabilityNone36 months from general availability
Legacy Couchbase Server 5.0 to 7.1Longer of 30 months or 6 months after the next major release18 months after the 30 months48 months from general availability
Couchbase Server 4.6 and priorLonger of 18 months or 6 months after the next release12 months after that30 months from general availability

The dated table stays the authority whenever it differs from the arithmetic, so check it before you commit to a window.

General availability date and the 30-month rule

The general availability date is the day a new version is first released for customers to download. For older major versions, the clock runs 30 months from that date, or until 6 months after the next major release, whichever is longer. Newer releases from 7.2 on get a flat three years. Count forward from the general availability date, not from the day you installed, and a general availability in Oct 2025 means the end of full maintenance exactly three years later. That end of full maintenance date is when fixes stop.

Major release versus minor release timing

The first number in x.y.z marks a major one, and the second marks a minor release. A later release does not always buy more time: 7.0 and 7.1 share the same Jul 2025 end of life even though 7.1 shipped ten months after 7.0. Check the table row for your exact minor release rather than assuming a rule.

Sync Gateway, Couchbase Lite and Autonomous Operator End-of-Life Dates

Couchbase Server is not the only product with dated stages. Each component has its own dates, and the same three stages apply. Current Sync Gateway, Couchbase Lite and Edge Server releases get three years of full maintenance, while the Autonomous Operator gets a shorter period: 15 months of full maintenance, then 9 months of reduced help, for 24 months in total.

Component releaseGeneral availabilityEnd of full maintenanceEnd of life
Sync Gateway 4.0Oct 2025Oct 2028Oct 2028
Couchbase Lite 4.0Oct 2025Oct 2028Oct 2028
Edge Server 1.0Mar 2025Mar 2028Mar 2028
Autonomous Operator 2.8Mar 2025Jun 2026Mar 2027
Operational Insights 3.0Oct 2026Oct 2029Oct 2029
  • SDKs, connectors, and frameworks and libraries: a year and a half of full maintenance and 12 months of reduced help, ending 30 months after release.
  • Analytics, which Couchbase renamed Operational Insights in October 2026: three years from release, with Analytics support commitments for earlier versions unchanged.
  • Agent Memory, Agent Catalog and the MCP Server: 12 months from release.

Sync Gateway and Couchbase Lite ship in step, so a Couchbase Lite 4.0 app pairs with Sync Gateway 4.0 until the end of full maintenance in Oct 2028. Couchbase Lite and Sync Gateway share one general availability date per generation, which keeps the general availability and support windows aligned. The Autonomous Operator moves faster: its row shows full maintenance ending in Jun 2026, well before its end of life in Mar 2027. Analytics and Operational Insights follow the longer pattern, and the Couchbase Lite documentation lists each general availability date. Analytics customers see the same three-year window, and the Analytics rename took effect in Oct 2026.

If your application pairs a server with a mobile or edge client, check both rows, because the client version can end sooner than the server. Managed Couchbase Capella deployments follow their own service terms rather than this one.

Enterprise Software Support Policy and Support Subscription Tiers

The support policy applies to every customer who holds a current enterprise subscription under the agreement and runs a supported version of the software. Support subscription tiers decide how fast Couchbase answers, based on the severity level of the problem:

  • Platinum: a P1 gets an initial response time of 30 minutes, around the clock.
  • Gold: a P1 gets an initial response time of 2 hours, around the clock.
  • Silver: a P1 gets 5 business hours, during business hours only.

P1 means a production outage, so it is not available for non-production environments. Support is break-fix only, in English, and Couchbase does not guarantee a fixed resolution time. It also owes nothing if you run an unsupported version, ignore the documentation, or lack a valid license for every deployment. If you bought through a reseller, your first contact may be the reseller.

A customer must keep a current plan, and the customer must supply the software version, environment type and logs with each request. The agreement governs whatever it leaves out, so a customer on a partner contract should read that agreement too. Any software that is altered or unsupported falls outside it, and each customer needs a plan for every deployment of the software.

Opening a support ticket for a legacy version

For a version past end of life, expect Couchbase to ask you to move to a current release before it provides help. A customer without an active plan is not entitled to support and must contact sales, and every support request goes through the Support Portal with the environment type and redacted log files.

Planning an Upgrade Before a Release Reaches End-of-Life

Start from the version of the software you run and work forward, because every customer upgrade needs testing time:

  1. Run cat /opt/couchbase/VERSION.txt on a node to confirm the exact release.
  2. Find that release of the software in the first table and note its end of full maintenance month, such as Mar 2027 for 7.6.
  3. Pick a supported release, ideally the newest, so you gain the longest runway.
  4. Rehearse the move in a staging cluster, then book the live cutover well before the deadline.

Starting at least six months ahead leaves room for testing while the customer, and the software, are still covered.

EOL dates of related software products