> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/jet-bridge-deployment/overview.md).

# Publish & Deploy overview

Take an app from a reviewed preview to a release your intended users can access.

## Release checklist

1. Confirm the app, environment, data connections, and audience.
2. Test pages, data actions, and permissions with representative accounts.
3. [Publish the reviewed app](/jet-bridge-deployment/publish-your-app.md).
4. [Verify the published release](/jet-bridge-deployment/publish-your-app/verify-a-release.md) at its actual address.
5. [Share or embed the app](/jet-bridge-deployment/share-and-embed.md) for the intended audience.
6. Record the released version and the [recovery approach](/jet-bridge-deployment/environments-releases-and-version-control.md).

## Choose your next task

| Section                                                                                             | What you will do                                                                     |
| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| [Publish your app](/jet-bridge-deployment/publish-your-app.md)                                      | Understand Preview and Publish, release changes, and verify the result.              |
| [Share and embed](/jet-bridge-deployment/share-and-embed.md)                                        | Invite the intended audience, embed supported apps, and set social preview metadata. |
| [Custom domains](/jet-bridge-deployment/custom-domains.md)                                          | Connect a subdomain and investigate domain problems.                                 |
| [Environments](/jet-bridge-deployment/environments.md)                                              | Create Staging, configure resources, and test platform updates before Production.    |
| [Version History and recovery](/jet-bridge-deployment/environments-releases-and-version-control.md) | Inspect app versions and plan configuration recovery.                                |
| [Deployment options](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises.md)                    | Choose Cloud, self-hosted Jet Bridge, or On-Premise.                                 |
| [Troubleshooting](/jet-bridge-deployment/logs-and-troubleshooting.md)                               | Diagnose missing changes, access failures, and resource or deployment errors.        |

## Know which operation you need

**Preview** lets a builder inspect the app. **Publish** releases app changes for its audience. **Share** helps people reach or join the app. **Deployment** determines where its supporting services run.

The Jet Admin platform version, an app version in Version History, and an environment backup serve different purposes. Identify which one changed before troubleshooting or attempting recovery.


---

# 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.jetadmin.io/jet-bridge-deployment/overview.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.