A product team is about to ship a Llama-4 fine-tune as part of a consumer feature inside an app with 800 million monthly active users. They've assumed the Llama community license is "basically open" and have not requested anything from Meta. Identify the specific clause they need to re-read, what threshold it sets, why it applies to a fine-tuned derivative as much as to the base model, and what they need to do BEFORE shipping.
The Llama Community License triggers a separate Meta commercial-license requirement above 700 million MAU on the deployed product. Fine-tuning does not reset the clock, the derivative inherits the same threshold.
Imagine borrowing a recipe from a chef who lets anyone use it, except for restaurants serving more than seven hundred million meals a month. Those huge restaurants have to call the chef first and arrange a separate deal before they can serve any dish that uses the recipe. Tweaking the recipe with extra spices does not change anything, because the new dish still uses the original. The size of the restaurant you serve in is what triggers the call, not whether the recipe section of the menu is busy. So if your restaurant chain has over seven hundred million monthly customers, you make the call before you open the kitchen.
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.
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.
The Llama Community License sits in an unusual place in the model-licensing landscape. It is far more permissive than a closed-API arrangement, which is why teams reach for Llama bases when they want to control fine-tuning, hosting, or fine-grained customisation. But it is not a permissive open-source licence, and conflating it with Apache 2 or MIT is the single most expensive licensing mistake teams make in 2026.
The gap between actually open and basically open shows up in one specific clause. The Llama Community License contains a monthly active user threshold, set at 700 million. Above that threshold the community licence ceases to grant rights, and a separate commercial licence from Meta is required before any use of the model or its derivatives. The clause was designed precisely to catch the case in this question: a large consumer app reaching for an open-weight model without negotiating a deal first.
This deep dive walks the exact clause language, why fine-tuning does not reset the licence, why the threshold is measured against the deployment surface rather than the AI feature usage, what the operational sequence looks like, and what the team should do if Meta declines or the timeline does not work. The audience is product and engineering leads who are not lawyers but who need to make the call before launch.
What the clause actually says
The relevant section of the Llama Community License is the additional commercial terms. The language, paraphrased and reduced to essentials, is: if on the day of the Llama version release, the monthly active users of the products or services made available by you, your affiliates, or your corporate group exceed 700 million in the preceding calendar month, you must request a licence from Meta, which Meta may grant to you in its sole discretion, and you are not authorised to exercise any of the rights under the agreement unless Meta otherwise expressly grants you such rights.
Four things stand out. First, the threshold is a hard numeric boundary, 700 million MAU, not a range or a soft cap. Second, the clause uses sole discretion, meaning Meta is not obliged to grant the licence on request. Third, the clause covers the licensee, its affiliates, and its corporate group, which closes a structural loophole where a large parent company might try to route Llama usage through a small AI subsidiary to argue the subsidiary alone is under the threshold. Fourth, the clause is keyed to the day of release of the Llama version you use, with the MAU measured in the preceding calendar month.
The practical reading for the team in the question: 800 million MAU on the consumer app crosses the threshold immediately, before any AI feature ships. The licence does not grant rights to use the Llama-4 base or any derivative of it. The team is operating without a licence unless and until Meta grants the commercial one.
Situations where this technique stops working.
2–4 min · Everything important, quickly.
Real products, models, and research that use this idea.
- Meta's Llama 4 Maverick released under the Llama Community License in 2026, with the same MAU threshold structure as Llama 2 and Llama 3.
- Mistral's Apache 2 licensed open-weight models like Mistral Small 3 are commonly chosen by large-MAU products specifically to avoid this constraint.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you advise a company whose MAU is currently 500 million but projected to cross 700 million within the next year?
Start the commercial-licence conversation with Meta now, before the threshold is crossed. Build the dependency on Llama with the explicit assumption that the licence will need to upgrade, and prepare a swap plan to a permissive-licence base as a fallback if the commercial deal is not in place by the time MAU crosses.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Believing that fine-tuning produces a fresh license-free model. The derivative inherits the upstream terms, including the MAU threshold, the LoRA training step changes nothing about that.
60 second bullets to scan on the way to the call.
The exact numeric MAU threshold in the Llama Community License
What surface the threshold is measured against and why
Primary sources. Browse if you want the original framing.
Same topic, related formats. Practice these next.