HyperQwen vs Jan

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.

Jan

Apache-2.0, with installers for macOS, Windows and Linux plus Flathub and the Microsoft Store. No release since 0.8.4 on 23 July 2026, while a security fix waits on main.

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

Jan

1. Ask the owner to start the server (Settings, Local API Server) or run jan serve. Nothing listens until then
2. Call http://127.0.0.1:1337/v1 for the app and localhost:6767/v1 for jan serve. The ports differ
3. Read /openapi.json from the running server, not the spec on the docs site, which describes the retired Cortex API
4. Branch on the status code. Error bodies are plain text
5. Keep the bind at 127.0.0.1 on 0.8.4. Trusted Hosts is ignored on 0.0.0.0 until the next release