Alpha
All entriesContact
Model

Gemma 4

Publisher
Google DeepMind (Google LLC; EU provider of record Google Ireland Limited) (US)
Family
Gemma
Openness
open_weights
Licence
Apache License 2.0
Context
128K / 256K

Use of these weights is owned outright: plain Apache-2.0, no gate, no use policy and no remote shut-off, which the older Gemma Terms of Use did have. What the weights are is not owned: the training data is closed, Google states that user data from its products went into training, and safety evidence is publisher-only. Adopt the instruction-tuned checkpoints behind your own guardrails and check the licence per checkpoint, because Gemma 1 to 3n and the Gemma 3 derivatives you may already run remain under the old terms.

Do you really own it?
Substantial
none·limited·partial·substantial·full
Analytical input: AOI C · 68.8/100
The four ownership factors

Floor-weighted, not averaged. Nothing is weak and both use & modify and data control are strong, so the floor is high; transparency and reliability sit at moderate, which is what keeps it short of full.

1

Use and modify freelyCan you run, modify and adapt it with no gate and no field-of-use trap?

Strong

Plain Apache-2.0 on every Gemma 4 checkpoint, ungated, with no field-of-use limit, no use policy and no remote-restriction right. Users may run, fine-tune, redistribute and sell derivatives (ev-license, ev-hf-inventory).

How this scores (AOI sub-dimensions)
Openness3/5how much is released - weights, data, code, licence - and how freelyOpen weights under an OSI licence, with a model card, a technical report and a Hugging Face weight release for every size.
Legal4/5how permissive and clean the licence is for real commercial usePlain Apache-2.0 with no use policy, field-of-use limit, gate or remote-restriction right, plus a model card, a technical report, a published EU Article 53 training-content summary (v1, 31 July 2026) and Google listed as a Code of Practice signatory.
2

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

Moderate

Weights, model card and technical report are open and a training-content summary exists. The training data is closed (the summary names no dataset), the pre-training pipeline is not released, and the summary discloses user-data and Gemini 3 synthetic-data use that cannot be inspected (ev-eu-summary, ev-tech-report).

How this scores (AOI sub-dimensions)
Provenance4/5how well we can trace and verify what went into the modelThe google organisation on Hugging Face is verified, the core checkpoints are safetensors only, each shard has an LFS sha256, the Hugging Face scan flags no files, and official quantised and drafter checkpoints are documented by use case.
Governance3/5how accountable and well-documented the publisher isAccountable, reputable publisher with a visible cadence (Gemma 1 to 4, dated chat-template and QAT updates, technical report v2) and open community discussions.
3

ReliabilityIs it reliable and good enough for the job?

Moderate

Operational readiness is good (score 4), but the safety evidence is publisher-only and qualitative (score 3) and no guard model has been identified, so the deployer supplies the safety layer (ev-tech-report, ev-docs-overview).

How this scores (AOI sub-dimensions)
Operational4/5how practical it is to run, serve and maintain in productionStandard safetensors on Transformers, with Google documenting official quantised routes for llama.cpp, vLLM and SGLang, drafter checkpoints for speculative decoding, a memory table per precision and 128K to 256K context.
Safety3/5whether misuse risks are evaluated and guardrails are providedInstruction-tuned checkpoints with a publisher safety evaluation and stated policies (child safety, dangerous content, sexually explicit content, hate speech, harassment), documented risks and mitigations, and a Responsible Generative AI Toolkit pointer.
4

Doesn't extract your dataDoes running it keep your knowledge and data yours?

Strong

Self-hosted weights under Apache-2.0 with no clawback of rights, so prompts and outputs stay on the deployer's infrastructure. The licence carries no telemetry or remote-restriction clause (ev-license).

How this scores
Not a scored AOI dimension. For a self-hosted model, data-control is a structural property of running the weights yourself, strong by default unless the model phones home or the licence claws back rights. For a hosted API this factor is the retention + train-on-inputs + residency read, scored from the binding terms.

How the AOI score is computed

The seven dimensions above, each scored 0 to 5, weighted and summed to the 0 to 100 headline. The score is the analytical input behind the ownership verdict, not the verdict itself.

