Sarvam 30B and 105B released
Sarvam · Model release
Source confirmed
Data as of October 1, 2026 · How the score is built
EstablishedOpen WeightReasoning
Released Mar 6, 202664K context
Sarvam 30B
Decision readingSarvam 30B is tracked, but not publicly ranked yet. The profile exposes 0 sourced benchmark rows and leaves unsupported fields blank until a published record exists.
Released Mar 6, 2026 — see all recent releases
Sarvam 30B will be repriced, updated or retired. Get each notice with its source and date. Follow model changes
Share or export
Lineage
The sequence follows explicit supersedes links. Each score is estimated for that model; a relative can inform a sparse estimate but never sets a floor, so a newer release can score below an earlier one. Scores and prices remain blank when the corresponding public row or first-party rate is unavailable.
Base entry
Radar
Full release historySarvam 30B release history
Radar confirmed these at the source. Use Sarvam 30B in your work? Explore Radar to follow supported changes and choose your alerts.
Radar
Spec sheet
Each documented value carries its source. Missing fields stay visible as not sourced or not published, rather than disappearing from the page.
- API model ID
- Not published
- Context window
- 64K
- Maximum output
- Not sourced yet
- Knowledge cutoff
- Not sourced yet
- Input modalities
- Not sourced yet
- Output modalities
- Not sourced yet
- Parameters
- Not sourced yet
- Availability
- Not sourced yet
- Cloud regions
- Not tracked yet
- Lifecycle
- Established
- API capabilities
- Tool calling, structured outputs, and batch support are not tracked yet
- Prompt caching
- Not documented in the pricing record
- Self-host
- Open weights available; hardware estimate not sourced
- Rate limits
- Not tracked yet
How to read this profile
The visual layer above carries the decisions. These notes preserve the model, ranking, coverage, and family context behind the numbers.
We track Sarvam 30B, but no weighted text-model benchmark result is published on the site yet. This page shows the metadata and separate protocol evidence we can verify now; a BenchLM score will appear only if compatible public evaluations land.
Sarvam 30B is a open weight model with a 64K context window. It uses an explicit reasoning mode, which can improve complex problem solving while adding latency and token use.
The profile has no source-displayable benchmark row yet.
Last updated October 1, 2026. Runtime fields remain blank until a sourced snapshot exists.
Deployment options
Self-host and provider-specific paths stay separate from benchmark evidence so operating constraints are visible before a score becomes the whole decision.
Published weights are available, but BenchLM does not yet have a sourced parameter and VRAM profile for this exact model. Hardware cost estimates stay unavailable until that sizing record is complete.
Estimate VRAM from known parametersQuestions
How does Sarvam 30B perform overall in AI benchmarks?
Sarvam 30B does not have any source-displayable benchmark rows yet, so this profile does not assign a public score or rank. Documented specifications remain visible, while score-led charts and claims stay unavailable until a published evaluation can be attached to the exact model.
Is Sarvam 30B open source?
Sarvam 30B is an open-weight model from Sarvam. Its weights can be downloaded for local or hosted deployment, subject to the published license. Open weight does not automatically mean open source: training data and training code may remain private, and commercial restrictions can still apply.
Does Sarvam 30B have full benchmark coverage on BenchLM?
No. Sarvam 30B currently has 10 source-displayable rows across 508 tracked benchmark slots. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.
What is the context window size of Sarvam 30B?
Sarvam 30B has a reported context window of 64K in the exact-model catalog record. The value stays visible, but the profile marks its source link as unavailable instead of presenting it as directly documented. Maximum output length remains separate because providers often publish a different limit.