> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/sdgm/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/sdgm/_mcp/server.

# Deployment Modes

> Overview of Kumo Engine Platform deployment options: VPC Kubernetes (Helm) and Simplified VPC (Docker Compose).

> **Prerelease documentation**
>
> This Kumo Studio information is prerelease and is not yet supported. Stay tuned for the Docker and Kubernetes releases.

The Kumo Engine Platform ships as software you deploy and operate inside your own cloud environment.
There are two deployment paths:

* The **[Virtual Private Cloud](/kumo-engine/1.0.0/kumo-studio-guide-coming-soon/preliminary-documentation/deployment-architecture/virtual-private-cloud)** deployment runs Kumo on a customer-managed Kubernetes cluster (EKS, AKS, GKE, or OpenShift) using the `kumo-helm` chart.
  This is the production path, supporting all data connectors and admin-configurable job concurrency.

* The **[Simplified VPC Deployment](/kumo-engine/1.0.0/kumo-studio-guide-coming-soon/preliminary-documentation/deployment-architecture/simplified-vpc-deployment)** runs all Kumo services on a single GPU VM using Docker Compose.
  It is designed for proof-of-concept evaluations: fast to stand up, limited to CSV and Parquet data sources, and capped at one training job at a time.

In both cases, all data and model artifacts remain in your cloud environment.

The following table compares the two deployment options:

|                  | **VPC - Kubernetes (Helm)**                                    | **Simplified VPC (Docker Compose)**                                              |
| ---------------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Infrastructure   | Customer-managed Kubernetes cluster (EKS, AKS, GKE, OpenShift) | Single GPU VM (AWS AMI, Azure VM image, or GCP VM image)                         |
| Data connectors  | Snowflake, Databricks, BigQuery, S3, GCS, file upload          | CSV and Parquet files from cloud storage (S3, GCS)                               |
| Data storage     | Customer-owned object storage (S3/GCS), Postgres, Temporal     | Customer-owned cloud storage bucket; ephemeral local storage for DiskGraph index |
| ML compute       | Customer-managed GPU and high-memory nodes                     | Single GPU on host VM                                                            |
| Auth             | BYO OIDC or password (configured through Helm values)          | Password or OIDC (disabled by default)                                           |
| Job concurrency  | Admin-configurable                                             | 1                                                                                |
| Clouds supported | AWS, Azure, GCP, on-premises (OpenShift)                       | AWS, Azure, GCP                                                                  |
| Intended use     | Production workloads                                           | Proof of concept and evaluation                                                  |