Manage deployments

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:

Dashboard: the Baseten web interface, for interactive changes and checking state.
Baseten CLI: terminal commands for scripting and automation. All commands except the baseten truss passthrough support --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.

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.
Label deployments: attach deployment metadata for ownership, source control, or CI automation.
Terminate a stuck replica: remove one unhealthy replica and let the autoscaler replace it.
Pull logs and metrics: inspect a deployment or environment from the dashboard, Baseten CLI, or Management API.
Download or inspect a deployment’s config: fetch a deployment’s Truss config or source from the Baseten CLI.

Before you start

Authenticate

UI
Baseten CLI
Management API

To sign in:

Go to app.baseten.co.
Enter your email and choose Continue, or choose Continue with Google or Continue with GitHub.

To create an API key:

In your workspace, open API keys in your settings.
Choose Create API key.

To sign in:

baseten auth login

? How would you like to authenticate?
  > Login with Baseten credentials (browser)
    Paste an API key

Browser opened to authenticate...

If it didn't open, visit:
  https://login.baseten.co/device?user_code=ABCD-1234

Verification code: ABCD-1234

Complete the sign-in in the browser; the CLI stores a profile that authenticates later commands.For more information, see baseten auth login.To create an API key:Create a personal key, tied to your account and its permissions, for local development and testing:

baseten org api-key create --type personal --name <label>

Save this key now. It will not be shown again.
abcd1234.ABCDEFGHIJKLMNOPQRSTUVWXYZabcdef01

Create a team key, not tied to any one user and optionally scoped to specific models, for production and shared automation:

baseten org api-key create --type workspace-invoke --name <label> --model-id <model-id>

Save this key now. It will not be shown again.
abcd1234.ABCDEFGHIJKLMNOPQRSTUVWXYZabcdef01

For more information, see baseten org api-key. Commands also accept the key through the BASETEN_API_KEY environment variable instead of a profile.

To authenticate API requests:The API doesn’t sign in; every request carries an API key. Create your first key in the dashboard or CLI.

Set the key as an environment variable, or store it in your secret manager:

export BASETEN_API_KEY="paste-your-api-key-here"

setx BASETEN_API_KEY "paste-your-api-key-here"

Pass the key in the Authorization header on every request:

curl "https://api.baseten.co/v1/models" \
  -H "Authorization: Bearer $BASETEN_API_KEY"

{
  "models": [
    {
      "id": "abc123",
      "name": "HelloWorld",
      "deployments_count": 1,
      "production_deployment_id": "def456",
      ...
    }
  ]
}

To create an API key with the API:Once you have a first key, create more over the API. type takes PERSONAL, WORKSPACE_MANAGE_ALL, WORKSPACE_INVOKE, WORKSPACE_EXPORT_METRICS, or WORKSPACE_MANAGE_API_KEYS:

curl -X POST "https://api.baseten.co/v1/api_keys" \
  -H "Authorization: Bearer $BASETEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type": "PERSONAL", "name": "<label>"}'

{"api_key": "abcd1234.ABCDEFGHIJKLMNOPQRSTUVWXYZabcdef01"}

For more information, see the create API key endpoint.

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.

UI
Baseten CLI
Management API

To find your IDs in the dashboard:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
Choose Copy ID next to the model name.
Select the deployment under Deployments. The deployment ID is the last segment of the page URL.

To list your models and deployments:

List your deployed models:

baseten model list

ID      NAME        TEAM     DEPLOYMENTS  CREATED
abc123  HelloWorld  Baseten  1            2026-05-28T15:52:18Z

Then list your model’s deployments:

baseten model deployment list --model-id <model-id>

ID      NAME          ENVIRONMENT  STATUS  INSTANCE                 REPLICAS  CREATED
def456  deployment-1  production   ACTIVE  1x2 - 1 vCPU, 2 GiB RAM  1         2026-05-28T15:52:19Z

Commands that take --model-id and --deployment-id also accept --model-name and --deployment-name to target by name instead.For more information, see model list and deployment list.

To list your models and deployments:

List your deployed models:

curl "https://api.baseten.co/v1/models" \
  -H "Authorization: Bearer $BASETEN_API_KEY"

{
  "models": [
    {
      "id": "abc123",
      "name": "HelloWorld",
      "deployments_count": 1,
      "production_deployment_id": "def456",
      ...
    }
  ]
}

Then list your model’s deployments:

curl "https://api.baseten.co/v1/models/{model_id}/deployments" \
  -H "Authorization: Bearer $BASETEN_API_KEY"

{
  "deployments": [
    {
      "id": "def456",
      "name": "deployment-1",
      "model_id": "abc123",
      "is_production": true,
      "status": "ACTIVE",
      ...
    }
  ]
}

For more information, see the list models and list deployments endpoints.

Download or inspect a deployment’s config

Fetch a deployment’s Truss config or source to inspect it locally. To print a deployment’s config.yaml:

baseten model deployment config --model-id <model-id> --deployment-id <deployment-id>

To download a deployment’s source:

baseten model deployment download --model-id <model-id> --deployment-id <deployment-id> --out-dir ./my-model

Use --out-file to save the source as a tar file instead of extracting it to a directory. Pass --overwrite to replace an existing file or non-empty directory. For more information, see deployment config and deployment download.

Next steps

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

Get started

Model APIs

Inference

Training

Development

Deployment

Engines

Model Labs

Organization

Hosting options

Observability

Troubleshooting

Manage deployments

Find your task

Before you start

Authenticate

Find your model and deployment IDs

Download or inspect a deployment’s config

Next steps

​Find your task

​Before you start

​Authenticate

​Find your model and deployment IDs

​Download or inspect a deployment’s config

​Next steps

Find your task

Before you start

Authenticate

Find your model and deployment IDs

Download or inspect a deployment’s config

Next steps