> For the complete documentation index, see [llms.txt](https://documentation.ocsinventory-ng.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ocsinventory-ng.org/administrator-docs/system-requirements.md).

# System Requirements

Below are the key requirements to ensure a smooth deployment of the OCS Inventory solution.

## **Hardware Requirements**

{% tabs %}
{% tab title="Server requirements" %}

#### Minimum:

* **Processor**: Dual-Core, 2.0 GHz
* **Memory**: 4 GB RAM
* **Storage**: 20 GB free disk space

#### Recommended:

* **Processor**: Quad-Core, 3.0 GHz or higher
* **Memory**: 8 GB RAM or more
* **Storage**: 50 GB free disk space for logs and inventories
  {% endtab %}

{% tab title="Agent requirements" %}
The OCS agent can run on most operating systems with minimal resource usage. Ensure client devices meet their OS's basic requirements.
{% endtab %}
{% endtabs %}

## **Operating System Compatibility**

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

* Debian-based distributions (e.g., Debian, Ubuntu)
* Red Hat-based distributions (e.g., RHEL, CentOS)
  {% endtab %}

{% tab title="Agent" %}
Refer to this compatibility matrix for the agent:

| Base OS                 | Supported versions                    | Notes                                              |
| ----------------------- | ------------------------------------- | -------------------------------------------------- |
| RHEL                    | 8, 9, 10                              | Version 7 requires extra compilation work          |
| CentOS                  | 8, 9, 10                              | Same constraints as RHEL                           |
| Rocky Linux / AlmaLinux | 8, 9, 10                              | Same constraints as RHEL                           |
| Ubuntu                  | 22.xx, 24.xx, 26.xx                   | 20.04 is still supported, but is EOL               |
| Debian                  | 11, 12, 13                            | Debian 11 is older but still has extended support. |
| Windows                 | 10, 11                                | Dart support starts with Windows 10.               |
| macOS                   | Sonoma (14), Sequoia (15), Tahoe (26) | Build separately for Intel and ARM.                |

{% hint style="info" %}
For older operating systems, the 2.x legacy agent can still be used. See [Managing legacy devices](/administrator-docs/agent-setup/managing-legacy-devices.md).
{% endhint %}
{% endtab %}
{% endtabs %}

## **Database Requirements**

* **MySQL**: version 8.0 or newer (MariaDB equivalent supported)
* **PostgreSQL**: version 17.0 or newer

## **Software Dependencies**

* Python 3.10 or newer for backend scripts or source installation.

## **Network Requirements**

Ensure the following ports are open for communication:

* **80/443**: Web console access and backend API access
* **3306**: MySQL database
* **5432**: PostgreSQL database

## **Additional Notes**

For information regarding legacy agents, please refer to the [OCS Inventory 2.X official documentation](https://wiki.ocsinventory-ng.org/).


---

# 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://documentation.ocsinventory-ng.org/administrator-docs/system-requirements.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.