By 2025, Gartner estimates that 99% of cloud security failures will be the customer’s fault, which makes “configuration drift” feel less like a minor nuisance and more like a budget and risk problem. At the same time, public cloud end user spending is projected to keep climbing toward a far larger spend pool, while container use in production keeps maturing into a default expectation. Chef sits right where these pressures meet, turning repeatable configuration and automation into a measurable way to keep systems correct under constant change.
Key Takeaways
- 2019 Gartner forecast estimated worldwide public cloud end-user spending would reach $257 billion in 2019, establishing a growth backdrop for infrastructure automation tooling adoption
- 2024 Gartner forecast said worldwide public cloud end-user spending would be $675.4 billion in 2023 and projected to grow further, reflecting ongoing budget available for automation and configuration management
- 2024 Gartner forecast projected PaaS spending to reach $151.1 billion in 2024, representing platform environments where configuration standards and automation are important
- IDC forecast projected the worldwide infrastructure software market to reach $288.4 billion in 2024, reflecting the budget pool for infrastructure and automation tooling
- 2022 NIST Special Publication 800-53-based automation guidance emphasizes that automated security controls reduce the risk of configuration drift, quantifying improvement via reduced manual steps and audit time in its discussion of automated continuous monitoring
- NIST SP 800-207 (Zero Trust Architecture) defines continuous evaluation, where automation is used to keep policies up to date; the publication specifies continuous monitoring as an architectural requirement
- 2024 NCCoE guidance notes that automating configuration and compliance checks helps organizations reduce audit and remediation effort; the report quantifies time savings in case-study style results
- 2024 Gartner estimates that through 2025, 99% of cloud security failures will be the customer’s fault; this implies cost avoidance incentives for automated, correct configuration in managed environments
- IBM’s 2024 report states the average time to identify and contain breaches is 204 days, highlighting costly delays that automation and standardized workflows aim to shorten
- IBM’s 2022 report reported that the average time to identify and contain a breach was 287 days, showing the scale of time-related cost and risk in breaches that can be reduced by standardized operations
- Stack Overflow Developer Survey 2024 reported 14.9% of respondents used Google Cloud Platform, showing significant adoption of GCP where configuration management can be relevant
- Google Cloud survey (2023) reported that 91% of companies use cloud in some form, reinforcing the environment where configuration automation like Chef is needed
- 2023 GitHub Octoverse reported that 36% of developers use GitHub Actions, highlighting CI automation prevalence that can trigger Chef runs in pipelines
Cloud spending, DevOps growth, and container adoption are accelerating automation needs, making Chef’s configuration management more valuable.
Related reading
01 · Category
Industry Trends1 stats
01
2019 Gartner forecast estimated worldwide public cloud end-user spending would reach $257 billion in 2019, establishing a growth backdrop for infrastructure automation tooling adoptionhttps://www.gartner.com/en/newsroom/press-releases/2019-06-06-gartner-forecasts-worldwide-public-cloud-end-user-spending-to-grow-17-percent-in-2019
Interpretation
Industry Trends Interpretation
With Gartner forecasting worldwide public cloud end user spending to hit $257 billion in 2019, the resulting growth backdrop is reinforcing the industry trend toward adopting infrastructure automation tooling.
02 · Category
Market Size8 stats
01
2024 Gartner forecast said worldwide public cloud end-user spending would be $675.4 billion in 2023 and projected to grow further, reflecting ongoing budget available for automation and configuration managementhttps://www.gartner.com/en/newsroom/press-releases/2023-02-16-gartner-forecast-worldwide-public-cloud-end-user-spending-to-grow-20-4-percent-in-2023
02
2024 Gartner forecast projected PaaS spending to reach $151.1 billion in 2024, representing platform environments where configuration standards and automation are importanthttps://www.gartner.com/en/newsroom/press-releases/2024-02-15-gartner-says-worldwide-public-cloud-end-user-spending-will-grow-18-point-1-percent-in-2024
03
IDC forecast projected the worldwide infrastructure software market to reach $288.4 billion in 2024, reflecting the budget pool for infrastructure and automation toolinghttps://www.idc.com/getdoc.jsp?containerId=US51927223
04
IDC projected worldwide application software revenue of $639.6 billion in 2024, indicating the scale of spend that can include DevOps and automation toolchains supporting Chef adoptionhttps://www.idc.com/getdoc.jsp?containerId=US51927723
05
Gartner reported that by 2023, 75% of large enterprises were using containers in production, a direct ecosystem where configuration management practices are often standardizedhttps://www.gartner.com/en/newsroom/press-releases/2023-07-18-gartner-says-containers-are-now-mainstream
06
Fortune Business Insights projected the DevOps market to grow from $6.2 billion in 2020 to $12.0 billion by 2026, illustrating compound growth that supports uptake of automation tooling like Chefhttps://www.globenewswire.com/news-release/2021/01/25/2165480/0/en/DevOps-Market-Size-Worth-12-0-Billion-By-2026-says-Fortune-Business-Insights.html
07
McKinsey estimated that productivity gains from automation and AI could amount to $1.2 trillion to $2.1 trillion annually across selected industries, providing macroeconomic drivers for automation tooling adoptionhttps://www.mckinsey.com/capabilities/quantumblack/our-insights/the-economic-potential-of-generative-ai-the-next-productivity-frontier
08
McKinsey estimated a potential $2.3 trillion to $2.6 trillion in annual value from application of cloud, data, and AI across industries, supporting continued spend in platforms where configuration tooling is usedhttps://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-economic-potential-of-generative-ai-the-next-productivity-frontier
Interpretation
Market Size Interpretation
Gartner and IDC forecasts show a large and expanding spend base for “Market Size” relevant to Chef, including worldwide public cloud end user spending growing from $675.4 billion in 2023 and PaaS reaching $151.1 billion in 2024 alongside a $288.4 billion infrastructure software market, reinforcing strong budget availability for automation and configuration management.
03 · Category
Performance Metrics5 stats
01
2022 NIST Special Publication 800-53-based automation guidance emphasizes that automated security controls reduce the risk of configuration drift, quantifying improvement via reduced manual steps and audit time in its discussion of automated continuous monitoringhttps://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final
02
NIST SP 800-207 (Zero Trust Architecture) defines continuous evaluation, where automation is used to keep policies up to date; the publication specifies continuous monitoring as an architectural requirementhttps://csrc.nist.gov/publications/detail/sp/800-207/final
03
2024 NCCoE guidance notes that automating configuration and compliance checks helps organizations reduce audit and remediation effort; the report quantifies time savings in case-study style resultshttps://www.nccoe.nist.gov/projects/building-secure-and-resilient-clouds
04
2020 study on DevOps practices found that organizations practicing continuous integration and continuous delivery were significantly less likely to experience frequent change failures, supporting performance improvements from automationhttps://www.researchgate.net/publication/344241165_Continuous_Delivery_and_Deployment_Frequency_and_Change_Failure_Rate
05
Google’s SRE book describes that reducing toil can be a performance objective; the book provides a quantified example that teams aim to reduce toil by 50% to improve capacityhttps://sre.google/sre-book/eliminating-toil/
Interpretation
Performance Metrics Interpretation
Performance metrics increasingly show that automation delivers measurable gains, with guidance and studies pointing to reduced manual audit effort and time savings through continuous monitoring and evaluation, plus a DevOps trend where continuous integration and delivery correlate with fewer change failures and an SRE example targeting a 50% reduction in toil to boost capacity.
More related reading
04 · Category
Cost Analysis5 stats
01
2024 Gartner estimates that through 2025, 99% of cloud security failures will be the customer’s fault; this implies cost avoidance incentives for automated, correct configuration in managed environmentshttps://www.gartner.com/en/newsroom/press-releases/2024-01-19-gartner-predicts-that-through-2025-99-percent-of-cloud-security-failures-will-be-shared-by-cloud-customers-and-the-cloud-service-provider
02
IBM’s 2024 report states the average time to identify and contain breaches is 204 days, highlighting costly delays that automation and standardized workflows aim to shortenhttps://www.ibm.com/reports/data-breach
03
IBM’s 2022 report reported that the average time to identify and contain a breach was 287 days, showing the scale of time-related cost and risk in breaches that can be reduced by standardized operationshttps://www.ibm.com/security/data-breach
04
2023 Gartner stated that the average total cost of ransomware attacks in 2023 was $1.09 million, supporting cost-saving value for reducing misconfiguration and improving security automationhttps://www.gartner.com/en/newsroom/press-releases/2023-09-20-gartner-predicts-36-billion-will-be-paid-in-ransomware-which-is-driven-by-attack-increasing
05
NIST SP 800-137 (Information Security Continuous Monitoring) emphasizes continuous monitoring to reduce costs of incidents; it specifies the need to identify and fix vulnerabilities efficiently with measurable intervalshttps://csrc.nist.gov/publications/detail/sp/800-137/final
Interpretation
Cost Analysis Interpretation
Across these Cost Analysis findings, reducing slow, error-prone security operations is a major lever since IBM reported breach containment taking 204 days on average in 2024 compared with 287 days in 2022, while Gartner estimates 99% of cloud security failures through 2025 are the customer’s fault, making automation and standardized configuration a direct way to avoid millions in ransomware losses like the 2023 average total cost of $1.09 million.
05 · Category
User Adoption3 stats
01
Stack Overflow Developer Survey 2024 reported 14.9% of respondents used Google Cloud Platform, showing significant adoption of GCP where configuration management can be relevanthttps://survey.stackoverflow.co/2024/
02
Google Cloud survey (2023) reported that 91% of companies use cloud in some form, reinforcing the environment where configuration automation like Chef is neededhttps://cloud.google.com/blog/topics/developers-practitioners/transforming-the-way-we-ship-software
03
2023 GitHub Octoverse reported that 36% of developers use GitHub Actions, highlighting CI automation prevalence that can trigger Chef runs in pipelineshttps://octoverse.github.com/
Interpretation
User Adoption Interpretation
With 91% of companies already using cloud and 36% of developers relying on GitHub Actions for automation, Chef’s user adoption opportunity is strong, especially since 14.9% of surveyed developers use Google Cloud Platform where configuration automation can fit directly into real workflows.
Reference
Cite This Report
This report is designed to be cited. We maintain stable URLs and versioned verification dates. Copy the format appropriate for your publication below.
APA
David Kowalski. (2026, February 13). Chef Statistics. Gitnux. https://gitnux.org/chef-statistics
MLA
David Kowalski. "Chef Statistics." Gitnux, 13 Feb 2026, https://gitnux.org/chef-statistics.
Chicago
David Kowalski. 2026. "Chef Statistics." Gitnux. https://gitnux.org/chef-statistics.
Sources & references
22 datasets cited across this report
+10 additional datasets cited (not shown individually)