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

# Manage Lakehouse deployments

> Find live blueprint deployments, compare versions, and resolve staged changes.

The Deployments page shows deployable catalog entities and their current version state. Use it to identify what is live and to open version control for a specific blueprint.

## Find a deployment

Open **Lakehouse** > **Deployments**. Enter an entity name in **Search deployments…**, or filter by **Type…** and **Status…**.

The table includes:

* **Entity**;
* **Version**;
* **Status**;
* **Updated by**;
* **Updated**;
* **Type**.

Select **Refresh deployments** after a publish or deployment action. Select an entity name to open its version history.

## Read deployment status

| Status                                        | Meaning                                               | Next step                                       |
| --------------------------------------------- | ----------------------------------------------------- | ----------------------------------------------- |
| **Draft**                                     | The entity does not yet have a live published version | Finish validation and publish it                |
| **Upgrade Available** or **Update Available** | A newer version can be compared with the live version | Review the diff before deployment               |
| **In Progress**                               | DataX is staging or applying a version                | Wait, then refresh                              |
| **Ready to Apply**                            | A target is staged                                    | Deploy or discard that target                   |
| **Applied**                                   | The published version is live                         | Confirm the version and downstream results      |
| **Canceled**                                  | A staged action was discarded                         | Confirm the intended target before trying again |

Labels can vary by entity state, but the detail page is authoritative about the live, selected, and staged versions.

## Compare and deploy

<Steps>
  <Step title="Open the entity">Select its name from **Deployments**.</Step>

  <Step title="Choose a version">
    In **Version history**, select a version other than **Live**.
  </Step>

  <Step title="Review the comparison">
    Check **Overview**, **Columns**, **SQL**, and **Sample rows**. Investigate any **Breaking
    change** indicator.
  </Step>

  <Step title="Take the appropriate action">
    Stage and deploy a newer version, deploy an existing staged version, restore a historical
    version, or discard the staged target.
  </Step>

  <Step title="Verify the result">
    Wait for the workflow to finish, refresh **Deployments**, and confirm the expected version is
    **Live**.
  </Step>
</Steps>

Only one version can be staged for an entity at a time. If another target is already staged, resolve it before selecting a different target.

<Warning>
  **Restore and deploy version** creates a new published version from historical content and makes
  it live. Review lineage and access as carefully as you would for a new change.
</Warning>

For the full comparison model, see [Manage blueprint versions](/datax/catalog/blueprint-versions).