[email protected]

Qwen Hosting in Germany: Run Qwen Models on a Dedicated GPU

You want to use Qwen for chat, coding or documents without sending prompts to a third-party API. We run the right Qwen checkpoint on a dedicated GPU server in a German data centre.

  • Operated in a German data centre
  • Operation under a DPA
  • vLLM and OpenAI-compatible API
Reviews
Cloud Wolke HerausforderungServer NachhaltigkeitIT Beratung Service Consulting SoforthilfeTimo Wevelsiep Robin ZinsExperten für Innovation Migration AWSHetzner Hosting zuverlässig

Customers from mid-sized business, industry and the public sector, in Germany and internationally

  • Stadtwerke Brühl
  • DGHO e.V.
  • solarwerkstatt berlin
  • Krüger Dirndl
  • ABCO Water Systems
  • Golem.de
  • EVADXB
  • nextGYM
  • AInergy
  • ml&s
  • Odiseo Solutions
  • Annota
  • ARGE
  • SweetConnect GmbH
  • Aphy AG
  • CORGOS
  • Rekorder
  • SolidProof
  • Yonju
  • Keymate
  • Paritel
  • Mr. Clipart
  • Millenium
  • Negosh
  • Führerscheinmacher
  • BTI
  • Deutsche Gesellschaft für Datenschutz
Read client reviews

Starting point

Why run Qwen yourself

Qwen is Alibaba's open-weight model family. The current models cover general chat with image input (Qwen3.8-27B), large mixture-of-experts models (Qwen3.5-122B-A10B) and dedicated coding models (Qwen3-Coder-Next). The checkpoints covered here are licensed under Apache 2.0. On your own server the weights run locally. Prompts, documents and source code are not sent to Alibaba or any other model API, and costs do not depend on the number of tokens.

  • Data stays in Germany

    The model runs on a dedicated server in a German data centre. Under a data processing agreement, with no data path to a model API.

  • Predictable costs

    A fixed monthly price per server tier instead of billing per consumed token. More requests do not increase the invoice.

  • Model version under control

    Checkpoint and quantisation stay until you agree to a change. No silent model update by a provider.

Model facts

Qwen checkpoints at a glance

Vendor specifications and weight file size per format, with source.

CheckpointReleasedParametersContext (vendor)Weights per format
Qwen/Qwen3.8-27B08/202627.8B (dense, with vision)262,144 tokens nativeBF16: 55.6 GB
FP8: 30.9 GB
NVFP4: 21.9 GB
Qwen/Qwen3.5-122B-A10B02/2026122B total / 10B active (MoE)262,144 tokens nativeBF16: 250.2 GB
FP8: 127.2 GB
Qwen/Qwen3-Coder-Next02/202680B total / 3B active (MoE)262,144 tokens nativeBF16: 159.4 GB
FP8: 80.4 GB
  • GB = 10⁹ bytes, sum of the weight files in the listed Hugging Face repository. Operation additionally needs memory for KV cache, runtime and image processing where applicable. As of October 2026.

Licence

Qwen: licence and commercial use

Licence

Apache License 2.0 (Licence text)

  • Commercial use: Yes, including products and services of companies of any size.
  • Obligations and thresholds: Include the licence text and copyright notices when redistributing and mark changes. No revenue or user threshold.
  • Checked: As of October 2026

Not offered

  • Qwen3.8-Flash-Next is licensed under the Qwen Community License 1.0. It requires companies running a model-as-a-service or AI work assistant business to obtain a separate licence from Qwen before any commercial use. We therefore do not offer this model as a hosted service.

Technical classification, not legal advice. The licence text of the deployed model version is authoritative. Open LLM licences compared

Server tier

Minimum recommended server tier for Qwen

The recommendation follows from the weight size plus headroom for context and runtime.

ModelFormatWeightsMinimum recommendedNote
Qwen3.8-27BBF1655.6 GBManaged GPU Server 96–
Qwen3.8-27BFP830.9 GBManaged GPU Server 96–
Qwen3.8-27BNVFP421.9 GBManaged GPU Server 96The weights alone occupy almost all of the 24 GB, leaving no room for context and runtime.
Qwen3.5-122B-A10BFP8127.2 GBManaged GPU Server 192–
Qwen3.5-122B-A10BBF16250.2 GBManaged GPU Server 384–
Qwen3-Coder-NextFP880.4 GBManaged GPU Server 192On 96 GB, around 15 GB remain for context and runtime after the weights. That only supports short contexts and few parallel requests.
Qwen3-Coder-NextBF16159.4 GBManaged GPU Server 384–
  • Which tier suits your use case depends on context length and concurrent requests. We check this before the proposal.

Pricing

The Managed GPU Server tiers

Managed GPU Server 24

1 × RTX PRO 4000 Blackwell, 24 GB GPU memory

€699 excl. VAT / monthcancellable monthly€499 excl. VAT one-time setup

Relevant for this family

Managed GPU Server 96

1 × RTX PRO 6000 Blackwell Max-Q, 96 GB GPU memory

€2,199 excl. VAT / monthcancellable monthly€1,999 excl. VAT one-time setup

Relevant for this family

Managed GPU Server 192

