Skip to content

Platform · Deployment

The runtime runs
where your data lives.

Same runtime on your servers, in your cloud, or in Voicing Cloud. Egress: none. Audio, transcripts, models and traces stay inside.

Book a Demo Request the security package
  1. On-premisesAir-gapped, CPU-only
  2. Your cloudAWS, Azure, GCP or OCI
  3. Voicing CloudPinned region, managed
  4. What stays insideAudio, models, traces

Three topologies

The boundary moves. The runtime does not.

  1. On-premisesa solid wall, in your own data centre
  2. Your cloudan account boundary, and you hold the gate
  3. Voicing Clouda region you pin, with one operations port
On-premises: your data centre, with the Voicing runtime inside itThe Voicing runtime, with its runtime, models and observability store, standing on your racks inside the solid wall of your data centre. The wall has no opening.Voicing runtimeRuntimeVoice AI AgentsReal-Time TranslationKnowledge MeshAgent AssistModelsSpeechLanguageVoiceObservability storeTranscriptsTracesEvaluationsYour data centreYour racksBuilt wallNo openingYour cloud accountYour cloud regionOne gateYoursA region you pinInfrastructure we operateOne portOperations

On-premises: a solid wall, in your own data centre

Three topologies

The boundary moves. The runtime does not.

  1. On-premisesa solid wall, in your own data centre
    On-premises: your data centre, with the Voicing runtime inside itThe Voicing runtime, with its runtime, models and observability store, standing on your racks inside the solid wall of your data centre. The wall has no opening.Voicing runtimeRuntimeVoice AI AgentsReal-Time TranslationKnowledge MeshAgent AssistModelsSpeechLanguageVoiceObservability storeTranscriptsTracesEvaluationsYour data centreYour racksBuilt wallNo opening
    On-premises: your data centre, with the Voicing runtime inside itThe Voicing runtime, with its runtime, models and observability store, standing on your racks inside the solid wall of your data centre. The wall has no opening.Voicing runtimeRuntimeVoice AI AgentsReal-Time TranslationKnowledge MeshAgent AssistModelsSpeechLanguageVoiceObservability storeTranscriptsTracesEvaluationsYour data centreYour racksBuilt wallNo opening
  2. Your cloudan account boundary, and you hold the gate
    Your cloud: your cloud account, with the Voicing runtime inside itThe same Voicing runtime standing in your cloud region, inside the ticked boundary of your cloud account. The boundary has one gate, and it is yours.Voicing runtimeRuntimeVoice AI AgentsReal-Time TranslationKnowledge MeshAgent AssistModelsSpeechLanguageVoiceObservability storeTranscriptsTracesEvaluationsYour cloud accountYour cloud regionOne gateYours
    Your cloud: your cloud account, with the Voicing runtime inside itThe same Voicing runtime standing in your cloud region, inside the ticked boundary of your cloud account. The boundary has one gate, and it is yours.Voicing runtimeRuntimeVoice AI AgentsReal-Time TranslationKnowledge MeshAgent AssistModelsSpeechLanguageVoiceObservability storeTranscriptsTracesEvaluationsYour cloud accountYour cloud regionOne gateYours
  3. Voicing Clouda region you pin, with one operations port
    Voicing Cloud: a region you pin, with the Voicing runtime inside itThe same Voicing runtime on infrastructure we operate, inside the chain dotted line of a region you pin. The line has one operations port.Voicing runtimeRuntimeVoice AI AgentsReal-Time TranslationKnowledge MeshAgent AssistModelsSpeechLanguageVoiceObservability storeTranscriptsTracesEvaluationsA region you pinInfrastructure we operateOne portOperations
    Voicing Cloud: a region you pin, with the Voicing runtime inside itThe same Voicing runtime on infrastructure we operate, inside the chain dotted line of a region you pin. The line has one operations port.Voicing runtimeRuntimeVoice AI AgentsReal-Time TranslationKnowledge MeshAgent AssistModelsSpeechLanguageVoiceObservability storeTranscriptsTracesEvaluationsA region you pinInfrastructure we operateOne portOperations
On-premises01 / 06

In your own data centre.

