Chef Infra Server End of Life (EOL) Dates and End of Support (EOS) Dates
Chef Infra Server end of life (EOL) and end of support (EOS) dates: 4 Chef Infra Server versions have reached EOL, including Chef Infra Server 14 (EOL date: Dec 31, 2025) — no longer receiving security updates or patches. Chef Infra Server 15.10.125 is the current supported release. Also see RabbitMQ end of support dates for related end-of-life information.
Currently Supported Chef Infra Server Releases - Active EOS/EOSL Support (1)
| Release | Released | Security Support | Active Support | Latest |
|---|---|---|---|---|
| 15 | (4 years and 5 months ago) | Active | Active | 15.10.125 (2 months ago) |
Chef Infra Server End of Life (EOL) Releases - No Longer Supported (4)
| Release | Released | Security Support | Active Support | Latest |
|---|---|---|---|---|
| 14 | (6 years and 5 months ago) | (10 months ago) | (4 years and 5 months ago) | 14.16.19 (4 years and 5 months ago) |
| 13 | (7 years and 5 months ago) | (5 years and 4 months ago) | (6 years and 5 months ago) | 13.2.0 (6 years and 7 months ago) |
| 12 | (11 years and 11 months ago) | (5 years and 10 months ago) | (7 years and 5 months ago) | 12.19.31 (7 years and 8 months ago) |
| 11 | (13 years and 9 months ago) | (7 years and 10 months ago) | (11 years and 11 months ago) | 11.1.7 (12 years and 5 months ago) |
If you run the Chef Infra Server End of Life countdown on your calendar, the answer is simple: the Chef Infra Server EOL lands in November 2026. Progress is retiring the open-source Chef Infra Server software in favor of the Chef 360 platform, and this guide covers the dates, the risks, and where to go next. The end-of-life announcement affects every team still running the open source release.
Chef Infra Server End of Life Dates and Lifecycle Stages
Chef follows a long-term support model with three lifecycle stages. Generally available means active development and releases. Deprecated means no scheduled releases, only critical fixes. EOL means support stops entirely. The infra server 15 line is deprecated, and its EOL date is November 30, 2026, while end of October 2026 is the last day for new upstream code. A deprecation date of November 1, 2026 applies to Chef Automate.
| Product | Status | EOL date | Replacement product |
|---|---|---|---|
| Infra Server 15.x | Deprecated | November 30, 2026 | Chef 360 Platform |
| Infra Server 14.x | EOL | December 31, 2025 | Chef 360 Platform |
| Chef Automate | Deprecated | November 30, 2027 | Latest release |
| Chef Infra Client 18.x | Deprecated | August 31, 2027 | Chef Infra Client 19.x |
Supported versions and status
Chef Infra Client 19.x, Chef Habitat 2.x, InSpec 7.x and Chef Workstation 26.x remain supported. Chef's N-1 support policy keeps active support for the newest release and security support for the previous one, and the repository of supported versions lives in the documentation.
Why Progress Retired the Open Source Server
Chef Infra Server (open source) was phased out because infrastructure changed. Static servers gave way to dynamic cloud, edge and DevOps environments, and Progress argues that a free community edition cannot supply the enterprise orchestration, policy as code and unified visibility those teams expect. The Chef 360 platform bundles that automation into one commercial product, though Chef Infra Client and Workstation stay open source and the free server is the retired piece.
What a Deprecated Server Means for Security and Compliance
Once the Chef Infra Server end-of-life date passes, the software still runs, but it is unpatched and unsupported. Three risks compound: security risk from new CVE and vulnerability disclosures, compliance risk when an audit flags old components, and operational risk from dependency drift. Existing repositories turn read-only, and telemetry stays in place.
Security fixes stop after October 2026
October 2026 is the last day of upstream code; the November 30 EOL follows. Expect no security fixes, CVE patches or security patches once end of updates arrives, so every new vulnerabilities report becomes an exposure you absorb yourself.
Migration Options for a Phased Out Server
Before the November 30, 2026 EOL, you have three migration options, and a planning horizon of a few months lets you finish a phased cutover deliberately. First, move your 15.x install to the commercial Chef 360 platform. Second, stay on the unsupported code and carry upgrade work yourself. Third, switch your configuration management stack to another tool and keep your infrastructure under version control. The commercial path adds migration guides and commercial support, but it is single-vendor, which raises lock-in worries for some teams.
Chef 360 SaaS
For a 15.x install, the managed SaaS edition replaces your current install and removes upgrade chores, while Chef 360 Self-Managed keeps control in-house. Either way, each managed node moves off the install you now administer with chef-server-ctl.
Ansible for teams leaving Chef
For many teams, Ansible is the usual destination thanks to market momentum, a deep hiring pool and an agentless design. Whatever you choose, demand role-based access, single sign-on, an audit trail and compliance reporting, plus cloud-ready enterprise automation.
Cinc Server as a Community Fork After EOL
Once upstream updates stop, the Cinc project plans to keep Cinc Server alive as a community fork in maintenance mode. Version 16.0.0 should be a drop-in continuation of 15.x, with omnibus binary builds, platform support updates and dependency upgrades for Erlang, PostgreSQL, Ruby and OpenSSL. Your cookbooks and knife setups keep working, which makes the community route the free option.