Gemma: AI Control Without Vendor Lock-in

For Norwegian businesses considering AI, the choice often stands between two different paths: cloud-based APIs from OpenAI or Anthropic, or open models that can be run locally. Google's Gemma family, with Gemma 4 launched in April 2026, represents the most mature alternative for the second path.

What is Gemma?

Gemma is a family of open language models from Google, launched in February 2024 and now in its fourth generation. The models are available in several sizes:

• Gemma 4 4B (~4 billion parameters): Fast, affordable, good for simple tasks
• Gemma 4 9B (~9 billion parameters): Balance between performance and resource usage
• Gemma 4 27B (~27 billion parameters): Strong performance for demanding tasks
• Gemma 4 1M (~1 billion parameters, 1M context): Special model for extremely long context

As of May 2026, the Gemma family has over 400 million downloads, according to Google.

Why open models for Norwegian businesses?

1. GDPR and data sovereignty

When you use a cloud-based API, data is sent to the vendor's servers. For Norwegian businesses processing personal data or sensitive business information, this creates legal and practical challenges:

• The Schrems II ruling from the EU Court of Justice in 2020 limits transfer of personal data to the USA
• GDPR Article 44 requires that data leaving the EEA has "adequate protection level"
• Data processing agreements with American companies are becoming increasingly complex

With Gemma run locally or on EU-based infrastructure, all data remains in your control.

2. Predictable costs

Cloud APIs bill per token. For a business with 50 employees using AI daily, costs can quickly become unpredictable:

Estimates based on GPT-4-turbo prices vs. Hetzner/Helsinki GPU server. Self-hosting requires expertise.

3. No vendor lock-in

With an open model, you own the weights. You can:

• Fine-tune the model on your own data
• Run it on any hardware
• Switch hosting provider without changing code
• Further develop the model internally

Apache 2.0: What does it mean in practice?

Gemma is licensed under Apache 2.0, one of the most permissive open source licenses. For Norwegian businesses, this means:

• Commercial use allowed: You can use Gemma in products you sell
• No copyleft: You don't need to open your own source code
• Patent protection: Google gives patent license to users
• Sublicensing: You can build on Gemma and sell the result

Compared to Meta Llama (which has special license terms for companies with >700M users) or Mistral (which has limited commercial license for some models), Apache 2.0 gives maximum flexibility.

Technical requirements for local deployment

Hardware

Software

To run Gemma locally, you need:

1. llama.cpp or Ollama for simple execution
2. Hugging Face Transformers for Python integration
3. vLLM or TGI for production serving

Quick start with Ollama

# Install Ollama
curl -fsSL https://ollama.com/install.sh | sh
 
# Download Gemma 4 4B
ollama pull gemma4:4b
 
# Run interactively
ollama run gemma4:4b

How to get started?

Step 1: Define the use case

Not all tasks require a 27B model. Start by mapping:

• What kind of text should the model generate? (Email, reports, code, customer service?)
• How important is latency? (Should the user wait 1 second or 10?)
• How important is accuracy? (Creative text vs. medical information)

Step 2: Choose model size

For most Norwegian SMBs, 4B or 9B is a good starting point:

• 4B: Chatbot, simple text generation, internal tools
• 9B: Customer service, more demanding text analysis
• 27B: Code generation, complex analysis, fine-tuning

Step 3: Set up infrastructure

Alternative A: Own server

• Hetzner Helsinki: ~500-1500 NOK/month for GPU server
• OVHcloud Gravelines: ~800-2000 NOK/month
• Own data center: High initial cost, low operating costs

Alternative B: Cloud with EU data center

• Google Cloud europe-west3 (Frankfurt)
• Azure West Europe (Amsterdam)
• AWS eu-north-1 (Stockholm)

Step 4: Test and fine-tune

Download the model, test it on representative tasks, and fine-tune if necessary:

from transformers import AutoModelForCausalLM, AutoTokenizer
 
model = AutoModelForCausalLM.from_pretrained("google/gemma-4-4b-it")
tokenizer = AutoTokenizer.from_pretrained("google/gemma-4-4b-it")
 
# Test in Norwegian
prompt = "Write a short email to a customer asking for feedback."
inputs = tokenizer(prompt, return_tensors="pt")
outputs = model.generate(**inputs, max_new_tokens=200)
print(tokenizer.decode(outputs[0]))

Common pitfalls

1. Underestimating infrastructure A 27B model requires significantly more resources than a 4B model. Many businesses start too large and struggle with performance.

2. Lack of fine-tuning Gemma is trained on general data. For specialized tasks (e.g., Norwegian legal text), fine-tuning on own datasets is required.

3. Security gaps Even local models can leak data if accessible from the internet without authentication. Use VPN/firewall.

4. Underestimating operations Local hosting requires expertise in model serving, updates, and monitoring. This is not "set up and forget".

Summary

Gemma represents a mature, open alternative for Norwegian businesses that want AI control. With Apache 2.0 license, local deployment, and predictable costs, it addresses the most important concerns around cloud-based AI services.

For most SMBs, the 4B or 9B model is a good starting point. Begin with a clear use case, test on representative data, and scale gradually as needed.

Next step: Want to know if AIKI can help you set up Gemma for your business? Book a no-obligation consultation.

Sources:

• Gemma 3 announcement (Google, February 2025)
• Gemma 4 announcement (Google, April 2026)
• Gemma models on Hugging Face (Google)
• Apache 2.0 license (Apache Software Foundation)
• GDPR Article 44 (EU)