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

# Deploy and maintain

[Building logic](/app-builder/build-backend.md) and [designing the UI](/app-builder/build-frontend.md) is only half the job. Heisenware also lets you test your work in real time, snapshot your progress, and deploy your [Apps to production](https://github.com/heisenware/heisenware-docs/tree/master/production-apps/production-apps-overview.md).

## App testing (test mode)

Before you deploy, test mode verifies your logic and UI directly inside the App Builder. Turn it on and the UI preview becomes fully interactive while all backend logic runs live.

* **How to start**: Click the Test button in the Top Bar.
* **Behavior**: The App starts polling data from connected sources or writing to databases. Form inputs become clickable, and buttons trigger their connected flows.
* **Manual triggers**: Even in test mode, click a trigger on any function block in the [Backend Builder](/app-builder/build-backend.md) to force-start a sequence.

<div align="center"><figure><img src="/files/4Dufw73BRe4ie95eM2o9" alt=""><figcaption><p>TEST button</p></figcaption></figure></div>

## Tags (snapshots)

A tag is a snapshot of your App's entire state, including all backend logic, UI elements, and data bindings.

<figure><img src="/files/ICEhYg9TlF6MTl7GDvU2" alt=""><figcaption><p>Tag icon in the App Builder</p></figcaption></figure>

{% hint style="warning" %}

#### What is not in a tag?

Tags do not store external files (from the [File Explorer](/app-builder/build-backend/file-explorer.md)), database table data, or global themes.
{% endhint %}

### Why use tags?

* **Undo/restore**: Create a save point before trying a risky logic change.
* **Templates**: Export a tag as a `.hwt` file to use it as a starting point for a new App.
* **Sharing**: Share your App configuration with other Heisenware accounts.

### Managing tags

* **Manual creation**: Click the tag icon and give your snapshot a name.
* **Auto-tags**: Heisenware automatically creates a tag every time you deploy an App.
* **Import/export**: Use the Download and Import icons in the tag history to move `.hwt` files between your computer and the platform.

{% hint style="info" %}

#### Recommendation

Before importing, create a new tag of your current App state. This gives you a rollback point if the imported tag isn't what you expected.
{% endhint %}

### Video demo

{% embed url="<https://www.youtube.com/watch?v=3bUe4TnlRQM>" %}

## Deployment

Deployment makes your App available to your users. To push your latest changes live, click DEPLOY in the Top Bar.

<div align="center"><figure><img src="/files/4Dufw73BRe4ie95eM2o9" alt=""><figcaption><p>DEPLOY button</p></figcaption></figure></div>

* **Downtime**: Depending on the App's complexity, it may be offline for 10 to 30 seconds during a fresh deployment.
* **Distribution**: Click the version number in the Top Bar after a successful deploy to find your unique App URL for sharing.

{% hint style="warning" %}
Avoid frequent deployments in live production environments. Every new version prompts users to reload the App.
{% endhint %}

<figure><img src="/files/zKNwDmrI030CvYWu0juR" alt=""><figcaption></figcaption></figure>


---

# 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.heisenware.com/app-builder/deploy-and-maintain.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.