0
LLM Engineering & APIs
Phase 2Module 5 of 12

Open Source Models

Closed APIs create vendor lock-in, data privacy concerns, and unpredictable pricing. Open-source models let organizations own their AI stack, fine-tune for domain-specific tasks, and deploy without per-token costs.

Closed models are like renting a furnished apartment — convenient but you can't renovate. Open-source is like buying a house — more work upfront, but you own it, customize it, and no monthly rent per token.

Visual Workflows

Start here — study each diagram, then use + / to zoom if needed.

100%
Loading diagram...

Scroll inside the frame · use + / − to zoom

Key Takeaways

  • 1.Open-source LLMs (Llama, Mistral, Qwen, Gemma) are publicly available models you can download, fine-tune, and deploy on your own infrastructure — offering transparency, customization, and cost control. Major families: Meta Llama 3 (8B-70B, strong general), Mistral/Mixtral (efficient, MoE), Qwen (Alibaba, multilingual, strong coding), Gemma (Google, compact), Phi (Microsoft, small but capable).
  • 2.Hosted on HuggingFace Hub. License matters: Llama Community License (commercial OK with limits), Apache 2.0 (fully open).
  • 3.Fine-tuning: LoRA/QLoRA for efficient adaptation. Deployment: Ollama (local), vLLM (production GPU), TGI (HuggingFace).
  • 4.Benchmark against closed models on your specific tasks — open models often match GPT-3.5 level.

Real Example

Scenario

Healthcare startup fine-tunes Llama-3-8B on medical Q&A with QLoRA (4-bit training on single GPU). Deploys on vLLM with HIPAA-compliant infrastructure. Matches GPT-3.5 on medical benchmarks at zero per-token cost.

What you would do

In LLM Engineering & APIs, apply Open Source Models to this scenario: Healthcare startup fine-tunes Llama-3-8B on medical Q&A with QLoRA (4-bit training on single GPU). Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.

Practice Task

Open the Code Walkthrough below and run it locally. Change one parameter related to Open Source Models (e.g. model, temperature, top_k, or tool name), observe the difference in output, and write 2–3 sentences explaining what changed.

Code Walkthrough

Highlighted lines show where Open Source Models happens in the code.

Open Source Models
1from transformers import AutoModelForCausalLM, AutoTokenizer  # import dependencies2import torch  # import dependencies3
4model_name = "meta-llama/Llama-3.1-8B-Instruct"5tokenizer = AutoTokenizer.from_pretrained(model_name)6model = AutoModelForCausalLM.from_pretrained(7    model_name,8    torch_dtype=torch.float16,9    device_map="auto",10)11
12messages = [{"role": "user", "content": "Explain open-source LLMs briefly."}]  # key line for Open Source Models13input_ids = tokenizer.apply_chat_template(messages, return_tensors="pt").to(model.device)14
15with torch.no_grad():16    output = model.generate(input_ids, max_new_tokens=100, temperature=0.7)17print(tokenizer.decode(output[0], skip_special_tokens=True))  # show output for debugging

Cheat Sheet

Quick recap

quick ref
  • Llama 3.1: meta-llama/Llama-3.1-8B-Instruct
  • Mistral: mistralai/Mistral-7B-Instruct
  • LoRA: train adapters, not full weights
  • QLoRA: 4-bit training
  • HuggingFace: model hub + transformers
  • vLLM for production serving

Common Mistakes

  • Ignoring model license restrictions for commercial use
  • Fine-tuning without eval set — can't measure improvement
  • Deploying FP16 70B model without quantization — OOM
  • Choosing model by benchmark alone — test on your data