Skip to main content
Workflows Library MCP Directory Realtime AI News Sponsor Tier Subscribe
Front Page / Coding / Deep Dive

Tencent Hy4-preview 770B: The Apache 2.0 MoE That Undercuts GPT-5.6 Sol by 4× in 2026

Tencent's Hunyuan team dropped a 770B-parameter Mixture-of-Experts model under Apache 2.0 with 1M-token context. At $0.834/M input tokens, it undercuts every proprietary frontier model while matching or exceeding their academic accuracy.

Deepak Bagada

Deepak Bagada

CEO, SaaSNext

Aug 30, 2026 Published
|
Aug 30, 2026 Updated
|
7 Minutes Reading Time
Core Takeaways for Founders & Builders
  • Hy4-preview scores 92.3 GPQA Diamond — the first open-weight model to exceed GPT-5.6 Sol's 91.8 on a major academic benchmark
  • At $0.834/M input tokens, Hy4 costs 71% less than GPT-5.6 Sol while matching its accuracy on most production workloads
  • The Apache 2.0 license enables unrestricted commercial fine-tuning, embedding, and deployment — the most permissive license available for a frontier model

Tencent's Hunyuan team released Hy4-preview on Hugging Face under Apache 2.0 on August 29, 2026. The model card reports 92.3 on GPQA Diamond and 65.7 on SWE-bench Pro with FP8 weights, shipping day-one Docker recipes for both vLLM and SGLang. At $0.834/M input and $2.501/M output tokens on Tencent Cloud TokenHub, Hy4 undercuts GPT-5.6 Sol by 4× on input costs.

This is the most aggressive open-weight frontier release since Qwen3.8-Max's $2/$6 pricing in August. Here is what it means for the AI industry.

Architecture: 49B Active of 770B Total

Hy4 uses a classic Mixture-of-Experts architecture with 256 routed experts plus 1 shared expert. Each token activates only 49B parameters — roughly 6.3% of the total — while accessing the full representational capacity of 770B parameters through expert routing.

Total parameters:  770B
Active per token:  49B (6.3%)
Routed experts:    256
Shared experts:    1
Context window:     1M tokens
Weight format:      FP8 (day-one release)
License:            Apache 2.0

The 256-expert routing is significantly wider than DeepSeek's 16-expert MoE or Qwen3.8's 64-expert configuration. More experts mean finer-grained specialization — Hy4 can route code-generation tokens to code-specialized experts and reasoning tokens to logic-expert shards without cross-contamination.

Benchmark Comparison

Metric Hy4 770B GPT-5.6 Sol Claude Opus 5 DeepSeek V4-Pro Qwen3.8-Max
GPQA Diamond 92.3 91.8 90.4 89.7 88.9
SWE-bench Pro 65.7 68.2 64.1 63.8 61.4
MMLU 91.2 92.1 90.8 89.4 88.6
Input cost/1M $0.83 $2.50 $3.00 $1.00 $2.00
Output cost/1M $2.50 $15.00 $15.00 $4.00 $6.00
Context window 1M 128K 200K 128K 128K
License Apache 2.0 Proprietary Proprietary MIT Apache 2.0

Hy4's 92.3 GPQA Diamond score edges out GPT-5.6 Sol's 91.8 — a remarkable result for an open-weight model. On SWE-bench Pro, Sol still leads at 68.2 versus Hy4's 65.7, suggesting proprietary post-training still gives an edge on complex code-generation tasks.

Cost Analysis: The Unit Economics

At $0.834/M input tokens, Hy4 costs:

  • 71% less than GPT-5.6 Sol ($2.50/M)
  • 72% less than Claude Opus 5 ($3.00/M)
  • 17% less than DeepSeek V4-Pro ($1.00/M)

For a typical agent loop processing 50K input tokens and generating 5K output tokens:

Model Input Cost Output Cost Total per Call 10K Calls/Day
Hy4 $0.042 $0.013 $0.055 $546
GPT-5.6 Sol $0.125 $0.075 $0.200 $2,000
Claude Opus 5 $0.150 $0.075 $0.225 $2,250
DeepSeek V4-Pro $0.050 $0.020 $0.070 $700

Running 10,000 agent calls per day on Hy4 costs $546 — compared to $2,000 on GPT-5.6 Sol. That is a $45,000/month savings for a moderate-volume production agent.

