For procurement, security teams and regulated buyers

Where the audio goes, and where it doesn't.

On Anuvo Resident, call audio never leaves your network. The entire voice stack runs inside your infrastructure — no third-party model dependency, no per-minute API fee, no data egress by design.

This page closes regulated deals and answers procurement before they ask. It is written to be forwarded to a security team and survive first contact.

Plan a Resident deployment Read the security docs

The architecture

Resident: everything inside the boundary

The dashed line is your network. Everything below it is yours — hardware, models, audio, logs.

Callers · PSTN / SIP trunk

Inbound calls from the public network arrive at your existing phone system.

↓

Your network boundary

Your PBX / SBC

Routes calls to Anuvo Resident — no phone system replacement.

↓

Anuvo Resident runtime

STT → orchestration → TTS, in-process. Latency budget enforced: 355 ms measured.

↓

Integrations & audit store

HIS / EHR / CRM writes · call recordings (consent-based) · transcripts · RBAC audit log — all inside the network.

optional, metadata only

Anuvo Cloud (optional)

Dashboards and fleet analytics receive metadata only — never audio, never transcripts unless you opt in explicitly.

Controls

What we do, concretely

Encryption

TLS 1.3 in transit, AES-256 at rest for recordings and transcripts, keys managed on your infrastructure on Resident.

No data egress

Resident makes no outbound calls carrying audio. Model inference, transcripts and logs all resolve inside your boundary.

RBAC & least privilege

Operator, supervisor and auditor roles with scoped permissions. Audit log tamper-evident and exportable.

Consent & retention

Announcement-and-consent flow you configure. Retention windows, deletion and export controls under your administration.

No model vendor in the loop

No third-party model dependency on Resident — your inference is yours, so no vendor sees, stores or prices your calls.

Updates you schedule

Versioned releases with signed artifacts. You apply updates on your own maintenance window; no forced telemetry.

The honest part

What Cloud means, plainly

Anuvo Cloud is a hosted service: inference runs on Anuvo-managed infrastructure, and call audio transits our region. That is the trade you accept for zero-ops speed — and it is exactly why Resident exists.

	Anuvo Cloud	Anuvo Resident
Where inference runs	Anuvo-managed cloud, region of your choice	Your infrastructure
Audio leaves your network?	Yes — to our hosted runtime	Never
Third-party model dependency	Hosted model API	None
Billing	Per-minute + setup	Annual license, no per-minute fee
Encryption & RBAC	Yes (TLS 1.3, AES-256)	Yes, keys on your infrastructure
Best for	Speed-driven commercial buyers	Regulated buyers: hospitals, labs, legal

If your security team's first question is "where does the audio go?", the answer that closes the deal is Resident's: nowhere. It never leaves your building.

Plan a Resident deployment Read the security docs