Alpha
All entriesContact
Model

Sarvam-30B, Sarvam-105B and Sarvam-105B-1711

Publisher
Axonwise Private Limited (Sarvam AI) (IN)
Family
Sarvam
Openness
open_weights
Licence
Apache License 2.0 (declared on the cards)
Context
128k / 65k evaluated (config 131k) / 131k (config 163k)

You can run and fine-tune Apache-2.0-declared weights, but you get no data, code, recipes or safety case, and the licence is a card declaration with no LICENSE file. Sarvam's own Terms and EULA restrict derivative works and training without mentioning the weights. Ownership rises if Sarvam adds a LICENSE file, clarifies those documents and publishes a safety evaluation.

Do you really own it?
Partial
none·limited·partial·substantial·full
Analytical input: AOI D · 44.4/100
The four ownership factors

Floor-weighted, not averaged. Reliability is weak, and the weakest factor sets the ceiling, so the verdict stays partial however strong the rest.

1

Use and modify freelyCan you run, modify and adapt it with no gate and no field-of-use trap?

Moderate

Apache-2.0 is declared, the weights are ungated and fine-tuning is possible. The licence is a card declaration with no LICENSE file, and Sarvam's Terms and EULA add limits on derivative works and training that do not mention the weights (ev-license, ev-tos, ev-eula).

How this scores (AOI sub-dimensions)
Openness3/5how much is released - weights, data, code, licence - and how freelyWeights are open under an Apache-2.0 declaration, with cards, a blog and a public 22-language evaluation prompt set.
Legal2/5how permissive and clean the licence is for real commercial useApache-2.0 is declared but no repo holds a LICENSE file, and Sarvam's Terms and EULA add limits on derivative works and training that do not mention the weights.
2

TransparencyDo you know what it is: weights, training, behaviour, and legible terms?

Moderate

Weights, cards and a blog are public. Training data, training code, post-training recipes, base checkpoints and a technical report are not (ev-card-105b, ev-blog, ev-no-report).

How this scores (AOI sub-dimensions)
Provenance2/5how well we can trace and verify what went into the modelThe canonical source is the sarvamai Hugging Face organisation, which is not verified.
Governance3/5how accountable and well-documented the publisher isSarvam AI is an accountable company in Bengaluru with a release record: the March release, fix pull requests in September and November, and the 1711 build in November.
3

ReliabilityIs it reliable and good enough for the job?

Weak

Safety scores 1: no safety evaluation, no guard model and silent 1711 cards. Operational scores 3 (ev-blog, ev-card-1711, ev-hub).

How this scores (AOI sub-dimensions)
Operational3/5how practical it is to run, serve and maintain in productionThe models run on Transformers with trust_remote_code, SGLang and vLLM.
Safety1/5whether misuse risks are evaluated and guardrails are providedThe blog says the fine-tuning data covered India-specific risks and red-team prompts.
4

Doesn't extract your dataDoes running it keep your knowledge and data yours?

Moderate

Weights run on your own hardware. The custom Python and the vLLM hot-patch script need review, and the hosted API terms conflict on training and retention (ev-hub, ev-privacy, ev-eula).

How this scores
Not a scored AOI dimension. For a self-hosted model, data-control is a structural property of running the weights yourself, strong by default unless the model phones home or the licence claws back rights. For a hosted API this factor is the retention + train-on-inputs + residency read, scored from the binding terms.

How the AOI score is computed

The seven dimensions above, each scored 0 to 5, weighted and summed to the 0 to 100 headline. The score is the analytical input behind the ownership verdict, not the verdict itself.

DimensionScoreWeightPoints
Openness3/50.1810.8
Provenance2/50.166.4
Legal2/50.166.4
Safety1/50.163.2
Performance2/50.145.6
Operational3/50.127.2
Governance3/50.084.8
HeadlineD · 44.4/100
Dossier coverageAssess 73%Implement 86%Use 78%Support 50%How complete our four-domain documentation is, a measure of our coverage, not of the model. Each domain links to its page.

Sources

Every rating traces to a primary document. Read means the text was verified; unverified means it is known to exist but has not yet been read.

DocumentWhat it grounds
Model cardread2026-11-19
The 105B card declares Apache-2.0 and lists 22 language codes plus English.
Model cardread2026-11-19
The 30B card declares Apache-2.0 and the same language codes.
Model cardread2026-11-19
The 105B-1711 cards declare Apache-2.0 and say the model shares the Sarvam-105B base and is further post-trained for tool calling, instruction following, agentic tasks and Indian languages.
Licenceread2026-11-19
All eight weights repos declare Apache-2.0 in the card front matter and none holds a LICENSE file (raw LICENSE returns HTTP 404).
Documentationread2026-11-19
The sarvamai Hugging Face organisation is not verified and lists 17 ungated model repos.
Vendor announcementread2026-11-19
The launch blog of 6 March 2026 says both models were trained from scratch on in-house data, 16T tokens for the 30B and 12T for the 105B, with the 10 most-spoken Indian languages emphasised in pre-training (publisher claims).
Documentationread2026-11-19
The indivibe dataset holds 4,840 evaluation prompts in the 22 scheduled languages, including Bodo, in native and romanised script, under CC-BY-4.0.
Documentationread2026-11-19
Sarvam's API documentation lists 10 Indian languages plus English for Sarvam-105B and for the deprecated Sarvam-30B.
Documentationread2026-11-19
The platform documentation says workspace data is retained indefinitely until an owner sets a period.
Terms of serviceread2026-11-19
Terms of Service v2.0, effective 29 July 2026, clause 10.5 bars using the Offerings or their output to train or fine-tune AI systems and bars discovering model weights.
Privacy Policyread2026-11-19
The Privacy Policy of 29 July 2026 headlines model training as opt-in but says Sarvam trains on inputs and outputs unless the user opts out.
Terms of serviceread2026-11-19
The EULA of 22 May 2026 defines Software to include 'proprietary language models' and bars derivative works.
Securityread2026-11-19
The Trust Center claims ISO 27001, SOC 2 Type II, India-only residency and no use of one customer's data to train models for other customers.
Third-party analysisread2026-11-19
Artificial Analysis scored Sarvam 105B at 18 and Sarvam 30B at 12 on its Intelligence Index in April 2026.
Documentationread2026-11-19
Official FP8 builds of both models and Q4_K_M GGUF builds (19.6 GB for the 30B, 64.2 GB for the 105B) exist.
Documentationread2026-11-19
Community threads ask for the training data and for newer checkpoints and have no Sarvam reply.
Vendor announcementread2026-11-19
The Token Factory post of 16 November 2026 says Sarvam serves the 105B in MXFP8 with DSpark speculative decoding from GPU clusters in India.
Technical_reportunverified2026-11-19
No technical report, paper or data statement for these models was found.
Documentationunverified2026-11-19
The AIKosh page for the 105B, linked from the blog as a second download source, is a JavaScript app and returns no text.