Skip to main content

Get Started

This section guides you through setting up and using OGC's Model Registry to upload and manage models for deployment.

Step 1: Create a Registry​

  1. From the main navigation, go to Model Registry.
  2. Click on the Registry tab in the sub-menu on the top.
  3. Select Create New Registry.
note

Every new organization starts with a default registry already configured. If you need a custom setup, you can create a new registry and choose your preferred location—this is where your model weights will be stored and made available for deployment to Endpoints.

Step 2: Create a New Model​

Once your registry is set up:

  1. Go to the Model sub-menu.
  2. Click Create New Model.
  3. In the form, provide:
    • A model name
    • The registry where it should reside
    • The preferred GPU types (you can select more than one)
info

Selecting the GPU types during model creation ensures that, at deployment time, the platform can match your model with compatible GPUs available in the chosen registry location.

Step 3: Upload Model Weights via CLI​

After creating a model, you’ll be taken to its details view, where you can view and manage its versions.

Example CLI command:

ogc model upload <file-path> --sku <model-name> --registry-name <registry-name> --tag v0.0.1
info

Supported file types include: .safetensors, .json, .md, .txt, .py, .gitattributes, .yml, and LICENSE

Upload Status and Version Availability​
  • Upload progress is visible on both the UI and CLI.
  • If the upload is interrupted or fails, the status will show as UploadFailed.
  • Once uploaded successfully:
    • The version status changes to Uploaded
    • Then transitions to Synchronizing
    • Finally becomes Available, and ready for deployment to Endpoints.

✨ Alternative: Use Fine-Tuned Models​

You don’t always need to create and upload a model manually.

When you launch a fine-tuning job (see Fine-Tuning Guide), the resulting model is automatically:

  • Created in the registry using the base model name + job suffix.
  • Populated with checkpoints as model versions once the job is Completed.
  • Made Available for deployment directly from the model version list.

Contents