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

# Prerequisites

Verify your server, operating system, network, and software requirements before deploying JetAdmin On-Premise.

Review and complete the following requirements before starting the JetAdmin On-Premise installation.

## Requirements

* Command-line experience
* Experience with and setups involving Docker Engine and Docker Compose are required.

#### Supported Operating Systems

JetAdmin On-Premise supports the following operating systems:

* Ubuntu 22.04+
* Debian 13+
* CentOS Stream 9+
* RHEL 10+

### Server Requirements

* Minimum 4 CPU
* Minimum 8 GB RAM
* 50 GB available storage
* Public IP address (required for HTTPS deployments)

#### Connect to Your Server

Before running the installation commands, connect to your server using SSH.

Example:

```bash
ssh username@your-server-ip
```

If you are running JetAdmin on your local machine, open a terminal application and run the commands locally.

#### Domain Requirements (HTTPS Deployments Only)

If you plan to deploy JetAdmin with HTTPS:

* Own a domain name
* Have access to your DNS provider
* Be able to create DNS records

Examples:

* Cloudflare
* Namecheap
* GoDaddy
* Route53

### Required Software

Install Docker:

```bash
sh <(curl -s https://get.docker.com)
```

Install Docker Compose:

```bash
sudo curl -L https://github.com/docker/compose/releases/latest/download/docker-compose-Linux-x86_64 -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
```

Install Nginx:

```bash
sudo apt install nginx -y
```

### Required Open Ports

```bash
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
```

Required ports:

| Port | Purpose                  |
| ---- | ------------------------ |
| 80   | Let's Encrypt validation |
| 443  | HTTPS access             |

### Verification

```bash
docker --version
docker-compose --version
nginx -v
```

<div align="left"><figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FvDsvJkGYyZxCVYXlZ7ke%2Fimage.png?alt=media&amp;token=3cbbecf2-d68d-497b-8f96-3deb810ae929" alt=""><figcaption></figcaption></figure></div>


---

# 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/prerequisites.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.