Enterprise infrastructure teams don’t adopt platforms based solely on features. They adopt platforms they can run, protect and recover with confidence within the security, networking and operational constraints they already have.
The Progress® Chef® 360™ platform was built with that reality in mind.
It is an enterprise automation platform that unifies infrastructure automation, continuous compliance, node management and job orchestration into a single system, thus helping teams standardize configurations, enforce policies and gain end-to-end visibility across cloud, on-premises and hybrid environments.
By bringing these capabilities together, the Chef 360 platform makes infrastructure more secure and consistent. This combination allows teams to move from fragmented tooling to a unified operating model, reducing risk, improving consistency and accelerating how infrastructure is managed at scale.
With the latest updates, the platform takes another step forward in enterprise readiness by directly addressing two questions every large or regulated organization asks early in the evaluation process:
The Chef 360 platform introduces two major capabilities designed specifically for enterprise environments: built-in disaster recovery and a fully supported Bring Your Own Kubernetes (BYOK) deployment model.
Let us look into the details of each of these capabilities to better understand them.
Disaster recovery is non-negotiable for enterprise platforms, but it’s often difficult to configure, hard to audit and dependent on specialized Kubernetes expertise.
The Chef 360 platform changes that by making disaster recovery a first-class, UI driven capability.
Admins can now configure disaster recovery directly from the Chef 360 Admin Console, without editing YAML files or running Kubernetes commands. This includes:
In addition to configuration, the Chef 360 platform’s disaster recovery system captures both PostgreSQL data and full cluster state, including the Admin Console, application data and platform configuration. This ensures that recovery is not limited to data alone but restores the entire operational state of the platform.
By moving disaster recovery into a guided UI, the Chef 360 platform makes critical workflows more accessible, auditable and operationally safe. Teams no longer need to rely on tribal knowledge or custom scripts to protect a core platform.
For enterprises, this means:
Most large enterprises already standardize on their own Kubernetes platforms, whether that’s Amazon EKS, Azure AKS, Red Hat OpenShift or another managed or self-hosted distribution. They expect critical workloads to run inside those environments, governed by established tooling and policies.
The Chef 360 platform now fully supports this model.
With Bring Your Own Kubernetes (BYOK), enterprises can deploy the Chef 360 platform on customer-managed Kubernetes clusters, rather than setting up separate or vendor-controlled environments. This allows teams to align Chef 360 with existing security, networking and operational standards of enterprises from day one.
Key elements of the BYOK experience include:
For regulated industries, network isolation and limited internet access are often mandatory, not optional.
The Chef 360 platform also supports air-gapped deployments, including air-gapped BYOK deployments, enabling customers to install and run the platform using private container registries and validated installation steps. This supports the Chef 360 platform’s ability to operate in environments with strict security controls, without requiring outbound connectivity.
For standard (connected) environments, installation follows a direct deployment model using Helm charts and publicly accessible registries. In contrast, air-gapped deployments require artifacts such as container images and Helm charts to be pulled from an internet-connected environment, re-tagged and pushed to a private registry before deployment.
To support long-term operations, the Chef 360 platform also includes dedicated tooling and documentation for customer-managed clusters, helping enterprise teams troubleshoot, maintain and scale the platform with confidence.
Enterprises evaluating critical platforms need confidence in three things before committing: resilience, recoverability and flexibility. Without them, tools stall in evaluation, not because they lack features, but because they lack operational fit.
The Chef 360 platform is beneficial for multiple teams in an enterprise in the following ways:
The Chef 360 platform isn't just about automating infrastructure. From unified infrastructure management and continuous compliance, to workflow orchestration and node visibility, it provides teams with a single platform to operate with control across every environment they run.
By simplifying disaster recovery and enabling fully supported deployment within existing Kubernetes environments, the Chef 360 platform gives organizations the confidence to standardize, scale and operate without compromise. Ultimately, it’s about reducing operational friction while aligning with the realities of enterprise environments, so teams can focus on delivering value rather than managing complexity.
See how the Chef 360 platform fits into your infrastructure. Request a free trial of the platform and its capabilities and explore what enterprise-ready automation really looks like.