Confluent Platform End of Support: 8.1.x Leaves Community Support October 15, 2026, and What the Community, Standard and Platinum Dates Mean

By Scott Bissett  ·  Published: October 11, 2026  ·  Reference guide  ·  Dates and policy wording read from Confluent's Supported Versions and Interoperability page at docs.confluent.io on the day of publication and re-checked at every site build.

Confluent Platform 8.1.x reaches the end of Confluent Community Software support on October 15, 2026, one year after its release on October 15, 2025. Customers on a Confluent Enterprise licence have longer: the same row of Confluent's Supported Versions and Interoperability page gives Enterprise Standard support until October 15, 2027 and Enterprise Platinum support until October 15, 2028. Confluent Platform is Confluent's self-managed distribution of Apache Kafka, and each release ships one Kafka version; 8.1 carries Kafka 4.1. Which of the three dates applies to a cluster depends on its licence and support agreement, and the rest of this guide is about telling them apart. The release's live status and EOL Risk Score are on its page.

Confluent's three tiers, in Confluent's words

Confluent prints up to three end-of-support dates for every release, in three columns headed Confluent Community Software End of Support, Confluent Enterprise Standard End of Support and Confluent Enterprise Platinum End of Support. The page explains the difference in a note under the table and in a change notice above it. Quoted exactly:

Two more sentences from the page govern how the dates apply. On patch releases: "The end of support date applies to minor versions and any maintenance versions that come after the minor version. This means that maintenance versions follow the same two year lifecycle of the minor version." A cluster on the latest 8.1 patch the page lists has the same three dates as 8.1.0. And on what Confluent does with an old release: "Confluent removes packages and repository metadata for versions that reach end of life (EOL). If your Confluent Ansible playbooks target an EOL version, deployments fail after Confluent removes the packages from the repositories." End of support at Confluent is not only the end of patches; it can be the end of the download.

The change notice also states the Enterprise side of the 8.0 change: "Confluent customers using a Confluent Enterprise license continue to receive patch updates for up to three years following minor version release." Three years is the Platinum figure; Standard is two. The page gives no release a long-term label of any kind, and neither does this guide.

What changes for 8.1 on October 15, 2026

For a cluster running the free Confluent Community software, October 15, 2026 is the end of the line for 8.1: Confluent's one-year Community window closes and new 8.1.x patches are no longer promised. For a cluster on a Confluent Enterprise licence with Gold or any other sub-Platinum agreement, nothing changes on the day; Standard support runs another year, to October 15, 2027. A Platinum agreement adds a further year, to October 15, 2028. The practical test is the licence file and the support contract, not the software: the Community and Enterprise builds of 8.1 run the same Kafka 4.1.

The 8.1 date is the first of several. Confluent Platform 7.8 reaches the end of Standard support on December 2, 2026; 7.9, the last 3.x-Kafka release, on February 19, 2027; 8.0 on June 11, 2027. Platinum customers on 7.6 have until February 9, 2027, and 7.6 Standard support already ended on February 9, 2026.

Every Confluent Platform release and its dates

Release and end-of-support dates as Confluent's table prints them. Releases 6.1 to 7.5 have left the current page, which says it covers releases "within active support windows"; their rows are read from the same page in the Confluent Platform 7.6 documentation, which printed two support columns (Standard and Platinum), so their Community date is the Standard date. The status column is computed from the Standard date at every build of this site.

The pattern is exact: for every release, Standard support ends two years after release to the day and Platinum three. The 8.0 change moved only the Community column, from two years to one. Confluent's example under the table is 7.6: "standard support for Confluent Platform 7.6.x ends on February 9, 2026." The Confluent for Kubernetes operator has its own policy ("Starting with CFK 2.9, the standard support policy of CFK is for 2 years from the first patch release (.0) date") and is not in this table.

Apache Kafka's support is a separate clock

It is tempting to read a Confluent Platform date as an Apache Kafka date, because the two columns sit side by side. They are not the same thing. Apache Kafka is an open-source project with its own release and bug-fix practice; Confluent's page describes it as "about one year of patch support for a Kafka version, from the minor version release date". Confluent Platform 8.1 bundles Kafka 4.1, which the Kafka project released on September 2, 2025, six weeks before Confluent shipped 8.1. The Kafka project's bug-fix releases for 4.1 follow the project's schedule; Confluent's Enterprise patches for 8.1.x follow Confluent's, and a Platinum customer can be receiving 8.1 fixes from Confluent in 2028, long after the Kafka community has moved on. Equally, a self-built Kafka 4.1 broker is not covered by any Confluent date, Community or otherwise.

So, plainly: Apache Kafka's own project support is tracked on our Apache Kafka page and explained in the Apache Kafka end-of-life guide; Confluent Platform's three dates are tracked here and on the Confluent Platform page. A date on one page does not move a date on the other. The Kafka version a Confluent release carries is the link between them, not a shared lifecycle.

What to do

1. Find out which column you are in. A cluster installed from Confluent's Community packages with no licence has the Community date. A cluster with an Enterprise licence has the Standard date unless the support agreement is Platinum, which Confluent's note defines by exclusion: everything below Platinum, Gold included, is Standard.
2. On Community 8.1: move before October 15, 2026. 8.2 (Community support to March 4, 2027) and 8.3 (to June 17, 2027) are the current lines; with a one-year Community window, a Community cluster needs an upgrade roughly every release.
3. On Enterprise Standard 8.1: the date is October 15, 2027. Plan the move to 8.3 or later for the first half of 2027, and check the operating-system and Java rows of Confluent's page for the target release, which drops older platforms as it goes.
4. On 7.8 or 7.9: these are the last releases on Kafka 3.x, and the 7.8 Standard date, December 2, 2026, is close. The move to 8.x is also the move to Kafka 4.x, which removed ZooKeeper; Confluent's upgrade documentation covers the KRaft migration that has to happen first.
5. Mirror the packages you depend on. Confluent says it removes packages and repository metadata for end-of-life versions and that Ansible playbooks targeting them fail. If a rebuild of an old cluster must stay possible during the migration, keep a local copy of the release's packages before its date, not after.
6. Watch the page. Confluent's table is the source for every date here, and it drops rows as windows close. The Confluent Platform page re-reads it at every build and shows each release's live status; the EOL Checker answers for a single version.

Frequently Asked Questions

Related

• Confluent Platform — every release, live status and EOL Risk Score
• Apache Kafka — the project's own versions and dates
• Apache Kafka end of life and support options — how the Kafka community's bug-fix practice works
• Cloudera 7.3.1 end of life — another data platform whose vendor dates differ from the open-source components inside it
• Apache Spark 4.0 end of life