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.
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 Debian ready to import. Guided 5-step 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 / department.
Features
Dashboard for phone taxation: costs per extension, department, direction.
CDR traffic analysis: inbound, outbound, internal, missed.
Alerts on off-hours calls or cost overruns per department.
CSV / Parquet / JSON export for internal re-billing.
RBAC with 4 roles: Viewer, Admin, Auditor, Integrator.
Immutable audit log, exportable to your SIEM (Splunk, ELK, Sentinel).
GDPR art.17 selective erasure per employee extension, audited and certified.
Phone numbers encrypted at rest, masked by default, revealed only to Admin (audited).
Inside the dashboard
Real screens from the local appliance — same data your teams see on the LAN.
Date window
Filter by date range to isolate a campaign, an audit period, an incident.
Direction filter
Drill into outbound only to track cost per extension, per department.
Full overview
All directions, all extensions — the snapshot a CFO or a department head 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 | On-trigger SSH, 72h max | Permanent HTTPS |
| Use case | Bank, mutual, defense, OIV | Mid-market, reactive support | Qualitative analysis of conversations — Natalia Analytics SaaS |
| RFP cycle | −3 to −6 weeks | −1 to −2 weeks | Standard SaaS |
New to the sovereignty argument? Read the sovereign voice AI overview →
Natalia On-Premise vs the market
Most legacy on-premise phone analytics tools predate GDPR. They do not articulate a Strict / Connected modes choice, and they rarely expose an immutable audit log out of the box.
| Natalia On-Premise | Jusan CallXpress GO | ComTrafic | |
|---|---|---|---|
| Air-gapped Strict mode | Yes, explicit, no DPA | Not articulated | Not articulated |
| Alcatel OXE / OXO native | Yes | Yes (multi-vendor) | Yes (multi-vendor) |
| GDPR art.17 selective erasure | Yes, audited | Manual / partial | Manual / partial |
| Immutable audit log | Yes, signed | Not documented | Not documented |
| Reversibility (open formats) | CSV / Parquet / JSON | CSV | CSV |
| Public pricing | On request | On request | On request |
Comparison based on public documentation of competitors as of 2026-06. We will update this table on request, with sources.
Technical prerequisites
Three sizing profiles validated on Alcatel OXE / OXO deployments. A 30% ingest headroom is already baked into the data disk.
| Small | Medium | Large | |
|---|---|---|---|
| vCPU | 2 | 4 | 8 |
| RAM | 4 GB | 8 GB | 16 GB |
| System disk | 20 GB | 20 GB | 20 GB |
| Data disk | 20 GB | 100 GB | 480 GB |
| PBX | 5 | 20 | 100 |
| Phone lines | 100 | 1 000 | 10 000 |
| CDR / day | 500 | 5 000 | 50 000 |
| Historical depth | 1 year | 3 years | 5 years |
| Concurrent admin users | 3 | 10 | 25 |
Performance targets, all tiers: dashboard p95 < 500 ms (5 RPCs fan-out), per-RPC p95 < 200 ms at 100k rows. PBX/users hard-stop enforced by the license.
GDPR & legal guarantees
DPA Strict (no signature needed)
Qualification: pure software publisher, no controller / processor relationship.
Light Support DPA (72h)
Art.28 §3 a-h scoped to point-in-time interventions, with intervention log.
Full art.28 DPA (Connected)
Standard SaaS DPA with sub-processor schedule (Gemini documented).
DPIA template (>5000 lines)
CNIL impact-assessment template for organizations crossing the systematic-monitoring threshold.
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.
Looking for qualitative textual analysis of your conversations on top of CDR? See Natalia Analytics SaaS →