Hortonworks Data Platform (HDP) End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Hortonworks Data Platform (HDP) versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.3 | — | Jul 1, 2015 | Jul 31, 2018 | 2929 days past EOL | EOL |
| 2.4 | — | Mar 1, 2016 | Mar 31, 2019 | 2686 days past EOL | EOL |
| 2.5 | — | Aug 1, 2016 | Aug 31, 2019 | 2533 days past EOL | EOL |
| 2.6 | 2.6.5 | Apr 1, 2017 | Dec 31, 2020 | 2045 days past EOL | EOL |
| 3.0 | — | Jul 1, 2018 | Jul 31, 2021 | 1833 days past EOL | EOL |
| 3.1 | 3.1.5 | Dec 1, 2018 | Dec 31, 2021 | 1680 days past EOL | EOL |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/hdp)
Hortonworks Data Platform (HDP) lifecycle status — the real story
The Hortonworks Data Platform is fully end of life, and earlier than most people assume: HDP 3.1 — the last HDP release, final build 3.1.5 — reached end of support in December 2021, not the March 2022 date often quoted (that date belongs to CDH). HDP 3.0 ended in July 2021, and the widely deployed 2.6 line ended in December 2020.
The March 2022 confusion comes from Cloudera's free 'Limited Support' window, which ran HDP 3.1 subscribers from January to June 2022 — but that offering excluded code fixes, root-cause analysis, and escalation, so no security patch for HDP has existed since December 2021. There was no paid extended-support option, and no new HDP subscriptions have been sold since; the migration path Cloudera points to is its current platform.
Cloudera publishes its lifecycle commitments at month granularity rather than as exact days. The dates in this table normalise each published month to its final day, which is how Cloudera's own support lifecycle policy reads; treat them as the end of the stated month, not as a guaranteed cut-off timestamp.
What does Hortonworks Data Platform (HDP) end of life mean for your organization?
When a version of Hortonworks Data Platform (HDP) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Hortonworks Data Platform (HDP) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Hortonworks Data Platform (HDP) reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Hortonworks Data Platform (HDP) versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Hortonworks Data Platform (HDP) has 6 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Hortonworks Data Platform (HDP) exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.