Skip to main content
Select an appropriate target for a registered model version. Deployment changes a runtime and can consume resources; review the destination and permissions before proceeding.

​
Before you begin

Select the intended organization and project. You need permission to manage model deployments, an available model version compatible with the target, and access to the target infrastructure. For Edge, identify the intended device and format. For cloud, coordinate the available instance type or compute and environment with the infrastructure administrator. Availability and supported model formats depend on the deployment.

​
Deploy to cloud

  1. Open MLOps → Models → Deployments and choose Cloud Online or Cloud Batch for the intended workload. Choose Add.
  2. Enter a Logical Name, choose Model and Version, and inspect the displayed deployment metadata. For online, select the instance type and count and review the request timeout. For batch, select compute and review instance count, mini batch size, concurrency and output settings.
  3. Submit the configuration. Open the deployment, refresh its details, and wait for both endpoint and deployment states to show success. Check the endpoint, model version, and any traffic settings before relying on it.

​
Deploy to an edge device

  1. On Deployments, choose Edge, select the intended device, and choose Add.
  2. Select Model, Version, Deploy Format, and desired Status. Choose Review Deploy, inspect the confirmation, and confirm only when the target and changes are correct.
  3. Refresh the device deployments and inspect the status, model version, format, and any reported error. Verify the runtime on the device separately before relying on the model; a submitted desired state is not proof of a successful rollout.

​
Troubleshoot

Check the selected project, permissions, target availability, compatibility, and the displayed status or error. Cloud provisioning can take time; inspect both endpoint and deployment state. For Edge, check the device and deployment status. Before retrying or changing a deployment, inspect the current destination to avoid duplicating an operation or overwriting an unintended version.