> ## Documentation Index
> Fetch the complete documentation index at: https://evalgate.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy an artifact

> Promote a versioned, immutable artifact to production.

# Deploy an artifact

A **deployable artifact** is an immutable, versioned bundle that contains the
winning prompt, model, parameters, and configuration. Deploying it points
production at that exact version.

## Step 1 — Open Deployable Assets

In the sidebar, click **Deployable Assets** (`/deployable-assets`). You will see
the list of artifacts and their versions.

## Step 2 — Pick the version

Open the artifact and pick the version you want to deploy. The version's
metadata records the full winning configuration and the exact experiment,
decision, comparison, and proposal that produced it.

## Step 3 — Approve and transition

1. Click **Approve** (requires the right permission).
2. Click **Transition** to move the version through the rollout stages (for
   example, `staged` → `canary` → `production`).

## Step 4 — Confirm health

After each transition, check the **health** view. Production must serve the exact
published version at the recorded revision. If health fails, roll back to the
previous version.

<Warning>
  A deployment is not "live" because the UI says so. Confirm the canonical and
  provider HTTP boundaries, the actual schema, and a real browser surface before
  declaring a release live.
</Warning>

## Roll back

Open the previous version and transition it back to production. Rollback is a
first-class, governed action — it is recorded with the actor and rationale.

## Up next

Carry the whole change end to end: [Run the eval loop](./run-eval-loop).