> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/app-builder/deploy.md).

# Deploy

Deploy an app when its current version is ready for users. Review the live preview and test results first.

## Publish an app

{% stepper %}
{% step %}

### Open the publish panel

Select **Publish** in the app workspace. The panel shows the last published version, its date, and the live URL.

Open or copy the URL, or select **Manage Domains** to manage its domain.

<figure><img src="/files/ucPPP707STAH8WZ72uhK" alt="The publish panel, showing the last published version, its date, and the live URL"><figcaption><p>The publish panel.</p></figcaption></figure>
{% endstep %}

{% step %}

### Complete the publish checklist

Review the dependencies for the published app:

* **Database** — required; select **Connect** when it shows **Not Configured**
* **External Services Used** — confirm each service for **Preview** and **Publish**
* **Environment Variables** — confirm values for **Preview** and **Publish**

Update database, domains, integrations, or environment variables in [App Config](/app-builder/build/app-config.md).

<figure><img src="/files/K5s1WOtYdSDXR9lE5OZA" alt="The publish checklist, showing Database, External Services Used, and Environment Variables status"><figcaption><p>The publish checklist.</p></figcaption></figure>
{% endstep %}

{% step %}

### Publish the version

Select **Publish Changes**. The platform deploys the current version and updates the live URL.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
A published app requires a configured database. Complete the checklist before publishing.
{% endhint %}

### Resolve a failed publish

When publishing fails, Qore shows **Publishing Failed** and **Failed to load preview**. Select one of these actions:

* **Try Again** to retry the publish
* **Fix with AI** to send the failure to the build agent
* **Close** to dismiss the notification

<figure><img src="/files/N0SuzqyUF4vN51Vs0Ck4" alt="The Publishing Failed notification, with Try Again, Fix with AI, and Close actions"><figcaption><p>A failed publish, with recovery actions.</p></figcaption></figure>

{% hint style="info" %}
**Fix with AI** sends the reported issue to Qore's build agent. Review the rebuilt preview before you continue.
{% endhint %}

Select **View Error Details** to open the deploy log. It shows numbered build steps and the underlying error. Use the log to fix the issue, then select **Try Again**.

<figure><img src="/files/poxTM5Cwx94220IqeBu4" alt="The deploy log, with numbered build steps and the underlying error"><figcaption><p>The deploy log's error details.</p></figcaption></figure>

For example, a missing `package.json` appears as an `npm install` failure with error code `ENOENT`.

## Versions

The version selector lists builds newest first. **Latest** marks the newest build. **Published** marks the live version. *Uncommitted changes* marks work outside a version.

Select a version to review or return to it. The published version can differ from the latest build.

## What ships

After testing, the platform packages the project as one deployment unit:

* **Frontend code** — UI components, state managers, and inline styles compile for production
* **Infrastructure settings** — connected database variables, storage links, and custom routing stay mapped to the container
* **Attached agents** — prompts, compliance skills, and reasoning logic travel with the app export package

## Enterprise publishing

The publishing engine supports high-concurrency environments and automates server configuration.

* **High-traffic infrastructure** — the pipeline manages concurrent enterprise publishing requests
* **Request queuing** — deployments process sequentially to prevent stuck states during peak periods
* **Zero-downtime rollouts** — infrastructure updates migrate in the background
* **Production stability** — backward-compatible upgrades preserve published apps through platform updates

## Staging and governance

* **Isolated staging controls** — deploy privately for compliance, risk, and security review
* **Performance-ready clusters** — published apps run on multi-region nodes optimized for sub-second load times

{% hint style="warning" %}
**Publish** is unavailable in **Plan Mode**. To gather feedback before compiling code, use the public view links from **Share Project**. See [Plan](/app-builder/plan.md#collaboration).
{% endhint %}

***

After publishing, use [Operate](/app-builder/operate.md) to track costs and acquisition.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/app-builder/deploy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.