The short answer
For Flink 1.20, the community's LTS line, the longest published dates come from Cloudera, whose Streaming Analytics 1.18 runs Flink 1.20.5 with support to March 2032, and Ververica, whose Platform 2.15 supports Flink 1.18 to 1.20 until May 2028. Confluent supports Flink 1.20 on Confluent Platform to August 2027 with Platinum support, and AWS runs it on Managed Service for Apache Flink. For Flink 1.19 and older, which the community no longer fixes, OSSeva publishes patched builds of 1.15 to 1.19, including the ZooKeeper client Flink bundles. AWS still runs 1.15.2, 1.18.1 and 1.19.1 as a managed service.
The deciding question is how your jobs are written. Flink 2.0 removed the DataSet API, the Scala APIs and SourceFunction and SinkFunction, so a job built on them cannot simply move to 2.x, and the vendor you choose has to support the 1.x line it runs on.
Running Apache Flink in production? OSSeva patches and supports it, end-of-life versions included.
Apache Flink extended support: what is coveredWhich Flink versions Apache still supports
Since March 2017 the Flink community has supported the current and previous minor release. Since March 2023 a minor that drops out of support gets one final bugfix release, and then nothing. Flink 1.20 is labelled LTS.
| Line | Status on 7 October 2026 | Latest release |
|---|---|---|
| 2.3 | Current | 2.3.0 (25 June 2026) |
| 2.2 | Previous minor, supported | 2.2.1 (15 May 2026) |
| 1.20 | LTS, supported | 1.20.5 (3 June 2026) |
| 1.19 | No longer supported | 1.19.3 (10 July 2025) |
| 1.18 and older | No longer supported | 1.18.1, 1.17.2, 1.16.3, 1.15.4 |
Every Flink release from 1.15 onwards also builds against a ZooKeeper line that is itself end of life, shaded as flink-shaded-zookeeper. The Flink end-of-life chart tracks every line, and Flink vulnerabilities by version lists the advisories.
How we chose and compared these providers
The list covers Ververica, Confluent, Cloudera, AWS, Aiven, OpenLogic and OSSeva. We compared them on the criteria this post's table applies:
- Which Flink versions the provider lists on its own site, and whether it lists none.
- Whether the support covers a platform or distribution the provider builds, a managed service it runs, or community Flink.
- Whether it publishes patched builds for Flink lines the community no longer fixes.
- Delivery model: self-managed platform, subscription, managed service or signed artifacts.
- Whether the jobs stay self-managed or move onto the provider's service.
Each provider is described only from its own documentation and pricing pages, read on 7 October 2026. We did not use reviews or analyst rankings. OSSeva sells one of the options, so read its row with that in mind and use the Best for column to rule any provider out.
Apache Flink support providers compared
Each row reflects what the provider publishes on its own site as of 7 October 2026.
| Provider | What it covers | Flink versions | Delivery model | Self-managed? | Best for |
|---|---|---|---|---|---|
| Ververica | Ververica Platform and its VERA engine, from the team that created Flink; each platform release supported for three years from general availability | Platform 2.15 supports Flink 1.18, 1.19 and 1.20 to 15 May 2028; 2.14 to November 2027. VERA engine versions are built on Flink 1.20 | Self-managed platform, BYOC or managed cloud | Yes, on Ververica Platform | Teams that want a Flink platform from the original Flink creators and can adopt Ververica's packaging, covering Flink 1.18 to 1.20 in Platform 2.15. |
| Confluent Platform for Apache Flink | Flink on Kubernetes managed through Confluent Manager for Apache Flink; Platinum adds a year | 1.20: standard ended 2 August 2026, Platinum to 2 August 2027. 1.19: Platinum to 18 March 2027. 1.18: Platinum to 24 October 2026. 2.0 to 2.2: standard to 2027, Platinum to 2028 | Confluent subscription | Yes | Teams already on Confluent that want Flink on their own Kubernetes with a Platinum option that extends the dates. |
| Confluent Cloud for Apache Flink | Serverless Flink SQL, Table API and user-defined functions; Confluent always runs the latest version | No version choice | Managed service | No | New Flink SQL, Table API or user-defined-function work where Confluent runs the latest version for you; there is no version choice. |
| Cloudera Streaming Analytics | Cloudera's Flink distribution, supported to each release's end-of-support date | CSA 1.18 runs Flink 1.20.5, supported to March 2032; CSA 1.17 to April 2028 | Cloudera subscription | Yes, on Cloudera's distribution | Teams already on Cloudera that want Flink 1.20.5 supported to March 2032. |
| Amazon Managed Service for Apache Flink | Managed Flink applications, with in-place version upgrades | 2.3.0, 2.2.1, 1.20.5, 1.19.1, 1.18.1 and 1.15.2. Support for 1.13 ended on 16 October 2025 | AWS managed service | No | Teams happy to hand jobs to AWS, with in-place upgrades and 1.15.2, 1.18.1 and 1.19.1 still offered. |
| Amazon EMR | Flink on YARN as part of a managed Hadoop cluster | EMR 7.14 ships Flink 1.20.0; EMR 6.15 ships 1.17.1 | AWS managed service | No | Teams running Flink on YARN inside a managed Hadoop cluster. |
| Aiven for Apache Flink | In service sunset: no new services, existing services remain available for now | 1.20, with no end date announced | Managed service | No | Existing Aiven for Flink users only: the service is in sunset and takes no new services. |
| Perforce OpenLogic | Apache Flink technical support at Gold, Silver and Bronze levels | No version list published | Support subscription | Yes | Teams that want help running community Flink under one contract with the rest of their stack; it does not publish patched builds. |
| OSSeva | Backported security fixes with a patched flink-shaded-zookeeper; HA review and 2.x API inventory on Assure; 24/7 job operations on Operate | 1.15, 1.16, 1.17, 1.18 and 1.19 | Signed Maven, Docker and tarball artifacts | Yes | Self-managed community Flink 1.15 to 1.19 with jobs that cannot move yet, such as those using APIs Flink 2.0 removed. |
The vendor rows cover Flink on their own platforms. Ververica, Confluent and Cloudera support their distributions and management layers, and the cloud services support the versions they host. A job running on Apache's own Flink binaries is covered only once it moves onto one of them.
How the providers differ
Ververica
Ververica describes itself as built by the original creators of Apache Flink. Its platform runs Flink jobs self-managed, in your own cloud account or as a managed service, and each Ververica Platform 2.x release is supported for three years from general availability, so 2.15 covers Flink 1.18 to 1.20 until May 2028. It is the natural choice for teams that want a Flink platform from the Flink specialists and can adopt Ververica's packaging.
Confluent
Confluent has two Flink products. Confluent Cloud for Apache Flink is serverless: you write Flink SQL, Table API code or user-defined functions, and Confluent always runs the latest version, so it suits new SQL and Table API work rather than an existing job pinned to one Flink version. Confluent Platform for Apache Flink runs Flink on your own Kubernetes, and its support ends at the earlier of two dates, the Flink version's and the Confluent Manager for Apache Flink release's. With Platinum support, Flink 1.20 is covered to 2 August 2027.
Cloudera
Cloudera Streaming Analytics 1.18, released in September 2026, runs Flink 1.20.5 and is supported to March 2032, the longest date in this comparison. For teams already on Cloudera, or those adding stream processing to a Cloudera estate, that is a long runway on the LTS line.
AWS and Aiven
Amazon Managed Service for Apache Flink still runs 1.15.2, 1.18.1 and 1.19.1 alongside 1.20 and 2.x, and its in-place version upgrade feature moves an application to a newer version without recreating it. AWS has ended older versions by stopping applications and then blocking restarts, as it did for 1.6, 1.8 and 1.11 in July 2025, so a long stay on an old version is not guaranteed. EMR runs Flink on YARN as one application among many. Aiven has put Aiven for Apache Flink into a service sunset and no longer creates new services.
Perforce OpenLogic
OpenLogic lists Apache Flink at all three support levels, which suits teams that want help running and upgrading community Flink under one contract with the rest of their stack. It does not publish patched Flink builds. See OSSeva vs OpenLogic.
OSSeva
OSSeva for Apache Flink patches community Flink 1.15 to 1.19 on the line you run, so job code, savepoints and connectors stay as they are, and replaces the shaded ZooKeeper with a patched one. Patch delivers the backports and transitive dependency fixes as signed Maven, Docker and tarball artifacts. Assure adds a high availability review, a ZooKeeper ensemble audit, an inventory of removed 2.x APIs used by each job, VEX statements for scanner findings and an upgrade plan to 1.20 LTS or 2.x. Operate adds 24/7 checkpoint and backpressure monitoring, a 15-minute P1 response, a named Flink engineer, savepoint management and a staged 2.x migration, and patches Critical CVEs (CVSS 9.0 and above) within 48 hours and High within 7 days. Pricing is per cluster, not per TaskManager, slot or job.
How to choose
| Situation | Usual answer |
|---|---|
| On 1.20 or 2.x and able to follow community releases | Community Flink, with OpenLogic or OSSeva Operate if you want help running it |
| Want a Flink platform from the Flink specialists | Ververica |
| Already on Confluent and writing SQL or Table API jobs | Confluent Cloud for Apache Flink, or Confluent Platform for Apache Flink on your own Kubernetes |
| Already on Cloudera | Cloudera Streaming Analytics 1.18 on Flink 1.20 |
| Happy to hand jobs to AWS | Amazon Managed Service for Apache Flink, using in-place upgrades |
| Community Flink 1.15 to 1.19 with jobs that cannot move yet | OSSeva patched builds while the move to 1.20 or 2.x is planned job by job |
The Flink 1.x to 2.x upgrade guide covers the API removals, and Flink HA on ZooKeeper or Kubernetes covers the HA choice.
Where OSSeva fits
OSSeva covers self-managed community Flink from 1.15 to 1.19 and the ZooKeeper inside and under it, which suits teams whose jobs depend on APIs that 2.0 removed. Flink extended support covers that case, and Flink and ZooKeeper covers the bundled client.
Frequently asked questions
Who provides support for Apache Flink 1.x?
For 1.20, Ververica, Confluent, Cloudera, AWS and OpenLogic all publish support on their own terms. For 1.15 to 1.19, which the community no longer fixes, OSSeva publishes patched builds, Confluent Platinum covers 1.19 to March 2027 and 1.18 to October 2026, and AWS still hosts 1.15.2, 1.18.1 and 1.19.1.
Is Flink 1.20 a long-term support release?
Yes. The Flink project labels 1.20 as its LTS line, and 1.20.5 shipped on 3 June 2026. Cloudera supports a Flink 1.20.5 build to March 2032, and Ververica Platform 2.15 supports 1.20 to May 2028.
What are the alternatives to Ververica for Flink support?
Confluent for Flink on Confluent Cloud or on your own Kubernetes, Cloudera Streaming Analytics on Cloudera's platform, Amazon Managed Service for Apache Flink, and OpenLogic for community Flink. OSSeva patches community Flink 1.15 to 1.19.
Is Aiven for Apache Flink still available?
Aiven has put the service into a sunset period. New services can no longer be created, existing ones remain available for now, and Aiven has not announced an end date for 1.20.
Who patches the ZooKeeper inside Flink?
Apache does not backport fixes to the shaded ZooKeeper in retired Flink lines. OSSeva builds Flink 1.15 to 1.19 with a patched flink-shaded-zookeeper, and on Kubernetes you can move to Flink's Kubernetes HA and drop ZooKeeper altogether.
Can I stay on Flink 1.x instead of moving to 2.x?
On 1.20 LTS, yes, with community releases and several vendors behind it. On 1.19 or older, only with a vendor that still supports that version, such as AWS's hosted versions, Confluent Platinum to its dates, or OSSeva's patched builds.
Tags
Related articles
How to Choose a Node.js Extended Support Vendor: 12 Questions to Ask
November 17, 2026OperationsNES, ELS and Stay-Put Support for Node.js: How the Models Differ
November 17, 2026OperationsHow to Choose a PostgreSQL Extended Support Vendor
November 17, 2026OperationsSpring Boot Commercial Support: What to Check Beyond Spring Enterprise
November 17, 2026OperationsEnd-of-life middleware patching: who covers Kafka, ZooKeeper, RabbitMQ and Redis
November 15, 2026OperationsHeroDevs vs TuxCare vs OpenLogic: which extended support fits your stack
November 14, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?