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 native MXFP4/MXFP8 weights from the verified moonshotai org on Hugging Face (huggingface.co/moonshotai/Kimi-K3) and serve them with vLLM, SGLang or TokenSpeed. Pin the exact revision hash and verify per-file checksums before loading.
Hardware & VRAM requirements
Kimi K3 is a 2.8T-parameter MoE (104B active). Even at native MXFP4 the full weights are about 1.4 TB, so serving needs a multi-GPU or multi-node cluster; there is no single-GPU or laptop path. The model card does not state exact per-GPU VRAM, so size against the cluster's aggregate memory and interconnect.
Serving stacks
The card documents vLLM, SGLang and TokenSpeed. KTransformers and TensorRT-LLM are not listed, so the supported stack is narrower than the Kimi K2 lineage. MXFP4/MXFP8 kernels are version-sensitive, so confirm current engine support and versions before committing.
Safe-deployment controls & Deployment Ceiling
Deployment Ceiling: T2 (customer-facing, human-reviewed), conditional. The weights ship with no safety tuning, guard model or refusal training, so the entire control stack must be supplied externally: a companion guard or classifier model, input and output guardrails, prompt-injection defences and conservative decoding.
The technical report documents offensive-cyber capability the model does not refuse. Sandbox and tightly bound any agentic, tool-use or code-execution deployment. T3+ (autonomous) is cautioned against without controls beyond what an open model can currently justify.
Complete the pre-deployment gate in the safe-deployment playbook, pin and checksum the checkpoint, and red-team for the specific use case before any exposed deployment.
Available quantizations
The weights are natively quantization-aware-trained (MXFP4 weights, MXFP8 activations), so the canonical checkpoint is already a low-precision artifact. Community MXFP4/GGUF quants make the 2.8T model more tractable but are community artifacts; verify each one.
Fine-tuning & adaptation
The downloadable weights and a broadly commercial licence support SFT and LoRA adaptation. Training data and code are closed, so there is no from-scratch reproduction path. Full fine-tuning at 2.8T scale is very resource-intensive, so parameter-efficient adaptation is the practical route without frontier-scale infrastructure.
API / OpenAI-compatible integration
Serve behind the OpenAI-compatible endpoint of vLLM or SGLang for drop-in client integration. Kimi K3 is natively multimodal, so text, image and video inputs and tool calls map onto the serving layer's APIs. Confirm the exact multimodal request format against the serving engine's documentation.
How this scores
The ownership factors this domain covers, drawn from the one entry record.
ReliabilityIs it reliable and good enough for the job?
WeakCapability is frontier-competitive, but safety scores 1: no safety tuning, guard or refusal training exists, and the report documents offensive-cyber capability the model does not refuse. The model is presented as deployable while safety is left entirely to the adopter. Under the ownership rule, safety <= 1 for a deployable model makes reliability weak regardless of benchmark strength.
Doesn't extract your dataDoes running it keep your knowledge and data yours?
StrongSelf-hosted, the weights run entirely on the deployer's own infrastructure with no telemetry or licence claw-back, so data stays with the deployer. The hosted platform.kimi.ai service differs: its terms and privacy policy train on user prompts, images, video and files by default, with opt-out only via an enterprise arrangement on request (Singapore law / SIAC). Data control therefore requires the weights and not the hosted API. Self-hosting is constrained by the ~1.4 TB footprint, which forces multi-node serving.
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.