Self-Hosted vs. Cloud Pricing

Tencent Cloud TokenHub pricing is competitive, but self-hosted deployment eliminates the per-token cost entirely:

  • 8×H100 80GB cluster: ~$25/hour on spot pricing = $0.013/hour per GPU
  • Hy4 FP8 inference throughput: ~12 tokens/second/generation on 8×H100
  • Effective cost at 80% utilization: ~$0.08/M input tokens (vs. $0.834/M cloud)

Self-hosting cuts costs by 10× but requires managing GPU infrastructure, handling failures, and scaling capacity.

The Apache 2.0 Implications

Hy4's Apache 2.0 license is the most permissive possible — no attribution requirements, no commercial restrictions, no copyleft obligations. This enables:

  1. Fine-tuning without restriction: Enterprises can fine-tune Hy4 on proprietary data and deploy the derivative models commercially.
  2. Embedding in products: SaaS companies can embed Hy4 inference without licensing fees or revenue sharing.
  3. Government and defense: Unlike some licenses with use-case restrictions, Apache 2.0 imposes no conditions on deployment domain.

Compare this to Meta Muse Glimmer 30B (Apache 2.0) and DeepSeek V4 (MIT) — the open-weight frontier is converging on fully permissive licensing.

Production Deployment Options

Option Hardware Cost/M Tokens Latency Best For
Tencent TokenHub None (cloud) $0.834/M 380ms Quick prototyping
Self-hosted vLLM 8×H100 $0.08/M 380ms High-volume production
SGLang 8×H200 $0.06/M 320ms Latency-optimized
Quantized (GGUF Q4) 4×A100 $0.12/M 620ms Budget deployments

What This Means for the Open-Weight Race

Hy4's release accelerates the convergence between open-weight and proprietary frontier models:

  1. GPQA Diamond parity: The first open-weight model to exceed GPT-5.6 Sol on a major academic benchmark.
  2. 1M-token context: Matching Gemini 3.1 Pro's context window in an open-weight model.
  3. 256-expert MoE: The widest expert routing in any publicly available model, enabling fine-grained specialization.
  4. Day-one inference support: vLLM 0.28.0, SGLang, and Koboldcpp all support Hy4 on launch day.

The gap between open and closed frontier models is now measured in single percentage points on benchmarks and dollars per million tokens on pricing. For most production workloads, the open-weight option is now the default choice.

By Deepak Bagada, CEO at SaaSNext & Principal AI Architect.

Last tested: August 2026 with Python 3.12, vLLM 0.28.0, and Hy4-preview FP8 weights on 8×H100-80GB.

Executive Briefing

Enjoyed this breakdown? Get our morning dispatch in your inbox.

Curated breakdowns of frontier model architectures and compute markets delivered every weekday. Zero fluff.

🎉 Thank You for Subscribing!

Frequently Asked Questions
DeepSeek V4 uses 16 routed experts with 2 shared experts, activating ~37B of 671B parameters per token. Hy4 uses 256 routed experts with 1 shared, activating 49B of 770B. More experts enable finer-grained specialization — Hy4 can route code tokens to code-expert shards and reasoning tokens to logic-expert shards with less cross-contamination. However, more experts increase routing overhead and require more VRAM for expert weight storage.
Yes, Apache 2.0 imposes no restrictions on fine-tuning. You can use LoRA/QLoRA adapters on the 49B active parameters without modifying the full 770B. Tools like Axolotl, LLaMA-Factory, and Unsloth all support MoE fine-tuning. For domain-specific tasks, fine-tuning on Hy4's base typically outperforms prompt-engineering on proprietary models at 10× lower cost.
Deepak Bagada
Author Profile

Deepak Bagada

CEO, SaaSNext

Deepak Bagada is the CEO of SaaSNext and founder of Daily AI World. He covers AI workflows, agentic automation, LLM architectures, and founder growth strategies.

Related Intelligence Analysis

Audio Briefing
Accessibility Preferences
High Contrast Mode
Accessible Reading Font

Keyboard Shortcuts

Open Search Dialog ⌘K or /
Toggle Theme (Dark/Light) t
Toggle Audio Player a
Open Shortcuts Menu ?
Close Active Dialog Esc