2 × RTX PRO 6000 Blackwell Max-Q, 192 GB GPU memory

Price and term on request

Relevant for this family

Managed GPU Server 384

4 × RTX PRO 6000 Blackwell Max-Q, 384 GB GPU memory

Price and term on request

The Managed GPU Server 288 with three GPUs is intended for several models side by side, because vLLM only splits a model when the attention heads are divisible by the number of GPUs.

All prices are net and exclude statutory VAT. The offers are addressed to businesses.

Payment
  • SEPA direct debit
  • Visa
  • Mastercard
  • American Express
  • Apple Pay
  • Google Pay
  • PayPal
  • Bank transfer

vLLM

Running Qwen with vLLM

Architecture, quantisation and distribution across several GPUs.

Architectures

Qwen3.8-27B uses the Qwen3_5ForConditionalGeneration architecture, Qwen3.5-122B-A10B its MoE variant and Qwen3-Coder-Next Qwen3NextForCausalLM. All three are listed among the models supported by vLLM.

Quantisation

Qwen publishes official FP8 checkpoints. The NVFP4 version of Qwen3.8-27B comes from NVIDIA and uses mixed precision: MLP layers in NVFP4, attention in FP8. We compare quality and memory use per format on the target hardware.

Tensor parallelism

Qwen3.5-122B-A10B has 32 attention heads, Qwen3-Coder-Next has 16. Both can be split across two or four GPUs in vLLM. Three GPUs do not divide the heads evenly, which is why the three-GPU server is intended for several models side by side.

Context

The models support 262,144 tokens natively. We set the configured context length according to available GPU memory and parallelism. The full vendor context is not automatically part of every tier.

Operated by WZ-IT

What operation includes

The Managed GPU Server is an operated model environment, not an empty server.

View Managed GPU Server
Model and API
  • Model and vLLM

    An agreed model in the agreed quantisation, served through a managed vLLM inference layer.

  • OpenAI-compatible API

    Applications and coding clients connect to the server via base URL and API key.

Interface and monitoring
  • Open WebUI

    A managed chat interface for teams using the model without their own application.

  • 24/7 monitoring

    Host, GPU, vLLM and Open WebUI are monitored proactively; incidents are handled according to the service level.

Maintenance and contract
  • Updates with CVE assessment

    Operating system, drivers, vLLM and Open WebUI are reviewed and updated in a controlled way. Model changes only by agreement.

  • DPA and documentation

    Data processing agreement, documented configuration and a personal point of contact.

Scope, prices and multi-GPU servers are on the product page.

Frequently asked questions about Qwen hosting

Licence, server tier, data path and operation

Reviews & projects

What clients say about working with us

From a knowledge base with an AI assistant and local AI integration to data sovereignty and ongoing operations.

AI Platform

We were looking for a secure yet easy-to-use alternative to the large American providers and came across WZ-IT. WZ-IT advised us on choosing the right models and implemented the integration for us. Beforehand, we were able to try everything out calmly on a test instance. Today WZ-IT runs Open WebUI for us on our own domain, with a convenient Microsoft login and open-source models hosted by a German provider. Our team can now work productively with AI without resorting to external tools or shadow AI. Working together is straightforward, and questions are answered quickly and clearly. With WZ-IT we also have a partner at our side for further AI projects. (translated)
Carl-Frederic KornHead of E-Commerce & Online Marketing, Krüger Dirndl GmbH
See the AI platform

Knowledge Management & AI

The knowledge from many years in the solar industry lived in the head of our former managing director, and it still lives in the heads of our employees today. We wanted to secure it, not as a folder full of notes, but in a way that lets us ask questions in daily work and get reliable answers. WZ-IT advised us from the start and weighed different approaches and knowledge management systems against each other with us before we decided. What was built is a custom knowledge base with an AI assistant that brings together conversations, notes, documentation and manuals: from the platform through onboarding our team to support in operation. Conversations are transcribed and facts are extracted; we review and correct everything ourselves before it is stored, because we do not want to trust an AI blindly. The system runs in our own environment, and the data stays with us. What surprised us was how efficient it was: WZ-IT used existing open-source software and extended it specifically for our requirements, instead of selling an expensive custom build from scratch, as is often usual with IT service providers. Timo and Robin understood our actual problem, preserving knowledge during the generational handover, and implemented it step by step: from the proof of concept through setup and validation with our own data to productive operation, explaining everything clearly along the way. Next, we want to extend this to the knowledge of our employees, so that this does not depend on individual people either.
Joshua von AmelnManaging Director, solarwerkstatt berlin GmbH
See knowledge transfer

Read client reviews

International

Selected projects

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.

Model assessment

Have your model and server tier assessed

Name the model, context length and concurrent requests. We check checkpoint, licence and server tier before the proposal.

  • You speak directly with Timo and Robin, who are technically responsible
  • A professional assessment of your situation
  • Concrete next steps for infrastructure, software or AI

The conversation is free and non-binding.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
Timo and Robin, founders of WZ-IT

Which server tier should be assessed?

The selection is non-binding. We confirm model fit, licence and term before a proposal.

We usually respond within one business day. Please do not send access credentials yet.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH