antirez/ds4: README-based editorial guide

antirez/ds4 describes itself in the README as "DeepSeek 4 Flash and PRO local inference engine for Metal, CUDA and ROCm". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: DwarfStar is a small native inference engine optimized first for DeepSeek V4 Flash. It also supports GLM 5.2 and, on very high-memory machines, DeepSeek V4 PRO. It is self-contained and deliberately narrow, not a general GGUF runner.. That establishes the project's stated boundary, not a production test.

The README's "README" section gives a useful starting point for deciding whether the project fits: NVIDIA CUDA, including multi-GPU systems and DGX Spark.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Metal, the primary target, on Macs with 96 GB or more. Smaller machines. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "README". The source evidence includes: Model support is intentionally opportunistic. The project follows the best open weights for useful local machine sizes, especially 128 GB laptops and 512 GB workstations. A model may be removed when a better replacement arrives.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: make # macOS Metal make cuda-spark # Linux CUDA, DGX Spark / GB10 make cuda-generic # Linux CUDA, other local CUDA GPUs make strix-halo # Linux ROCm, AMD Strix Halo make cpu # CPU-only diagnostics build When the README contains no runnable command, this article does not invent one. Open its "Motivations" section and confirm system dependencies, default ports, and first-run initialization before using a public server.