> 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/cloud-jet-bridge-and-on-premises.md).

# Deployment options

Choose where the app's supporting services run and who will operate them.

| Approach               | What you operate                                                                                     | Start with                                                                                     |
| ---------------------- | ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Cloud                  | Your app configuration, connected resources, identities, and access policy                           | [Cloud](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/cloud.md)                      |
| Self-hosted Jet Bridge | The bridge service and its resource connectivity; the Jet Admin interface remains a separate service | [Self-hosted Jet Bridge](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/jet-admin.md) |
| On-Premise             | The deployed Jet Admin services and their supporting infrastructure                                  | [On-Premise deployment](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise.md) |

## Decide before installation

Document where source data lives, which services may communicate, who manages credentials, and which authentication system users need. Include AI providers, email, and external integrations in the dependency review when you use them.

Confirm plan and deployment availability for your organization before committing to a hosting approach. The comparison above describes operating responsibilities, not a guarantee of a particular network or data-processing boundary.

## Follow the matching setup path

Use the installation and configuration guides under the selected approach. Confirm required software and versions from the guide for that deployment; do not combine commands from different installation methods.

After setup, validate service health, resource access, user sign-in, and [the published app](/jet-bridge-deployment/publish-your-app/verify-a-release.md). A healthy service response alone does not prove the whole application works.

See [resource and deployment troubleshooting](/jet-bridge-deployment/logs-and-troubleshooting/resource-and-deployment-errors.md) for failures and [Security and data handling](/access-and-sharing/data-privacy-and-security.md) for storage and recovery responsibilities.


---

# 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/cloud-jet-bridge-and-on-premises.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.