Deployment

Runs where you do.

One platform, three ways to run it. Your data stays in the jurisdiction you choose.

Three ways in

Pick your walls.

01 · Cloud
2–4 weeks

India-region cloud

Isolated tenancy, region-pinned providers. The fastest path to a pilot.

Best forFast pilots, mid-size lenders and insurers
02 · Private cloud
4–8 weeks

Your private cloud

Azure or GCP, in your subscription, with your keys.

Best forBanks and insurers with Azure / GCP mandates
03 · On-prem
8–12 weeks

On-prem

Dedicated GPUs in your data centre. Air-gapped option.

Best forPSU banks, strictest localisation mandates
Side by side

Same platform. Your choice of walls.

deployment.compare · 3 targets · 1 codebase
CapabilityIndia-region cloudPrivate cloud (VPC)On-prem / dedicated
Best forFast pilots, mid-size lenders and insurersBanks and insurers with Azure / GCP mandatesPSU banks, strictest localisation mandates
Time to first call2–4 weeks4–8 weeks8–12 weeks, hardware dependent
Data residencyIndian region, isolated tenancyYour subscription, region and keysYour racks. Air-gapped option.
Training on your dataOnly your models, only from your data. Never a shared model.
Speech & LLMManaged by FormantAI, region-pinnedYour accounts or ours, in your VPCSelf-hosted open models on dedicated GPUs
Operated byFormantAIFormantAI with your cloud teamYour team; FormantAI on-site at rollout, on-call after
TelephonyOurs or yours (SIP)Yours, SIP trunk into VPCYours, on-prem PBX / SBC
Logs & recordingsEncrypted, region-pinned, exportableNever leave your accountNever leave your network
CommercialPer conversation / minutePlatform fee + usageAnnual licence + support

Green cells mark where the data, keys or timeline sit entirely on your side. Timelines are typical ranges and depend on integration scope. See how we work.

Architecture

What moves, and where it stays.

Audio streams in-region. Customer data is read through scoped APIs, never cached. Weights live in your environment.

call.path · ap-south-1
t+0sip_invitetrunk=customer · region=ap-south-1
t+0.2sstt_streamprovider=pinned-in-region
t+0.3saccount_lookupscope=read:balance,due_date
t+0.4spolicy_enginerbi_fpc · irdai · dpdp
t+endrecording_storedAES-256 · retention=90d · region-pinned
t+endtranscript_redactedpii=masked · exported→client SIEM
AES-256 at rest

Encrypted recordings

Recordings and transcripts are encrypted at rest and pinned to the region you choose.

Your retention policy

Automated deletion

Retention windows are yours to set; deletion runs on schedule and is logged.

Tenant-isolated weights

Your model, your walls

Fine-tuned weights live in your environment and never train a shared model.

Nothing cached beyond the call

Scoped, ephemeral reads

Account data is read through scoped APIs during the call and dropped when it ends.

For infra teams

Common questions.

Can you run fully air-gapped?
Yes, with self-hosted speech and language models on dedicated GPUs. Some provider-hosted voices are unavailable; we benchmark open alternatives on your recordings first.
Which clouds do you support for VPC?
Azure and GCP today, where we run our own production — so deploying into yours is configuration, not a re-platform. AWS on request.
Who holds the encryption keys?
In VPC and on-prem, you do (customer-managed keys). In the India-region cloud, keys are per tenant in a regional KMS, and you can bring your own.
Do you need our recordings to start?
No. We start from your scripts and generic Indic models, then fine-tune once consented recordings arrive. Recordings shorten the path to your brand voice.
Reference architecture

Bring your infra team.

Data-flow diagram, reference architecture and security questionnaire, walked through for your cloud.

Book an architecture call
Security & compliance

Mapped to the rulebook.

Consent, redaction, calling hours and retention — each control mapped to RBI, IRDAI and DPDP.

Read the security page