Join our Newsletter — 33% off our NHI Course
Home› Guides› Open-Weight Frontier Models Compared: Licences, Sizes, Hardware and…
Guide AI Platforms

Open-Weight Frontier Models Compared: Licences, Sizes, Hardware and Hosting

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 15 November 2026 16 min read
On this page

The largest open-weight models now reach hundreds of billions to trillions of parameters, but their licences, memory needs, serving engines and reasoning controls differ so much that "open weights" alone says little about whether a team can legally and practically run one. This page compares the largest current open-weight language model from each of twelve providers, using identical fields: licence and its stated conditions, total and active parameters, architecture, context length, input modalities, published precision formats, named inference engines, stated hardware, reasoning controls and whether the provider also sells the model as a hosted API. It is written for platform teams, ML engineers, legal reviewers and buyers deciding whether to self-host. For the basic open versus closed distinction, read Open-Weight vs Closed Models Explained first. Providers are listed alphabetically; the order is never a ranking, and the page draws no verdicts.

Last checked: 2026-11-15.

This is an independent reference page from NHI Mgmt Group based on public provider documentation; it is not sponsored or endorsed by any provider. Model cards and licences change between releases, so read the licence file in the repository before use.

Key takeaways

  • Licences fall into three groups. Five models use a standard licence (Apache 2.0 for Gemma 4, gpt-oss-120b, Hy3 and K-EXAONE 2.0; MIT for DeepSeek-V4-Pro), one uses OpenMDW-1.1, and six use a publisher's own licence.
  • Size spans roughly two orders of magnitude. Total parameters run from 31B (Gemma 4 31B) to 2.8T (Kimi K3.1 Pro), and active parameters per token from 5.1B (gpt-oss-120b) to 104B (Kimi K3.1 Pro).
  • Hardware statements are rare. Only Google, Meta, NVIDIA, OpenAI and Tencent state memory or GPU needs on the pages checked; for the rest, the serving examples are the only guide.
  • Low-precision weights are now published by providers. DeepSeek (FP4 plus FP8), Meta (NVFP4), Moonshot AI (MXFP4, trained with quantisation-aware training), NVIDIA (NVFP4), Tencent (FP8) and Z.ai (FP8) publish reduced-precision checkpoints or formats.
  • Most also run as hosted APIs. Alibaba, DeepSeek, Mistral AI, Moonshot AI, OpenAI (including Amazon Bedrock) and Z.ai document hosted versions, so the same model can be tested by API before committing to hardware.

Which models are included?

The inclusion rule is objective: for each provider, the largest current open-weight text-generation model whose model card or official documentation could be fetched on 2026-11-15. Preview checkpoints are excluded (for example Tencent Hy4-preview and StepFun Step-5-Preview), as are providers whose largest open release is under 30B parameters. Each provider's smaller open models, such as Mistral Small 4, Qwen3.8-27B or Nemotron 3 Super, are covered on the provider pages. Restricted-access status is stated where a card requires an access request.

Open-weight frontier models at a glance

As of 2026-11-15. Parameters are the figures in the model card text; where the Hugging Face file header differs, the card text is used and the difference is noted below the table.

