WZ-IT Logo

Llama 4 vs. Qwen 3.5 vs. DeepSeek V4: Which Open-Source Model for Local Enterprise AI? (Q4 2026 Update)

Timo Wevelsiep
Timo Wevelsiep
••Updated: 01.10.2026
#LLM #Llama4 #Qwen #DeepSeek #Gemma4 #MistralSmall4 #OpenSource #AI #OnPremise

Editorial note: The information in this article was compiled to the best of our knowledge at the time of publication. Technical details, prices, versions, licensing terms, and external content may change. Please verify the information provided independently, particularly before making business-critical or security-related decisions. This article does not replace individual professional, legal, or tax advice.

Llama 4 vs. Qwen 3.5 vs. DeepSeek V4: Which Open-Source Model for Local Enterprise AI? (Q4 2026 Update)

Want to use an open language model in your organisation without handing data to cloud providers?

We test candidates against your tasks and run the chosen model where it fits: on the AI Cube inside your own network (from €6,490 excl. VAT one-time plus AI Cube Care from €349.90 excl. VAT per month) or on a Managed GPU Server from €699 excl. VAT per month. The LLM hosting page compares the operating options.

Explore AI Cube · Explore Managed GPU Server · Schedule a consultation

In May 2026 this comparison came down to three model families: Llama 4 from Meta, Qwen 3.5 from Alibaba and DeepSeek V4. Since then the field has shifted considerably. Qwen3.8-27B, Gemma 4, Mistral Small 4 and IBM Granite 4.2 are models that run on a single GPU and are licensed under Apache 2.0. At the same time, GLM-5.3, MiMo-V2.6 and DeepSeek-V4.1-Flash are new large models that can only be run sensibly on multi-GPU systems.

This article assesses the models from the perspective of a company that wants to run AI in its own data centre or on dedicated hardware: size, licence, context window and above all what actually fits into 24 GB, 96 GB or 128 GB of memory. All figures come from the model cards on Hugging Face and vendor pages, as of October 2026.

Table of Contents

  1. What has changed since May 2026
  2. Models at a glance
  3. How to read benchmarks
  4. What fits on 24 GB, 96 GB and 128 GB
  5. Large models for multi-GPU systems
  6. Context windows and RAG
  7. Licensing
  8. Recommendation by use case
  9. Our approach at WZ-IT
  10. Further guides

What has changed since May 2026

Model Vendor Release Licence Relevance for local operation
Gemma 4 (E2B, E4B, 26B A4B, 31B) Google DeepMind 31 March 2026, 12B on 3 June 2026 Apache 2.0 26B A4B and 31B fit on 24 GB at 4 bits
Mistral Small 4 Mistral AI 16 March 2026 Apache 2.0 MoE with 119B parameters for 96 GB or 128 GB
Qwen3.8-27B Alibaba (Qwen) August 2026 Apache 2.0 dense model with image and video input, fits on 24 GB at 4 bits
Granite 4.2 (3B, 8B, 30B) IBM 25 August 2026 Apache 2.0 dense text models, German officially tested
GLM-5.3 and GLM-5.3-Flash Z.AI late August 2026 GLM-5.3 License or MIT large models, multi-GPU only
DeepSeek-V4.1-Flash DeepSeek September 2026 MIT multimodal MoE, multi-GPU only
MiMo-V2.6 (Flash, Pro) Xiaomi September 2026 MIT MoE with text, image, video and audio, multi-GPU only

Dates without a day refer to the publication of the weights on Hugging Face. Llama 4 has not received new weights since April 2025; the Llama 4 models on Hugging Face date from the release on 5 April 2025.

Models at a glance

As of October 2026, figures according to the model cards. "Total / active" distinguishes, for Mixture-of-Experts (MoE) models, between all stored parameters and those used per token.

