> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-commerce/add-ons/packages/deploy.md).

# Deploy

This is the documentation for the Deploy package for Umbraco Commerce.

Umbraco Commerce Deploy is a free and open-source add-on package for Umbraco Commerce. It provides Umbraco Deploy and Umbraco Cloud support, allowing the transfer of Umbraco Commerce settings between environments.

In this section, we will guide you through the key steps necessary to get you started with the Deploy package for Umbraco Commerce.

It is assumed that you already have one of the following setups:

* A Umbraco Cloud site with Umbraco Commerce installed and configured.
* A Umbraco CMS site configured with Umbraco Deploy and Umbraco Commerce installed and configured.

If you are not at this stage yet, read the [core Umbraco Commerce documentation](/umbraco-commerce/readme.md) to learn how to get started.

## Useful links

As well as the content in these documentation, the following links may prove useful when using this package:

* [Umbraco Commerce Deploy source code](https://github.com/umbraco/Umbraco.Commerce.Deploy)
* [Umbraco Commerce Deploy issue tracker](https://github.com/umbraco/Umbraco.Commerce.Deploy)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-commerce/add-ons/packages/deploy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.