# Deploy Qwen3-Coder-Next on dedicated GPUs

Qwen3-Coder-Next by Qwen, deployable on sference as a dedicated deployment: reserved GPU capacity, private endpoint, European GPUs, billed per GPU-hour on monthly commitments. Request it at https://sference.com/models/Qwen/Qwen3-Coder-Next.

## Specs

- Hugging Face: https://huggingface.co/Qwen/Qwen3-Coder-Next
- Category: Coding
- Parameters: 80B
- Architecture: MoE · 512 experts, 10 active
- Context: 256K tokens
- Published precision: BF16
- Checkpoint size: 159 GB
- Minimum footprint: 4 GPUs (80 GB) or 2 GPUs (141 GB) to load the weights; more for long contexts and concurrency
- License: Apache 2.0 (Commercial use allowed) — https://huggingface.co/Qwen/Qwen3-Coder-Next/blob/main/LICENSE

## FAQ

### Can I run Qwen3-Coder-Next on a dedicated deployment in Europe?

Yes. sference deploys Qwen3-Coder-Next on GPU capacity reserved for you, behind a private endpoint, with every request processed on European GPUs and logged in your audit trail. Tell us your expected volume and latency targets with the form on this page and we come back with a sizing and a quote.

### How many GPUs does Qwen3-Coder-Next need?

The published checkpoint is about 159 GB (BF16), so loading it takes at least 4 GPUs with 80 GB of memory each, or 2 GPUs with 141 GB each. Long contexts and high concurrency need more for the KV cache; quantization needs less. You don't pick hardware on sference: you choose a performance tier and we size the deployment.

### Is Qwen3-Coder-Next licensed for commercial use?

Qwen3-Coder-Next is published under the Apache 2.0 license. Permissive: commercial use, modification, and private deployment allowed; keep the license and notices.

### How is a dedicated deployment priced?

Per GPU-hour on a monthly commitment, sized to your throughput and latency targets.

Facts from Hugging Face, synced 2026-10-27. All deployable models: https://sference.com/dedicated.md