Confluent Product Lifecycle

Release dates, version history and support and end-of-life dates as published by Confluent. Dates within the next 12 months are highlighted; past dates are dimmed. Retrieved 2026-10-14.

• Confluent Platform support policy. Commercial components receive two years of Standard support from the minor version release date, extended by one year for Platinum agreements; maintenance versions share the minor version dates. [1]
• Confluent Community software support. Starting with Confluent Platform 8.0, Community software follows the Kafka release cycle with about one year of patch support from the minor version release date. [1]
• Control Center support policy. Each Control Center version lists a Standard End of Life and a Standard End of Support date, and works across several Confluent Platform versions. [1]
• Fully managed connector lifecycle (Confluent Cloud). Connectors move from general availability to deprecated and then end of life, with one year to migrate from the deprecation date. [3]
• Self-managed connector support policy. Connectors are deprecated on a Confluent Platform release day and supported until end of support of the respective platform version, with 2 years for standard and 3 years for Platinum plans from deprecation. [4]
• Confluent Cloud updates. Confluent Cloud is regularly updated with improvements and new features, published by release date in the release notes. [5]

Continuously updated 12

Confluent Cloud (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud (cloud marketplace listings) (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud Basic cluster (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud custom connectors (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud Dedicated cluster (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud Enterprise cluster (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud for Apache Flink (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud Freight cluster (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud fully managed connectors (Connectors follow a lifecycle of general availability, deprecated and end of life; one year from deprecation to end of life. Per-connector deprecation and end of life dates are listed on the vendor page.)[3], Confluent Cloud ksqlDB (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Cloud Standard cluster (Fully managed service that Confluent updates regularly; no version end-of-life dates are published.)[5], Confluent Platform commercial connectors (Self-managed connectors follow a support policy: deprecation happens on a Confluent Platform release day and the connector is supported until the end of support of the respective Confluent Platform version; standard support plans receive 2 years from deprecation.)[4]

No published lifecycle 4

Confluent Platform Basics, Confluent Private Cloud, Customer-Managed Confluent Platform for Confluent Cloud, WarpStream