--- title: "Natalia Analytics On-Premise - Documentation" description: "Natalia VM appliance documentation. 3 contractual modes (Strict / +72h / Connected), RFP-ready security, guided installation." url: https://getnatalia.com/en/natalia-analytics-on-premise/ lang: en --- [Home](https://getnatalia.com/en/) / [Documentation](https://getnatalia.com/en/documentation) / On-Premise edition On-Premise documentation # Natalia Analytics On-Premise Documentation VM appliance running on your infrastructure. 3 contractual modes depending on your GDPR requirements. No data has to leave your datacenter. ### Data sovereignty Your data stays on your infrastructure. In Strict mode, no outbound connection is required. ### 3 contractual modes Strict (no DPA) / +72h Support (light DPA) / Connected (full art.28 DPA). You choose. ### GDPR by design Pseudonymization, RBAC, immutable audit log, GDPR art.17 (right to erasure). ## Pick your contractual mode Three modes, three GDPR postures, one appliance. The choice is yours, made at installation in the first-boot wizard. | | Strict Air-gapped | +72h Support On-demand remote support | Connected Permanent link | | --- | --- | --- | --- | | Outbound connectivity | None | One-off remote support access, on your trigger, 72 h at most, per the Support DPA | Permanent HTTPS to Natalia | | DPA art.28 | None required (you are sole controller) | Light Support DPA, art.28 §3 a-h | Full art.28 DPA with sub-processor schedule | | Typical use case | Bank, mutual, defense, public-sector OIV | Mid-market, integrators wanting reactive support | Organizations that accept a permanent outbound flow to Natalia | | RFP cycle gain | −3 to −6 weeks (no DPA review) | −1 to −2 weeks (light DPA) | Standard SaaS cycle | [See the full matrix and decision tree](https://getnatalia.com/en/natalia-analytics-on-premise/contractual-modes) ## Architecture per mode One appliance, three network postures. The diagram you can show your CISO depends on the mode you pick. Mode 1 ### Strict flowchart TB subgraph LAN\_S\["Your premises"\] PBX\_S\["Alcatel PBX"\] APP\_S\["Natalia appliance"\] USER\_S\["Your teams"\] end PBX\_S -.->|Billing tickets| APP\_S USER\_S -->|HTTPS local| APP\_S style LAN\_S fill:#eef2ff,stroke:#6366f1,stroke-width:2px Zero outbound connection. The appliance never talks to Natalia or the public internet. Mode 2 ### +72h Support flowchart TB subgraph LAN\_T\["Your premises"\] PBX\_T\["Alcatel PBX"\] APP\_T\["Natalia appliance"\] USER\_T\["Your teams"\] end SUPPORT\_T\["Natalia support"\] PBX\_T -.->|Billing tickets| APP\_T USER\_T -->|HTTPS local| APP\_T APP\_T -.->|On your trigger, 72 h max| SUPPORT\_T style LAN\_T fill:#eef2ff,stroke:#6366f1,stroke-width:2px style SUPPORT\_T fill:#fef3c7,stroke:#d97706 One-off remote support access, on your trigger, 72 h at most, per the light Support DPA (art.28). Mode 3 ### Connected flowchart TB subgraph LAN\_C\["Your premises"\] PBX\_C\["Alcatel PBX"\] APP\_C\["Natalia appliance"\] USER\_C\["Your teams"\] end CLOUD\_C\["Natalia"\] PBX\_C -.->|Billing tickets| APP\_C USER\_C -->|HTTPS local| APP\_C APP\_C -->|HTTPS permanent| CLOUD\_C style LAN\_C fill:#eef2ff,stroke:#6366f1,stroke-width:2px style CLOUD\_C fill:#dbeafe,stroke:#2563eb Permanent HTTPS to Natalia. Full art.28 DPA, sub-processor schedule. ## Inside the appliance Two screens, two promises kept: the appliance boots in minutes and gives your teams a clean local UI. Nothing leaves your network. ![Natalia appliance first-boot login screen](https://getnatalia.com/en/ova-agent-first-boot.732f5272.png) ### 8-screen wizard Admin password, license, network and mode, PBX, first collection. No internet required. ![Natalia analytics CDR dashboard: phone taxation statistics, volume per day, inbound/outbound ratio, top callers, duration histogram, cost per extension](https://getnatalia.com/en/dashboard-cdr-overview-window.271fc4d3.png) ### CDR analytics dashboard Volume per day, inbound/outbound ratio, top callers, cost per extension. Accessed via HTTPS on your LAN, role-based. [Walk through the step-by-step install](https://getnatalia.com/en/natalia-analytics-on-premise/installation) ## Documentation sections ### Decide #### Contractual modes Strict / +72h / Connected matrix: DPA, outbound flows, use cases. #### On-Premise security CISO reference: GDPR, encryption, roles, audit log. #### Reversibility Your data stays on your disk. Export, archive, delete. ### Install #### Alcatel PBX prerequisites Checklist before the wizard: accounts, flows, license. #### OVA installation VMware / Proxmox / Hyper-V. Single VM profile, 8-screen wizard. #### OXE configuration Taxation over IP, SSH, mtcl account, /usr4/account. #### OXO configuration Embedded FTP, port 30021, ftp\_nmc account. ### Operate #### License lifecycle States, renewal, hardware fingerprint, 72 h emergency license. #### Backup and restore Daily dump kept 7 days, plus your hypervisor snapshot. #### In-place upgrade System disk swap, data disk kept, automatic rollback. #### Data exports CSV, JSONL, JSON Schema. Admin only, audited. #### MCP server Query your CDR from Claude Desktop, Cursor or Claude Code. ### Troubleshoot #### Error codes The five connection test codes of the wizard. #### Troubleshooting Network flows, collection incidents, appliance access. #### Glossary CDR, OXE, OXO, SCP, embedded FTP, MCP… ## CISO frequently asked questions The eight questions we hear most often in security reviews. Every answer is screenshot-friendly. What outbound connections are made in Strict mode? None. In Strict mode, the appliance reaches only your PBX (read-only) and exposes a local HTTPS UI on your LAN. The license is verified locally, with no call-home. You can put it behind a default-deny egress firewall. How does licensing work without internet? Each license is a cryptographically signed file delivered out-of-band (USB, encrypted email) and validated locally by the appliance. No call-home, no online activation. A grace period covers expiry so collection never stops abruptly. Renewal = paste a new file. Who can access the data and how is access traced? Four built-in roles (Viewer, Admin, Auditor, Integrator), each with a least-privilege policy. Phone numbers are encrypted at rest and displayed masked; no interface returns the full number. Sensitive actions (export, license installation, PBX key re-approval) are recorded in an immutable audit log. How does the right to erasure (GDPR art.17) work? Selective erasure by employee (matched by extension). The operation is irreversible, audited, and produces a signed destruction certificate reporting the number of call records and reveal-log entries deleted. Absent a specific request, data is otherwise kept for the configured retention period (5 years for call records, 3 years for audit logs, by default). How do I back up the appliance? Two layers. The appliance makes a database dump every day and keeps the last 7, on the data disk: protection against logical corruption. Against the loss of the disk or the host, snapshot the data disk from your hypervisor (VMware, Proxmox, Hyper-V): this part is yours. How does an upgrade work? Your integrator partner replaces the system disk with the new version; the data disk is kept. At boot the appliance applies the migrations and restores the pre-upgrade dump by itself if one fails, then checks every service. Collection resumes at restart. What is the reversibility procedure? Export in CSV or JSONL with a JSON Schema, readable without Natalia. The data stays on your disk, including after license expiry: only the dashboard locks, collection continues. Export before the expiry date. What does the audit log record? One entry per event: who, what, when, on which resource. Immutable. Details of the format are available for CISO audits under NDA. [Open the complete CISO security reference](https://getnatalia.com/en/natalia-analytics-on-premise/security-on-premise) **Trade secret notice.** The internal architecture, source code, deployment scripts, license generation, anti-tamper mechanisms, and per-tenant isolation policies of the Natalia On-Premise 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. For RFP packs or RSSI Q&A 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)