Zenaique

Match open base model to its license consideration

Match pairs·Medium·4.0 · 0·~2 min·Asked atBraintrustElevenlabsIntel·Relevant atMetaMistral AI
Attempt it

Drag each answer to line up with its matching prompt

Llama 3 / 3.1 / 3.3

Meta Llama Community License: generally permissive but has a 700M monthly active users clause: companies above that user threshold need a separate license from Meta.

Mistral 7B / Mixtral

Google's own Gemma Prohibited Use Policy: permissive for most commercial use but with explicit category exclusions you must review.

Qwen 2 / 2.5

MIT license for the base weights, with model card specific commercial use clarifications: among the most permissive frontier quality open releases.

DeepSeek-V2 / V3

Apache 2.0 for the open weight base models: broadly permissive commercial use including for fine-tuning and redistribution.

Gemma 2 / 3

Apache 2.0 for most sizes (with a small number of variants under their own commercial license): fine-tuned derivatives generally inherit the permissive terms.

TL;DR

Open base model licenses split three ways: standard OSI licenses (Apache 2.0, MIT) and custom vendor licenses that add clauses like Meta's user threshold or Google's use-case exclusions.

Memory aid
Sign in to see the mnemonic that makes this stick.
Easy to grasp

Imagine borrowing tools from five workshops to build something you'll sell. Some workshops hand over the tool and say 'use it however you like, just keep our name on the box': that's Apache and MIT. One workshop says 'free for almost everyone, but if your shop gets enormous, come back and sign a deal': that's Meta's Llama rule about huge user counts. Another says 'free, but here's a list of things you're not allowed to build': that's Google's Gemma policy. The tool works the same in every case. The difference is the paperwork attached, and that paperwork decides whether your business can ship the thing you built.

Concept explanation~2 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Fine-tuning is not a clean-room operation. The moment you load an open base model and update its weights, your result is a derivative work, and the base model's license follows you into production. This is why license consideration belongs at the start of a fine-tuning project, alongside the benchmark and cost analysis, not bolted on at legal review.

The trap is intuitive but wrong: weights that download for free feel like public-domain assets. They are not. The five model families on this card all publish open weights anyone can pull from Hugging Face, yet they sit under three genuinely different legal regimes. Two carry standard open-source licenses with almost no conditions. One is even more minimal. The remaining two are custom vendor licenses that read like a contract, with clauses that can quietly disqualify a specific deployment.

This deep dive maps each family to its bucket, explains what each license actually permits and forbids, and unpacks the two conditions that catch teams off guard: Meta's user-count threshold and Google's use-case exclusion list. The goal is to leave you able to defend a base model choice in an interview on legal grounds, not only on quality scores.

The three license buckets

The cleanest mental model splits open base models into three buckets, and every family on this card lands in exactly one.

The first bucket is standard permissive open source. Mistral 7B, Mixtral, and most Qwen 2 / 2.5 sizes ship under Apache 2.0. This is an OSI-approved license: you may use, modify, fine-tune, and redistribute commercially. The two obligations are keeping the license notice and respecting an explicit patent grant. DeepSeek-V2 and V3 sit nearby under MIT, which grants the same freedoms in even fewer words and without the patent clause.

The second and third buckets are custom vendor licenses. Meta's Llama Community License is permissive for the vast majority of users but adds a scale-based gate. Google's Gemma combines its own terms with a Prohibited Use Policy that gates by use case.

The headline takeaway: Apache and MIT are open source in the formal sense, while the Llama and Gemma terms are vendor contracts that happen to allow most commercial use. The download mechanics look identical, so the difference is invisible until you read the text.

The Llama clause: a user-count threshold
The Gemma clause: a use-case exclusion list
Variant exceptions and why they bite
Three layers: weights, data, and outputs
Sign in to unlock the full deep dive.

Situations where this technique stops working.

Sign in to see when this approach fails.

2–4 min · Everything important, quickly.

Sign in to see the quick scan of the deep dive.
Model familyLicenseKey condition to check
Llama 3 / 3.1 / 3.3Meta Llama Community LicenseSeparate Meta license required above 700M monthly active users
Mistral 7B / MixtralApache 2.0Broad commercial use; keep the notice and attribution
Qwen 2 / 2.5Apache 2.0 (most sizes)A few variants carry their own license; check per size
DeepSeek-V2 / V3MIT (base weights)Model-card commercial clarifications; among the most permissive
Gemma 2 / 3Gemma terms + Prohibited Use PolicyCategorical use-case exclusions you must review

Real products, models, and research that use this idea.

  • Together.ai and Fireworks host Llama 4 and Mistral fine-tunes, surfacing each base model's license in the deployment console so customers see the Meta user-count clause before serving.
  • DeepSeek V4 shipped under MIT for its base weights, which is why many startups pick it as a fine-tuning base with minimal legal review.
Sign in to see more production examples.

What an interviewer would ask next. Try answering before peeking at the approach.

QHow does a base model's license propagate to a fine-tuned derivative you redistribute?
A

Treat the fine-tune as a derivative work. The base terms carry forward, so Apache requires notice retention and Llama carries its threshold and naming clauses into your release.

2 more follow-ups an interviewer would ask next. Sign in to reveal them.

Red flags & common mistakes

The phrases that signal junior thinking. Click to expand.

Most common mistake

Assuming every open-weight model is open source. Several use custom vendor licenses with conditions that can block your specific commercial use, even when the weights download freely.

Sign in to see all red flags and common mistakes.

60 second bullets to scan on the way to the call.

  • Which families are Apache 2.0 versus MIT versus custom vendor

  • What the Llama 700M monthly active users clause actually triggers

Sign in to unlock the revision sheet.

Primary sources. Browse if you want the original framing.

Similar questions

Same topic, related formats. Practice these next.

4 curated
Next question
What is RLHF, and why is it used after pretraining?
MCQ·Easy