Model Architecture Total / active Context (native) Input Licence
Llama 4 Scout MoE 109B / 17B 10M text, image Llama 4 Community License
Llama 4 Maverick MoE 400B / 17B 1M text, image Llama 4 Community License
Qwen3.5-397B-A17B MoE 397B / 17B 262K, extensible to approx. 1M text, image Apache 2.0
Qwen3.5-122B-A10B MoE 122B / 10B 262K, extensible to approx. 1M text, image Apache 2.0
Qwen3.8-27B dense 27B 262K, extensible to 1M text, image, video Apache 2.0
Qwen3.8-Flash-Next MoE 125B / 6B (plus 51B n-gram embedding) 262K, extensible to 1M text, image Qwen Community License 1.0
Gemma 4 31B dense 30.7B 256K text, image Apache 2.0
Gemma 4 26B A4B MoE 25.2B / 3.8B 256K text, image Apache 2.0
Mistral Small 4 MoE 119B / 6.5B 256K text, image Apache 2.0
Granite 4.2 30B dense 30B 128K, extension to 512K text Apache 2.0
gpt-oss-120b MoE 117B / 5.1B 128K text Apache 2.0
DeepSeek V4 Flash MoE 284B / 13B 1M text MIT
DeepSeek V4 Pro MoE 1.6T / 49B 1M text MIT
DeepSeek-V4.1-Flash MoE 552B backbone / 8B (prefill) or 16B (decode) 1M text, image MIT
GLM-5.3 MoE around 750B (safetensors) up to 1M (evaluation) text GLM-5.3 License
GLM-5.3-Flash MoE 320B / 18B up to 1M (evaluation) text, image MIT
MiMo-V2.6-Flash MoE 309B / 15B 1M text, image, video, audio MIT
MiMo-V2.6-Pro MoE 1.02T / 42B 1M text, image, video, audio MIT

Two corrections compared with the first version of this article: DeepSeek V4 was released in April 2026 as Flash (284B / 13B) and Pro (1.6T / 49B); the previously stated 685B / 37B describe the previous generation. According to its model card, Qwen 3.5 supports 201 languages and dialects. Llama 4 officially supports 12 languages, including German.

Relevant for German-speaking organisations: Granite 4.2 explicitly lists German as a tested language, Mistral Small 4 lists German among its supported languages, and Gemma 4 states support for more than 140 languages.

How to read benchmarks

The first version of this article contained a benchmark table with partly estimated values. That table has been removed because several values could not be traced to a primary source.

The model cards contain extensive benchmark tables, but the values are only comparable within a single model card:

  • Different harnesses: Z.AI measures coding benchmarks for GLM-5.3 with Claude Code as the agent environment, while DeepSeek uses its own environment for V4.1-Flash.
  • Different reasoning levels: Many models support reasoning_effort. Published scores are usually produced at the highest level with very long outputs, which increases latency and cost in day-to-day operation.
  • Vendor benchmarks within a family: Qwen reports 61.7 on SWE-bench Pro for Qwen3.8-27B versus 53.5 for Qwen3.6-27B (model card). Comparisons within one family are more meaningful than comparisons across vendors.

Public benchmarks say little about German domain texts, your own document formats or structured output. A test with 50 to 200 representative tasks from your own data is more reliable. The article Which LLM to self-host? describes such a selection process.

What fits on 24 GB, 96 GB and 128 GB

Important with Mixture-of-Experts: Memory requirements depend on the total parameters, not the active ones. Active parameters only determine the compute per token; all experts must be held in memory. KV cache, activations and runtime come on top of the weights. The KV cache grows with context length and the number of parallel requests, see Sizing GPU and VRAM.

The sizes below are the actual file sizes of the weights on Hugging Face, as of October 2026. Some GGUF files come from community quantizers (unsloth), FP8 and NVFP4 variants from the vendors or NVIDIA. Which format suits which hardware is explained in LLM quantization.

24 GB VRAM: Managed GPU Server 24

WZ-IT's Managed GPU Server 24 uses an NVIDIA RTX PRO 4000 Blackwell with 24 GB GDDR7 ECC.

Model Format Weights Assessment
Gemma 4 26B A4B QAT Q4_0 (Google) 14.4 GB plenty of room for context, MoE with 3.8B active parameters
Qwen3.8-27B Q4_K_M 16.5 GB around 7 GB for KV cache and context
Gemma 4 31B QAT Q4_0 (Google) 17.7 GB plus 1.2 GB vision projector image input possible, limited context
Granite 4.2 30B Q4_K_M 17.7 GB text-only model, official GGUF from IBM
Qwen3.8-27B NVFP4 21.9 GB too tight on 24 GB for productive context

On 24 GB, dense models up to roughly 30B parameters run at 4 bits. The earlier recommendation in this article to run Llama 4 Scout or Qwen 3.5 on a 24 GB card was wrong: Llama 4 Scout needs around 55 GB at 4 bits.

96 GB VRAM: Managed GPU Server 96

The Managed GPU Server 96 uses an NVIDIA RTX PRO 6000 Blackwell Max-Q with 96 GB GDDR7 ECC.

