Support · GLM
Will it last?
Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input C · 65.2/100
This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
Which domain expands which factor
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Common problems & fixes
Common pitfalls, not an exhaustive catalogue.
Out-of-memory on the MoE: the 355B and 106B MoE hold their full parameter count in memory even
at 32B/12B active. Use a smaller variant, quantize, or move to a multi-GPU node, and reduce
max context to shrink the KV cache at the 200K window.
Garbled or over-verbose output usually means the chat template is not applied or the
thinking/agentic mode is mishandled. Use apply_chat_template.
Checksum drift across hubs: the dual Hugging Face (zai-org) / ModelScope distribution means
checksums must match, and a mismatch signals a stale mirror or the legacy THUDM org.
Wrong-LICENSE assumption: not every GLM checkpoint is MIT, and the original glm-4-9b is
custom-licensed. Read the LICENSE on the exact model.
Non-reproducible results come from floating on main. Pin an exact revision.
Versions, changelog & cadence
Releases follow a rapid cadence, GLM-4-0414 → GLM-4.5 / GLM-4.5-Air → GLM-4.6, not a rolling
semantic-version stream. Versions are tracked as immutable Hugging Face / ModelScope revisions
on the verified zai-org org, so the revision hash is the changelog anchor. Pin it, and diff
against a newer revision when upgrading. GitHub repositories (zai-org/GLM-4,
zai-org/GLM-4.5) and technical reports accompany the releases.
Newer releases exist outside this entry's scope: GLM-4.7 (2025-12), GLM-5 (2026-02), GLM-5.1
(2026-04), GLM-5.2 (2026-06), GLM-5.3 and GLM-5.3-Flash (2026-08). They are not scored here,
and GLM-4.6 is the newest tracked checkpoint. GLM-5.3 carries a custom licence
(ev-license-glm53).
Usage questions go to the Hugging Face model discussion tabs on the zai-org org
(ev-hf-zai). The China-facing community is on ModelScope org discussions
(ev-modelscope). Inference-code and integration problems go to GitHub issues on the
zai-org/GLM-4 and zai-org/GLM-4.5 repositories (ev-github).
There is no paid support tier around the open weights, only community and maintainer support.
Zhipu offers a separate commercial hosted API under the Z.ai brand.
Tracked known issues
These come from model-card and third-party caveats, not a formal issue tracker, hence partial.
China-aligned alignment and hosted-API content moderation affect politically sensitive topics.
Safety tuning is lighter than at the large Western labs, with no companion guard model.
Capability leadership is concentrated in coding and agentic tasks. The 355B MoE has an
unresolved EU systemic-risk / Article 55 question, with no published documentation.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
2
TransparencyDo you know what it is: weights, training, behaviour, and legible terms?
WeakThe weights are held but cannot be explained: training data and training code are closed, the models carry China-aligned alignment that cannot be inspected, and the hosted Z.ai API applies Chinese content moderation.
How this scores (AOI sub-dimensions)
Provenance3/5how well we can trace and verify what went into the modelThe zai-org org on Hugging Face is verified, with official ModelScope publication, safetensors with checksums and no malicious incident on the canonical org (checklist 5/8).
Governance3/5how accountable and well-documented the publisher isZhipu AI / Z.ai is an active, accountable publisher with a rapid release cadence and a verified presence on Hugging Face and ModelScope.
What this means for adoptionYou substantially but not uniformly own the GLM line, and the split is per variant. The current line is MIT: GLM-4.6 ships a checked-in MIT LICENSE ('Copyright (c) 2026 Zhipu AI') and the GLM-4.5 and GLM-4-0414 siblings declare the same MIT via HF metadata and README. They can be run, fine-tuned, distilled, redistributed and commercialised with no gate. The legacy glm-4-9b is not plain MIT. Its custom 'glm-4' licence requires commercial-use registration, 'Built with glm-4' attribution and a name prefix, and is governed by PRC law with disputes to Beijing's Haidian District court. Verify the LICENSE per checkpoint. Two things hold ownership at partial: training is opaque (closed data and code, China-aligned alignment that cannot be inspected) and no safety battery is benchmarked, so supply your own guards. The weights you self-host are yours. The hosted Z.ai service is Singapore-governed (SIAC arbitration), a different legal regime from the PRC glm-4-9b weights licence, and the two should be kept apart.
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.
Model cardread2026-07-25
GLM-4.6 is a 355B-total / 32B-active MoE with a 200K context window, released by Zhipu AI / Z.ai and hosted on the zai-org Hugging Face org; the model card/metadata declares MIT.
Model cardread2026-07-25
GLM-4.5 (355B/32B) and GLM-4.5-Air (106B/12B) are MoE models on the zai-org Hugging Face org; the GLM-4.5 README states "They are released under the MIT open-source license and can be used commercially and for secondary development."
Model cardread2026-07-25
GLM checkpoints are hosted on the verified zai-org org on Hugging Face in safetensors with checksums (the current org; legacy checkpoints are under THUDM).
Licenceread2026-11-19
GLM-4.5, GLM-4.5-Air and GLM-4.6 declare the OSI-approved MIT license, which permits commercial use, via HF metadata ("license: mit") and README only.
Licenceread2026-11-19
GLM-5.2 ships an in-repo MIT LICENSE file: standard MIT text with no custom clauses, "Copyright (c) 2026 Zhipu AI." GLM-5.1 carries a byte-identical file and GLM-5.3-Flash a standard MIT file ("Copyright (c) 2026 Z.AI Co., Ltd").
Licenceread2026-11-19
Boundary evidence, outside the tracked checkpoints.
Licenceread2026-07-25
Licensing is per variant and the legacy glm-4-9b is NOT plain MIT.
Licenceread2026-11-19
The GLM-4-0414 family (dense GLM-4-32B-0414 and GLM-4-9B-0414, up to 128K extended context) was open-sourced under the MIT license.
Documentationunverified2026-07-25
Zhipu / Z.ai publishes GLM inference code and technical reports on GitHub (zai-org/GLM-4, zai-org/GLM-4.5), but not the training data or training pipeline.
Model cardunverified2026-07-25
GLM models are also officially published on Alibaba's ModelScope hub (dual distribution) by Zhipu.
Terms of serviceread2026-11-19
Hosted Z.ai Terms of Service (Last Update April 14, 2026): governed by Singapore law with SIAC arbitration (seat Singapore).
Privacy Policyread2026-11-19
Hosted Z.ai Privacy Policy (Last Update September 29, 2025): data is processed in Singapore.
Third-party analysisunverified2026-07-25
Third-party evaluation places GLM-4.6 among the stronger open models for real-world coding, tool use and agentic tasks.
Third-party analysisunverified2026-07-25
GLM models carry China-aligned alignment and the hosted Z.ai API applies Chinese content moderation on politically sensitive topics.
Third-party analysisunverified2026-07-25
GLM is supported for local serving on vLLM and SGLang (with community GGUF quants for the dense sizes) and distributed across Hugging Face and ModelScope.
Third-party analysisunverified2026-07-25
GLM instruct variants are safety-tuned but with lighter alignment coverage than Western frontier labs and no companion guard model.
Model cardunverified2026-07-25
No public EU AI Act training-content summary, copyright policy, or Article 55 documentation is published for GLM, and the 355B MoE's systemic-risk status is unconfirmed.