Alpha
Ctrl K
Contact
Support · Meta Llama 4

Will it last?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input C ยท 70.8/100

This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor
  • AssessUse & modify + Transparency
  • ImplementData control + Reliability
  • UseReliability
  • SupportTransparency

Common problems & fixes

The recurring issues are multimodal input formatting, very-long-context memory pressure, MoE sharding for Maverick/Behemoth, and chat-template / special-token errors. Not exhaustive - the very large Llama-ecosystem community and cloud partners are the practical first stop.

Versions, changelog & cadence

Scout and Maverick are released, with the larger Behemoth alongside, on the verified meta-llama organisation with per-version licence tags. The Hugging Face revision hash is the changelog anchor.

Security / vulnerability disclosure

Meta provides a reporting path (LlamaUseReport@meta.com) and ships Llama Guard / Prompt Guard as a safety layer, though a formal model-vulnerability-disclosure policy is limited.

Community & support channels

The meta-llama organisation, Meta's Llama site and docs, and the very large Llama-ecosystem community and cloud partners.

Deprecation / end-of-life policy

No published deprecation or end-of-life policy for Llama 4 checkpoints. Prior versions remain downloadable, but there is no documented sunset commitment - recorded as a gap.

Tracked known issues

The standing issues are the EU-domiciled multimodal licence gap, the systemic-risk status of the large models, the 700M-MAU commercial trigger, and the download access gate. See Assess for the detail.

How this scores

The ownership factor this domain covers, drawn from the one entry record.

2

TransparencyDo you know what it is: weights, training, behaviour, and legible terms?

Moderate

Weights are inspectable and documentation is strong, but training data and code are closed - open weights, closed process, so moderate.

How this scores (AOI sub-dimensions)
Provenance4/5how well we can trace and verify what went into the modelCanonical, verified (and access-gated) meta-llama org on Hugging Face distributing safetensors with checksums and per-version licence tags; no malicious-checkpoint incident on the canonical org.
Governance3/5how accountable and well-documented the publisher isA named, accountable US provider (Meta) with a verified org and a reporting path (LlamaUseReport@meta.com), meeting the score-3 anchor.
What this means for adoptionFor non-EU users you partially own self-hosted Llama 4: it runs on your infrastructure, performs strongly as a multimodal family, and pairs with Meta's Llama Guard and Prompt Guard (reliability strong), but the Community Licence's 700M-MAU trigger, naming conditions, and access gate keep use-and-modify at moderate - ownership partial. For EU-domiciled individuals and companies the picture is worse: the licence denies you any grant to the multimodal models, so your effective ownership is none - prefer the Llama 3.1 text line (the meta-llama entry, no EU clause) or a non-Llama family. Either way, check the 700M-MAU trigger, honour the Llama attribution terms, and confirm your domicile against the AUP before use.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Licenceread2026-08-03
Llama 4 Community License, read verbatim (via Meta's canonical GitHub mirror meta-llama/llama-models): the "Additional Commercial Terms" 700M-MAU threshold ("greater than 700 million monthly active users in the preceding calendar month, you must request a license from Meta"), the "Built with Llama" attribution clause, California governing law, and the incorporated AUP carrying the EU multimodal restriction.
Terms of serviceread2026-08-03
Llama 4 Acceptable Use Policy, read verbatim: "With respect to any multimodal models included in Llama 4, the rights granted under Section 1(a) ...
Model cardread2026-08-03
Llama 4 on the verified, access-gated meta-llama HF org: Scout (109B/17B, very long context), Maverick (400B/17B), Behemoth (larger); natively multimodal MoE; safetensors with checksums and a llama4 licence tag; hosted on Bedrock/Vertex/Together/Groq.
Third-party analysisunverified2026-08-03
On public leaderboards Llama 4 Maverick is competitive among open multimodal models; the family adds native multimodality and very long context.
Model cardunverified2026-08-03
Meta ships Llama Guard (input/output moderation) and Prompt Guard (prompt-injection/jailbreak detection) with the Llama family and documents safety tuning; no broad independent multimodal red-team is aggregated here.