Skip to main content

Choose your Chef 360 Platform deployment path

Before you set up Chef 360 Platform, decide where it will run and who will manage its infrastructure. This choice determines your environment’s requirements, deployment steps, and operational responsibilities.

Use this page to choose the right path for your organization: a hosted SaaS service that Progress operates, a self-managed deployment with an embedded Kubernetes cluster that Chef manages, or a self-managed deployment on a Kubernetes cluster that your organization operates. After you choose a path, follow the linked steps to get access, deploy the platform, and prepare it to manage your nodes.

Choose how to use Chef 360 Platform

Choose the option that matches how your organization wants to operate Chef 360 Platform:

  • Choose SaaS: Progress hosts and operates the platform. You don’t install or manage Kubernetes or Chef 360 Platform infrastructure.
  • Choose an embedded cluster: a self-managed deployment where Chef provisions and manages the embedded Kubernetes environment as part of the Chef 360 Platform deployment.
  • Choose Bring Your Own Kubernetes (BYOK): a self-managed deployment on a Kubernetes cluster that your organization already operates and controls.

For a detailed technical comparison, see the deployment model overview.

Considerations

Use the following factors to compare the three options before you decide:

ConsiderationSaaSEmbedded ClusterBYOK
Infrastructure ownershipProgress owns and operates all infrastructure.Your organization hosts the servers; Chef provisions and manages the embedded Kubernetes environment on them.Your organization owns, provisions, and operates the Kubernetes cluster and all supporting infrastructure.
Operational effortLowest. No Kubernetes or Chef 360 Platform administration.Lower than BYOK. You manage the host servers; Chef manages the Kubernetes layer.Highest. Your team manages Kubernetes networking, storage, security, and lifecycle, as well as the platform.
CostIncluded in your SaaS subscription; no separate infrastructure cost.Infrastructure costs for the hosts you provide, plus the subscription.Infrastructure and Kubernetes operational costs, plus the subscription.
Compliance and controlLowest direct control; relies on Progress’s hosted environment and compliance posture.More control than SaaS; your organization controls the host environment while Chef manages the cluster layer.Highest control; your organization enforces its own compliance, network, and security policies end to end.
Support modelProgress supports the hosted platform and its infrastructure.Progress supports the platform; your team supports the host infrastructure.Progress supports the platform; your team supports the Kubernetes cluster and its infrastructure.

Confirm that your choice matches your situation:

  • Choose SaaS if your priority is using the platform without operating its underlying infrastructure.
  • Choose an embedded cluster if you need a self-managed deployment but want Chef to manage the Kubernetes environment.
  • Choose BYOK if your organization owns the Kubernetes platform and needs control over its lifecycle and configuration.

Choose SaaS

Chef 360 SaaS is the hosted deployment model for Chef 360 Platform. Progress operates the platform infrastructure, so your organization doesn’t install, patch, or manage Kubernetes, Chef 360 Platform, or the supporting data services.

Who operates the infrastructure

Progress owns and operates every layer of the infrastructure: the Kubernetes environment, Chef 360 Platform, and the supporting data services. Your organization interacts only with the platform through its UI and APIs.

When to choose SaaS

Choose SaaS when your priority is using Chef 360 Platform’s capabilities rather than operating its infrastructure. SaaS is a good fit when:

  • Your team wants the fastest path to a working platform without provisioning servers or a Kubernetes cluster first.
  • You want Progress to handle platform upgrades, patching, and infrastructure scaling for you.
  • Your organization doesn’t require hosting the platform within its own network or data center.
  • You don’t want to assign staff to administer Kubernetes or Chef 360 Platform.

If your organization must host the platform in its own infrastructure—for example, because of network isolation, data residency, or infrastructure ownership requirements—choose a self-managed option: an embedded cluster or BYOK.

Before you begin

Next step

Request access and sign up for Chef 360 SaaS, then sign in to the platform.

Check whether this applies

Confirm SaaS is the right fit before you sign up:

  • You don’t need to host the platform within your own network or data center.
  • Your organization accepts that Progress operates and supports the underlying infrastructure.
  • You don’t require direct control over the Kubernetes layer or Chef 360 Platform’s host infrastructure.

If none of these conditions fit, review choose an embedded cluster or BYOK.

Choose an embedded cluster

An embedded cluster deployment lets your organization host Chef 360 Platform on its own infrastructure. Chef provisions and manages the embedded Kubernetes environment that runs the platform.

