> 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/release-notes.md).

# Release Notes

## 1.0.0

Nov 2026

The first release of **Nidhi for Milestone XProtect**, which brings cloud storage as an XProtect archive, looked after from the Management Client.

**Cloud Extension**

* Each recording server gets a **cloud drive** (normally X:, *Nidhi Cloud*) that shows a folder in your bucket. XProtect archives to it like any other archive disk, and plays footage back from it with no restore step. Searching, exporting, evidence locks and bookmarks work as usual.
* Storage: **Amazon S3**, **S3-compatible** storage (such as Wasabi, MinIO or Backblaze B2) and **Google Cloud Storage** (HMAC key of a service account).
* A **local cache** on the recording server takes XProtect's archive runs and uploads them from there. The setup suggests its size from the cameras, their bitrate and the archive schedule.
* **Only XProtect deletes.** Nidhi never deletes footage in the cloud and sets no lifecycle or expiry rules on the bucket, so evidence-locked footage is kept.
* **The drive outlives the service.** Restarting, updating or a crash of the Nidhi Recorder Service doesn't unmount the drive, so XProtect keeps archiving and playing back.
* **Boot order.** At start-up the XProtect Recording Server waits for the cloud drive (at most 3 minutes), so it finds its cloud archive. XProtect's archive index on the drive is put back from the cloud if a power cut emptied it.
* Several sites and recording servers can share one bucket. Each site has its own folder, and each recording server a folder in it.

**Management Client**

* The **Nidhi** plug-in, under **MIP Plug-ins** in the Site Navigation pane.
* A **Dashboard** for the whole site, with one sentence on whether every recording server's footage is safe off the recorder, and one row per recording server with its status, cloud runs in the last 24 hours, footage off-site, upload headroom, outage cover, licence and version. Filters **All**, **Needs you** and **Suggestions**.
* A **page per recording server**, with the tabs [Footage](https://docs.vega365.com/nidhi/management-client/recording-server-page/footage.md) (each storage profile as a timeline from now to its oldest recording, live, local archive and cloud), [Outlook](https://docs.vega365.com/nidhi/management-client/recording-server-page/outlook.md) (how long it can manage without the cloud, and what to change), [Traffic](https://docs.vega365.com/nidhi/management-client/recording-server-page/traffic.md) (upload speed, headroom and the last 24 hours), [Bandwidth schedule](https://docs.vega365.com/nidhi/management-client/recording-server-page/bandwidth-schedule.md) (whether all footage gets uploaded with your upload limits) and [Details](https://docs.vega365.com/nidhi/management-client/recording-server-page/details.md).
* **Suggestions** for storage size limits, upload, archive schedule and cache, worked out from what XProtect actually archived, for the time you plan to manage without the cloud (1 hour to 30 days).
* A **setup wizard** for each recording server, covering licence, storage and key, cloud folder and drive letter, cache, start-up, and adding the archive in XProtect. Each step is saved as you go. The setup proves the key can list, read, write, overwrite, rename and delete in the folder before it is used.
* **Upload bandwidth schedule**: slow down or pause uploads at busy times, with an answer, as you edit, to whether all footage still gets uploaded. Playback is never slowed.
* **Failure alerts** to XProtect's Event Server, as alarms in the Smart Client or events for your own rules (e-mail, SNMP). They cover cloud down, Recording Server stopped, disk almost full, uploads stuck, archive runs failing, expired footage left in the cloud, Nidhi service stopping, certificate ending and failed jobs, each with an optional **back to normal**. Nidhi sets up the data source, events and alarms in XProtect itself.
* **Cloud cleanup** and **Cloud archives** list footage XProtect left in the cloud past its retention, and archives no longer in use, by full bucket path, with Copy and Export to PDF. You decide what to delete, in the provider's console.
* **Update storage key** replaces the cloud key without unmounting the drive, at a quiet moment.
* **Reset configuration** to set a recording server up again. The footage in the cloud stays.
* **Footage Protection Report** (PDF) of the whole site, for a customer or an audit.
* **Export logs** from every recording server and the Management Client PC in one zip, without cloud keys.

**Software management**

* One setup file (`Nidhi-1.0.<build>.msi`) with two parts, the **Management Client plugin** and the **Nidhi Recorder Service**. Silent installation with `ADDLOCAL`.
* Install, update and remove Nidhi on the recording servers **from the Management Client**, over the network, one at a time. Updates keep the cloud drive mounted. Nidhi never installs an older version over a newer one.
* Removal checks first that no XProtect archive uses the cloud drive and that every file is uploaded, then frees the licence (online or with a request file), unmounts the drive and puts the Recording Server's start-up back as it was.

**Licensing**

* One **annual subscription** per recording server, with a **trial** to start. Activation, renewal and handing a licence back from the Management Client, **online** or **offline** with request and response files.

**Security**

* **HTTPS** between the Management Client and the recording servers, on the same port (TCP 48984), with Nidhi's own certificate (renewed by itself) or one from your CA. The Management Client pins each recording server's certificate.
* Cloud keys stay on the recording server. The Management Client never reads them back, and they are never in logs, exports or reports.
* See [Security](https://docs.vega365.com/nidhi/security/security.md).

**Recorder Console**

* On the recording server itself, with its status, the cloud drive, the licence wizard, HTTPS, and a log viewer with export, which also works while the service is stopped.

### Requirements

* Milestone XProtect, tested with **XProtect 2026 R1**.
* Management Client PC: Windows 64-bit, .NET Framework 4.7.2 or later.
* Recording servers: Windows 64-bit, .NET Framework 4.8, WinFsp (installed with Nidhi).

See [Requirements](https://docs.vega365.com/nidhi/getting-started/requirements.md) and [Ports](https://docs.vega365.com/nidhi/getting-started/ports.md).

### Not in this release

* Azure Blob Storage, and archiving to a network share (SMB) or NAS.
* Nidhi's own encryption of the footage. Use the storage provider's server-side encryption.

### Known issues

* **A trial shows as Subscription** on the Dashboard, the recording server's page and the Recorder Console. The end date shown is the trial's.
* **Raising the cloud drive's cache.** When Outlook suggests a larger cache, it names a setting that isn't in this release. Change the cache size with **Reset configuration** and a new setup on the same bucket and folder. The footage in the cloud stays. See [Changing the cache](https://docs.vega365.com/nidhi/management-client/recording-server-page/outlook.md#changing-the-cache).
* **"Error getting volume name of directory 'X:'"** in XProtect's Recording Server log. It's harmless. Archiving and playback on the cloud drive work as usual.
* **No Start-menu shortcut** for the Recorder Console. Run `NidhiRecorderService.exe` in `C:\Program Files\Vega Systems Inc\NidhiRecorderService` as an administrator.

### Upgrading from a pre-release

Recording servers running a pre-release of Nidhi (the *Nidhi Agent*, or Backup mode) need a hand-over to the Nidhi Recorder Service. Contact <support@vega25.com> before updating them.
