Lesson 01 · The map before the territory

The Open-LLM Landscape

LLMs & Open Source · ~10 min · verified June 2026

Before you rent a single GPU, you need a map. This lesson gives you the one mental model that organises the entire open-LLM world — so that every service, price, and buzzword you meet later snaps into a slot you already understand.

Why this matters for you: your bet is that top closed models may get gated, while open models stay good enough to run yourself. To act on that bet — build on open models, advise a business, or eventually buy a box — you first need to see the whole board. That's today.

1 · An open model is just a file

Here's the unlock. A closed model like Claude or GPT is a service you can only rent. An open-weight model is a file — a few gigabytes of numbers — that you can download and run anywhere you have a big enough GPU.1 Almost everything "open source LLM" reduces to one question:

The core question Whose computer runs the file, and how do you pay for that computer? Everything else — Hugging Face, Ollama, OpenRouter, RunPod, on-prem boxes — is an answer to that one question.

(Careful with words: most "open source" LLMs are precisely open-weight — you get the file, not the training data. For your purposes that's fine; just check the license on the model card. Apache-2.0 and MIT models are the safe commercial picks.1)

2 · The four decisions

Running any open model is four choices stacked on top of each other. Learn the stack and you can place any tool you meet.

DecisionThe questionExample answers (June 2026)
ModelWhich file?Qwen3.5, DeepSeek V4, GLM-5.2, Llama 4, Mistral, gpt-oss2
EngineWhat software runs it?llama.cpp (portable) · vLLM (production)3
HostWhose computer?A hosted API · a rented GPU · your own box
AccessHow does your code call it?An OpenAI-compatible endpoint — almost always4
Developer's relief The Access layer is standardised. Nearly every host and engine speaks the same OpenAI-style API, so switching models or providers means changing a base URL and an API key — not rewriting your app.4 You are never locked in. This is the quiet superpower of the open ecosystem.

3 · The cost & control ladder

The Host decision is the one your mission really turns on — it's the whole "OpenRouter vs rent GPUs vs buy a box" question. There are exactly four rungs, from least to most control (and least to most operational burden):

Hosted inference API — pay per token

Someone else runs the model; you just call it. Zero ops. OpenRouter (one endpoint → 300+ models), DeepInfra/Novita (cheapest tokens), Groq (fastest), Together/Fireworks (also fine-tune).5

≈ $0.06–$1 per 1M tokens for mid-size open models · OpenRouter adds ~5.5% on credit top-ups, no per-token markup5

Serverless GPU — pay per second of compute

You deploy a model/container; the platform spins a GPU up on demand and scales to zero when idle. Modal, RunPod Serverless, HF Inference Endpoints.6 More control than an API, no idle cost.

Billed by the second of active GPU time · HF Endpoints from ~$0.03–0.50/hr-equivalent at the low end7

Rented GPU instance — pay per hour

Rent a whole GPU machine; run anything (vLLM, experiments, agents). You manage the server. RunPod, Vast.ai (marketplace, cheapest), Lambda.8 This is your "cheaper access if I run it myself" path — and the no-strong-computer playground.

RTX 4090 from ~$0.31/hr · H100 ~$1.87–2.99/hr (down 64–75% since 2024)8

Your own hardware — pay capex, then power

A personal GPU/Mac for experimentation, or an on-prem server "as an employee" for a business. You own everything: privacy, no per-call cost, full control — and all the maintenance.9

Consumer box ~$2–4k (runs up to ~32B comfortably) · serious H100 server $25–40k/GPU + power, cooling, ~$750–3k/mo labor910

Where do your favourite names sit? Hugging Face is the library behind all four — where the model files live (2.4M+ of them), plus its own hosting on rungs 1–2.7 Ollama / LM Studio live on rung 4 (and rung 3 once you rent a GPU): the friendly software that runs a model on a machine you control.3

4 · The insight that saves you money

Counter-intuitive but load-bearing Climbing the ladder for "cheaper access" usually loses money until you're big. Renting/owning only beats a per-token API at roughly 50–100M tokens/month sustained, or when privacy/compliance forces it — because once you add idle time, ops, and labor, a busy API is astonishingly cheap.10 So the honest 2026 default is: start at rung 1, climb only when the math or the privacy requirement forces you.

This reframes your mission's "rent GPUs to run open models cheaper" idea: it's true — but conditional. The skill you're really building is knowing where the break-even sits for a given workload, so you can advise a business honestly instead of cargo-culting "self-host = cheaper."

Check yourself

Retrieval beats re-reading. Answer from memory before you peek — the effort is what makes it stick.

1. The clearest difference between an open model and a closed model like Claude is:

2. You want to call an open model from code with zero infrastructure work. Which rung?

3. Roughly when does self-hosting an open model start beating a per-token API?

4. Switching your app from one open-model provider to another usually means:

Your primary source

Read one thing this week: "Best Open-Source LLMs in 2026" on the Hugging Face blog.2 It's the highest-signal current roundup — licenses, sizes, and what each model is actually for. Don't memorise the rankings (they change monthly); read it to feel the shape of the field and the names that keep recurring.

Then lurk in r/LocalLLaMA — the practitioners' watering hole. It's where you'll find honest, same-week reports of what runs well on what hardware, and real cost talk. This is where wisdom lives; the lessons give you the vocabulary to follow along.

Next lesson, your pick. Now that the map exists, we drill into one rung hands-on. Likely candidates: (A) rent a GPU and serve a model end-to-end · (B) call open models from code via a hosted API and compare prices · (C) spec a personal/on-prem box and prove what it could run. Tell your teacher which — your answer reshapes the path.

Remember: I'm your teacher, not just a document. If any rung, price, or term here is fuzzy, ask me to expand it, draw it differently, or pressure-test it against your real use case.


Sources (verified June 2026; prices and model names drift monthly — re-check before quoting):

  1. Hugging Face — Best Open-Source LLMs 2026 (licenses & openness)
  2. llm-stats.com — model releases & news feed · BentoML — open-source LLMs 2026
  3. Red Hat — llama.cpp vs vLLM (Jun 2026) · Ollama vs LM Studio vs vLLM vs llama.cpp vs MLX (2026)
  4. Helicone — LLM API providers (OpenAI-compatible endpoints)
  5. Infrabase — AI inference API providers compared (2026) · Costbench — OpenRouter pricing
  6. GPU cloud pricing — RunPod, Lambda, Modal (Jun 2026)
  7. Hugging Face — pricing (Spaces, Inference Endpoints, storage)
  8. Spheron — GPU cloud pricing comparison 2026
  9. SitePoint — local LLM hardware requirements, Mac vs PC 2026
  10. Spheron — on-premise vs cloud break-even analysis 2026