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

# License Types

Hex-Rays offers IDA licenses for individual users, for teams that share a pool of seats, and for scripts and agents that run without a user interface.

## Which license type fits how you use IDA?

<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><h3>Named and computer licenses</h3></td><td>For individual users: a named license is linked to a person through their email address, a computer license to one computer.</td><td><a href="https://docs.hex-rays.com/editions-and-licenses/license-types/named-and-computer-licenses.md">Named and Computer Licenses</a></td></tr><tr><td><h3>Floating licenses</h3></td><td>For teams: a pool of concurrent seats served by your Hex-Rays License Server. IDA Pro only, for business use.</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>Headless licenses</h3></td><td>For scripts, pipelines and AI agents: headless seats on your License Server, taken only while a script or agent runs.</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>


---

# 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-types.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.