Who operates the infrastructure

Your organization provides and operates the host servers. Chef 360 Platform installs and manages its embedded Kubernetes cluster on those hosts, so your team doesn’t need prior Kubernetes administration experience to run the platform.

When to choose an embedded cluster

Choose an embedded cluster when Chef 360 Platform must run in your infrastructure, but you don’t want to operate Kubernetes yourself. An embedded cluster is a good fit when:

  • Your organization requires the platform to run within its own network, data center, or cloud account, rather than a Progress-hosted environment.
  • Your team doesn’t have dedicated Kubernetes administrators, or you want to avoid the ongoing effort of managing a cluster.
  • You want Chef to handle Kubernetes-layer provisioning, upgrades, and lifecycle management, while your team manages the host servers.
  • You need more direct control over the platform’s infrastructure and compliance posture than SaaS provides, without taking on full Kubernetes operational responsibility.

If your organization already operates Kubernetes clusters or requires direct control over cluster networking, storage, security, and lifecycle management, choose BYOK. If you don’t need to host the platform, choose SaaS.

Before you begin

Next step

Deploy Chef 360 Platform with an embedded cluster, then sign in to the platform.

Check whether this applies

Confirm an embedded cluster is the right fit before you deploy:

  • Your organization must host the platform in its own infrastructure.
  • Your team doesn’t want to provision, upgrade, or operate the Kubernetes layer directly.
  • You can provide and maintain the host servers that Chef 360 Platform and its embedded cluster run on.

If none of these conditions fit, review choose SaaS or BYOK.

Choose Bring Your Own Kubernetes (BYOK) deployment

Bring Your Own Kubernetes (BYOK) is a self-managed deployment model. Your organization installs Chef 360 Platform on a Kubernetes cluster that it already operates and controls.

Who operates the infrastructure

Your organization owns, provisions, and operates the Kubernetes cluster, including its networking, storage, security, and lifecycle management. Chef 360 Platform runs as a workload on that cluster.

When to choose a BYOK deployment

Choose BYOK when your organization already operates Kubernetes or requires direct control over cluster networking, storage, security, and lifecycle management. BYOK is a good fit when:

  • Your organization already runs Kubernetes clusters and has the expertise to operate one for Chef 360 Platform.
  • You need to enforce your own networking, storage, security, or compliance policies at the cluster level, beyond what an embedded cluster allows.
  • Your organization uses a specific Kubernetes distribution, version, or configuration to host its workloads, including Chef 360 Platform.
  • You want full control over cluster upgrades, scaling, and lifecycle decisions, independent of the platform’s release cadence.

If your team doesn’t want to administer Kubernetes, choose an embedded cluster so Chef manages the Kubernetes layer for you. If you don’t need to host the platform, choose SaaS.

Before you begin

Next step

Install Chef 360 Platform on your Kubernetes cluster, then sign in to the platform.

Check whether this applies

Confirm BYOK is the right fit before you deploy:

  • Your organization already operates a production-grade Kubernetes cluster or is ready to operate one.
  • You need direct control over cluster networking, storage, security, or lifecycle management.
  • Your team can take ongoing responsibility for both the Kubernetes layer and the platform.

If none of these conditions fit, review choose SaaS or choose an embedded cluster.

Next steps

After you choose how to use Chef 360 Platform, follow the path for your environment. When you can sign in, continue with the shared workstation and node setup steps.

  1. Review the system requirements and confirm that your subscription, platform, network, storage, and nodes meet the applicable requirements.
  2. Deploy Chef 360 Platform using your selected deployment method, or sign up for Chef 360 SaaS:
  3. Set up your workstation by installing the Chef 360 Platform CLIs and registering your computer. Use the platform UI to download the CLIs, get the tenant root certificate, and register your workstation.
  4. Prepare your infrastructure by enrolling nodes. Choose single-node enrollment, bulk enrollment, cookbook-based enrollment, or self-enrollment based on how you want to connect the nodes.
  5. Run a Courier job to verify that the platform can manage an enrolled node. Then review the job’s execution details and results.

Get access to Chef 360 Platform

Chef 360 Platform access depends on your product subscription, evaluation entitlement, or license. Review the Chef 360 Platform product page to learn more. Contact the Chef Support or your account team about SaaS access, self-managed deployment options, and licensing.

Thank you for your feedback!

×