---
title: "On-Premise Phone Analytics | GDPR Sovereign - Natalia"
description: "Sovereign VM appliance to analyse your Alcatel OXE/OXO CDRs inside your datacenter. GDPR Strict mode, no outbound data, guided 30-45 minutes deployment."
url: https://getnatalia.com/en/analytics-on-premise
lang: en
---

  

On-Premise edition

# Analyse your Alcatel CDRs.  
Inside your datacenter.  
Without Internet.

Natalia Analytics On-Premise is a VM appliance you deploy on your own infrastructure. Your phone taxation data never leaves your network.

GDPR Strict mode No outbound data Alcatel OXE / OXO 3 contractual modes

[Request an on-premise demo](https://getnatalia.com/en/analytics-on-premise#contact) [Open the documentation](https://getnatalia.com/en/natalia-analytics-on-premise)

https://natalia.lan/analytics-cdr **LAN**

![Natalia analytics CDR dashboard: volume per day, inbound/outbound ratio, top callers, duration histogram, cost per extension](https://getnatalia.com/en/dashboard-cdr-overview-window.271fc4d3.png)

## Why on-premise for phone CDRs

Phone CDRs are sensitive: they contain extension numbers, calling parties, durations, and destinations. Sending them outside your network is rarely a choice, often a constraint.

## What sets Natalia Analytics On-Premise apart

-   ### Full sovereignty

    In Strict mode, no outbound connection, no DPA to sign. You remain the sole controller of your data.

-   ### Deploy in 30-45 min

    OVA appliance ready to import. Guided 8-screen wizard. VMware / Proxmox / Hyper-V supported.

-   ### Native Alcatel CDR analysis

    Alcatel OXE and OXO supported out of the box. Taxation reports, hourly traffic, costs per extension.

## Features

-   Dashboard for phone taxation: costs per extension and direction.

-   CDR traffic analysis: inbound, outbound, internal, missed.

-   CSV / JSONL export for internal re-billing.

-   RBAC with 4 roles: Viewer, Admin, Auditor, Integrator.

-   Immutable audit log, available to auditors.

-   GDPR art.17 selective erasure per employee extension, audited and certified.

-   Phone numbers encrypted at rest and displayed masked; no interface returns the full number.

## Inside the dashboard

Real screens from the local appliance — same data your teams see on the LAN.

-   ![Dashboard — narrowed date window](https://getnatalia.com/en/dashboard-cdr-overview-window.271fc4d3.png)

    ### Date window

    Filter by date range to isolate a campaign, an audit period, an incident.

-   ![Dashboard — outbound calls only](https://getnatalia.com/en/dashboard-cdr-overview-outbound.f3d1b5e3.png)

    ### Direction filter

    Drill into outbound only to track cost per extension.

-   ![Dashboard — full overview](https://getnatalia.com/en/dashboard-cdr-overview.e7d01d9e.png)

    ### Full overview

    All directions, all extensions — the snapshot a CFO or a head of service opens daily.

Volume per day · Inbound / outbound ratio · Top callers by duration · Duration histogram · Cost per extension.

## Pick your sovereignty level

Three contractual modes for one appliance. Strict mode is the only mode where you stay a pure software publisher — no art.28 sub-processor relationship.

|  | Strict | +72h Support | Connected |
| --- | --- | --- | --- |
| DPA required | None | Light Support DPA | Full art.28 DPA |
| Outbound network | None | Remote support on your trigger, 72 h max | Permanent HTTPS |
| Use case | Bank, mutual, defense, OIV | Mid-market, reactive support | Qualitative analysis of conversations — [Natalia Analytics SaaS](https://getnatalia.com/en/analytics) |
| RFP cycle | −3 to −6 weeks | −1 to −2 weeks | Standard SaaS |

Want the full matrix with sub-processors, network diagrams and a decision tree? [Open the canonical reference →](https://getnatalia.com/en/natalia-analytics-on-premise/contractual-modes)

New to the sovereignty argument? [Read the sovereign voice AI overview →](https://getnatalia.com/en/sovereignty)

## What the appliance provides

What the appliance provides, documented in the public documentation.

<table class="op-t"><tbody><tr><td>Air-gapped Strict mode</td><td class="n">Yes, explicit, no DPA</td></tr><tr><td>Alcatel OXE / OXO native</td><td class="n">Yes</td></tr><tr><td>GDPR art.17 selective erasure</td><td class="n">Yes, audited</td></tr><tr><td>Immutable audit log</td><td class="n">Yes, chained (integrity check)</td></tr><tr><td>Reversibility (open formats)</td><td class="n">CSV / JSONL</td></tr><tr><td>Pricing</td><td class="n">On request</td></tr></tbody></table>

Comparing with a specific tool? [Read the sourced Natalia vs Jusan comparison →](https://getnatalia.com/en/comparisons/natalia-vs-jusan)

## Technical prerequisites

One VM profile for every deployment.

<table class="op-t"><tbody><tr><td>vCPU</td><td>4</td></tr><tr><td>RAM</td><td>8 GB</td></tr><tr><td>System disk</td><td>20 GB, replaced at each upgrade</td></tr><tr><td>Data disk</td><td>100 GB, kept across upgrades</td></tr></tbody></table>

The license tier sets the default capacity: Small 5 PBX / 10 users, Medium 20 PBX / 50 users, Large 100 PBX / 200 users.

VMware vSphere / ESXi

Proxmox VE

Microsoft Hyper-V

## GDPR & legal guarantees

### DPA Strict (no signature needed)

Qualification: pure software publisher, no controller / processor relationship.

<https://getnatalia.com/en/legal/dpa/dpa-strict>

### Light Support DPA (72h)

Art.28 §3 a-h scoped to point-in-time interventions, with intervention log.

<https://getnatalia.com/en/legal/dpa/dpa-support>

### Full art.28 DPA (Connected)

Standard SaaS DPA with sub-processor schedule (sub-processors documented).

<https://getnatalia.com/en/legal/dpa/dpa-connected>

### DPIA template (>5000 lines)

CNIL impact-assessment template for organizations crossing the systematic-monitoring threshold.

<https://getnatalia.com/en/legal/dpia-template-client>

**Trade secret notice.** The internal architecture, source code, anti-tamper mechanisms and per-tenant isolation policies of the appliance constitute trade secrets within the meaning of article L. 151-1 of the French Commercial Code. They are disclosed only under written NDA, to qualified prospects engaged in a documented procurement process. Contact [security@getnatalia.com](mailto:security@getnatalia.com).

## Sovereignty & GDPR: frequent questions

### Does an on-premise voice AI really keep data in-house?

Yes. Natalia Analytics On-Premise is an appliance deployed in your own datacenter: phone-metering data never leaves your network. In Disconnected strict mode, the appliance has no outbound internet access, so no transfer and no article 28 GDPR sub-processor relationship to document.

### What is a sovereign AI phone system?

A sovereign AI phone system processes voice and call metadata without relying on a third-party cloud or on infrastructure subject to extraterritorial laws. With Natalia's disconnected on-premise edition, processing stays on your own infrastructure, in France, under your sole control.

### Is the on-premise edition GDPR-compliant?

Yes, with three contractual modes. In Disconnected strict you remain a pure software publisher, with no controller/processor relationship. There is therefore no article 28 DPA to negotiate, which shortens the RFP cycle by several weeks. The 72h Support and Connected modes add a DPA scaled to the actual need.

### Where is the data hosted with Natalia On-Premise?

Your data stays on your own infrastructure: VMware, Proxmox or Hyper-V, in your datacenter in France. No call data needs to transit through an external cloud. You keep physical and legal control of your data end to end.

## Ready to deploy?

Reach out for an on-premise demo on your own VMware, Proxmox or Hyper-V environment. Response within 48h.

[Request an on-premise demo](https://getnatalia.com/en/contact) [Open the documentation](https://getnatalia.com/en/natalia-analytics-on-premise)

Looking for qualitative textual analysis of your conversations, alongside CDR? [See Natalia Analytics SaaS →](https://getnatalia.com/en/analytics)