Self-Hosted Deployments
Self-Hosted Deployments
Run Sarvam’s models inside your own cloud. Instead of calling the Managed API at api.sarvam.ai, you subscribe to a Sarvam model package on the AWS Marketplace and deploy it as an Amazon SageMaker endpoint in your own account and VPC. Your audio, documents, and transcripts never leave your infrastructure.
Self-hosted deployments are a different delivery model from the Managed Sarvam API. Same models, two ways to run them — see Managed vs Self-Hosted to choose.
Models available for self-hosting
Indic-first ASR across 23 languages with five output modes (transcribe, translate, verbatim, translit, codemix). Real-time and streaming.
Indic-first TTS with 38 voices. Text in, base64 or streamed audio out — real-time, server-side streaming (SSE), and bidirectional.
3B-parameter vision-language model for OCR and document parsing across 23 languages. PDFs and images in, clean HTML or Markdown out.
Why self-host
Audio and documents are processed inside your own VPC. Nothing is sent to Sarvam — ideal for BFSI, healthcare, and government workloads with data-residency requirements.
You pay AWS for the instance hours you run — a flat software fee plus infrastructure — instead of a per-call price.
The endpoint lives next to your application in the same region and VPC, with no public-internet round trip.
Endpoints deploy with network isolation enabled — the model container has no outbound internet access.
How it works, end to end
Subscribe on AWS Marketplace
Accept the EULA on the Sarvam listing and copy the model package ARN for your region.
There is no license key or license proxy to run. AWS Marketplace handles entitlement — once you’re subscribed, the endpoint is fully licensed for the instances you run it on.