> 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/ida-pro-headless/how-tos/work-offline.md).

# Work offline with a borrowed seat

A machine that cannot reach the license server, such as an isolated VM or an air-gapped analysis host, works with a seat **borrowed** for it. You borrow the seat once, while online, with the license server client shipped in the package. The machine then uses it with no network at all, until you return it or the borrow period ends.

## Prerequisites

* IDA Pro Headless installed, as in [Getting Started](https://docs.hex-rays.com/editions-and-licenses/license-types/ida-pro-headless/getting-started.md).
* A machine that can reach the license server, to borrow and return the seat. It can be the offline machine itself, before it goes offline, or another machine.

## Borrow a seat

Use `borrow-for` with the name of the machine that will use the seat, a name for the borrow, its duration, and the file to write. This example borrows one seat for this machine, for one day:

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

```bash
license-client/license-client -h licsrv.example.com:65434 \
    borrow-for $(hostname) nightly +1d -o nightly.borrow
```

{% endtab %}

{% tab title="macOS" %}

```bash
license-client/license-client -h licsrv.example.com:65434 \
    borrow-for $(UUID) nightly +1d -o nightly.borrow
```

{% endtab %}

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

```powershell
license-client\license-client.exe -h licsrv.example.com:65434 `
    borrow-for $env:COMPUTERNAME nightly +1d -o nightly.borrow
```

{% endtab %}
{% endtabs %}

The first time the client connects to a server, it shows the server's certificate and asks you to trust it. Check the fingerprint with your administrator before you answer `y`.

```
License XX-XXXX-XXXX-XX has been borrowed until 2026-11-12 22:40:05
License XX-XXXX-XXXX-XX borrowed for review-machine as review-machine#nightly-83e90f63236c
Use it on review-machine with IDA_LICENSE=<file>; return it with: return-for review-machine#nightly-83e90f63236c
```

Keep the borrow ID it prints: you need it to return the seat.

## Use the borrowed seat

Copy the borrow file to the offline machine, and set `IDA_LICENSE` to its path instead of a server:

```
$ export IDA_LICENSE=$PWD/nightly.borrow
$ python examples/check_license.py
License  XX-XXXX-XXXX-XX (floating)
Product  IDAPROHEADLESS, edition ida-pro-headless
Valid    until 2026-11-12
Seat     nightly-83e90f63236c, borrowed until 2026-11-12
```

Your scripts, `idat` and the examples now work without any connection to the license server.

## Return the seat

A borrowed seat is not free for anyone else until it is returned or its period ends. When you are done, return it from a machine that can reach the license server:

```bash
license-client/license-client -h licsrv.example.com:65434 \
    return-for review-machine#nightly-83e90f63236c
```

{% hint style="info" %}
Borrow for the time you need, not more: a borrowed seat stays unavailable for the whole period, even if the machine no longer uses it. Administrators can also return a borrowed seat from the **Allocations** page of the license server console.
{% endhint %}


---

# 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/ida-pro-headless/how-tos/work-offline.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.
