Can you run it?
This page is a projection of the one entry record, the Reliability and Data control factors that Implement covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Install & run
Download the safetensors from the verified THUDM organisation on Hugging Face and serve with transformers, vLLM, llama.cpp, or Ollama; it runs on a single consumer GPU. Complete the glm-4 commercial registration first if your use is commercial. Pin the exact revision and verify checksums.
Hardware & VRAM requirements
A 9B dense model runs on a single consumer GPU, or CPU when quantized. The GLM-4-9B-Chat-1M variant advertises a 1M-token context, which is memory-intensive; the standard Chat is 128K.
Serving stacks
vLLM, transformers, llama.cpp, and Ollama give broad support for a small 2024 model, though the tooling is older than the current GLM line.
Safe-deployment controls & Deployment Ceiling
Deployment Ceiling: T2 (conditional). First, complete the commercial registration and honour the glm-4 naming and field-of-use terms, which are binding licence conditions. Account for the revocable grant in your risk assessment. Then supply your own input/output guardrails and a guard/classifier model (China-aligned alignment, no first-party guard), and add prompt-injection defences for agentic use.
Available quantizations
Widely quantized (GGUF and lower-bit) as a small model. Redistribution of these derivatives must carry the glm-4 licence and the name rules; verify provenance per mirror.
Fine-tuning & adaptation
Fine-tuning is permitted, but derivatives carry the revocable, registration-gated licence and the mandatory "glm-4" name prefix. The training data and code are closed, so there is no from-scratch reproduction.
API / OpenAI-compatible integration
Serve behind vLLM's OpenAI-compatible endpoint. The 2024-era chat template and tool-call conventions are older than the current GLM line, so confirm behaviour per serving stack.
How this scores
The ownership factors this domain covers, drawn from the one entry record.
ReliabilityIs it reliable and good enough for the job?
ModeratePerformance 2 (dated, succeeded by newer models), operational 4, safety 3: runnable and broadly supported, but the below-average current capability holds reliability to moderate.
Doesn't extract your dataDoes running it keep your knowledge and data yours?
ModerateSelf-hosting keeps your processing local, but the licence grant is revocable and commercial use hinges on a registration the publisher controls, so your control over continued use is contingent and not assured. Moderate and not strong.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.