Model Format Weights Assessment
Qwen3.8-27B FP8 (Qwen) 30.9 GB plenty of room for long contexts and parallel requests
Qwen3.8-27B BF16 55.6 GB full precision, room for KV cache
Gemma 4 31B BF16 62.5 GB full precision
gpt-oss-120b MXFP4 65.2 GB large text model on a single card
Mistral Small 4 NVFP4 (Mistral) 70.8 GB image input, around 25 GB for context
Qwen3.5-122B-A10B Q4_K_M 76.5 GB fits, context and concurrency are tight

NVFP4 is natively supported by Blackwell GPUs. For Qwen3.5-122B-A10B with more context and concurrency, a system with two 96 GB cards is the more stable choice, see vLLM with Qwen 122B on two RTX PRO 6000 and Multi-GPU inference without NVLink.

128 GB unified memory: AI Cube

The AI Cube is based on the NVIDIA GB10 with 128 GB of unified memory, shared by the operating system, inference server, weights and KV cache.

Model Format Weights Assessment
gpt-oss-120b MXFP4 65.2 GB proven choice, see GPT-OSS 120B on the AI Cube
Mistral Small 4 NVFP4 70.8 GB Apache 2.0, text and image, ample headroom
Qwen3.5-122B-A10B Q4_K_M 76.5 GB Apache 2.0, headroom for context
Qwen3.8-Flash-Next UD-Q4_K_XL 111.3 GB borderline, hardly any room for context, different licence
GLM-5.3-Flash UD-Q4_K_XL 199.7 GB does not fit

More on models in this class is in the article LLM models on 128 GB unified memory.

The model is decided, but the GPU is missing?

The model pages for Qwen, Gemma, gpt-oss and DeepSeek show which Managed GPU Server is the minimum recommended tier. Operated in a German data centre, with vLLM and an OpenAI-compatible API.

Explore LLM hosting · Explore Managed GPU Server

Large models for multi-GPU systems

The models that lead vendor benchmarks are too large for single cards. Weight sizes according to Hugging Face, as of October 2026:

Model Weights (format) Minimum required
Llama 4 Scout around 55 GB (4 bits, rule of thumb) one 96 GB GPU or AI Cube
DeepSeek V4 Flash 159.6 GB (mixed FP4/FP8, original format) two 96 GB GPUs, tight
GLM-5.3-Flash 204.4 GB (NVFP4) three to four 96 GB GPUs
Llama 4 Maverick around 200 GB (4 bits, rule of thumb) three to four 96 GB GPUs
Qwen3.5-397B-A17B around 200 GB (4 bits, rule of thumb) three to four 96 GB GPUs
DeepSeek-V4.1-Flash 527.3 GB (NVFP4) server with eight 96 GB GPUs
DeepSeek V4 Pro, MiMo-V2.6-Pro, GLM-5.3 from around 750B parameters multi-node cluster

The rule of thumb for 4 bits is around 0.5 GB per billion parameters. Most enterprise applications such as chat, RAG, summarisation and classification do not need this class. It pays off when models in the 30B and 120B class demonstrably fall short in your own tests. For such cases WZ-IT plans an individual system with multiple GPUs. Alternatively, a large model can be used via a European API, see European LLM APIs compared.

Context windows and RAG

Large context windows are a differentiator on paper, but in local operation they are limited by memory:

  • Llama 4 Scout: 10M tokens. The KV cache for such lengths far exceeds the memory of any single GPU.
  • DeepSeek V4, V4.1-Flash and MiMo-V2.6: 1M tokens. DeepSeek states a global KV cache of 890 bytes per token for V4.1-Flash, around a quarter of V4 Flash (model card). This lowers the memory needed for long contexts but does not change the size of the weights.
  • Qwen3.8-27B, Gemma 4, Mistral Small 4: 256K to 262K tokens. Sufficient for RAG pipelines, because the retrieval stage only passes on the relevant sections anyway.
  • Granite 4.2: 128K native. Sufficient for typical RAG queries.

For enterprise RAG, retrieval quality matters more than the maximum context length. A model with 256K context and good retrieval usually gives better answers than a model that is handed entire document collections. How search and reranking work together is described in Hybrid search and reranking.

Licensing

As of October 2026, according to the licence files on Hugging Face and vendor pages. This overview is a technical assessment, not legal advice.

