Can you run it?
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.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Install & run
Download the safetensors from the verified deepseek-ai organisation on Hugging Face (V3-0324 or V3.1) and serve with vLLM, SGLang, llama.cpp or Ollama. Pin the exact revision and verify checksums before loading. Use a V3-0324-or-later checkpoint for the MIT grant.
Hardware & VRAM requirements
The model is a 671B-total / 37B-active MoE. Even quantized the weights are large, so full-fidelity deployment needs multiple GPUs or nodes. Community quantizations (GGUF and lower-bit) make reduced-precision serving tractable on smaller footprints, at the usual quality cost. The 128K context adds KV-cache pressure on long inputs.
Serving stacks
vLLM, SGLang, llama.cpp and Ollama all support the model, and third-party hosting was wide shortly after release.
Safe-deployment controls & Deployment Ceiling
Deployment Ceiling: T2 (conditional). No first-party guard model ships and safety tuning is lighter than at Western frontier labs. Supply input/output guardrails and a guard or classifier model, add prompt-injection defences, and treat retrieved and tool content as untrusted in agentic use. Account for China-aligned topic filtering on sensitive prompts. With these controls the model is deployable for general-purpose assistant use. Without them it is not customer-safe.
Available quantizations
Community quantizations (GGUF and lower-bit) are widely available. MIT permits redistribution of these derivatives. Each is a separate artifact whose trust equals its uploader, so verify provenance and prefer hosts already trusted.
Fine-tuning & adaptation
MIT permits unrestricted fine-tuning and distillation of the released V3-0324 and V3.1 weights. Training data and code are closed, so the model cannot be reproduced from scratch.
API / OpenAI-compatible integration
Serve behind the OpenAI-compatible endpoint of vLLM or SGLang and point the existing client at it. V3.1 exposes a hybrid reasoning mode, so the client must separate any reasoning segment from the final answer.
How this scores
The ownership factors this domain covers, drawn from the one entry record.
ReliabilityIs it reliable and good enough for the job?
StrongPerformance 4, operational 5 and safety 3: all three are at or above 3 and two at or above 4, so reliability is strong. The caveat is that no first-party guard model ships.
Doesn't extract your dataDoes running it keep your knowledge and data yours?
StrongSelf-hosted, the MIT weights run entirely on the deployer's own infrastructure with no telemetry and no licence claw-back, so data stays with the deployer. The hosted DeepSeek API is separate and has its own data terms.
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.