Explainers
Learn: multi-model AI, routing and orchestration
Plain explanations of the techniques behind multi-model AI — routing, consensus, verification, RAG, memory, and running open-weight models on your own hardware.
Last reviewed:
Pick a concept
- What is multi-model AI?Using several models in one workflow instead of committing to one.
- What is LLM orchestration?The layer that decides which model runs, in what order, and what happens to the output.
- What is AI model routing?Sending each request to a model chosen by task, cost, privacy or latency.
- What is model fallback?What should happen when the first model is down, rate-limited or refuses.
- What is AI consensus?Asking several models the same question and using their agreement as a signal.
- What is best-of-N?Generating several candidate answers and keeping the best one.
- What is an AI judge?Using a model to score other models’ answers, and where that breaks down.
- What is AI answer verification?Checking an answer against something other than the model that produced it.
- What is a context window?The working memory of a single request, and why it is not the same as memory.
- What is retrieval-augmented generation?Retrieving your own documents and putting them in front of the model.
- What is AI memory?What persists between conversations, and what it costs you.
- What are context packs?Reusable bundles of context you attach to a conversation on purpose.
- What is local AI?Running a model on hardware you control, and what that actually changes.
- What are open-weight models?Models whose weights you can download — and what "open" does and does not mean.
- What is self-hosted AI?Running the whole application yourself, not just the model.
- Ollama vs llama.cppTwo ways to run open-weight models locally, and which job each suits.
- Cloud AI vs local AIThe real trade: capability and convenience against control and cost shape.
- AI agent vs AI chatbotThe difference between answering you and doing something for you.