Manage the deployment lifecycle

Manage your deployment through its lifecycle. After you push a model, promote its deployment to serve an environment, deactivate it to stop compute spend, activate it to bring it back, and delete it when you no longer need it. For what each deployment state means, see Deployments.

Promote to an environment

Promote a validated deployment to production (or a custom environment) to route that environment’s traffic to it. What happens to the previously promoted deployment is controlled by the target environment’s promotion cleanup strategy; see Environments for the concepts and Rolling deployments for incremental traffic shifting. Promotion can create a new published deployment with a different ID. For example, Baseten creates one when you promote a development deployment. A promotion can also reuse the source deployment. In both cases, use the id in the promotion response as the promoted deployment ID. The request can return while that deployment is still BUILDING, DEPLOYING, or UPDATING, before the target environment points to it. The cURL examples use jq to extract fields from JSON responses.

UI
Baseten CLI
Management API
CI/CD

To promote a deployment:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
Select the deployment under Deployments.
Choose Promote to….
In the Promote deployment dialog, choose the target environment.
Choose Promote to confirm.

To promote a deployment:Promote to production, the CLI’s default target, and save the returned deployment ID:

target_environment=production
promoted_deployment_id="$(
  baseten model deployment promote \
    --model-id <model-id> \
    --deployment-id <deployment-id> \
    --yes \
    --jq '.id'
)"
printf 'Promoted deployment ID: %s\n' "$promoted_deployment_id"

Promoted deployment ID: <promoted-deployment-id>

Promote to another environment with --environment <name> and save the returned deployment ID:

target_environment=staging
promoted_deployment_id="$(
  baseten model deployment promote \
    --model-id <model-id> \
    --deployment-id <deployment-id> \
    --environment "$target_environment" \
    --yes \
    --jq '.id'
)"
printf 'Promoted deployment ID: %s\n' "$promoted_deployment_id"

Promoted deployment ID: <promoted-deployment-id>

To promote a deployment:The response examples below show development deployment promotions. The returned published deployment is still BUILDING, so the target environment doesn’t point to it yet. A response for a reused published deployment can show ACTIVE or UPDATING and include the target environment’s name.Promote to production and save the returned deployment ID:

target_environment=production
promotion_response="$(
  curl -sS -X POST "https://api.baseten.co/v1/models/{model_id}/deployments/{deployment_id}/promote" \
    -H "Authorization: Bearer $BASETEN_API_KEY"
)"
promoted_deployment_id="$(printf '%s' "$promotion_response" | jq -r '.id')"
printf '%s\n' "$promotion_response" |
  jq '{id, is_production, is_development, status, environment}'

{
  "id": "<promoted-deployment-id>",
  "is_production": false,
  "is_development": false,
  "status": "BUILDING",
  "environment": null
}

Promote to another environment by sending the source deployment ID to that environment’s promote endpoint. Save the ID from the response:

target_environment=staging
promotion_response="$(
  curl -sS -X POST "https://api.baseten.co/v1/models/{model_id}/environments/$target_environment/promote" \
    -H "Authorization: Bearer $BASETEN_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"deployment_id": "{deployment_id}"}'
)"
promoted_deployment_id="$(printf '%s' "$promotion_response" | jq -r '.id')"
printf '%s\n' "$promotion_response" |
  jq '{id, is_production, is_development, status, environment}'

{
  "id": "<promoted-deployment-id>",
  "is_production": false,
  "is_development": false,
  "status": "BUILDING",
  "environment": null
}

To promote from CI/CD:Each push to main deploys the Truss and promotes the new deployment to production:

.github/workflows/deploy.yml

name: Deploy to production

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: basetenlabs/action-truss-push@v0.1.2
        with:
          truss-directory: "./my-model"
          baseten-api-key: ${{ secrets.BASETEN_API_KEY }}
          environment: "production"
          cleanup: false

For more information, see CI/CD and the Truss Push GitHub Action reference.

The promotion request can return before the target environment changes. The promotion is complete when the target environment’s current_deployment.id matches the returned promoted_deployment_id. Check the environment, rather than the source deployment:

UI
Baseten CLI
Management API

To verify the promotion:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
On the model’s overview, confirm the environment card’s Current deployment shows the promoted deployment.

