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.

UI
Baseten CLI
REST 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):

baseten model deployment promote --model-id <model-id> --deployment-id <deployment-id>

Promoted deployment <deployment-id> to environment production

Promote to another environment with --environment <name>:

baseten model deployment promote --model-id <model-id> --deployment-id <deployment-id> --environment staging

Promoted deployment <deployment-id> to environment staging

To promote a deployment:Promote to production:

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

{
  "id": "{deployment_id}",
  "name": "deployment-2",
  "model_id": "{model_id}",
  "is_production": true,
  "is_development": false,
  "status": "ACTIVE",
  "active_replica_count": 1,
  "environment": "production",
  "instance_type_name": "1x2 - 1 vCPU, 2 GiB RAM",
  "autoscaling_settings": {
    "min_replica": 0,
    "max_replica": 1,
    "autoscaling_window": 60,
    "scale_down_delay": 900,
    "concurrency_target": 1,
    "target_utilization_percentage": 70
  },
  "created_at": "2026-07-07T18:29:11.147Z",
  "labels": {}
}

Promote to another environment by POSTing the deployment ID to that environment’s own promote endpoint:

curl -X POST "https://api.baseten.co/v1/models/{model_id}/environments/staging/promote" \
  -H "Authorization: Bearer $BASETEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"deployment_id": "{deployment_id}"}'

{
  "id": "{deployment_id}",
  "name": "deployment-2",
  "model_id": "{model_id}",
  "is_production": false,
  "is_development": false,
  "status": "ACTIVE",
  "active_replica_count": 1,
  "environment": "staging",
  "instance_type_name": "1x2 - 1 vCPU, 2 GiB RAM",
  "autoscaling_settings": {
    "min_replica": 0,
    "max_replica": 1,
    "autoscaling_window": 60,
    "scale_down_delay": 900,
    "concurrency_target": 1,
    "target_utilization_percentage": 70
  },
  "created_at": "2026-07-07T18:29:11.147Z",
  "labels": {}
}

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
        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.

Promotion routes the environment’s traffic to the new deployment. Verify it:

UI
Baseten CLI
REST 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 your deployment.

To verify the promotion:

baseten model deployment describe --model-id <model-id> --deployment-id <deployment-id> --jq '.environment'

"production"

To verify the promotion:

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

{
  "id": "def456",
  "environment": "production",
  "is_production": true,
  "status": "ACTIVE",
  ...
}

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
REST 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.

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
REST 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
REST 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}"}

You can also delete the model itself, which removes all of its deployments:

UI
Baseten CLI
REST API

To delete a model:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
On the model’s overview, choose Actions, then Delete model.
Type the model’s name to confirm, then choose Delete.

To delete a model:

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

Deleted model <model-name> (<model-id>)

To delete a model:

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

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

For more information, see the delete deployment and delete model endpoints, and the CLI’s delete reference.

Next steps

With lifecycle transitions scripted, the same commands slot into CI jobs, cron cleanups, and incident runbooks.

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.

​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