> 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/on-premise.md).

# On-Premise deployment

Deploy Jet Admin services on infrastructure your organization operates.

## Setup sequence

1. Review [Prerequisites](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/prerequisites.md) for supported software, capacity, and network requirements.
2. Follow [Deploy On-Premise Jet Admin with Docker](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/deploy-on-premise-jet-admin-with-docker.md) or the applicable [deployment guide](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/deploy-jetadmin-on-premise.md).
3. Configure the environment using [.env configuration](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/.env-configuration-local-host.md).
4. Complete required domain, authentication, and integration setup.
5. Run [Service Health Check](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/service-health-check.md).
6. Test the complete [published-app journey](/jet-bridge-deployment/publish-your-app/verify-a-release.md) with representative users.

Use the installation path appropriate to your deployment. Follow its supported versions and configuration rather than mixing examples from separate guides.

## Configure the services you use

* [Custom domain configuration](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/.env-configuration-local-host/custom-domain-configuration-on-premise.md)
* [Nginx configuration](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/.env-configuration-local-host/nginx-configuration.md)
* [Email sending configuration](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/.env-configuration-local-host/email-sending-configuration.md)
* [Enabling AI features](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/.env-configuration-local-host/enabling-ai-features-in-on-premises.md)

Hosting the application yourself does not make every feature independent of external services. Identify the network dependencies of authentication, email, AI, and connected resources before restricting traffic.

## Operate and recover

Assign owners for monitoring, updates, secrets, and backups. Use the [Update guide](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/update.md) for platform maintenance and confirm configuration and database recovery separately.

For errors, start with [On-Premise common problems](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/common-problems.md) and the affected service's logs. Use [Cross-Instance Backup & Restore](/jet-bridge-deployment/environments-releases-and-version-control/version-control/cross-instance-backup-and-restore.md) when moving supported backups between instances.


---

# 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/on-premise.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.