> 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/core/idalib/concepts/deployment.md).

# Deployment

Running fully headlessly, idalib is a natural fit for automated environments. This page covers common deployment patterns.

## CI/CD

Use [HCLI](https://hcli.docs.hex-rays.com/) to install IDA and idalib in any CI pipeline. The setup is fully headless and requires only two shell commands. Authentication uses an API key and license ID, passed as environment variables.

See [Getting Started: HCLI option](/core/idalib/getting-started.md#option-1-hcli) for the exact commands.

## GitHub Actions

GitHub Actions is a practical way to run idalib across multiple configurations. A matrix strategy can test many OS, architecture, and version combinations in a single workflow run.

**Resources**: See [HCLI GitHub Action](https://github.com/HexRaysSA/ida-hcli-actions) for a ready-to-use action.

## Docker

Build a Docker image with idalib installed, then push it to your private registry and pull it in any container-based workflow.

**Tip**: IDA is single-threaded. Allocate one vCPU per container.

**Resources**: See [Example Dockerfile](https://github.com/HexRaysSA/ida-hcli/blob/main/docs/advanced/docker/Dockerfile).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hex-rays.com/core/idalib/concepts/deployment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.