ProviderModelTotal / active parametersArchitecture (as stated)Context lengthInput modalitiesLicence
Alibaba (Qwen)Qwen3.8-2.4T-A95B2.4T / 95BMoE, 512 experts (10 routed, 1 shared); Gated DeltaNet and Gated Attention hybrid262,144 native, up to 1,010,000Textqwen3.8-max (publisher licence)
DeepSeekDeepSeek-V4-Pro1.6T / 49BMoE; Compressed Sparse Attention and Heavily Compressed Attention1MTextMIT
GoogleGemma 4 31B31B (dense)Dense; the family also has a 26B A4B MoE256K (medium models)Text, image (video and audio support vary by size)Apache 2.0
LG AI ResearchK-EXAONE 2.0 750B-A37B750B / 37BMoE, 256 experts (8 active, 1 shared); sliding-window and global attention262,144TextApache 2.0
MetaMuse Spark Open 816B-A42B816B / 42BMoE, 256 experts (8 active), with a 1.8B Perception Encoder1MText, image, video, audioMuse Model License (publisher licence)
MiniMaxMiniMax-M3About 428B / about 23BMoE with MiniMax Sparse Attention1MText, image, videominimax-community (publisher licence)
Mistral AIMistral Large 41.05T / 52B, plus a 1.6B vision encoderGranular MoE1MText, imageMistral Ecosystem Open Weight License (publisher licence)
Moonshot AIKimi K3.1 Pro2.8T / 104BMoE, 896 experts (16 selected, 2 shared); KDA and Gated DSA attention; 401M MoonViT-V2 vision encoder1,048,576Text, imageKimi K3.1 Pro License (publisher licence)
NVIDIANemotron 3 Ultra 550B-A55B550B / 55BLatentMoE hybrid of Mamba-2, MoE and attention layersUp to 1M (256K default serving configuration)TextOpenMDW-1.1
OpenAIgpt-oss-120b117B / 5.1BNot stated by OpenAI on the model page beyond total and active parameters131,072TextApache 2.0
TencentHy3295B / 21B (plus 3.8B MTP layer)MoE, 192 experts (top 8)256KTextApache 2.0
Z.aiGLM-5.3753B / not stated by Z.ai on the cardTagged glm_moe_dsa; shares its base model with GLM-5.2Not stated as a specification on the model cardTextglm-5.3 (publisher licence)

File headers on Hugging Face differ from card text for Meta (822B), NVIDIA (561B), Tencent (299B) and LG AI Research (749B). Google's Gemma 4 page groups sizes into small models with 128K context and medium models with 256K, and lists native audio input on E2B, E4B and 12B only. For how total and active parameters relate, see Mixture of Experts Explained.

What does each licence allow?

Licence names come from each model card. Conditions are listed only where the card or official page states them; where the card names a licence without summarising it, the licence file in the repository is the only source of the terms.

