← ← Back to all products
Chef Infra Server
Active
DevOps & CI/CD Latest Version: 15.10.91 Latest Release: Feb 5, 2026
Chef Infra Server acts as a hub for configuration data, storing cookbooks, policies, and node metadata.
Versions
5
Latest Version
15.10.91
Active Support
1
EOL
3
Lifecycle Timeline
Today ↓
15
15
14
14
13
13
12
12
11
11
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 15 | Jun 13, 2022 | Yes | No | 15.10.91 | No | Active |
| 14 | Jun 8, 2020 | Jun 13, 2022 | No | 14.16.19 | No | Security |
| 13 | May 31, 2019 | Jun 8, 2020 | Jun 30, 2021 | 13.2.0 | No | EOL |
| 12 | Nov 25, 2014 | May 31, 2019 | Dec 31, 2020 | 12.19.31 | No | EOL |
| 11 | Feb 4, 2013 | Nov 25, 2014 | Dec 31, 2018 | 11.1.7 | No | EOL |
Frequently Asked Questions
Which versions of Chef Infra Server have reached end of life?
The following Chef Infra Server versions have reached end of life and no longer receive security updates: 13, 12, 11. It is recommended to upgrade to a supported version.
Is it safe to continue using Chef Infra Server 13?
Chef Infra Server 13 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Chef Infra Server?
The latest version of Chef Infra Server is 15.10.91, released in the 15 release cycle.
How many versions of Chef Infra Server are currently supported?
Chef Infra Server currently has 2 actively supported version(s): 15, 14.
When does Chef Infra Server 15 reach end of life?
Chef Infra Server 15 does not have a specific end-of-life date announced yet.
What should I do when Chef Infra Server reaches end of life?
When a Chef Infra Server version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.