Deep Principle, China · Released October 31, 2026New
Hydrogen-1.0 has 753.3B parameters (40.3B active per token). In BF16 its weights alone take 1385 GiB; quantized to 4-bit, about 418 GiB. Each 32K-token request adds 2.83 GiB of KV cache. Cheapest way to run it today: 5 × RTX PRO 6000 Blackwell (96 GB) at $6.33 per hour.
Weights plus the KV cache of one request (BF16 cache), in GiB. Add 1 to 3 GiB for the inference engine itself.
Weights format
Weights only
+ 8K context
+ 32K context
+ 128K context
+ 1M context
NVFP4 experts + BF16 (native)
423
424
426
434
513
BF16 / FP16
1385
1385
1387
1396
1475
FP8 / INT8
694
695
697
705
785
4-bit (GGUF Q4_K_M)
418
419
421
429
509
How many GPUs to run Hydrogen-1.0
Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.
GPU
NVFP4 experts + BF16 (native)
BF16 / FP16
8-bit
4-bit
GeForce RTX 4090 24 GB
Not on this GPU
96 (several machines)
48 (several machines)
24 (several machines)
GeForce RTX 5090 32 GB
Not on this GPU
64 (several machines)
32 (several machines)
16 (several machines)
RTX PRO 6000 Blackwell 96 GB
Not on this GPU
16 (several machines)
8
5
Mac M5 Max 128 GB 96 GB usable
Not on this GPU
16 (several machines)
8
5
Ryzen AI Max+ 395 128 GB 96 GB usable
Not on this GPU
16 (several machines)
8
5
DGX Spark (GB10) 128 GB
Not on this GPU
16 (several machines)
6
4
NVIDIA H100 80 GB
Not on this GPU
24 (several servers)
16 (several servers)
7
NVIDIA H200 141 GB
Not on this GPU
16 (several servers)
6
4
NVIDIA B200 (HGX) 180 GB
3
16 (several servers)
5
3
8-bit: FP8 with vLLM (INT8 on GPUs without FP8), Q8_0 with llama.cpp. 4-bit: AWQ / GPTQ with vLLM, Q4_K_M with llama.cpp, both counted at the Q4_K_M size. Not on this GPU: the official NVFP4 experts + BF16 weights do not run there (llama.cpp needs a GGUF version, and vLLM needs a GPU with FP4 support).
Cheapest way to run Hydrogen-1.0 today
For each GPU: the fewest cards that fit Hydrogen-1.0 with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-11-06).
On-demand prices from AWS, Google Cloud, Azure, RunPod, Vast.ai, Oracle Cloud, OVHcloud, Scaleway, Verda, Akash and UpCloud, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.
Architecture: GLM-5.3 post-trained for science · MoE 256 experts · MLA (512 + 64 latent) on 78 layers · sparse-attention indexer keys on 21. Its cache stays compact because MLA stores one compressed latent per token and layer instead of full keys and values. Only 40.3B parameters are active per token, but all 753B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.71 GiB
0.41 GiB
32K tokens
2.83 GiB
1.65 GiB
128K tokens
11.3 GiB
6.58 GiB
1M tokens
90.5 GiB
52.7 GiB
Hydrogen-1.0 VRAM FAQ
How much VRAM does Hydrogen-1.0 need?
In BF16 the weights alone take 1385 GiB (1487 GB). In FP8 that is 694 GiB, and about 418 GiB with 4-bit quantization (Q4_K_M); the official NVFP4 experts + BF16 checkpoint is 423 GiB. Each request then adds KV cache: 0.71 GiB at 8K tokens and 2.83 GiB at 32K (BF16 cache).
Can Hydrogen-1.0 run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 24 RTX 4090s, spread over several machines. In 4-bit it needs 7 H100 GPUs.
Can Hydrogen-1.0 run on an RTX 5090 (32 GB)?
No. Even in 4-bit it needs 16 RTX 5090s, spread over several machines.
Can Hydrogen-1.0 run on a Mac?
No single Mac holds it, even in 4-bit: it needs 419 GiB with an 8K-token context, and the largest Mac (512 GB) gives its GPU about 384 GB.
Can Hydrogen-1.0 run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
No. Even in 4-bit it needs 4 DGX Spark units or 5 Ryzen AI Max+ 395 machines (128 GB), linked over the network.
What is the cheapest way to run Hydrogen-1.0?
On 2026-11-06, the cheapest on-demand setup is 5 × RTX PRO 6000 Blackwell (96 GB) with Q4_K_M weights on Vast.ai, at $6.33 per hour (about $4,624.55 per month). Next: 3 × AMD MI300X (192 GB) with 4-bit weights on RunPod, at $7.17 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Hydrogen-1.0 need?
With one request and an 8K-token context: 24 in BF16, 16 in FP8 and 7 in 4-bit (vLLM, 90% of memory usable). Above 8 GPUs, that means several servers. Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
Hydrogen-1.0 VRAM badge
For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/hydrogen-1-0.json.
Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.