# GLM-5.3, 756GB of Weights, and the Ten Billion Dollar Gate > Source: > Published: 2026-08-29 16:47:19+00:00 Z.ai released the weights for GLM-5.3 on Friday. The release package includes 756 GB of model files across 141 Safetensors shards, support for vLLM and SGLang, and an architectural configuration with 256 routed experts where 8 activate per token across a one-million-token context window. Two technical details in the release notes tell a practical story about where frontier model development is heading. The first detail is that Z.ai kept the exact base foundation from GLM-5.2. The company did not run a larger pretraining cluster or change the underlying parameter structure. The performance jump came from post-training: reinforcement learning environments, task verification harnesses, and domain data for software engineering and vulnerability hunting. Z.ai reports that Terminal-Bench 3.0 moved from 4.6 to 28.3, DeepSWE went from 46.2 to 66.9, and ExploitBench jumped from 24.4 to 54.4. Those numbers come from vendor-run evaluations under specific harness configurations, including 400,000 tokens of context and 10-hour timeouts per rollout. Independent reproduction across different serving stacks will show the real operational variance. Still, the architectural choice is clear: pretraining gave them a stable base, and the agentic capabilities were built almost entirely during post-training rollouts. The second detail is the license. Z.ai used a custom open-weight license that grants broad rights to run, modify, distribute, and commercialize the weights. Anyone building a product with embedded model features can run it freely. However, the license introduces a specific commercial condition: companies operating a Model-as-a-Service platform with combined group revenue exceeding ten billion dollars must pass a Z.ai security review before offering controllable inference or fine-tuning APIs. This splits open distribution into two tiers. If you are an indie developer, an early-stage startup, or an enterprise running internal automation, you have full access without asking for permission. If you are AWS, Microsoft Azure, or Google Cloud wanting to sell GLM-5.3 endpoints directly to your customers, you have to sit down for a vendor review. That distinction matters for open-weight definitions. It is not an OSI-approved open source license, and calling it unrestricted would be inaccurate. It is a targeted defense mechanism against cloud platforms capturing all the margin from an open model without contributing compute or licensing revenue back to the creators. Then there is the physical reality of running the model. A 756 GB weight download puts native, unquantized self-hosting in multi-GPU data center territory. Even with FP8 quantization, this is not something running on a single developer workstation or a modest homelab node. For most builders, the primary path will still be hosted endpoints. Cloudflare added GLM-5.3 to Workers AI right at launch at $1.40 per million input tokens, 26 cents per million cached tokens, and $4.40 per million output tokens. That gives developers an immediate way to test the coding and vulnerability triage capabilities without provisioning a dedicated H100 cluster. For engineering teams working with autonomous coding agents, the release reinforces two practical rules. First, agent capability is increasingly determined by the scaffolding and verification loops created during post-training rather than raw pretraining scale. A model that understands multi-turn execution and sandbox feedback behaves differently from a model that simply predicts the next code token well. Second, open weights shift operational responsibility to the deployer. When a model with strong vulnerability-discovery capabilities runs inside your infrastructure, network segmentation, egress controls, and tool permissions must be verified on your own host. The vendor provides the weights, but you own the blast radius.