The runtime, the models and the observability store install on your own servers, air-gapped where the review requires it, with nothing dialling out of the room.

  • Your servers

    Ordinary CPU servers in your own racks, sized with your infrastructure team in the review.

    CPU-only

  • Your network

    Inside your own segments and firewall rules. No inbound path is opened for us.

    Air-gapped

  • Your keys

    Encryption keys and credentials are issued, rotated and revoked by your own team.

    Your custody
Your cloud02 / 06

Or in the cloud account you already have.

The same runtime deploys into your own subscription on AWS, Azure, GCP or OCI, behind your own IAM boundary, in the region your data policy names.

  • Your subscription

    Billed, monitored and access-controlled by you, alongside the rest of your estate.

    Your account

  • Your region

    Pinned to the region your data policy names, and it does not move without you.

    In region

  • Your policy

    Network policy, private endpoints and logging follow standards you already enforce.

    Your controls

The account is yours, on any of the four.

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
  • Oracle
Voicing Cloud03 / 06

Or managed by us, in a region you pin.

Voicing Cloud runs the same build on infrastructure we operate, in a region you name, on the data handling terms the architecture review settles before anything is signed.

  • Same build

    The image running here is the image you would run yourself. There is no hosted variant.

    Same runtime

  • Pinned region

    The region is written into the agreement, and processing does not leave it.

    In region

  • Operated

    Patching, capacity and upgrades are ours, on a change window your team approves.

    Managed
What stays inside04 / 06

Audio and transcripts never leave the boundary.

Recordings, transcripts, model weights and the trace of every call are written inside the deployment, and no transcript trains a model anyone else uses.

  • Audio and transcripts

    Written to storage inside the deployment, under the retention period your policy sets.

    Inside

  • Models

    Loaded from the deployment. No third-party endpoint is called while a caller is on the line.

    Inside

  • Traces

    Every turn, tool call and handoff is recorded where the rest of your audit evidence lives.

    Inside

The three stores

Every path ends at the wall.

The three stores: three stores and a wallThree stores inside the wall of your deployment. Audio and transcripts shows rows of recorded speech over a line of transcript; Models shows stacks of model layers on their bases; Traces shows the spans of one call on a time axis. A path runs from each store to the wall and stops on it. The wall has one gate, cut in its foot and shut, and the wall itself is marked egress none.Your deploymentEgress: noneAudio and transcriptsModelsTraces
  1. Audio and transcripts
  2. Models
  3. Traces

Audio and transcripts

The three stores

Every path ends at the wall.

The three stores: three stores and a wallThree stores inside the wall of your deployment. Audio and transcripts shows rows of recorded speech over a line of transcript; Models shows stacks of model layers on their bases; Traces shows the spans of one call on a time axis. A path runs from each store to the wall and stops on it. The wall has one gate, cut in its foot and shut, and the wall itself is marked egress none.Your deploymentEgress: noneAudio and transcriptsModelsTraces
The three stores: three stores and a wallThree stores inside the wall of your deployment. Audio and transcripts shows rows of recorded speech over a line of transcript; Models shows stacks of model layers on their bases; Traces shows the spans of one call on a time axis. A path runs from each store to the wall and stops on it. The wall has one gate, cut in its foot and shut, and the wall itself is marked egress none.Your deploymentEgress: noneAudio and transcriptsModelsTraces
The path to production05 / 06

From the review to the first traced call.

A deployment starts with an architecture review and ends with a call you can replay. Your infrastructure team is part of every step between.

  1. Architecture review

    An architect goes through your topology and your questions.

  2. Sizing

    Servers are sized with your team, on the CPU you already run.

  3. Install

    Runtime, models and store install inside the chosen boundary.

  4. Connect

    Your trunk and your records are joined with keys you issue.

  5. First traced call

    The first calls run, and every turn of them is on record.

One level line across the frame with five ports on it, and under each a card: architecture review, sizing, install, connect, first traced call.

Closing06 / 06

Bring one call type. Leave with an architecture.

A white suite case opening on six coloured discs, the product surfaces, rising between its lid and its base.
Deployment

The whole suite, inside your perimeter

A working session with an engineer who has deployed inside a bank’s perimeter. We map your telephony, data boundary and handoff rules, and tell you what we would not automate.

Book a Demo