To verify the promotion:Run this check again while the promotion is in progress:

current_deployment_id="$(
  baseten model environment describe \
    --model-id <model-id> \
    --environment "$target_environment" \
    --jq '.current_deployment.id // empty'
)"

if [ "$current_deployment_id" = "$promoted_deployment_id" ]; then
  printf 'Promotion complete: %s\n' "$current_deployment_id"
else
  printf 'Promotion not complete\n'
fi

Promotion complete: <promoted-deployment-id>

To verify the promotion:Run this check again while the promotion is in progress:

environment_response="$(
  curl -sS "https://api.baseten.co/v1/models/{model_id}/environments/$target_environment" \
    -H "Authorization: Bearer $BASETEN_API_KEY"
)"
current_deployment_id="$(
  printf '%s' "$environment_response" |
    jq -r '.current_deployment.id // empty'
)"

if [ "$current_deployment_id" = "$promoted_deployment_id" ]; then
  printf 'Promotion complete: %s\n' "$current_deployment_id"
else
  printf 'Promotion not complete\n'
fi

Promotion complete: <promoted-deployment-id>

For more information, see the promote deployment and promote to environment endpoints.

Deactivate a deployment

Deactivate a deployment to stop compute spend without deleting it. The deployment keeps its configuration and stays visible in the dashboard, but releases its replicas. Requests to a deactivated deployment fail with a 400 error; see troubleshooting for the error and recovery.

UI
Baseten CLI
Management API

To deactivate a deployment:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
Select the deployment under Deployments.
Choose Deactivate deployment.
Choose Yes, deactivate to confirm.

To deactivate a deployment:

baseten model deployment deactivate --model-id <model-id> --deployment-id <deployment-id>

Deactivated deployment <deployment-id>

The CLI prompts for confirmation; pass --yes to skip it (required when scripting).

To deactivate a deployment:

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

{"success": true}

The deployment’s status moves to INACTIVE within a few seconds. If you want the deployment to keep serving but stop paying for idle replicas, scale to zero instead. Deactivating also releases the deployment’s slot against your workspace’s deployment limit. Scaling to zero doesn’t, since the endpoint stays live.

Activate a deployment

Activate an inactive deployment to bring it back. Activation redeploys the model, so the deployment passes through DEPLOYING before reaching ACTIVE.

UI
Baseten CLI
Management API

To activate a deployment:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
Select the inactive deployment under Deployments.
Choose Activate deployment.

To activate a deployment:

baseten model deployment activate --model-id <model-id> --deployment-id <deployment-id>

Activated deployment <deployment-id>

To activate a deployment:

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

{"success": true}

For more information, see activate and the activate endpoint.

Delete a deployment

Delete deployments to clean up finished experiments and stale versions.

Deletion is irreversible, and requests to a deleted deployment return 404. Deactivate instead if you might need the deployment again.

A deployment that’s associated with an environment, or is the only deployment of a model, can’t be deleted; push a new deployment and promote it first, or delete the whole model.

UI
Baseten CLI
Management API

To delete a deployment:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
Select the deployment under Deployments.
Choose Delete deployment and confirm.

The button is disabled while the deployment serves an environment or is the model’s only deployment.

To delete a deployment:

baseten model deployment delete --model-id <model-id> --deployment-id <deployment-id>

Deleted deployment <deployment-id>

To delete a deployment:

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

{"id": "{deployment_id}", "deleted": true, "model_id": "{model_id}"}

Deleting a model removes all of its deployments. See baseten model delete or the delete model endpoint. For more information, see the Management API delete deployment endpoint and the Baseten CLI deployment delete reference.

Next steps

Scale a deployment to change replica behavior without a lifecycle change.
Pull logs and metrics to verify a deployment’s health after a transition.
CI/CD to run deploys and promotions from GitHub Actions.

Get started

Model APIs

Inference

Training

Development

Deployment

Engines

Model Labs

Organization

Hosting options

Observability

Troubleshooting

Manage the deployment lifecycle

Promote to an environment

Deactivate a deployment

Activate a deployment

Delete a deployment

Next steps

​Promote to an environment

​Deactivate a deployment

​Activate a deployment

​Delete a deployment

​Next steps

Promote to an environment

Deactivate a deployment

Activate a deployment

Delete a deployment

Next steps