Model Licence Commercial use Notes
Qwen3.8-27B, Qwen3.5-397B, Qwen3.5-122B Apache 2.0 Yes patent licence, notice obligations
Gemma 4 Apache 2.0 Yes licence per Google
Mistral Small 4 Apache 2.0 Yes none
Granite 4.2 Apache 2.0 Yes none
gpt-oss-120b Apache 2.0 Yes none
DeepSeek V4, V4.1-Flash MIT Yes keep copyright notice
GLM-5.3-Flash, MiMo-V2.6 MIT Yes keep copyright notice
GLM-5.3 GLM-5.3 License Yes security review by Z.AI for model-as-a-service providers with more than USD 10 billion in revenue
Qwen3.8-Flash-Next Qwen Community License 1.0 Yes, with restriction separate licence required for model-as-a-service and AI work assistant offerings, internal use exempt
Llama 4 Llama 4 Community License Yes, with restrictions 700M MAU clause, "Built with Llama", EU exclusion for multimodal models

Llama 4 and the EU: The Acceptable Use Policy does not grant the rights under Section 1(a) of the licence for multimodal Llama 4 models to individuals domiciled in, or companies with their principal place of business in, the EU. End users of a product that incorporates such a model are exempt. Since Llama 4 Scout and Maverick natively process text and images, this affects the models themselves, not just the image capability. The licence also requires a separate licence above 700 million monthly active users, the notice "Built with Llama" and the prefix "Llama" in the name of derived models.

Not every Qwen is the same: The small and mid-sized Qwen models are Apache 2.0. Qwen3.8-Flash-Next, by contrast, uses the Qwen Community License 1.0: anyone offering model inference as a service to third parties, or an AI work assistant for coding or office work, needs a separate licence from Qwen. Internal use is exempt as long as the model and its outputs are not made available to any third party.

GLM-5.3 is not MIT: GLM-5.3-Flash is MIT, while the larger GLM-5.3 uses its own licence with a security review for very large model-as-a-service providers.

For most companies, Apache 2.0 and MIT models are the clearest choice from a legal point of view. A more detailed assessment of fine-tuning, hosting for third parties and derived models is in the article Open LLM licences for commercial use.

Recommendation by use case

As of October 2026. The table lists candidates for your own tests, not a fixed ranking.

Use case Candidates Hardware Rationale
Internal chat and RAG for small teams Qwen3.8-27B, Gemma 4 26B A4B, Gemma 4 31B 24 GB Apache 2.0, under 18 GB at 4 bits, 256K context
Documents with images and scans Qwen3.8-27B, Gemma 4 31B, Mistral Small 4 24 to 96 GB native image input, see Vision-language models for OCR
Text-only processing with clear licensing Granite 4.2 30B or 8B 24 GB Apache 2.0, German tested, dense architecture
More users and longer contexts Qwen3.8-27B in FP8, Mistral Small 4 96 GB room for KV cache and concurrency
Large model inside your own network gpt-oss-120b, Mistral Small 4, Qwen3.5-122B-A10B AI Cube (128 GB) 65 to 77 GB of weights, the rest for context
Top-tier code and agents DeepSeek V4 Flash, GLM-5.3-Flash multi-GPU system 160 to 205 GB of weights
Multimodal with headquarters in the EU not Llama 4 - EU exclusion in the Acceptable Use Policy

For the majority of enterprise applications, the 30B class is sufficient. Qwen3.8-27B and Gemma 4 run on a 24 GB card, are licensed under Apache 2.0 and process images. If you need more quality headroom or concurrency, move to 96 GB or the AI Cube with Mistral Small 4, gpt-oss-120b or Qwen3.5-122B-A10B. The large models with several hundred billion parameters only make sense once your own tests show that the smaller models cannot solve the task.

Still unsure which tool fits? The AI opportunity check tests which approach holds up on a concrete process and ends with a pilot recommendation. From €3,900 excl. VAT.

Our approach at WZ-IT

WZ-IT selects models based on the specific use case and runs them on dedicated hardware:

  1. Gather requirements: languages, document types, share of images, number of users, data protection needs and licence requirements.
  2. Test candidates: compare two to four models with representative tasks from your own data, using identical quantization and inference engine.
  3. Define hardware: AI Cube inside your own network (from €6,490 excl. VAT one-time, plus AI Cube Care from €349.90 excl. VAT / month) or a Managed GPU Server with 24 GB (€699 excl. VAT / month) or 96 GB (€1,799 excl. VAT / month), each plus setup.
  4. Set up operations: vLLM or Ollama, Open WebUI or your preferred interface, gateway, monitoring and updates.
  5. Plan model changes: new releases are checked with the same test tasks before they replace the running version.

Support, consulting and implementation by WZ-IT.

