Google releases Gemma 3 as open weights under Apache 2.0 — the semi-open era ends, and Llama 4 just lost its licensing edge

On August 5, 2026, Google DeepMind upended the open-source model market by releasing Gemma 3 under the Apache 2.0 license — a permissive license that allows commercial use, modification, and redistribution without restriction. This is not a minor evolution of the Gemma line. It is a complete strategic pivot. The first two generations of Gemma (February and June 2024) shipped under a proprietary « Gemma Terms of Use » license that explicitly banned certain commercial uses and required companies to declare their usage. Gemma 3 buries those restrictions.

With 27 billion parameters, a one-million-token context window, and performance that places its 7B variant above Llama 4 8B on the MMLU-Pro benchmark, Google is not just catching up with Meta in the open model race — it is changing the rules by choosing a license that even the most risk-averse enterprises can accept without legal review.

Apache 2.0: Google’s real strategic weapon

Raw model performance has become a numbers race that enterprise users are growing tired of. The difference between 85% and 87% on MMLU-Pro is not what makes a CISO or CTO decide to deploy an LLM in production. What decides is legal certainty around the license.

The Apache 2.0 license has been the gold standard of permissive open source for twenty years. Every legal department understands it, every compliance scanner (FOSSA, Snyk, Black Duck) supports it, and it raises zero questions during due diligence. By comparison:

• Llama 4 (Meta) uses a proprietary license with usage restrictions, monthly active user thresholds beyond which a commercial license is required, and an automatic termination clause for non-compliance.
• Mistral Large 3 (Mistral AI) is available under the Mistral Research License for weights, with a separate paid commercial license for production deployment.
• Qwen 3 (Alibaba) uses a « Qwen License » with restrictions that block usage by entities with more than 100 million monthly active users — a clause that rules out every large enterprise.

Gemma 3 under Apache 2.0 removes this friction entirely. A bank, an insurance company, or a government agency can integrate the model into its pipeline, fine-tune it on internal data, and deploy it in its data center or private cloud without ever consulting its legal department.

This decision is not philanthropy. Google owns Google Cloud, which sells TPU v6 instances and GKE clusters optimized for large model inference. By distributing the most permissively licensed model on the market for free, Google removes the primary barrier to adoption — fear of legal risk — and captures infrastructure revenue downstream. This is the exact strategy that made Kubernetes successful a decade ago: the software is free, the control plane is free, hosting on Google is optional, not mandatory — but extremely convenient.

What 27 billion parameters mean in August 2026

Gemma 3 ships in two sizes: 7B and 27B. The 27B variant is a dense model (not a mixture-of-experts like Mixtral), meaning all 27 billion parameters are engaged on every inference pass. The trade-off is well understood: a dense model costs more memory than an equivalently sized MoE, but it is more coherent, more reliable on multi-step reasoning, and easier to fine-tune without degrading performance on non-targeted tasks.

The benchmarks published by Google DeepMind on August 5, 2026 place Gemma 3 7B above Llama 4 8B on MMLU-Pro (81.2% vs. 79.8%), HumanEval (72.5% vs. 68.3%), and MATH (58.7% vs. 52.1%). The 27B variant rivals Llama 4 70B on most academic benchmarks while consuming three times less VRAM — a decisive ratio for deployment on constrained infrastructure.

The one-million-token context window is the second decisive technical argument. It enables processing the equivalent of three novels or a 200,000-line codebase in a single inference pass. For enterprise use cases — contract analysis, code review, knowledge extraction from technical documentation — this capacity reduces the need for chunking and intermediate summarization, two major sources of accuracy loss in RAG architectures.

Weights are available in bfloat16 (for recent GPUs) and int4 quantized (for CPU or consumer GPU deployment). The int4 version of Gemma 3 27B fits in 18 GB of VRAM, making it runnable on a single RTX 4090 or a Mac Studio M3 Ultra with 64 GB of unified memory.

Fine-tuning: verticalizing the model without losing general capabilities

The Apache 2.0 license shows its full value when it comes to fine-tuning. A company can train Gemma 3 on its internal documentation and support logs to build a tier-1 assistant that knows its products, contracts, and procedures — without ever sending data to the Google Cloud API and without a contractual clause authorizing Google to use that data.

The use cases emerging from early community feedback (Hugging Face, r/LocalLLaMA) are significant:

• Internal legal assistance: Gemma 3 27B fine-tuned on thousands of contracts and amendments, capable of flagging a non-standard clause in a new contract within seconds.
• Code review in proprietary languages: the million-token context window allows ingesting an entire module in a single pass, and fine-tuning on the internal codebase captures domain-specific idioms that a general-purpose LLM does not know.
• Tier-1 customer support in 15 languages: Gemma 3 was natively trained on a multilingual corpus covering major European and Asian languages, and fine-tuning on an existing ticket database verticalizes response quality without losing language coverage.

The cost of fine-tuning remains the limiting factor. Fine-tuning Gemma 3 27B with LoRA (Low-Rank Adaptation) on a 10,000-example dataset takes approximately 4 hours on 4× A100 80 GB using the Unsloth library, for a cloud cost of around $90 on a spot instance. This is an order of magnitude accessible to an SME with a modest R&D budget.

The open-weight trap: maintenance and updates

Publishing a model as open weights does not solve the lifecycle problem. A model deployed in production must be updated — to incorporate new knowledge, to fix biases discovered post-release, or simply to keep pace with shifting benchmarks that redefine the state of the art every three months.

Google DeepMind has not announced a release cadence for future Gemma 3.x versions, unlike Meta which has established a six-month release rhythm for Llama 4.x. Companies adopting Gemma 3 for production must assume that the successor to Gemma 3 could arrive without notice, under a different license, and with architectural changes that would render existing fine-tuning obsolete.

The best practice is to treat the model as an interchangeable infrastructure component: abstract model calls behind an internal API (such as vLLM or TGI), version fine-tuning as an MLflow or DVC artifact, and maintain an automated retraining pipeline capable of reproducing the fine-tuning on a new model version in under 24 hours.

Verdict

If you need to deploy an LLM in production in a regulated environment or a large enterprise, choose Gemma 3 27B. The Apache 2.0 license removes the legal barrier that Llama 4 and Mistral maintain, performance rivals models three times its size, and the million-token context window opens use cases the previous generation could not handle without compromise.

If you already have a Llama 4 pipeline in production, do not rush to migrate. The migration cost — re-fine-tuning, re-benchmarking, re-certification — outweighs the marginal performance gain. But for your next project, Gemma 3 is the default choice. The Apache 2.0 license is not a detail: it is the argument that moves the model from « technically interesting » to « deployable without friction in a large organization ». And in August 2026, neither Meta nor Mistral offers that.

References

• Google DeepMind — Gemma 3 Technical Report, August 5, 2026.
• Hugging Face — Gemma 3 Model Card, August 5, 2026.
• Apache License 2.0, Apache Software Foundation.
• Meta — Llama 4 Acceptable Use Policy, Meta Platforms.
• Unsloth — LoRA Fine-tuning Guide, Unsloth documentation, August 2026.