> ## Documentation Index
> Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Before you start

> Pre-deployment checklist and environment verification for GitLab integration.

Verify your environment meets these requirements.

## Supported hardware

* CryptoHub, application version `7.0.3.14` or later, with initial setup completed (including loading a Platform Master Key and network configuration).

## Supported operating systems

* **Ubuntu:** LTS versions (20.04, 22.04, 24.04)
* **Debian:** Stable versions (11, 12)
* **Red Hat Enterprise Linux (RHEL):** 8,9
* **CentOS Stream:** 8, 9
* **AlmaLinux:** 8, 9
* **OpenSUSE:** Leap 15.x
* **SUSE Linux Enterprise Server (SLES):** 12 SP5, 15 SP2+

## Required access

* An account on the CryptoHub with administrator permissions.
* Local administrator/root access on the machine where GitLab is installed.

## Network and firewall

* Allow outbound TCP port **2001**(default Host API port) from the computer running GitLab to the CryptoHub, specified by FQDN (for example, `cryptohub.example.com`) or CIDR (for example, `10.0.0.0/24`).

<Warning>
  TLS inspection or SSL proxies can break mutual TLS handshakes. Exempt the CryptoHub FQDN(s) from inspection. Configure the CryptoHub with a FQDN so the exemption applies.
</Warning>

## Other

* **Core GitLab Application:** Manages the code repository, user permissions, and pipeline orchestration.
* **GitLab Runner:** The open-source, lightweight agent responsible for running your CI/CD jobs.

<Note>
  The Core GitLab Application and the GitLab Runner can be installed on different machines, but it is not required.
</Note>