Further guides

Which model fits your use case? We test candidates with your data and run the selected model on the AI Cube or a Managed GPU Server, with Open WebUI or your preferred interface. Schedule a consultation | AI Cube

Sources

Enquiry

Select the right local model with real data

We compare quality, licensing, hardware requirements, and throughput for your use case, then deploy the selected model on private infrastructure.

Where are you in the model selection process?

How should we get back to you?

Frequently Asked Questions

Answers to important questions about this topic

There is no universally best model. For a single 24 GB GPU, Qwen3.8-27B, Gemma 4 31B and Gemma 4 26B A4B in 4-bit quantization are the obvious candidates. With 96 GB of VRAM or 128 GB of unified memory, Mistral Small 4, Qwen3.5-122B-A10B and gpt-oss-120b become options. The choice depends on language, task, licence and hardware and should be made with your own test data.

As of October 2026, new releases include Qwen3.8-27B (Apache 2.0, August 2026), GLM-5.3 and GLM-5.3-Flash (late August 2026), IBM Granite 4.2 (25 August 2026), DeepSeek-V4.1-Flash (September 2026) and Xiaomi MiMo-V2.6 (September 2026). Gemma 4 (31 March 2026) and Mistral Small 4 (16 March 2026) were already available and belong in the comparison for local setups as well.

No. Llama 4 Maverick has 400B parameters, 17B of them active. In Mixture-of-Experts models all experts have to be held in memory; at 4 bits that is around 200 GB for the weights alone. The 17B active parameters determine the compute per token, not the memory requirement.

Not without restriction for the multimodal Llama 4 models. The Llama 4 Acceptable Use Policy does not grant the rights under Section 1(a) of the licence for multimodal models to companies with their principal place of business in the EU. Llama 4 Scout and Maverick natively process text and images. End users of a product that incorporates such a model are exempt. This is an assessment, not legal advice.

No. Qwen3.8-27B, Qwen3.5-397B-A17B and Qwen3.5-122B-A10B are Apache 2.0. Qwen3.8-Flash-Next uses the Qwen Community License 1.0, which requires a separate licence for model-as-a-service and AI work assistant offerings. Qwen3.8-2.4T-A95B has its own Qwen3.8-Max License. Check the licence per model on the model card.

Only GLM-5.3-Flash. GLM-5.3 uses its own GLM-5.3 License: it allows use, modification and redistribution but requires a security review by Z.AI if a licensee runs a model-as-a-service business with more than USD 10 billion in revenue over twelve months. For most companies this threshold does not apply, but the licence is still not plain MIT.

Dense models up to roughly 30B parameters at 4 bits. Examples with file sizes on Hugging Face: Qwen3.8-27B Q4_K_M 16.5 GB, Gemma 4 31B QAT Q4_0 17.7 GB, Gemma 4 26B A4B QAT Q4_0 14.4 GB, Granite 4.2 30B Q4_K_M 17.7 GB. The remaining memory is left for KV cache and context. Models with more than 100B parameters do not fit on 24 GB, not even as MoE.

No, but the obligations are minor. MIT requires keeping the copyright and licence notice when redistributing. Apache 2.0 additionally requires marking changes and passing on NOTICE files, and includes a patent licence. Both allow commercial use, fine-tuning and hosting for third parties without a user cap.

Only to a limited extent. Vendors measure with their own harnesses, context lengths, reasoning levels and comparison models. A score from Qwen's model card is not directly comparable with a score from Z.AI or DeepSeek. For model selection, tests with your own tasks, languages and documents are what counts.

Timo Wevelsiep

Written by

Timo Wevelsiep

Co-Founder & CEO

Co-Founder of WZ-IT. Specialized in cloud infrastructure, open-source platforms and managed services for SMEs and enterprise clients worldwide.

LinkedIn

Let's Talk About Your Idea

Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.

Arrange a callback

Callback

Arrange a callback

Leave your number and we will call back by the next business day at the latest.

For a longer conversation you can book an appointment instead.

Companies worldwide trust WZ-IT

  • ml&s
  • Rekorder
  • Keymate
  • Führerscheinmacher
  • SolidProof
  • ARGE
  • Boese VA
  • nextGYM
  • SweetConnect GmbH
  • Golem.de
  • Millenium
  • Paritel
  • Yonju
  • EVADXB
  • Mr. Clipart
  • Aphy AG
  • Negosh
  • ABCO Water Systems
1/3 - Topic Selection33%

What is your inquiry about?

First select the service area that best matches your project.