K2HorizonStart guide
Every way to use it

All the ways to use K2 Horizon

From a browser tab to a GPU cluster. Pick the one that fits you, then start a guided route or copy the official command.

Reference

The K2 Horizon family

Six sizes, from small devices to GPU servers. On a laptop, the guide picks a size for you and the check level confirms it. The server sizes run with vLLM or SGLang, or through a hosted API.

SizeMade forGood atWatch outDownloadSpeed*
On a laptop
0.9B8 GB computers, quick commandsInstant replies, reminders, simple tool callsSlips on reasoning. Not for coding.0.7–1.2 GB~165 tok/s
3.7B16 GB laptopsSummaries, document Q&A, tool calls, code fixesArabic phrasing was partly wrong in testing3.2–5.4 GB~46 tok/s
7.0B24 GB+ laptops and workstationsPassed every check in our testsSlowest of the three. Needs about 16 GB free.5.6–9.6 GB~40 tok/s
On GPU servers
32BGPU servers (recipe validated on 2× H200)Large dense model with a 512K context windowToo big for laptopsBF16 · FP8 · NVFP4—
36B
MoVA-36B-A4B
GPU servers (recipe validated on 2× H200)Mixture of experts: 36B stored, only 4B active per tokenNeeds expert parallel in vLLM or SGLangBF16 · FP8—
375B
375B-A23B
One 8× H200 nodeThe flagship. Agentic tool use, terminal and long multi-step workNeeds a full 8-GPU nodeBF16 · FP8 · NVFP4—

*Measured on an Apple M4 Pro Mac with 24 GB. A token is about ¾ of a word. Computers without a GPU are several times slower. For server speeds, see the vLLM and SGLang recipes. All models are on Hugging Face.

Reference

Fix a problem

Each of these happened during real testing. Search for what you see, or paste your error into any level's check box and the guide spots it for you.