Hybrid controlled — recommended pilot
Keep internal: identity/consent, exact field boundaries, treatment history, approved documents/rules, audit, long-term media and officer records.
Send externally only sanitized transcript, selected images/frames, minimum context and pseudonymous request ID.
Enterprise cloud
Require approved retention, regional processing, encryption, customer-managed keys where supported, private networking, audit exports, deletion and subprocessor controls.
Fully sovereign
Operate media, STT, reasoning, embeddings, retrieval, TTS, databases, storage and logs inside government infrastructure. This maximizes control but adds GPU, model-ops, patching and performance burdens.
Migration sequence
- embeddings/reranker;
- TTS;
- STT;
- vision/reasoning model;
- controlled research proxy/mirror.
Every replacement passes the same Urdu, agriculture, safety, latency and cost suite.
Provider record
For each provider document data sent, processing location, retention, training use, subprocessors, encryption/keys, audit, incident notice, deletion and exit/portability.
Live media deployment
The hybrid pilot may use an approved managed or government-hosted LiveKit deployment. Identity, precise field data, approved knowledge, policy, audit and long-term selected media remain government-controlled. A fully sovereign option moves SFU/TURN, STT/TTS and reasoning inside approved infrastructure. Raw call egress and recording require explicit deployment-class approval.