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

# License Server

The Hex-Rays License Server serves floating licenses to your analysts and headless licenses to your scripts and agents, from a single server on your own infrastructure.

The Hex-Rays License Server runs on your own infrastructure and hands out IDA seats from your pool of licenses.

## License types it serves

One server handles both license types side by side.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>Floating licenses</h3></td><td>For analysts. An analyst takes a seat when they work in IDA Pro, and the seat goes back to the pool when they close it.</td><td><a href="https://docs.hex-rays.com/editions-and-licenses/license-types/floating-license.md">Floating License</a></td></tr><tr><td><h3>IDA Pro Headless licenses</h3></td><td>For scripts, pipelines and AI agents. A script or agent takes a headless seat while it has a database open. Headless seats require License Server 9.5.2 or later.</td><td><a href="https://docs.hex-rays.com/editions-and-licenses/license-types/ida-pro-headless.md">Headless License</a></td></tr></tbody></table>

If your analysts already use floating licenses, your scripts and agents can use the same server, but they need their own [IDA Pro Headless license](https://docs.hex-rays.com/editions-and-licenses/license-types/ida-pro-headless.md).

## Admin resources

Guidance for administrators who install, configure and manage the License Server.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Administer a License Server</strong></td><td>Install and set up the License Server, then manage it from the administration console.</td><td><a href="https://docs.hex-rays.com/editions-and-licenses/license-server/admin/license-server.md">License Server Administration</a></td></tr><tr><td><strong>Installation Checklist</strong></td><td>A quick, step-by-step guide to installing and configuring your License Server.</td><td><a href="https://docs.hex-rays.com/editions-and-licenses/license-server/admin/license-server/license-server-checklist.md">Installation Checklist</a></td></tr><tr><td><strong>Migrate a License Server</strong></td><td>Choose the migration path for a Flexera-based server or a previous Hex-Rays License Server deployment.</td><td><a href="https://docs.hex-rays.com/editions-and-licenses/license-server/admin/hex-rays-license-server-migration-guide.md">Migrate to the current Hex-Rays License Server</a></td></tr><tr><td><strong>Configure License Server on WSL</strong></td><td>Run the License Server in Windows Subsystem for Linux.</td><td><a href="https://docs.hex-rays.com/editions-and-licenses/license-server/admin/license-server-on-wsl.md">Configure Hex-Rays License Server on WSL</a></td></tr><tr><td><strong>Headless License Server setup</strong></td><td>Prepare the License Server and the network for IDA Pro Headless.</td><td><a href="https://docs.hex-rays.com/editions-and-licenses/license-server/admin/headless-license-server-setup.md">Headless License Server setup</a></td></tr></tbody></table>

For what is new in each version of the License Server, see the [Release Notes](https://docs.hex-rays.com/editions-and-licenses/license-server/release-notes.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.hex-rays.com/editions-and-licenses/license-server.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.
