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

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

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

CDR analytics dashboard

Volume per day, inbound/outbound ratio, top callers, cost per extension. Accessed via HTTPS on your LAN, role-based.

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.

Last updated :

Suggest an edit