DimensionScoreWeightPoints
Openness3/50.1810.8
Provenance4/50.1612.8
Legal4/50.1612.8
Safety3/50.169.6
Performance3/50.148.4
Operational4/50.129.6
Governance3/50.084.8
HeadlineC · 68.8/100
Dossier coverageAssess 93%Implement 96%Use 94%Support 50%How complete our four-domain documentation is, a measure of our coverage, not of the model. Each domain links to its page.

Sources

Every rating traces to a primary document. Read means the text was verified; unverified means it is known to exist but has not yet been read.

DocumentWhat it grounds
Licenceread2026-11-19
The Gemma 4 licence page (linked as license_link by every Gemma 4 model card) is the Apache License 2.0.
Documentationread2026-11-19
The Hugging Face API (anonymous) shows the google organisation as verified.
Model cardread2026-11-19
The Gemma 4 model card (README of google/gemma-4-31B-it, same text in the other cards, plus the gemma.ai model card page) lists five sizes: E2B, E4B, 12B Unified, 26B A4B and 31B.
Documentationread2026-11-19
The Gemma 4 overview page gives a memory table per precision for each size and routes official QAT checkpoints: q4_0 GGUF for llama.cpp and LM Studio, w4a16 compressed-tensors for vLLM and SGLang, mobile builds, unquantised QAT weights and matching -assistant drafters.
Technical_reportread2026-11-19
The Gemma 4 Technical Report (arXiv 2607.02770 v2, 24 Jul 2026) states that the models are released under Apache 2.0.
Documentationread2026-11-19
Google's EU AI Act Article 53(1)(d) Public Summary of Training Content for the Gemma 4 family is v1, last updated 31 July 2026, from provider Google Ireland Limited.
Terms of serviceread2026-11-19
The Gemma Terms of Use (last modified April 1, 2026) apply only to the models in their Appendix (Gemma 1, 1.1, 2, 3, 3n and siblings; Gemma 4 is not listed) and state 'For Gemma 4 terms, see the Gemma 4 license'.
Terms of serviceread2026-11-19
The Gemma Prohibited Use Policy (last modified February 21, 2024) lists restricted uses for 'Gemma or Model Derivatives' and is bound into a contract only through section 3.2 of the Gemma Terms of Use.
Vendor announcementread2026-11-19
The launch blog (2 April 2026) says Gemma 4 is 'released under a commercially permissive Apache 2.0 license'.
Third-party analysisread2026-11-19
Hugging Face platform data for google/gemma-4-31B-it shows scansDone true with no files with issues, safetensors BF16 parameters 31,273,088,876, an LFS sha256 for each weight shard and no signature files.
Third-party analysisread2026-11-19
The Decoder (2 April 2026) reports Gemma 4 shipping under Apache 2.0 'for the first time' and says earlier Gemma versions used a more restrictive Google proprietary licence.
Third-party analysisread2026-11-19
The Artificial Analysis page for Gemma 4 31B (Reasoning) gives an Intelligence Index v5.0.1 score of 4 and 'Intelligence #14 / 15', and describes the model as at the lower end among comparable open-weights models (median 10).
Third-party analysisread2026-11-19
The European Commission page on the General-Purpose AI Code of Practice (last update 7 October 2026) lists Google among the signatories; it does not say which chapters.
Third-party analysisread2026-11-19
Ollama library page for gemma4: tags e2b, e4b, 12b, 26b and 31b; capability tags vision, tools, thinking and audio; 29.5M downloads; run command 'ollama run gemma4'.
Documentationread2026-11-19
google-deepmind/gemma README and LICENSE: a JAX library to use and fine-tune Gemma with Gemma 4 checkpoint paths; code under Apache-2.0; the library is not the pre-training pipeline; issues go to the repository's GitHub tracker.
Securityread2026-11-19
Google's organisation-wide GitHub SECURITY.md says to report vulnerabilities at g.co/vulnz and that the Google Security Team processes a report within a day and responds within a week.
Third-party analysisunverified2026-11-19
The ADAPT Centre AI Accountability Lab evaluation of the Gemma 4 public training summary is referenced by a secondary blog.