---
title: "Install Natalia On-Premise | 8-Screen VM Appliance - Natalia"
description: "Install the Natalia On-Premise appliance on vSphere, Proxmox or Hyper-V: single VM profile, network flows per mode, 8-screen wizard, first collection."
url: https://getnatalia.com/en/natalia-analytics-on-premise/installation
lang: en
---

[Home](https://getnatalia.com/en/) / [Documentation](https://getnatalia.com/en/documentation) / [On-Premise](https://getnatalia.com/en/natalia-analytics-on-premise) / Installation

# Install Natalia On-Premise

One VM appliance that holds everything: PBX collection, storage, dashboard. An 8-screen wizard guides the first boot. Check the [PBX prerequisites](https://getnatalia.com/en/natalia-analytics-on-premise/alcatel-pbx-prerequisites) first.

## VM sizing

A single hardware profile, whatever the license tier.

<table class="text-sm w-full"><tbody class="text-police-grey"><tr class="border-line border-t first:border-t-0"><th scope="row" class="font-semibold p-4 text-left text-police-titre">vCPU</th><td class="p-4">4</td></tr><tr class="border-line border-t"><th scope="row" class="font-semibold p-4 text-left text-police-titre">RAM</th><td class="p-4">8 GB</td></tr><tr class="border-line border-t"><th scope="row" class="font-semibold p-4 text-left text-police-titre">System disk</th><td class="p-4">20 GB, replaced at each upgrade</td></tr><tr class="border-line border-t"><th scope="row" class="font-semibold p-4 text-left text-police-titre">Data disk</th><td class="p-4">100 GB, label <code>NATALIA_DATA</code>, kept across upgrades</td></tr></tbody></table>

### License tiers

The tier sets the default limits written in the license:

|  | Small | Medium | Large |
| --- | --- | --- | --- |
| PBX | 5 | 20 | 100 |
| Users | 10 | 50 | 200 |

Changing tier means installing a new license file. Beyond Large, contact us.

## Supported hypervisors

VMware vSphere / ESXi

Proxmox VE

Microsoft Hyper-V

Standard OVA image (OVF archive).

## Network flows per mode

| Mode | LAN flows | Internet flows |
| --- | --- | --- |
| Strict | Inbound: admin browsers on 443 (80 redirects to HTTPS). Outbound: PBX on 22 (OXE) or 30021 (OXO). | None. |
| \+ 72h Support | One-off remote support access, on your trigger, 72 h at most, per the Support DPA. |
| Connected | Permanent outbound HTTPS to Natalia. |

[Compare the three contractual modes](https://getnatalia.com/en/natalia-analytics-on-premise/contractual-modes)

Step 1/5

## Download and verify the OVA

From the partner portal (your integrator partner or Natalia). A SHA-256 checksum file ships with the image: check it before import.

```bash
sha256sum -c <image>.ova.sha256
```

bash

Step 2/5

## Import into the hypervisor

Standard OVF import. Attach the two disks (system and data) and allocate the resources above.

Data disk required

The appliance refuses to start if the data disk is not mounted. The reason is printed on the serial console.

Step 3/5

## First boot

The initial admin password is displayed once on the serial console, and stored in the first-connection file of the data disk. Then open the web interface over HTTPS from your LAN (self-signed certificate at first boot).

Password lost: see [appliance access](https://getnatalia.com/en/natalia-analytics-on-premise/troubleshooting#acces-appliance).

![Natalia appliance administrator login screen](https://getnatalia.com/en/ova-agent-first-boot.732f5272.png)

Administrator login: paste the initial password.

Step 4/5

## 8-screen wizard

<table class="bg-white text-sm w-full"><tbody class="text-police-grey"><tr class="border-line border-t first:border-t-0"><td class="font-semibold p-4 text-police-titre w-10">1</td><th scope="row" class="font-semibold p-4 text-left text-police-titre">Welcome</th><td class="p-4">Overview of the steps.</td></tr><tr class="border-line border-t first:border-t-0"><td class="font-semibold p-4 text-police-titre w-10">2</td><th scope="row" class="font-semibold p-4 text-left text-police-titre">Admin password</th><td class="p-4">Enter the initial password, then set your own.</td></tr><tr class="border-line border-t first:border-t-0"><td class="font-semibold p-4 text-police-titre w-10">3</td><th scope="row" class="font-semibold p-4 text-left text-police-titre">License</th><td class="p-4">Paste or drop the signed license.toml file.</td></tr><tr class="border-line border-t first:border-t-0"><td class="font-semibold p-4 text-police-titre w-10">4</td><th scope="row" class="font-semibold p-4 text-left text-police-titre">Network and mode</th><td class="p-4">Network checks and choice of the contractual mode.</td></tr><tr class="border-line border-t first:border-t-0"><td class="font-semibold p-4 text-police-titre w-10">5</td><th scope="row" class="font-semibold p-4 text-left text-police-titre">PBX</th><td class="p-4">Declare one or more OXE / OXO, test each connection.</td></tr><tr class="border-line border-t first:border-t-0"><td class="font-semibold p-4 text-police-titre w-10">6</td><th scope="row" class="font-semibold p-4 text-left text-police-titre">First collection</th><td class="p-4">The appliance fetches the first tickets. MCP setup.</td></tr><tr class="border-line border-t first:border-t-0"><td class="font-semibold p-4 text-police-titre w-10">7</td><th scope="row" class="font-semibold p-4 text-left text-police-titre">Summary</th><td class="p-4">Review of the configuration before validation.</td></tr><tr class="border-line border-t first:border-t-0"><td class="font-semibold p-4 text-police-titre w-10">8</td><th scope="row" class="font-semibold p-4 text-left text-police-titre">Done</th><td class="p-4">Access to the dashboard.</td></tr></tbody></table>

The PBX collector is built into the appliance: nothing else to install. PBX screen details: [OXE](https://getnatalia.com/en/natalia-analytics-on-premise/oxe-configuration), [OXO](https://getnatalia.com/en/natalia-analytics-on-premise/oxo-configuration). Test codes: [error codes](https://getnatalia.com/en/natalia-analytics-on-premise/error-codes).

![PBX configuration form: type, IP, port, login](https://getnatalia.com/en/ova-agent-pbx-config-oxe.fdffda8a.png)

PBX screen: type, IP, port, login.

![Test connection button clicked, validation in progress](https://getnatalia.com/en/ova-agent-test-connection-ok.f1c4ecd0.png)

Test the connection before saving.

Step 5/5

## Verify CDR collection

Open the dashboard and check that the first tickets arrive. Collection runs every 30 minutes by default (adjustable from 5 min to 24 h). Message "no CDR file detected yet": see [troubleshooting](https://getnatalia.com/en/natalia-analytics-on-premise/troubleshooting#collecte).

![Appliance dashboard with PBX state](https://getnatalia.com/en/ova-agent-dashboard.5d708052.png)

Dashboard, visible on your LAN only.

## Next

Plan the [data disk backup](https://getnatalia.com/en/natalia-analytics-on-premise/backup-restore), note the [license expiry](https://getnatalia.com/en/natalia-analytics-on-premise/license-lifecycle), read the [security model](https://getnatalia.com/en/natalia-analytics-on-premise/security-on-premise).

Trade secret notice

The selection, organization and presentation of the information contained in this documentation constitute a proprietary asset of Natalia. The precise internal architecture (software versions, implementation choices, data schemas) is a trade secret under article L. 151-1 of the French Commercial Code and is not publicly disclosed. Post-installation details are governed by the signed proprietary license. Full CISO audit available under NDA — contact [security@getnatalia.com](mailto:security@getnatalia.com).

Last updated : October 5, 2026

[Suggest an edit](mailto:doc@getnatalia.com?subject=Doc%20edit%3A%20natalia-analytics-on-premise%2Finstallation)