Skip to main content
Monte runs a team’s jobs, artifact storage, and endpoints in Monte Cloud, or in the team’s own AWS, GCP, or Azure account with BYOC (bring your own cloud). In both, Monte runs the control plane: the Console, run history, and the scheduler.

The Operator

With BYOC, the Monte operator runs in the team’s Kubernetes cluster and connects outbound only. It fetches job specs from the control plane and sends back status, scores, and metrics. The control plane holds no credentials to the cluster or to artifact storage, and removing the operator revokes access. Jobs read and write data inside the team’s account. Inference requests go from the team’s application to the endpoint and never pass through Monte. Security and Privacy lists what Monte can see with each option.

Connect a Cloud

monte cloud connect creates these resources in the team’s account and installs the operator.
  • GKE: GPU node pools that stay at zero nodes until a job or deployment needs them
  • Cloud Storage: artifact storage
  • Artifact Registry: job images
  • Secret Manager: secrets
  • Service account: the operator’s cloud identity
  • Load balancer: the public endpoint
The operator’s access covers only its own namespace, artifact storage, the registry, and the secret store. The command runs with the signed-in gcloud, az, or aws session, which needs admin rights only while it runs. To use an existing cluster, add --cluster <name> --namespace <namespace>. The command then installs the operator there and creates no cluster or node pools. A team can connect more than one cloud, and each deployment names its cloud with --cloud.