Lesson 1594 of 2244
AI model families: open-weight vs closed — what actually changes
Open weights give you portability, customization, and self-hosting. Closed APIs give you frontier quality and managed ops. Pick by what you'll actually use.
Adults & Professionals · Model Families · ~24 min read
The premise
Open-weight models trade frontier quality for control: portability across clouds, fine-tuning freedom, on-prem deployment. Closed APIs trade control for managed quality and rapid capability updates.
What AI does well here
- Open weights: run anywhere with compatible runtime, fine-tune freely, audit weights. Closed APIs: serve at scale with managed reliability, get capability updates automatically
What AI cannot do
- Open weights cannot match top closed-API frontier capabilities at this moment
- Closed APIs cannot give you weight-level inspection or guaranteed long-term availability
Key terms in this lesson
End-of-lesson quiz
Check what stuck
12 questions · Score saves to your progress.
Tutor
Curious about “AI model families: open-weight vs closed — what actually changes”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 10 min
Choosing a Local Model: Llama, Mistral, Hermes, Qwen, DeepSeek, and Friends
There are too many open-weight models. A short, opinionated tour of the major families and what each is actually good at.
Creators · 18 min
Local Model Family: Llama
Llama is the reference ecosystem for many local-model tools, formats, fine-tunes, and community workflows.
Creators · 11 min
AI Vendor Lock-In: Patterns and Mitigations
AI vendor lock-in happens through API quirks, fine-tunes, and integrations. Mitigation requires deliberate architecture.