> For the complete documentation index, see [llms.txt](https://docs.presearch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.presearch.io/nodes/overview/hardware-and-system-requirements.md).

# Hardware and system requirements

## Software requirements

* **64bit enabled operating system** with virtualization capabilities to run a container
* **Docker** service to run containers (Presearch preferred and supported option)

This is by default covered in vast majority of Linux distributions. We know there are dozen of good Linux based distributions, but most used or recommended distribution is currently Ubuntu distribution for running Presearch Nodes.

{% hint style="warning" %}
Raspberry Pi Models 3/4 are also supported if they are running on a [64-bit Raspberry Pi operating system](https://docs.presearch.org/nodes/raspberry-pi).
{% endhint %}

Nodes were successfully installed on VPS machines with minimal resources:

* 1 CPU (x64 or arm64 architecture)
* 768 MB RAM (under minimized OS editions even 512 MB RAM)
* 10 GB storage
* 100+ Mbit network link

{% hint style="warning" %}
Docker image is only for 64bit architectures like x64 / ARM64 based CPU's for now. 
{% 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 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.presearch.io/nodes/overview/hardware-and-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.