Calls run in Sydney, in a shared account, one dedicated to you, or your own cloud account. Call records, recordings and keys are stored in the account the calls run in.
An account for you aloneFor you aloneShared with other customers
Control planeDashboard, sign-in, releases
Call planeEverything a call touchesCallsTranscriptsRecordingsKeys
On every call Phone carrier, media in Sydney Speech in Sydney
Shared. Control plane: Our account. Call plane: Our account, shared. Your workspace runs on the multi-tenant platform in Sydney. Every row carries your workspace ID, and row-level security limits each read and write to it.
Dedicated. Control plane: Our account. Call plane: An account for you alone. Your call plane gets its own cloud account in Sydney, with its own network, database, keys and model quota. No other customer's calls draw on it.
Hybrid. Control plane: Our account. Call plane: Your own cloud account. The call plane runs in a cloud account you own in Sydney, so call audio, transcripts, recordings and keys are stored there. We run the dashboard and releases from ours.
Your account. Control plane: Your own cloud account. Call plane: Your own cloud account. Both planes run in your account, and the dashboard is reachable only inside your network. Calls do not depend on our account at any point.
Four deployments
Choose where the call plane runs. The control plane runs with us unless you take both.
Shared
Control planeOur account
Call planeOur account, shared
Your workspace runs on the multi-tenant platform in Sydney. Every row carries your workspace ID, and row-level security limits each read and write to it.
Suits a pilot, or a team that accepts multi-tenant isolation.
Dedicated
Control planeOur account
Call planeAn account for you alone
Your call plane gets its own cloud account in Sydney, with its own network, database, keys and model quota. No other customer's calls draw on it.
Suits single tenancy without running a cloud account yourself.
Hybrid
Control planeOur account
Call planeYour own cloud account
The call plane runs in a cloud account you own in Sydney, so call audio, transcripts, recordings and keys are stored there. We run the dashboard and releases from ours.
Suits a security team that wants call data and keys in its own account.
Your account
Control planeYour own cloud account
Call planeYour own cloud account
Both planes run in your account, and the dashboard is reachable only inside your network. Calls do not depend on our account at any point.
Suits a policy that allows no outside control plane.
Control plane and call plane
Every deployment splits the platform in two, and the call plane holds everything a call touches.
Control plane
Holds agent settings and user accounts. It never stores call audio, transcripts or recordings.
Dashboard and agent editor
Sign-in, roles and single sign-on
Billing from usage counts
Image builds and releases
Call plane
Holds everything a call touches. Call content is written here and nowhere else.
Phone and SIP ingress
Call workers, one call per process
The AI model, in Australia
Speech connections
Transcripts, recordings and call records
Simulated test calls
Encryption keys
Where your calls are processed
By default every call stays in Australia: call audio, speech recognition, the voice, the AI model, recordings and transcripts. Nothing about a call leaves Australia unless you switch an agent to an overseas model or voice.
On every call
Phone lines
Australian carrier, media in Sydney
Speech
Sydney, or in your VPC
AI model
Sydney and Melbourne
Model failover
None outside Australia
Overseas voices
Only if you pick one
Browser test calls
Sydney
Sub-processors
The sub-processor list names each provider, what it does, the data it handles and its region. It is sent on request from privacy@verticalai.com.au, and architecture detail for a security review is shared on request.
Dedicated, Hybrid and Your account deployments each get their own VPC, database, keys and model quota.
Your encryption key
The database, recordings and stored secrets are encrypted under a key that can live in your own cloud account. Revoke it and the data is unreadable.
Private network
Services run in private subnets. Cloud services are reached over private endpoints, and outbound traffic passes a domain allow-list.
Single sign-on
Your team signs in through your identity provider over SAML 2.0 or OIDC.
Releases without dropped calls
A release moves new calls to a second voice service once a zero-dropped-call gate passes. Rolling back returns new calls to the old version within 5 seconds.
Failover in Melbourne
If Sydney does not answer within 5 seconds, a handler in Melbourne answers and forwards the caller to your fallback number.
From contract to first call
Every deployment is built from code, never by a person at a console. Our team built a private AI platform for a client in Sydney the same way.
1
Architecture review
We take your security and network teams through the design and pick the deployment.
2
Account and network
We create the cloud account, or you create one and grant our deploy role. Model access is requested in that account.
3
Keys and sign-in
You create or grant the encryption key and connect your identity provider.
4
Phone lines
We provide or port Australian numbers, or connect a SIP trunk from your phone system.
5
Tests and go-live
Simulated calls test every agent before a number moves. Canary calls then test the line around the clock.
Questions about running voice agents in your own cloud account
Vertical AI runs the call plane in a cloud account you own in Sydney, called a Hybrid deployment, or both planes there, called a Your account deployment. You create the account and grant our deploy role, our infrastructure code builds it, and you create or grant the encryption key. Call audio, transcripts, recordings and keys are then stored in your account.
Vertical AI runs every deployment on servers in Sydney. Failover answering, backups and the audit trail sit in Melbourne. The AI model answers calls in Australia, with inference kept in Sydney and Melbourne.
Yes. Your PBX or session border controller connects to a SIP connection on our carrier, calls reach the Vertical AI agent, and transfers go back over SIP. Our carrier is licensed in Australia and anchors call audio in Sydney.
No. By default every Vertical AI call stays in Australia: call audio, speech recognition, the voice, the AI model, recordings and transcripts. Nothing about a call leaves Australia unless you switch an agent to an overseas model or voice.
No. Vertical AI runs the platform on servers in Sydney. The closest option is a Your account deployment, where both planes run in a cloud account you own and the dashboard is reachable only inside your network.
Deployment detail
Each page holds the evidence for one part of the design.