> For the complete documentation index, see [llms.txt](https://docs.vega365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vega365.com/nidhi/getting-started/requirements.md).

# Requirements

## XProtect

* Milestone XProtect with the **Management Client** and one or more **Recording Servers**.
* Nidhi is tested with **XProtect 2026 R1**.

## Management Client PC

The PC (or server) where you run the XProtect Management Client to look after Nidhi.

* Windows, 64-bit.
* .NET Framework **4.7.2** or later (installed with the XProtect Management Client).
* Network access to each recording server on the [ports](https://docs.vega365.com/nidhi/getting-started/ports.md) Nidhi uses.
* A Windows account that is an administrator on the recording servers, for **Software management** (installing Nidhi on the recording servers from here).

## Each recording server

* Windows, **64-bit**.
* .NET Framework **4.8**.
* **WinFsp**, the file system driver the cloud drive needs. It comes with Nidhi and is installed with it. The setup offers to install it if it is missing.
* A free drive letter between **D:** and **Z:** for the cloud drive (X: by default).
* Disk space for the **local cache**. That is about two archive runs of footage, at least 10 GB, plus 10 GB kept free. A disk other than the one XProtect records to is best.
* An internet connection (outbound HTTPS) to the cloud storage, fast enough to upload what the cameras record. The Dashboard measures it for you.
* One Nidhi [licence](https://docs.vega365.com/nidhi/getting-started/license-activation.md) (trial or annual subscription).

## Cloud storage

One of:

| Provider                                                         | You need                                                                                                                                                             |
| ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Amazon S3**                                                    | A bucket, its **region**, and an access key of an IAM user (access key ID and secret access key).                                                                    |
| **S3-compatible** storage, such as Wasabi, MinIO or Backblaze B2 | A bucket, the provider's **S3 endpoint URL** (and region, if the provider asks for one), and an access key.                                                          |
| **Google Cloud Storage**                                         | A bucket and an **HMAC key of a service account** (in the Google Cloud console, **Cloud Storage > Settings > Interoperability > Access keys for service accounts**). |

The key must be allowed to **list, read, write, overwrite, rename and delete** in the bucket. That is everything XProtect does on a drive. Nidhi tries each of these when you set a recording server up, and says which one is missing.

{% hint style="warning" %}

* Use a key that belongs to the system, not to a person. That means an IAM user's key on AWS, or a **service account**'s HMAC key on Google Cloud. A personal Google key stops working when that person's access is removed, and a temporary AWS key expires.
* **Don't add lifecycle (expiry) rules** to the bucket. Only XProtect deletes footage. See [Only XProtect deletes](https://docs.vega365.com/nidhi/how-nidhi-works.md#only-xprotect-deletes).
  {% endhint %}
