Featured Stories

Progress Chef Infra Client 19 has new habitat-based packaging system, smooth installs and faster upgrades.

Clinton Wolfe Rahul Goel

AI and platform engineering are taking over IT Ops and Progress Chef is leading the way. Find out how.

Smitha Ravindran

Discover how Progress Chef simplifies configuration management with modern features like YAML and JSON recipes, agentless execution, local mode and robust testing via Test Kitchen. Learn why Chef is now easier to adopt and scale than Ansible, especially for compliance, heterogeneous environments and enterprise needs.

George Westwater

Latest Stories

Automation failures often stem not from bad tools, but from unmanaged execution. When separate approved workflows collide, organizations pay hidden costs in investigation, coordination, recovery, audits, and delays. Platform-governed automation provides a single trusted execution path, improving visibility, control, accountability, and trust without requiring teams to rewrite existing automation.

Kimball Johnson

Gartner's 2026 ThreatScape identifies software supply chain attacks as a top enterprise security threat. Learn why build-chain assurance matters for infrastructure automation and how organizations can evaluate the security, accountability and trustworthiness of the software managing their environments.

Derek Kiely Stephen Blankenship

Notification Management in the Progress Chef 360 Platform helps organizations stay informed about important infrastructure and platform events through centralized, configurable notifications. Administrators can configure notification providers, while users can personalize their notification preferences to receive updates relevant to their roles. This article explores the core concepts of Notification Management, walks through the configuration process, and highlights best practices for improving operational visibility and reducing response times across enterprise environments.

Akshay Parvatikar Vaamica Mahajan

Most enterprises have succeeded with automation, but often in disconnected silos using tools such as Chef, Ansible, Puppet, Terraform and custom scripts. This creates "automation islands" where teams lack visibility into each other's changes, making audits, troubleshooting and governance difficult. Rather than attempting costly rip-and-replace standardisation efforts, organisations should implement a shared execution layer that governs how automation is executed across tools. This approach improves visibility, auditability, execution control and operational consistency while allowing teams to continue using their existing automation investments.

Kimball Johnson

A practical guide to upgrading from CINC to Chef 360, covering migration phases, key considerations and how to transition to a cloud-native, policy-driven automation platform while minimizing risk and maximizing the long-term value.

Jnanankur Ghosh Kimball Johnson

Apply a zero-trust, policy-driven lifecycle model to NVIDIA DGX Spark using Chef. Standardise AI infrastructure, enforce compliance and manage workloads at enterprise scale.

Derek Kiely Mark Cavins

AWS has updated the AWS-ApplyChefRecipes document to support upcoming Chef licensed download requirements. This blog explains the June 13, 2026 change, introduces the new Chef License Id parameter, and provides step-by-step instructions for updating AWS Systems Manager State Manager associations to ensure continued Chef Infra Client downloads and automation workflows.

Akshay Parvatikar

Transform infrastructure ops with Chef Opsmith-AI automation in Chef 360 for faster execution, sandbox validation and scalable workflows.

Nischal Reddy Jnanankur Ghosh

Organizations are shifting from isolated servers to shared, dynamic infrastructure platforms, increasing the need for continuous visibility and control at scale. While automation jobs and workflows help execute changes, they fall short in maintaining a trusted, real-time understanding of system state. Over time, drift, loss of context and fragmented processes increase operational risk and cost. The key challenge is not executing change, but ensuring systems remain aligned with intended state under constant change. A modern operating model must link execution with ongoing validation, enabling teams to detect drift early, maintain compliance and act with confidence. Chef 360 addresses this gap by combining automation with operational context, giving teams a continuous, reliable view of infrastructure posture across environments. This shifts operations from tracking past actions to maintaining real-time operational confidence.

Kimball Johnson