Skip to main content
Learn to operate deployments on Baseten. After you push a model, you’ll scale it ahead of traffic, promote new versions, inspect logs and metrics, and deactivate or delete deployments you no longer need. You can manage your deployments using any of the following methods:
  • Console: the Baseten dashboard, for interactive changes and checking state.
  • Baseten CLI: terminal commands for scripting and automation. Every command supports --output json and --jq filtering.
  • Management API: REST endpoints for managing models, deployments, and environments from your own code.
  • CI/CD: automated deploys and promotions from GitHub Actions.

Authenticate

Sign in with your Baseten account and create an API key:
To sign in:
  1. Go to app.baseten.co.
  2. Enter your email and choose Continue, or choose Continue with Google or Continue with GitHub.
To create an API key:
  1. In your workspace, open API keys in your settings.
  2. Choose Create API key.
For enterprise authentication, including identity-provider sign-in and SCIM user provisioning, see SSO and SCIM or contact support to enable it for your workspace.

Find your model and deployment IDs

Each deployment has an ID, associated with the model that owns it. Use the two IDs together to target every operation on these pages. Both appear in the model’s page URL: Anatomy of the deployment page URL. In app.baseten.co/models/abc123/deployments/def456, abc123 is the model ID and def456 is the deployment ID.
To find your IDs in the console:
  1. Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
  2. Select your model.
  3. Choose Copy ID next to the model name.
  4. Select the deployment under Deployments. The deployment ID is the last segment of the page URL.

Find your task

  • Scale a deployment: change how much compute a serving deployment uses. Pre-scale before a traffic spike, scale to zero, or wake a scaled-to-zero deployment.
  • Manage the deployment lifecycle: change whether and where a deployment serves. Promote, deactivate, activate, and delete deployments.
  • Terminate a stuck replica: fix one bad copy inside a deployment and let the autoscaler replace it.
  • Pull logs and metrics: read what a deployment, or a whole environment, is doing. Fetch or stream logs and read metrics from scripts.

Next steps

For the concepts behind these operations, see Deployments and Environments. For incremental promotion, see Rolling deployments.