> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/editions-and-licenses/license-server/admin/headless-license-server-setup.md).

# Headless License Server setup

IDA Pro Headless takes its seats from a Hex-Rays license server, the same server that serves [floating licenses](https://docs.hex-rays.com/editions-and-licenses/license-types/floating-license/overview.md) to your analysts. This page covers what to prepare on the server and on the network before your scripts and agents connect.

## Requirements

* Hex-Rays License Server **9.5.2 or later**. Earlier versions do not serve headless seats.
* Your IDA Pro Headless license, added to the server.
* Network access from every machine that runs scripts or agents to the server's RPC port (65434 by default).

## Set up the server

### If you do not have a license server yet

Install it as described in [License Server Administration](https://docs.hex-rays.com/editions-and-licenses/license-server/admin/license-server.md), then add your IDA Pro Headless license.

{% hint style="info" icon="desktop-arrow-down" %}

### Get the server files with HCLI

On the server, [HCLI](https://hcli.docs.hex-rays.com/) downloads the license server package and its license without a browser:

```bash
uvx ida-hcli download                         # pick the IDA License Server package
uvx ida-hcli license get --type LICENSE_SERVER
```

{% endhint %}

From 9.5.2, the license server can also run as a Docker container: the license server package includes what you need to build the image.

### If you already have a license server

If your analysts already use floating licenses, you do not need a second server:

1. Upgrade the server to 9.5.2 or later. See [Upgrading the server](https://docs.hex-rays.com/editions-and-licenses/license-server/admin/license-server.md#upgrading-the-server).
2. Add your IDA Pro Headless license to the server, next to your existing licenses.

## Open the network to your machines

A license server set up for analysts is reachable from their workstations. Your scripts and agents may run elsewhere: build servers, analysis clusters, containers, cloud VMs. Make sure those machines can reach the server's RPC port too.

To check from a machine:

{% tabs %}
{% tab title="Linux, macOS" %}

```bash
nc -vz licsrv.example.com 65434
```

{% endtab %}

{% tab title="Windows (PowerShell)" %}

```powershell
Test-NetConnection licsrv.example.com -Port 65434
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
In a virtual machine, the route to the license server must reach the VM too: give it a network adapter that can reach the server (for example NAT), or run your VPN client inside the VM.
{% endhint %}

Machines that cannot be given access, such as air-gapped hosts, work with [borrowed seats](https://docs.hex-rays.com/editions-and-licenses/license-types/ida-pro-headless/how-tos/work-offline.md).

## Give your users the connection string

Scripts and agents find the server through the `IDA_LICENSE` environment variable:

```
IDA_LICENSE=server:host=licsrv.example.com:port=65434
```

The **Dashboard** of the administration console shows this value, ready to copy, in its **IDA Configuration** card. Ask your users to add `:instance=<name>` to tell their workloads apart. See [Environment variables](https://docs.hex-rays.com/editions-and-licenses/license-types/ida-pro-headless/reference/environment-variables.md#ida_license).

## Follow seat usage

In the [administration console](https://docs.hex-rays.com/editions-and-licenses/license-server/admin/license-server.md#the-administration-console):

* The **Dashboard** shows the seats in use, and the free seats of each license, including your IDA Pro Headless license.
* The **Allocations** page lists every seat in use, with the user, the machine and the instance name from `IDA_LICENSE`. You can check in a seat that a vanished process left behind, or return a borrowed seat early.

Use the peak usage to size your pool of headless seats. See [Headless seats](https://docs.hex-rays.com/editions-and-licenses/license-types/ida-pro-headless/concepts/headless-seats.md#how-many-seats-do-you-need).


---

# 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.hex-rays.com/editions-and-licenses/license-server/admin/headless-license-server-setup.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.