ProviderLicenceConditions stated on the page checkedAccess
Alibaba (Qwen)qwen3.8-maxTerms not summarised on the model cardPublic repository
DeepSeekMITThe card states the repository and the model weights are licensed under the MIT LicensePublic repository
GoogleApache 2.0 (linked as the Gemma 4 license)Google states the models are provided with open weights and permit responsible commercial useDownloads on Kaggle and Hugging Face
LG AI ResearchApache 2.0Released so the community can inspect, deploy and build on the modelPublic repository
MetaMuse Model License (dated 15 October 2026)Display "Built with Muse Spark Open"; a licensee offering AI models as a service by API with aggregate gross revenue above US$20 million in a 12-month period must notify Meta and sign a separate agreement first (internal use, research and features in the licensee's own products are excluded); usage policy in Exhibit A; not intended for users under 18Gated: an access request form asks for legal name, date of birth and organisation
MiniMaxminimax-communityTerms not summarised on the model cardPublic repository
Mistral AIMistral Ecosystem Open Weight LicenseTerms not summarised on the model cardHugging Face repository linked from the card
Moonshot AIKimi K3.1 Pro LicenseTerms not summarised on the model cardPublic repository
NVIDIAOpenMDW-1.1The card states the model is ready for commercial and non-commercial usePublic repository; some training datasets gated
OpenAIApache 2.0Described as a permissive Apache 2.0 licenceWeights on Hugging Face
TencentApache 2.0No territory restriction stated on the cardPublic repository
Z.aiglm-5.3Terms not summarised on the model cardPublic repository

As of 2026-11-15. Licences can change between versions of the same family, so record the licence name, version and repository commit for every checkpoint you deploy. For approval workflows see the Open Source Licence Compliance Guide.

How much hardware do they need?

Hardware figures below are only those stated by the provider. Where no figure is stated, the provider's own serving example is described; examples are not minimums.

ProviderModelPublished precision formatsHardware stated or shown
Alibaba (Qwen)Qwen3.8-2.4T-A95BBF16No requirement stated; Docker example uses all GPUs and 32 GB shared memory
DeepSeekDeepSeek-V4-ProFP4 (MoE experts) plus FP8 mixed; Base checkpoint FP8 mixedNo requirement stated; SGLang example uses all GPUs and 32 GB shared memory
GoogleGemma 4 31BBF16, 8-bit, 4-bit (Q4_0) memory figures69.9 GB (BF16), 34.9 GB (8-bit), 17.5 GB (Q4_0) to load weights; the 26B A4B needs 57.7 GB, 28.8 GB and 14.4 GB; figures exclude KV cache
LG AI ResearchK-EXAONE 2.0BF16Examples run on two nodes of 8 NVIDIA H200 GPUs with tensor parallelism of 16; a B200 flag is needed in SGLang to avoid a known generation issue
MetaMuse Spark OpenBF16, NVFP4At least 700 GB VRAM for NVFP4; about 2 TB for BF16; optimised for two Mac Studio M5 Ultra machines with MLX
MiniMaxMiniMax-M3BF16; quantised versions linkedNo requirement stated; SGLang example uses all GPUs and 32 GB shared memory
Mistral AIMistral Large 4Not stated on the model cardNot stated on the model card
Moonshot AIKimi K3.1 ProMXFP4 weights and MXFP8 activations (quantisation-aware training)Not stated on the model card
NVIDIANemotron 3 UltraBF16; separate NVFP4 repositoryBF16: 8 GB200, B200, GB300 or B300, or 16 H100, or 8 H200
OpenAIgpt-oss-120bNot stated on the model page"Fits into a single H100 GPU"
TencentHy3BF16; separate Hy3-FP8 repositoryFor 8-GPU serving, H20-3e or GPUs with larger memory recommended
Z.aiGLM-5.3BF16, FP8No VRAM figure; Ascend NPU support through vLLM-Ascend, xLLM and SGLang

As of 2026-11-15. Weight memory is only part of the total: the KV cache grows with context length and concurrent requests, which is why long-context serving often needs more GPUs than the weights alone suggest. See Running LLMs Locally Explained for the smaller end of the range.

Which inference engines are named?

ProviderEngines named on the cardQuantised community builds mentioned
Alibaba (Qwen)Transformers, vLLM, SGLang, TokenSpeed, Docker Model Runnerllama.cpp, Ollama, LM Studio, Jan
DeepSeekvLLM, SGLang, Transformers, Docker Model Runnerllama.cpp, Ollama, LM Studio, Jan
GoogleNot listed on the docs page checked; downloads on Kaggle and Hugging FaceQ4_0 memory figures published
LG AI ResearchSGLang and vLLM (LG AI Research forks), Transformers, Docker Model Runnerllama.cpp, Ollama, LM Studio
MetaSGLang, vLLM, Transformers, TensorRT-LLM, Unsloth, llama.cppllama.cpp, Ollama, LM Studio
MiniMaxSGLang, vLLM, Transformers, KTransformers, Unsloth, ATOM, Docker Model Runnerllama.cpp, Ollama, LM Studio
Mistral AINot stated on the model cardNot stated on the model card
Moonshot AIvLLM, SGLang, TokenSpeedNot stated on the model card
NVIDIAvLLM, SGLang, TensorRT-LLM (Blackwell only at present), Transformers, Docker Model RunnerGGUF for llama.cpp, Ollama, LM Studio
OpenAINot stated on the model page; also served on OpenAI API endpointsNot stated on the model page
TencentvLLM (MTP speculative decoding), SGLang (EAGLE speculative decoding), Transformers, Docker Model Runnerllama.cpp, Ollama, LM Studio
Z.aiSGLang, vLLM, TokenSpeed, Transformers, KTransformers, Unsloth, vLLM-Ascend, xLLM, Docker Model Runnerllama.cpp, Ollama, LM Studio

As of 2026-11-15. Inference servers expose network APIs and often run with broad GPU host access; see the vLLM, Triton and NVIDIA NIM Inference Server Security Guide.

Reasoning controls in the open checkpoints

Most of these models reason by default, and the control is usually a chat-template argument rather than an API field, so it must be set in the serving layer.

ProviderControlValuesDefault
Alibaba (Qwen)reasoning_effortlow, medium, xhigh; thinking cannot be disabledxhigh
DeepSeekMode via prompt and templateNon-think, Think High, Think Max (at least 384K context recommended for Think Max)Not stated on the model card
GoogleConfigurable thinking modesNot listed on the docs page checkedNot stated on the docs page checked
LG AI Researchenable_thinking; preserve_thinkingTrue or FalseThinking on; preserve_thinking off (True recommended for agentic tasks)
Metareasoning_effortlow, medium, high, xhighxhigh
MiniMaxthinkingenabled, adaptive, disabledNot stated on the model card
Mistral AIreasoning_effort (API)low, medium, highhigh recommended
Moonshot AIreasoning_effortlow, high, maxmax
NVIDIAenable_thinking; medium_effort; client-side reasoning_budgetOn or off, medium effort, token budgetThinking on
OpenAIReasoning effortlow, medium, highNot stated on the model page
Tencentreasoning_effortno_think, low, highno_think
Z.aireasoning_effort; clear_thinking template flaglow, high, maxmax (clear_thinking false by default; set true for chat)

As of 2026-11-15. For how these controls compare with closed-model APIs, see Reasoning LLMs Compared Across Providers.

Where can each model be used without self-hosting?

ProviderHosted option documentedListed price (USD per 1M tokens, input / output)
Alibaba (Qwen)Qwen3.8-Max on Qwen Cloud and Model Studio is the managed version of the checkpoint$2 / $6 (international, Singapore)
DeepSeekdeepseek-v4-pro (DeepSeek-V4-Pro-0813) on the DeepSeek API; 1M context, 384K maximum output$1.32 / $3.96 peak; $0.66 / $1.98 off-peak (cache miss)
GoogleNot stated on the Gemma docs page checkedNot stated on the Gemma docs page checked
LG AI ResearchNo Hugging Face Inference Provider at the time checked; a FriendliAI API is linked from the cardNot stated on the model card
MetaNot stated on the model cardNot stated on the model card
MiniMaxNot stated on the model cardNot stated on the model card
Mistral AImistral-large-4 on the Mistral API$0.70 / $2.10 ($0.07 cached input)
Moonshot AIkimi-k3.1-pro on the Kimi platform with OpenAI- and Anthropic-compatible interfaces; also HuggingChat and Inference ProvidersNot stated by Moonshot AI on the pages checked (2026-11-15)
NVIDIANot stated on the model card section readNot stated on the model card section read
OpenAIOpenAI API endpoints and Amazon Bedrock (openai.gpt-oss-120b)Not stated on the model page
TencentNot stated on the model cardNot stated on the model card
Z.aiglm-5.3 on the Z.ai API$1.40 / $4.40 ($0.26 cached input)

As of 2026-11-15. The DeepSeek-V4-Pro model card describes the April 2026 release, while the API serves the DeepSeek-V4-Pro-0813 update; check which checkpoint matches the hosted version before comparing results. For the trade-offs between the two routes, see Self-Hosted LLMs vs Hosted LLM APIs.

Training data and transparency

  • NVIDIA: the Nemotron 3 Ultra card states that major portions of the pre-training corpus, the post-training corpus and the reinforcement learning environments are released, with code, maths and multilingual data gated behind approval and some third-party datasets kept private; training recipes and a technical report are published.
  • Other providers: the remaining cards checked describe architecture and serving and link technical reports or papers where they exist (DeepSeek, LG AI Research and MiniMax link papers); none of them describes a training data release.
  • Base checkpoints: DeepSeek publishes a Base model alongside the instruct model (DeepSeek-V4-Pro-Base), which matters for teams that plan to fine-tune.

For what a model card should contain, see Model Cards and System Cards Explained.

Benchmarks

Each card publishes its own evaluation tables, with different test sets, effort levels and sampling settings (for example temperature 1.0 and top_p 1.0 on DeepSeek and Meta, top_p 0.95 on Kimi, MiniMax and LG AI Research, temperature 0.9 on Tencent). Because no single dated source covers every row, this page lists no scores. Compare scores only when the effort level, context and sampling settings match. See How to Read LLM Benchmarks.

Security and governance when self-hosting

  • Supply chain: pull weights only from the publisher's own organisation on the hub, pin the repository commit and verify file hashes; see the Hugging Face Security Guide.
  • Gated access: Meta's gated repository requires personal details on request; use an organisational account and record who accepted the licence.
  • Serving layer: chat-template flags such as Z.ai's clear_thinking and NVIDIA's enable_thinking are set by whoever controls the server, so treat template files as configuration under change control.
  • Safety tuning: once weights are local, provider-side filters do not apply; see the Open-Weight Model Security Guide and the Self-Hosted LLM Security Guide.

How to choose an open-weight model: factual criteria

If you needCheckModels documented with it
A standard licence your legal team already approvesApache 2.0 or MITDeepSeek-V4-Pro (MIT); Gemma 4, gpt-oss-120b, Hy3, K-EXAONE 2.0 (Apache 2.0)
A single-GPU deploymentProvider hardware statementgpt-oss-120b (single H100, per OpenAI); Gemma 4 31B at 8-bit or 4-bit by Google's memory table
Image, video or audio inputInput modalitiesMuse Spark Open (text, image, video, audio); MiniMax-M3 (text, image, video); Gemma 4 (text and image, with audio on smaller sizes); Kimi K3.1 Pro and Mistral Large 4 (text, image)
Context of about 1M tokensStated context lengthDeepSeek-V4-Pro, Kimi K3.1 Pro, MiniMax-M3, Mistral Large 4, Muse Spark Open, Nemotron 3 Ultra (with configuration), Qwen3.8-2.4T-A95B (extended)
Non-NVIDIA acceleratorsNamed hardware supportGLM-5.3 (Ascend NPU); Muse Spark Open (Apple MLX)
A hosted API for trial before self-hostingHosted option tableQwen3.8-Max, deepseek-v4-pro, gpt-oss-120b, kimi-k3.1-pro, mistral-large-4, glm-5.3

Small teams usually start with models that fit one or two GPUs and a standard licence; at the trillion-parameter end, multi-node serving and a licence review are both part of the project plan. Larger organisations often pair a hosted API for evaluation with a self-hosted deployment once usage and licence terms are settled.

Practitioner checklist

  • Read the licence file in the repository, not the licence tag, and record name, version and commit for each deployed checkpoint.
  • Check revenue or service thresholds such as Meta's US$20 million API-service clause before offering a model to customers.
  • Size hardware for weights plus KV cache at your target context and concurrency, not for weights alone.
  • Prefer provider-published low-precision checkpoints (FP8, NVFP4, MXFP4) over community conversions where the provider offers them.
  • Set the reasoning default explicitly in the chat template; several models default to their highest effort.
  • Test the hosted API version first where one exists, and confirm it matches the checkpoint version you plan to run.
  • Pin model repositories and verify hashes, and keep chat templates under change control.
  • Re-check each card when a new version ships; parameters, licences and defaults change between releases.

Standards and references

Related NHI Mgmt Group resources: Open-Weight vs Closed Models Explained, Open-Weight Model Security Guide, Self-Hosted LLMs vs Hosted LLM APIs, Frontier AI Models Compared, Mixture of Experts Explained.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 15 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org