Chef 360 Platform deployment models
Use this page to choose the deployment model that best fits your environment, hosting preferences, and operational requirements. The right deployment model depends on whether you want Progress to host and operate the platform, or you want to run it in your own infrastructure, and if so, who manages the underlying Kubernetes environment.
Chef 360 Platform supports three deployment models: a hosted SaaS service that Progress operates, and two self-managed options for running Chef 360 Platform Server in your own infrastructure—an embedded Kubernetes deployment managed by Chef, and a bring your own Kubernetes (BYOK) deployment that runs on a customer-managed Kubernetes cluster. The supported path depends on your environment, compliance requirements, and operational preferences.
Before you begin
- Confirm that you have the required Chef 360 Platform license or subscription for the model you’re considering.
- Decide whether you want Progress to host and operate the platform (SaaS) or you want to run it in your own infrastructure (self-managed).
- If you’re considering a self-managed deployment, identify whether your organization manages the Kubernetes cluster and its underlying infrastructure, and review the Chef 360 Platform system requirements to confirm the requirements for your target environment.
- If you’re considering a self-managed deployment, decide whether you want a simpler managed Kubernetes deployment or a Kubernetes environment you own and operate.
Choose the deployment model
| Deployment model | Best for | Operational model | Typical considerations |
|---|---|---|---|
| SaaS | Teams that want to use the platform without operating its underlying infrastructure | Progress hosts and operates the platform | Fastest onboarding, no Kubernetes or server management, subject to SaaS entitlement and tenant access |
| Embedded cluster | Teams that want a simpler setup and rely on Chef-managed Kubernetes | Chef manages the Kubernetes platform | Faster setup, reduced platform administration, fewer cluster-management tasks |
| BYOK | Teams that already manage Kubernetes or need deeper cluster control | Your organization manages the Kubernetes environment | More infrastructure ownership, existing cluster reuse, stricter control over networking and security |
Chef 360 SaaS
Use Chef 360 SaaS when you want Progress to host and operate the platform infrastructure for you. Your team doesn’t install or maintain Kubernetes, Chef 360 Platform Server, or the supporting data services—you sign up, sign in, and start enrolling nodes.
This deployment model is typically best for:
- Teams that want to use the platform’s capabilities without operating the infrastructure behind them.
- Organizations that want the fastest path to a working tenant, with no cluster or server administration.
- Environments where a hosted, Progress-operated service meets your compliance and operational requirements.
Review the SaaS requirements, then sign up for Chef 360 SaaS for this path.
Embedded cluster deployment
Use the embedded cluster deployment when you want Chef 360 Platform Server to run in a Kubernetes environment that Chef provisions and manages for you. This option reduces the operational burden of cluster setup and is the recommended choice when you want the quickest path to deployment and a simpler operational model.
This deployment model is typically best for:
- New deployments that need a streamlined setup process.
- Teams that don’t want to manage the Kubernetes control plane or worker nodes.
- Environments where the main requirement is a supported, ready-to-use deployment.
Use the Install and configure Chef 360 Platform Server procedure for this path.
Bring your own Kubernetes deployment
Use the bring your own Kubernetes (BYOK) deployment when your organization already manages a Kubernetes cluster or when your environment requires tighter control over the underlying Kubernetes platform. This option gives you more flexibility over the cluster lifecycle, networking, storage, and security controls while still using Chef 360 Platform Server as the application layer.
This deployment model is typically best for:
- Environments that already have a supported Kubernetes cluster.
- Teams that want to manage cluster administration themselves.
- Security, networking, or compliance workflows that require specific Kubernetes controls.
Use the Bring your own Kubernetes (BYOK) guidance for this path.
Check whether this applies
Use the following checks to decide which deployment model fits your environment:
- If your priority is using the platform without operating Kubernetes or server infrastructure, choose the SaaS deployment.
- If your team wants Chef-managed Kubernetes and a faster self-managed deployment path, choose the embedded cluster deployment.
- If your organization already runs or manages Kubernetes and needs control over the cluster architecture, choose the BYOK deployment.
- If your environment has strict networking, storage, or security requirements, confirm that the selected deployment model and cluster design meet the applicable system requirements.
- If your deployment requires a supported installation path with clear operational ownership, choose the model that matches your internal platform team and support model.
Next steps
After you choose your deployment model, complete the corresponding onboarding path:
- For SaaS, review the SaaS requirements and sign up for Chef 360 SaaS.
- For an embedded cluster, follow Install and configure Chef 360 Platform Server.
- For a BYOK deployment, follow Bring your own Kubernetes (BYOK).
- Before a self-managed installation, review Check Chef 360 Platform system requirements to confirm that your environment meets the required platform, storage, networking, and licensing criteria.
Need access to this capability?
Installing and running Chef 360 Platform requires access to the appropriate product entitlement and deployment support. Review the Chef 360 Platform product page to learn more about deployment options and connect with the marketing or account team about licensing and access.
Alternatives
If you don’t want to operate Kubernetes or server infrastructure at all, the recommended path is Chef 360 SaaS, since Progress hosts and operates the platform for you. For self-managed environments that aren’t ready for a full cluster deployment, evaluate the embedded cluster deployment first because it reduces Kubernetes management overhead. If your organization has an established Kubernetes platform and strict platform governance, the BYOK deployment is the supported alternative that preserves cluster ownership while still enabling Chef 360 Platform Server installation.