Data Flow
Understand how data flows through Vapi when using custom storage and custom models
When using Vapi, data flows through multiple components during a voice conversation. Understanding this flow is essential for security-conscious organizations, especially when integrating custom bucket storage or custom model providers.
This guide explains:
Vapi generates two distinct types of logs during calls:
System Logs are strictly internal to Vapi and are never shared with customers or uploaded to custom storage buckets. They contain infrastructure-level data used for Vapi’s operational purposes only.
Vapi orchestrates a sophisticated voice pipeline with multiple modular components. Each component can be configured to use Vapi’s default providers, your own API keys, or your own custom servers.
The transport layer handles real-time audio streaming between users and Vapi.
Audio Formats:
Converts user audio into text in real-time using streaming recognition.
Custom Transcriber: Vapi supports custom transcriber integration via WebSocket. See Custom Transcriber.
Bring Your Own API Key:
Vapi runs proprietary real-time models that make conversations feel natural. These models are not customizable and run on Vapi’s infrastructure.
Orchestration models process data in real-time but do not persist the audio or intermediate results. All processing is ephemeral. Only final transcripts and call logs are stored (unless HIPAA mode is enabled).
Generates conversational responses based on transcribed user input.
Custom LLM: Vapi supports custom LLM integration via OpenAI-compatible endpoints. See Custom LLM.
Bring Your Own API Key:
Converts LLM responses into spoken audio.
Custom Voice: Vapi supports custom TTS integration via audio streaming endpoints. See Custom TTS.
Bring Your Own API Key:
In the default configuration, Vapi handles all pipeline components and stores artifacts on Vapi’s infrastructure.
Default storage on Vapi:
When you configure custom bucket storage, call recordings and call logs are uploaded to your infrastructure. System logs and product usage metrics remain on Vapi’s infrastructure.
Supported storage providers:
System Logs and Product Usage Metrics are always stored on Vapi’s infrastructure and are never uploaded to custom storage buckets. These are internal operational data used by Vapi only.
When using custom transcriber, LLM, or voice servers, data flows to your infrastructure for processing.
With full custom configuration:
The Orchestration Layer (endpointing, interruption detection, emotion detection, backchanneling, filler injection) is Vapi’s core value proposition and runs exclusively on Vapi infrastructure. Audio processed by these models is ephemeral and not stored.
HIPAA Mode Important Notice: When HIPAA mode is enabled (hipaaEnabled: true) and no custom storage is configured, Vapi will not store call recordings or transcripts. This data will be lost after the call ends. To retain call data in HIPAA mode, you must configure a custom storage bucket.
Even with maximum custom configuration, certain data passes through Vapi’s orchestration:
Configure:
Result: Only orchestration signals (ephemeral) pass through Vapi. System logs remain on Vapi infrastructure (never shared).
Note: Orchestration models run on Vapi’s US/EU infrastructure (data is ephemeral). System logs remain on Vapi infrastructure.
hipaaEnabled: trueWithout custom storage configured, HIPAA mode will result in no call recordings or transcripts being stored. Data will be lost after call completion.