BitRun vs HyperQwen

BitRun

BitRun packages patched llama.cpp builds for ternary models into one download for macOS on Apple silicon, Windows and Linux, with a loopback-only OpenAI-compatible server. It is three days old with three pre-release versions, one maintainer and no CI, and its published power figures come from a fixed formula rather than measurement.

HyperQwen

HyperQwen packages a patched vLLM 0.32.0 and requantised Qwen3.8-27B weights into one container with tool calling preset and a loopback bind when no key is set. It runs one model family, its speed figures come from one RTX 3090, and it has no versioned releases, changelog or security policy.

BitRun

1. Ask the user to install BitRun and run bitrun pull <tag> and bitrun serve <tag> first. Then call http://127.0.0.1:11435/v1 with any API key string
2. Poll /health before the first request. The server loads the model in the background and answers only when ready
3. Use a model tag from the catalogue (bitnet-70m, bonsai-1.7b, falcon3-1b, bitnet-2b, falcon3-3b, bonsai-8b) and keep prompts within its context window
4. Treat the README's energy figures as estimates, and don't report them as measured power
5. Expect small research checkpoints. Check outputs before relying on them for code or facts

HyperQwen

1. Call http://127.0.0.1:18020/v1 with model qwen3.8-27b and the VLLM_API_KEY value, or any string if no key was set
2. Poll /health before the first request. A first start downloads and prepares the model and compiles kernels, which can take over 30 minutes
3. Declare the context window your setup uses (65,536 by default, 131,072 for CTX=long, 245,760 for CTX=huge) so the client doesn't truncate
4. Ask the owner to set VLLM_API_KEY before setting BIND=0.0.0.0, and to front the port with a proxy that allowlists routes
5. Treat the README's tokens-per-second figures as the project's measurements on one RTX 3090 at 250 W