Alpha
Contact
Implement · DeepSeek-R1-Distill

Can you run it?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input C ยท 61.6/100

This page is a projection of the one entry record, the Reliability and Data control factors that Implement covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor
  • AssessUse & modify + Transparency
  • ImplementData control + Reliability
  • UseReliability
  • SupportTransparency

Install & run

Download the safetensors from the verified deepseek-ai organisation on Hugging Face and serve with Ollama, llama.cpp, vLLM or SGLang. The 8B runs on a single consumer GPU. Pin the exact revision and verify checksums. The weight licence is the Llama Community Licence.

Hardware & VRAM requirements

The 8B runs on a single consumer GPU. The 70B runs on a single data-centre GPU, or on high-end consumer hardware when quantized. Context is 128K. The Llama base gives the broadest hardware and toolchain support of any distil base.

Serving stacks

vLLM, SGLang, llama.cpp and Ollama all support these models first-class. The Llama base has the widest toolchain coverage in the ecosystem.

Safe-deployment controls & Deployment Ceiling

Deployment Ceiling: T2 (conditional). Honour the Llama Community Licence first: the Acceptable Use Policy, the 700M-MAU clause and the "Built with Llama" naming and attribution are binding conditions.

Supply your own input/output guardrails and a guard model, because the models have no safety tuning of their own. Add prompt-injection defences and treat retrieved and tool content as untrusted in agentic use. Account for the China-aligned filtering carried over from R1.

Available quantizations

The models are extensively quantized (GGUF and lower-bit) via the Llama ecosystem. Redistribution of these derivatives must carry the Llama licence and AUP. Verify provenance per mirror.

Fine-tuning & adaptation

Fine-tuning and derivatives are permitted and carry the Llama restrictions (AUP, 700M-MAU and "Llama" naming and attribution). The distillation data and code are closed, so the distillation cannot be reproduced from scratch.

API / OpenAI-compatible integration

Serve behind an OpenAI-compatible endpoint (vLLM, SGLang or Ollama) and point the client at it. Handle the reasoning / think-tag output format at the client.

How this scores

The ownership factors this domain covers, drawn from the one entry record.

3

ReliabilityIs it reliable and good enough for the job?

Strong

Performance 3, operational 5 and safety 3: solid reasoning for the size and the broadest serving support of the distils. All three scores are at or above 3 and operational is 5, so reliability is strong. The gap is the absence of own safety tuning or a first-party guard model.

How this scores (AOI sub-dimensions)
Operational5/5how practical it is to run, serve and maintain in productionSmall dense models on a Llama base, which has the broadest toolchain and hardware support of any distil base.
Safety3/5whether misuse risks are evaluated and guardrails are providedReasoning behaviour is documented, which meets the score-3 anchor.
4

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

Strong

Self-hosted, the weights run entirely on the deployer's own infrastructure, on-device at 8B, with no telemetry and no claw-back. The licence restrictions limit use, not data residency.

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.
What this means for adoptionYou partially own these self-hosted Llama-base R1-Distill models. Self-hosting keeps your data yours (data-control strong, reliability strong). The Llama Community Licence's acceptable-use policy, 700M-MAU clause and naming and attribution duties hold use-and-modify at moderate. Ownership is therefore partial, one step below the Apache-2.0 Qwen distils (deepseek-r1-distill-qwen), which reach substantial. Prefer the Qwen distils unless the Llama toolchain is needed. Where these models are used, honour the Llama terms and deploy behind your own guardrails. No EU open-source exemption applies on the licence axis.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Licenceread2026-11-19
The DeepSeek-R1 README and the distil checkpoint cards state that the R1-Distill-Llama checkpoints are built on Meta Llama bases (Llama-8B on Llama 3.1, Llama-70B on Llama 3.3).
Model cardread2026-11-19
The R1-Distill-Llama model cards on the verified deepseek-ai HF org describe dense 8B and 70B models distilled from R1, with 128K context and safetensors weights.
Third-party analysisunverified2026-08-03
On public leaderboards the R1-Distill-Llama-70B is a strong reasoning model for its size and the 8B is modest.
Third-party analysisunverified2026-08-03
The R1-Distill checkpoints are research distils with no safety tuning of their own.
Third-party analysisunverified2026-08-03
The R1-Distill-Llama checkpoints are small (8B-70B) and below the systemic-risk threshold.