COMMUNITY COLLECTION / DEPLOYMENT RECIPE
Start with a fixed source revision, then select a matching model artifact and hardware profile.
The current recipe selects the 1017 checkpoint by default. Check precision, engine version and hardware-specific flags before serving.
Model-specific serving recipe with NVFP4, FP8 and BF16 paths, hardware overrides and optional acceleration.
Dense Qwen3.8 deployment reference with separate quantization artifacts and workstation or accelerator profiles.
Large MoE recipe with explicit multi-GPU strategies and distinct native versus extended context claims.
Serving recipe for Flash with FP8, NVFP4 and BF16 choices and model-specific engine settings.
Full GLM-5.3 recipe, including quantization alternatives and accelerator-specific serving controls.
Kimi K3 deployment recipe with separate MXFP4, NVFP4 and other artifact paths and parallelism strategies.
M3 serving recipe covering full and converted weights, hardware overrides and optional acceleration.
Step 3.7 Flash engine recipe with separate BF16, FP8 and NVFP4 artifacts.
MiMo serving reference whose default artifact is MOPD and whose RL variant preserves the separate RL checkpoint.
Nemotron Lightning recipe with distinct NVFP4 and BF16 choices and engine constraints.
Recent multimodal Nemotron recipe with per-artifact hardware restrictions and selected GB200 layouts.
A smaller MoE deployment recipe with publisher and third-party FP8/NVFP4 alternatives.
Compact Qwen3.5 recipe with explicit Intel CPU/GPU artifact allowlists in the pinned version.
MXFP4 serving recipe with accelerator allowlists and model-specific serving controls.
Gemma 4 serving recipe with BF16 and multiple converted precision paths.
Large DeepSeek Pro recipe with a dated default checkpoint and separate draft/quantized variants.
Image-generation recipe with vLLM-Omni requirements and separate precision choices.
Start with the upstream build and server documentation for a GGUF deployment. Choose the backend for your own platform and keep the model artifact separate from the runtime revision.
A maintainer starting point for native installation and local model serving. Use its linked documentation to check platform support, installed model identity and local/cloud behavior.
Follow the serving project and its documentation when planning a compatible model-serving environment. Backend, architecture, package and model support are version-dependent.
An upstream reference for model-serving deployments. Begin with the project documentation, then verify the exact backend, model and container combination you intend to use.
The converter reports a 1000-tensor base, its exact assembled file size and a successful loader binding check. The separate vision sidecar and official 1017 Engram files retain individual identities. These are artifact and loader observations. The selected source explicitly has no 1017-specific serving speed, peak RAM or model-quality measurement.
Optional Google Analytics helps us understand which sources and tools are useful. It stays off unless you allow it. You can change your choice at any time. Read our privacy notice.
