Self-Hosted Deployments

View as Markdown

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

Why self-host

Data stays in your cloud

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.

Predictable, usage-independent cost

You pay AWS for the instance hours you run — a flat software fee plus infrastructure — instead of a per-call price.

Low, in-network latency

The endpoint lives next to your application in the same region and VPC, with no public-internet round trip.

Runs in air-gapped setups

Endpoints deploy with network isolation enabled — the model container has no outbound internet access.

How it works, end to end

1

Subscribe on AWS Marketplace

Accept the EULA on the Sarvam listing and copy the model package ARN for your region.

2

Deploy a SageMaker endpoint

Create a model from the package, then a real-time, async, or batch endpoint — via the console, boto3, or Terraform.

3

Invoke it from your app

Call InvokeEndpoint with your audio, text, or document. Results come back as JSON (STT), audio (TTS), or HTML/Markdown (Vision).

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.

Next steps