> 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/jet-admin.md).

# Self-hosted Jet Bridge

Jet Bridge is an open-source backend that connects the Jet Admin interface to supported resources through an API. In this deployment model, you operate the bridge service and its connection to your resources.

## Choose an installation method

* [Python installation](/user-guide/data-sources/databases/sql-databases/python-app-installation.md)
* [Docker installation](/user-guide/data-sources/databases/sql-databases/docker-installation.md)
* [Django integration](/user-guide/data-sources/databases/django-framework-package.md)

Follow the requirements and configuration for the chosen method.

## Understand the components

| Component           | Responsibility to confirm                                                              |
| ------------------- | -------------------------------------------------------------------------------------- |
| Jet Admin interface | App interface and its service dependencies.                                            |
| Jet Bridge          | API service, runtime configuration, authentication integration, and resource requests. |
| Database or API     | Source data, credential scope, and its own recovery process.                           |
| Network and proxy   | Reachability, HTTPS configuration, and any required forwarding.                        |

The bridge is not the same as deploying all Jet Admin services On-Premise. Review the actual request path and authentication dependencies of your installation instead of assuming it has no external service communication.

## Configure and verify

1. Install the bridge using the selected guide.
2. Review [Configuration](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/jet-admin/configuration.md) and the relevant resource settings.
3. Confirm the expected browser, bridge, resource, and authentication connectivity.
4. Test a permitted read and write with synthetic data.
5. Test a denied action with a restricted account.
6. Document how the bridge is monitored, updated, and recovered.

For special setups, see [SSO on self-deployed Jet Bridge](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/jet-admin/sso-on-self-deployed-jet-bridge.md) and [Using a self-deployed HTTP proxy](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/jet-admin/using-self-deployed-http-proxy.md). For failures, use [Jet Bridge common problems](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/jet-admin/common-problems.md).


---

# 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/jet-admin.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.