The Back Page

*The Tech Stack's reference — a back page for the human to read, to find the tools, the models,

the information. Written by the desk's AI, 2026-07-26. Organized by what YOU need, not by taxonomy. Entries marked ⚑ move fast — the desk re-verifies them on cadence;

everything else is stable ground. This document drops into THE WHOLE STACK (the codex).*

I NEED A MODEL

The frontier (API, pay per token):

• Claude (Anthropic) — claude.ai · API at docs.anthropic.com. Opus (flagship) / Sonnet (workhorse) / Haiku (fast-cheap) ⚑ tiers move. Strongest at: long documents, code, agents that stay coherent. Start here if your work is text-heavy or multi-step.
• ChatGPT / GPT (OpenAI) — chatgpt.com · platform.openai.com. The broadest ecosystem and tooling; reasoning tiers spend extra compute thinking and price accordingly ⚑. Start here if you want maximum integrations and plugins.
• Gemini (Google) — gemini.google.com · ai.google.dev. The context-length and multimodal play, priced aggressively in the light tier ⚑; native to Google's cloud and Workspace. Start here for very long documents, video understanding, or if you live in Google's stack.
• Mistral — mistral.ai. The European lab; strong mid-size models, open-weight releases alongside API. Start here for EU data posture or efficient mid-tier work.

Open weights (download and run):

• Llama (Meta) — llama.com · on Hugging Face. The anchor of the self-host world; the ecosystem's default base ⚑ versions move.
• DeepSeek — deepseek.com. Open-weight reasoning models that reset cost expectations ⚑; watch licenses per release.
• Qwen (Alibaba) — on Hugging Face. Broad size range, strong multilingual + coding; heavy presence in the self-host and coding-assistant world ⚑.
• Gemma (Google) — open-weight siblings of Gemini; the downloadable tier for Google's ecosystem.
• Where all of them live: huggingface.co — the registry. Search the model, read the card, check the license. If it isn't on Hugging Face, be suspicious.

How to choose (the desk's rule): name your task → set your constraints (privacy, latency, budget) → test the cheapest candidate that plausibly clears the bar on TEN of your own real tasks. The leaderboard is marketing; your ten prompts are procurement. Full procedure: the choosing-a-model chapter.

I NEED TO RUN A MODEL MYSELF

• Ollama — ollama.com. The on-ramp: one command, a local model on your laptop. Start here, tonight.
• LM Studio — lmstudio.ai. The GUI for the same job; model browser + chat + local server.
• llama.cpp — github.com/ggerganov/llama.cpp. The engine underneath most local inference; quantized GGUF files run on consumer hardware.
• vLLM — github.com/vllm-project/vllm. The serving engine when it's a server, not a laptop — batching + PagedAttention = the throughput standard.
• Text Generation Inference (Hugging Face) — the other production server; tight HF integration.
• What hardware: VRAM decides everything. ~8GB runs 7-8B quantized; ~24GB runs 30B-class; 70B+ wants multiple cards or heavy quantization. The Hardware area's calculator does your math.

I NEED TO BUILD WITH AI (the working stack)

Call a model: the vendor SDK first (anthropic / openai / google-genai on PyPI). No framework needed to send a prompt.

Orchestrate when it's real:

• LangChain / LangGraph — langchain.com. The broadest glue; LangGraph for stateful agent graphs.
• LlamaIndex — llamaindex.ai. Retrieval-first framing; strongest at document pipelines.
• Vercel AI SDK — sdk.vercel.ai. The TypeScript/front-end lane.

Vector stores (RAG's shelf):

• pgvector — Postgres extension. If you have Postgres, start here; boring wins.
• Qdrant — qdrant.tech (what this desk runs) · Weaviate · Milvus — dedicated engines when scale demands.
• Chroma — trychroma.com. The prototyping default; in-process, zero ceremony.
• Pinecone — pinecone.io. Managed, serverless; pay to not operate it.

Embeddings: vendor APIs (OpenAI text-embedding, Cohere, Voyage) or open (BGE, GTE, E5 families on HF — this desk runs bge-m3 locally). Same rule as models: test on YOUR corpus.

Evals + observability: Langfuse (open) · LangSmith (LangChain's) · Braintrust · promptfoo for CI-style prompt tests. If you ship without evals you're shipping vibes.

Agents, honestly: the loop is model + tools + memory in a while-loop — the Orchestration area shows it in twenty lines. Frameworks (LangGraph, CrewAI, the vendor agent SDKs ⚑) buy you persistence and tracing, not reliability. Reliability comes from short loops, checkpoints, and human gates.

I NEED AI IN MY EDITOR / TERMINAL

• Claude Code (Anthropic) — terminal + IDE agentic coding ⚑.
• Cursor — cursor.com. The AI-first editor fork.
• GitHub Copilot — the incumbent autocomplete + chat inside VS Code/JetBrains.
• Windsurf / Zed / Continue ⚑ — the fast-moving second shelf; Continue is the open-source route.
• The desk's rule from the IDE guide: pick the tool that sees the most of your real context (files, diffs, terminal) — context supply beats model choice inside an editor.

I NEED TO LEARN THIS PROPERLY

Start (the free canon):

• Andrej Karpathy — "Intro to Large Language Models" + "Let's build GPT" (YouTube). The best hours available at any price.
• 3Blue1Brown — the neural network series. The visual math foundation.
• The Illustrated Transformer (Jay Alammar). The canonical visual explainer — our Principles receipts cite it for a reason.

Go deeper:

• fast.ai — Practical Deep Learning. Top-down, code-first.
• DeepLearning.AI short courses — free, current, tool-specific (prompting, RAG, agents).
• Hugging Face Learn — the NLP/LLM course; open ecosystem native.
• Stanford CS224N / CS25 — lecture-grade depth, on YouTube.

Keep it honest: the papers that matter start with "Attention Is All You Need" (2017) — but read explainers first, papers second. The desk's chapters cite the load-bearing ones per concept.

And this desk: the 8 areas + 33 chapters + the films — built to take you from zero to dangerous. Start at Principles, type a sentence into the tokenizer.

I NEED TO KEEP UP (without drowning)

• The desk's own feed — THE STACK THIS WEEK (arriving) — releases, tools, one tip, curated, no junk.
• Simon Willison's weblog — simonwillison.net. The most honest running record of using these tools.
• Interconnects (Nathan Lambert) — the open-model and post-training state of play.
• Latent Space — the AI-engineer beat: patterns from people shipping.
• AI Explained (YouTube) — release-day analysis that respects your intelligence.
• SemiAnalysis — when you need to know what the hardware layer is actually doing.
• Epoch AI — epoch.ai — the numbers on compute and scaling, with methods.
• The rule: two or three sources read weekly beat twelve skimmed daily. Everything else, let the desk catch.

I NEED THE REFERENCE (the deep shelves on this site)

• The 33 chapters — every concept, mechanism-deep, with receipts. Under each area.
• The layer dossiers — the long-form deep reads (hardware, infrastructure, foundation, orchestration, application): what each layer is, what it does, and where it breaks.
• The kits — 85 tools by layer, each with what-it's-for.
• The resources directory — 188 links and growing under the research build.
• The model dossiers — Claude · OpenAI · Gemini · open-source: buying-and-using guides.
• The films — the 8 layer films + the documentary; the section, watchable.
• The Playbook — best practices · how-tos · integrations · the prompt library: what to actually do, arranged the way problems arrive.

*⚑ entries ride the Librarian's cadence for re-verification. Gaps this v1 knows it has: per-cloud

AI services (AWS Bedrock / Azure AI / GCP Vertex — a shelf of their own, next pass), the audio/

image/video generation stack (its own section, next pass), and the newest releases past the desk's

last verification date — exactly what THE STACK THIS WEEK exists to carry.*

The Directory

The tool and platform landscape, organized by the stack’s own layers — each entry: what it is, and when to reach for it. Grows every research pass.

SHELF I — HARDWARE (the silicon)

*The chips, and the places you rent them by the hour. For most readers "hardware" means a GPU cloud

account, not a purchase order — the rental entries are where the action is.*

The chipmakers (reference — know who makes the floor you stand on)

• NVIDIA — the company whose GPUs run the overwhelming majority of AI training and inference; CUDA is the moat. Reach for it when: you're buying or renting compute and want the default that everything supports. · Chips
• AMD (Instinct MI-series) — the credible challenger; MI300/MI325-class accelerators with large memory, running the ROCm software stack. Reach for it when: you want price-per-gigabyte-of-VRAM leverage and your stack runs on ROCm. · Chips
• Google TPU — Google's in-house accelerator, rentable only through Google Cloud; the one major stack that isn't NVIDIA. Reach for it when: you're training on JAX or want an alternative supply curve. · Chips
• Cerebras — wafer-scale chips (one giant chip instead of many small ones) sold as systems and as an inference API. Reach for it when: you want extremely fast inference on supported open models. · Chips
• Groq — custom "LPU" inference silicon behind an API; known for very high tokens-per-second on open-weight models. Reach for it when: latency is the product and an open model is good enough. · Inference silicon
• TSMC — the fab that manufactures nearly every advanced AI chip; the physical chokepoint of the entire industry. Reach for it when: you're reading the supply chain, not buying anything. · Fab / reference

GPU clouds & rental (the money shelf — this is where readers actually spend)

• Lambda — AI-first GPU cloud; on-demand and reserved H100/B200-class instances plus one-click clusters. Reach for it when: you want serious training hardware without hyperscaler procurement. · GPU cloud
• CoreWeave — the biggest of the neoclouds; hyperscale GPU capacity, Kubernetes-native, now a public company. Reach for it when: you need real cluster scale and a negotiated commitment. · GPU cloud
• RunPod — pay-per-second GPU rental with a community cloud tier and serverless GPU endpoints. Reach for it when: you want the cheapest practical way to grab a single GPU for hours, or serverless inference on your own model. · GPU cloud
• Vast.ai — a marketplace of other people's GPUs, from data centers to hobbyist rigs; lowest prices, variable reliability. Reach for it when: cost matters more than SLAs — experiments, batch jobs, fine-tune runs you can restart. · GPU marketplace
• Together AI (GPU Clusters) — beyond its inference API, Together rents dedicated training clusters with the plumbing pre-solved. Reach for it when: you're fine-tuning or pretraining and want cluster ops handled. · GPU cloud
• Crusoe — GPU cloud built on stranded/low-carbon energy; a data-center operator that rents compute. Reach for it when: you want capacity with an energy story, or you're watching the power layer. · GPU cloud
• Hyperstack / Nebius / neoclouds (category) — the second tier of dedicated GPU clouds competing on price and availability. Reach for it when: the big names are sold out or you're price-shopping a known workload. · GPU cloud
• Paperspace (DigitalOcean) — approachable GPU notebooks and machines under the DigitalOcean umbrella. Reach for it when: you want a friendly on-ramp — a notebook with a GPU attached, minutes from signup. · GPU cloud
• Google Colab — hosted notebooks with free and paid GPU tiers; the classroom of the whole field. Reach for it when: learning, prototyping, or running someone's shared notebook. · Notebook + GPU
• Kaggle Notebooks — free GPU/TPU notebook hours plus the datasets and competitions community. Reach for it when: you want free compute for learning and a dataset already attached. · Notebook + GPU
• Apple Silicon (local) — Macs with unified memory run surprisingly large open models via llama.cpp/MLX; the zero-marginal-cost inference path. Reach for it when: privacy, offline, or "I already own the hardware." · Local hardware

SHELF II — INFRASTRUCTURE (the physical plant & the platform layer)

*Where compute lives and how jobs get placed on it: the hyperscalers, the serverless-GPU platforms, and

the scheduling software underneath.*

The hyperscalers

• AWS — the largest cloud; AI surface spans Bedrock (managed model APIs), SageMaker (ML platform), and Trainium/Inferentia custom silicon. Reach for it when: your company is already on AWS — gravity wins — or you need Bedrock's model menu inside an enterprise-compliance envelope. · Cloud
• Microsoft Azure — the cloud wired most tightly to OpenAI; Azure OpenAI Service is how enterprises consume GPT models with enterprise controls. Reach for it when: you need OpenAI models with enterprise data guarantees, or Microsoft-stack integration. · Cloud
• Google Cloud (GCP) — Vertex AI platform, Gemini APIs, and the only rentable TPUs; the most vertically integrated AI cloud. Reach for it when: you want Gemini at enterprise terms or TPU economics. · Cloud
• Oracle Cloud (OCI) — the surprise fourth player; large GPU superclusters at aggressive prices, host to major AI-lab workloads. Reach for it when: negotiating big GPU commitments and you want a fourth bidder in the room. · Cloud

Serverless & job platforms (rent the abstraction, not the box)

• Modal — serverless GPUs defined in Python; your function scales to hundreds of containers and to zero. Reach for it when: you want to ship a GPU workload without touching infrastructure — the fastest idea-to-production path on this shelf. · Serverless GPU
• Replicate — run and publish models behind a one-line API; the community catalog makes it a demo engine. Reach for it when: you want someone else's open model (image, video, audio, LLM) behind an API in one minute. · Model hosting
• Baseten — production-grade model serving with performance tooling (their Truss packaging) and autoscaling. Reach for it when: your own model needs real production serving with SLAs. · Model serving
• Cloudflare Workers AI — inference on Cloudflare's edge network, priced per request, wired into their developer platform. Reach for it when: you're already on Workers and want small-model inference close to users. · Edge inference
• SkyPilot — open-source broker that runs your job on whichever cloud is cheapest/available, with spot-instance failover. Reach for it when: you have multi-cloud accounts and want the price arbitrage automated. · Scheduler (OSS)

Cluster software (the plumbing — reference for the dossier, and real choices for builders)

• Kubernetes — the container orchestrator that most GPU clouds speak natively; the default control plane of the modern cluster. Reach for it when: you operate services, not just jobs. · Orchestration (OSS)
• Slurm — the venerable HPC batch scheduler; still what most large training clusters actually run. Reach for it when: you're queueing multi-node training jobs on dedicated hardware. · Scheduler (OSS)
• Ray / Anyscale — the distributed-Python framework used inside many training and serving stacks; Anyscale is its managed cloud. Reach for it when: scaling Python workloads across machines without writing distributed systems. · Distributed compute (OSS) / managed
• Docker — containers; the unit of shipping in all of the above. Reach for it when: always — it's the envelope everything above expects. · Containers (OSS)

Training-run tooling (MLOps)

• Weights & Biases — experiment tracking, model registry, and now LLM tracing (Weave); the lab notebook of ML teams. Reach for it when: any run you might need to compare against another run. · MLOps
• MLflow — the open-source experiment tracker and model registry; the self-hosted counterpart to W&B. Reach for it when: you want tracking without a vendor. · MLOps (OSS)
• Hugging Face Hub — the GitHub of models: weights, datasets, Spaces demos, and the transformers library ecosystem. Reach for it when: finding, publishing, or evaluating any open model or dataset — the field's reference shelf. · Model hub

SHELF III — FOUNDATION (the models themselves)

*The frontier APIs, the open-weight families, the inference providers that serve them, and the tooling for

making a model your own. The densest shelf, because the model is the heart of the stack.*

Frontier model APIs (closed weights, top capability)

• OpenAI API (GPT family) — the market-defining model line; broadest ecosystem, most third-party integrations. Reach for it when: you want the default the whole tool ecosystem assumes. · Model API
• Anthropic API (Claude family) — frontier models with a long-context, agentic-coding, and reliability reputation. Reach for it when: long documents, coding agents, and tasks where instruction-following under pressure matters. · Model API
• Google Gemini API — frontier multimodal models with very large context windows and aggressive pricing tiers. Reach for it when: multimodal input, huge context, or price-performance at the mid-tier. · Model API
• Mistral (La Plateforme) — Europe's frontier lab; strong mid-size models, open and commercial, EU data residency. Reach for it when: efficiency-tier workloads or European compliance requirements. · Model API
• Cohere — enterprise-focused models (Command family) with strong embeddings and reranking; RAG-centric positioning. Reach for it when: enterprise search/RAG where embeddings + rerank + generation come from one vendor. · Model API
• xAI API (Grok) — the Grok model family via API, with real-time X data as a differentiator. Reach for it when: you want frontier-class output wired to live social data. · Model API

Open-weight model families (reference — the weights are the product)

• Meta Llama — the open-weight family that reset the industry; the default base for fine-tunes and local deployment. Reach for it when: you need weights you control, with the biggest tooling ecosystem. · Open weights
• DeepSeek — Chinese lab whose open reasoning and MoE models matched closed frontier scores at a fraction of the claimed training cost. Reach for it when: open-weight reasoning capability per dollar is the criterion. · Open weights
• Qwen (Alibaba) — the broadest open family — sizes from sub-1B to frontier-class, strong multilingual and coding variants. Reach for it when: you need a specific size/capability point; there's a Qwen for almost every slot. · Open weights
• Mistral open models — the efficient open line (and the Mixtral MoE lineage) from the Paris lab. Reach for it when: permissive-license weights at strong quality-per-parameter. · Open weights
• Google Gemma — Google's small open family, distilled from Gemini tech. Reach for it when: small, well-behaved models for on-device or cheap serving. · Open weights
• OpenAI open-weight models (gpt-oss) — OpenAI's return to open weights, released 2025 as gpt-oss-120b and gpt-oss-20b. Reach for it when: you want OpenAI-flavored behavior on your own hardware. · Open weights

• Phi (Microsoft) — Microsoft's family of small open-weight models trained on curated and synthetic data; they consistently outperform models larger than them on reasoning benchmarks. Reach for it when: you need a capable model that runs on a laptop, an edge device, or a tight inference budget. · Open weights

Inference providers (someone else's GPUs serving open models)

• Together AI — the leading open-model inference API; big catalog, fine-tuning, and dedicated endpoints. Reach for it when: you want open-weight models at production scale without owning serving. · Inference
• Fireworks AI — speed-focused inference for open models, with function-calling and compound-AI features. Reach for it when: latency-sensitive production on open models. · Inference
• Groq (API) — the LPU silicon, consumed as an API; extreme tokens-per-second on supported models. Reach for it when: perceived speed is the feature — voice, live chat, rapid agent loops. · Inference
• OpenRouter — one API key, hundreds of models across every provider, with routing and price comparison built in. Reach for it when: you want to try everything without ten accounts, or route across providers by price/uptime. · Gateway / inference
• DeepInfra / Novita / value tier (category) — the discount aisle of open-model inference; same models, thinner margins. Reach for it when: a batch workload where cost per million tokens is the only line that matters. · Inference
• Hugging Face Inference Providers — serverless inference across partner providers, integrated with the Hub. Reach for it when: you're already on the Hub and want one-click serving of what you find. · Inference

Self-hosted serving (your GPUs, open software)

• vLLM — the de facto open serving engine; continuous batching and PagedAttention made it the throughput standard. Reach for it when: serving an open model on your own GPUs in production. · Serving (OSS)
• SGLang — the fast-rising alternative serving engine, strong on structured output and multi-turn workloads. Reach for it when: you're chasing serving throughput and vLLM isn't winning your benchmark. · Serving (OSS)
• Ollama — one-command local model runtime for laptops and servers; the front door of local AI. Reach for it when: running open models locally with zero ceremony — development, privacy, or hobby hardware. · Local runtime (OSS)
• llama.cpp — the C++ inference engine that made CPU/consumer-GPU inference real; GGUF quantized models everywhere. Reach for it when: squeezing a model onto modest hardware, or embedding inference in an application. · Local runtime (OSS)
• LM Studio — a polished desktop app for downloading and chatting with local models; llama.cpp with a friendly face. Reach for it when: you want local models without touching a terminal. · Local app

Fine-tuning & customization

• Unsloth — open-source fine-tuning that cuts VRAM and time dramatically; the default answer to "how do I fine-tune on one GPU." Reach for it when: LoRA/QLoRA fine-tunes on a single consumer or rented GPU. · Fine-tuning (OSS)
• Axolotl — config-driven open fine-tuning framework covering most model families and methods. Reach for it when: reproducible fine-tune recipes beyond a notebook. · Fine-tuning (OSS)
• OpenPipe — fine-tune small models on your production LLM traffic to replace expensive frontier calls. Reach for it when: a high-volume prompt is burning money on a frontier model and a distilled small model would do. · Fine-tuning SaaS
• Predibase — managed LoRA fine-tuning and serving with per-adapter economics (LoRAX lineage). Reach for it when: serving many fine-tuned variants cheaply. · Fine-tuning SaaS
• Together / Fireworks fine-tuning — the inference providers' managed fine-tune paths. Reach for it when: you already serve there and want the weights close to the serving. · Fine-tuning SaaS

Embedding models (the quiet workhorses)

• OpenAI text-embedding-3 — the default embedding API; cheap, good, everywhere. Reach for it when: starting any RAG build — it's the baseline to beat. · Embeddings
• Voyage AI — embedding-and-rerank specialist (now under MongoDB), strong domain-specific models (code, law, finance). Reach for it when: retrieval quality in a specific domain is the bottleneck. · Embeddings
• Cohere Embed + Rerank — multilingual embeddings and the most-used commercial reranker. Reach for it when: adding a rerank stage — often the single cheapest retrieval-quality win. · Embeddings
• Open embeddings (nomic-embed, BGE/bge-m3, GTE family) — open-weight embedding models that run anywhere, including multilingual (bge-m3). Reach for it when: embeddings must run locally or for free — quality is close, price is zero. · Embeddings (OSS)

SHELF IV — ORCHESTRATION (the wiring around the model)

*Frameworks, agents, retrieval, vector stores, evals, gateways, guardrails. The highest tool churn and the

highest affiliate density on the site — and the shelf where "learn the slot, not the logo" matters most.*

App & agent frameworks

• LangChain / LangGraph — the biggest LLM-app ecosystem; LangGraph is its graph-based agent runtime, the current center of gravity. Reach for it when: building agent workflows with the largest integration catalog and hiring pool. · Framework (OSS) [AFFILIATE via LangSmith]
• LlamaIndex — the data-framework: ingestion, indexing, and retrieval pipelines over your documents. Reach for it when: the hard part of your app is the data side of RAG. · Framework (OSS) [AFFILIATE via LlamaCloud]
• CrewAI — role-based multi-agent framework ("crew of agents"), with a managed platform. Reach for it when: prototyping multi-agent workflows quickly with an opinionated structure. · Agents (OSS)
• Microsoft AutoGen / Semantic Kernel — Microsoft's multi-agent research framework and its enterprise SDK sibling. Reach for it when: .NET/enterprise-Microsoft environments, or research-grade multi-agent patterns. · Agents (OSS)
• OpenAI Agents SDK — OpenAI's first-party agent framework wired to its Responses API and tools. Reach for it when: all-in on OpenAI and want the paved road. · Agents (OSS)
• Claude Agent SDK — Anthropic's agent harness — the machinery behind Claude Code, exposed as an SDK. Reach for it when: building long-running, tool-using agents on Claude. · Agents (OSS)
• DSPy — programs, not prompts: declarative pipelines whose prompts are optimized automatically against a metric. Reach for it when: you have an eval metric and want the prompt engineering done by optimization. · Framework (OSS)
• Haystack — the production-focused open RAG/pipeline framework from deepset. Reach for it when: enterprise search pipelines with a stability-first culture. · Framework (OSS)
• Model Context Protocol (MCP) — the open standard for connecting tools and data to models; the USB port of the agent layer. Reach for it when: exposing any tool or data source to any MCP-speaking client — write once, plug everywhere. · Standard (open)

Vector databases & retrieval infrastructure

• pgvector (Postgres) — vector search inside the database you already run. Reach for it when: first choice for most teams — if your app has Postgres, start here and only leave when scale forces you. · Vector DB (OSS)
• Pinecone — the managed vector-DB pioneer; serverless, zero-ops, scales without thought. Reach for it when: you want retrieval as a utility bill, not a system you operate. · Vector DB
• Qdrant — open-source vector engine in Rust with strong filtering and a managed cloud. Reach for it when: self-host-first with a cloud escape hatch; heavy metadata filtering. · Vector DB (OSS) [AFFILIATE cloud]
• Weaviate — open-source vector DB with hybrid (keyword+vector) search and built-in vectorizer modules. Reach for it when: hybrid search out of the box matters. · Vector DB (OSS) [AFFILIATE cloud]
• Milvus / Zilliz — the open vector DB built for billion-vector scale; Zilliz is its managed cloud. Reach for it when: the vector count has nine-plus digits. · Vector DB (OSS) [AFFILIATE cloud]
• Chroma — the developer-friendly embedded vector store; pip install and go. Reach for it when: prototypes, notebooks, and small apps — the SQLite of vector stores. · Vector DB (OSS)
• Turbopuffer — object-storage-backed serverless vector search, cost-optimized for large, mostly-cold corpora. Reach for it when: huge, mostly-cold vector corpora where storage cost dominates. · Vector DB
• Elasticsearch / OpenSearch — the incumbent search engines, now with dense-vector support; where keyword search already lives. Reach for it when: you have an ES cluster and need hybrid retrieval without a new system. · Search (OSS) [AFFILIATE Elastic Cloud]
• MongoDB Atlas Vector Search — vector search inside Atlas, next to your operational data. Reach for it when: your data is already in Mongo. · Vector DB

Evals, observability & tracing (the "does it actually work" layer)

• LangSmith — LangChain's tracing/eval platform; the most common first observability tool. Reach for it when: you build on LangChain/LangGraph — the integration is free. · Evals/obs
• Langfuse — open-source LLM engineering platform: tracing, evals, prompt management; self-host or cloud. Reach for it when: you want observability you can own — the open default. · Evals/obs (OSS) [AFFILIATE cloud]
• Braintrust — eval-first platform for shipping AI products with regression-tested prompts. Reach for it when: evals are the center of your dev loop, not an afterthought. · Evals
• Arize Phoenix — open-source tracing and eval library from the ML-observability world. Reach for it when: OSS tracing with strong RAG-specific evals. · Evals/obs (OSS)
• W&B Weave — Weights & Biases' LLM tracing/eval layer. Reach for it when: your team already lives in W&B. · Evals/obs
• Helicone — proxy-based LLM observability — one base-URL change gives you logging, caching, and cost tracking. Reach for it when: you want cost visibility in five minutes. · Obs
• Promptfoo — open-source prompt testing and red-teaming from the CLI/CI. Reach for it when: prompt regression tests in CI, before anything reaches production. · Evals (OSS)

Gateways, routing & guardrails

• LiteLLM — open-source proxy that makes 100+ providers look like one OpenAI-compatible API, with keys, budgets, and fallbacks. Reach for it when: any team serving multiple models to multiple internal users — the standard self-hosted gateway. · Gateway (OSS)
• Portkey — managed AI gateway: routing, retries, guardrails, and cost controls as a service. Reach for it when: gateway-as-SaaS instead of running LiteLLM yourself. · Gateway
• Guardrails AI — open framework for validating LLM inputs/outputs against schemas and policies. Reach for it when: structured-output enforcement and policy checks in code. · Guardrails (OSS)
• NVIDIA NeMo Guardrails — open toolkit for conversational rails — topic bounds, jailbreak resistance, tool-use policies. Reach for it when: dialog systems that must stay on the rails. · Guardrails (OSS)
• Lakera — commercial prompt-injection and content-safety firewall API. Reach for it when: a production app faces untrusted user input and you want a managed shield. · Security

Automation platforms (agents for people who don't code)

• Zapier — the no-code automation incumbent, now with AI steps and agent features across thousands of app integrations. Reach for it when: wiring AI into business tools without engineering time. · Automation
• Make — visual automation with more control per dollar than Zapier. Reach for it when: complex branching flows on a budget. · Automation
• n8n — source-available, self-hostable automation with first-class AI/LangChain nodes. Reach for it when: you want your automations (and their data) on your own box. · Automation (source-available) [AFFILIATE cloud]

SHELF V — APPLICATION (where it meets the user)

What people actually subscribe to. The broadest shelf and the natural home of "best tool for X" listicles.

AI assistants (the front doors)

• ChatGPT — the product that started the consumer era; assistant, search, voice, agents, and an app ecosystem. Reach for it when: the general-purpose default; the one non-technical people already know. · Assistant
• Claude — Anthropic's assistant; Projects, Artifacts, and a reputation for long-document work and writing quality. Reach for it when: serious documents, code, and long-context work. · Assistant
• Google Gemini — Google's assistant, woven through Workspace, Android, and Search. Reach for it when: you live in Google's ecosystem — it's increasingly just there. · Assistant
• Perplexity — the AI answer engine: search that reads the web and cites its sources. Reach for it when: research questions where you want sources, not vibes. · Search assistant
• Poe — one subscription, many models — a multi-model chat aggregator by Quora. Reach for it when: comparing frontier models side-by-side on one bill. · Aggregator

• Microsoft Copilot — Microsoft's general-purpose AI assistant, built into Windows and Edge. Reach for it when: you are already in the Microsoft ecosystem and want an assistant that requires no extra setup. · Assistant
• Elicit — an AI research assistant that searches and synthesizes academic literature; extracts claims, methods, and findings from papers into structured tables. Reach for it when: you need to survey a research area and do not want to read 40 abstracts by hand. · Research
• Consensus — an answer engine that returns answers sourced and cited directly from peer-reviewed papers, not the open web. Reach for it when: you need a factual claim backed by published evidence, fast. · Research
• Semantic Scholar — a free scholarly search engine covering roughly 200 million papers, with AI-generated summaries and citation graphs. Reach for it when: you want deep literature coverage without a journal subscription or a paid tool. · Research · free
• Kagi — a paid, ad-free search engine with built-in AI answers and no ad-based ranking; revenue comes from subscribers. Reach for it when: you are tired of search results shaped by advertisers and want to pay for quality instead. · Search

Coding (the killer app — deepest affiliate shelf on the site)

• GitHub Copilot — the most-deployed AI coding tool; completions, chat, and agent mode inside your editor. Reach for it when: the safe enterprise default in VS Code/JetBrains. · Coding
• Cursor — the AI-first code editor (a VS Code fork); repo-aware chat, multi-file edits, background agents. Reach for it when: you want the editor itself built around AI, not a plugin bolted on. · Coding
• Claude Code — Anthropic's terminal/IDE coding agent — plans, edits across files, runs tests, ships. Reach for it when: agentic work on real codebases; the strongest pure-agent option. · Coding
• Windsurf — AI-native editor known for its agentic "Cascade" flow. Reach for it when: Cursor-style editing with a different agent personality and price point. · Coding
• Aider — open-source terminal pair-programmer that commits as it goes; bring your own API key. Reach for it when: CLI-native workflows with full control of model and cost. · Coding (OSS)
• Cline / Roo Code — open-source agentic coding extensions for VS Code, BYO-key. Reach for it when: agent coding inside VS Code without a subscription. · Coding (OSS)
• Replit — browser IDE where an agent builds and deploys whole apps from a prompt; hosting included. Reach for it when: idea-to-deployed-app with no local setup — the vibe-coding on-ramp. · Coding/platform
• v0 (Vercel) — prompt-to-UI generator that emits production React/Tailwind, deployable on Vercel. Reach for it when: frontend scaffolding and marketing pages at speed. · Coding/UI
• Lovable — prompt-to-full-stack-app builder aimed at non-engineers. Reach for it when: a founder needs a working product without hiring yet. · App builder
• Bolt.new — StackBlitz's in-browser AI app builder; prompt, run, deploy in one tab. Reach for it when: fast prototypes with the runtime right there in the browser. · App builder
• Tabnine — privacy-first completions that can run on-prem; trained to respect licensing. Reach for it when: enterprises whose counsel won't let code leave the building. · Coding
• JetBrains AI — AI assistant across the IntelliJ family. Reach for it when: your team lives in JetBrains IDEs. · Coding

Image generation

• Midjourney — the aesthetic benchmark of AI image generation; web editor and a famously opinionated look. Reach for it when: beauty is the deliverable — concept art, covers, mood. · Image
• FLUX (Black Forest Labs) — the strongest open-weight image family, from the original Stable Diffusion team; API and self-host. Reach for it when: open weights with near-frontier quality — control plus rights clarity. · Image (open + API)
• Stable Diffusion / Stability AI — the model line that made image generation open; the foundation of the entire local-image ecosystem. Reach for it when: the customization universe — LoRAs, ControlNet, fine-tunes. · Image (open)
• Ideogram — image model known for actually rendering legible text. Reach for it when: posters, logos, anything with words in it. · Image
• Leonardo AI — production-oriented image platform (Canva-owned) for game and marketing assets. Reach for it when: consistent asset pipelines, not one-off art. · Image
• Adobe Firefly — Adobe's commercially-safe image model inside Photoshop and Creative Cloud. Reach for it when: the legal department requires trained-on-licensed-content, or you live in Photoshop. · Image
• ComfyUI — the node-graph power tool for local image/video pipelines. Reach for it when: exact control over a generation pipeline, on your own GPU. · Image (OSS)

• Canva Magic Studio — Canva's integrated AI suite for generating images, writing copy, and remixing designs inside the workspace non-designers already use. Reach for it when: your team needs polished visuals and no one on it is a designer. · Design
• Figma AI — AI features built into Figma: generating first-draft layouts, filling content, and accelerating prototyping without leaving the design tool. Reach for it when: you are already designing in Figma and want AI to speed up the blank-canvas stage. · Design

Video generation

• Runway — the AI-video pioneer (Gen-4 line) with editor tooling aimed at filmmakers. Reach for it when: image-to-video and video editing workflows with production intent. · Video
• Google Veo — frontier text-to-video (with audio) via Gemini/Flow. Reach for it when: high realism and native soundtracks. · Video
• OpenAI Sora — OpenAI's video model and social-style app. Reach for it when: the ChatGPT-ecosystem video path. · Video
• Kling — Kuaishou's video model; strong motion quality, aggressive pricing tiers. Reach for it when: high volume image-to-video on a budget. · Video
• Pika / Luma / Hailuo (category) — the fast-moving second rank of video generators, each with a distinct look. Reach for it when: shopping styles per shot — this category churns monthly. · Video
• HeyGen — AI avatar video — talking presenters, dubbing, and translation. Reach for it when: training videos and localized talking-head content at scale. · Avatar video

• Synthesia — an AI video platform that generates talking-head avatar videos from a script, no camera or studio needed. Reach for it when: you need a professional training video or corporate explainer and a filmed production is not in the budget. · Video

Audio, voice & music

• ElevenLabs — the leading voice platform: TTS, cloning, dubbing, and conversational voice agents. Reach for it when: any production voice work — the quality bar the others chase. · Voice
• OpenAI Whisper — the open speech-to-text model that made transcription free. Reach for it when: transcription on your own hardware at zero marginal cost. · STT (OSS)
• AssemblyAI / Deepgram — production speech-to-text APIs with diarization, streaming, and audio intelligence. Reach for it when: transcription as a scaled product feature rather than a script. · STT
• Suno — text-to-song generation — full tracks with vocals. Reach for it when: jingles, demos, and scored content without a studio. · Music
• Udio — Suno's main rival; some listeners favor it for fidelity. Reach for it when: same job, different ear — try both. · Music
• Descript — edit audio/video by editing the transcript; overdub voices, remove filler words. Reach for it when: podcast and video post-production without a timeline editor. · Audio/video editing

Writing, meetings & work

• Notion AI — AI woven through the Notion workspace — writing, Q&A over your docs, meeting notes. Reach for it when: your team's knowledge already lives in Notion. · Productivity
• Grammarly — the incumbent writing assistant, now generative. Reach for it when: org-wide writing polish with admin controls. · Writing
• Jasper / Copy.ai (category) — marketing-content platforms with brand-voice controls. Reach for it when: marketing teams producing on-brand copy at volume. · Marketing
• Gamma — prompt-to-presentation; decks, docs, and sites from an outline. Reach for it when: a presentable deck in ten minutes. · Presentations
• Otter / Fireflies (category) — meeting transcription and AI notes that join your calls. Reach for it when: meetings should write themselves up. · Meetings
• Exa / Tavily (category) — search APIs built for AI agents — clean, structured web results for RAG and research loops. Reach for it when: your agent needs to search the web programmatically. · Search API

• Microsoft 365 Copilot — AI assistance woven across Word, Excel, PowerPoint, Outlook, and Teams for organizations on Microsoft 365. Reach for it when: your company is on M365 and you want AI where the work already happens, not in a separate tool. · Productivity
• NotebookLM — Google's research notebook that grounds every answer and audio overview in the specific sources you upload, not the open web. Reach for it when: you have a pile of documents and need to interrogate them without the model hallucinating outside them. · Research · free
• Slack AI — AI features native to Slack: thread summaries, channel recaps, and search over your workspace history. Reach for it when: your team runs on Slack and you need to catch up on a long thread without reading every message. · Productivity
• Julius AI — a conversational data analysis tool: upload a spreadsheet or connect a database, ask questions, and get charts and statistics back. Reach for it when: you have data to explore and writing SQL or Python is not how you want to spend the afternoon. · Data

SHELF VI — LEARN (the reference shelf)

*Everything above churns; understanding compounds. This shelf is where the compounding happens — and it

starts with our own textbook.*

• AI Principles (TheCatch.AI) — our open textbook: 6 parts, 34 chapters, plain English → math → runnable code, every mechanic bridged to its economics. Reach for it when: you want to understand the whole stack from a token upward — start here. · Internal · free
• Andrej Karpathy — Neural Networks: Zero to Hero — the best free deep-learning course on the internet; build GPT from scratch, by hand, on video. Reach for it when: you're ready to actually build one, not read about one. · Course · free
• 3Blue1Brown — Neural network series — the visual intuition for neural nets, gradient descent, and transformers; unmatched animation-driven teaching. Reach for it when: before anything else — 90 minutes that make everything after easier. · Video · free
• DeepLearning.AI — Andrew Ng's course platform; short courses on RAG, agents, fine-tuning, usually co-taught with the tool vendors. Reach for it when: a structured 1-3 hour on-ramp to a specific technique. · Courses [AFFILIATE via Coursera]
• fast.ai — Practical Deep Learning — the famous top-down free course: train real models first, theory later. Reach for it when: you learn by doing and want results in week one. · Course · free
• Hugging Face Learn — free hands-on courses (LLM, agents, deep RL) built around the HF ecosystem. Reach for it when: learning the open-source stack you'll actually use. · Courses · free
• Stanford CS224N / CS336 — the university courses on NLP and building LLMs, lectures free on YouTube. Reach for it when: academic depth with problem sets — the real thing. · Course · free
• "Build a Large Language Model (From Scratch)" — Sebastian Raschka — the book version of Karpathy's arc: a working LLM, line by line. Reach for it when: you want the from-scratch path in book form. · Book
• "AI Engineering" — Chip Huyen — the production side: evals, RAG, fine-tuning decisions, serving — the field manual for shipping AI. Reach for it when: your questions changed from "how does it work" to "how do I ship it." · Book
• The Illustrated Transformer — Jay Alammar — the single most-cited visual explainer of the transformer. Reach for it when: attention finally needs to click. · Article · free
• arXiv (cs.AI / cs.LG / cs.CL) — the preprint server where the frontier appears first, before press releases. Reach for it when: reading the source, not the coverage. · Papers · free
• Hugging Face Papers — daily-curated trending papers with community discussion — a practical successor to Papers with Code (which wound down in 2025). Reach for it when: keeping up with what practitioners are actually reading. · Papers · free
• Simon Willison's Weblog — the sharpest practitioner blog in the field; every model release tested within hours, honestly. Reach for it when: a new model drops and you want a trustworthy hands-on read. · Blog · free
• Latent Space — the AI-engineering podcast and newsletter of record. Reach for it when: hour-deep interviews with the people building the tools above. · Podcast · free
• Import AI (Jack Clark) / The Batch (DeepLearning.AI) — the two steadiest weekly digests: policy-aware and practitioner-plain respectively. Reach for it when: one email a week is your budget for keeping up. · Newsletter · free
• Interconnects (Nathan Lambert) — the best open analysis of model training, RLHF, and the open-vs-closed race. Reach for it when: you want to understand why labs make the choices they make. · Newsletter · free/paid
• Epoch AI — the research group measuring compute trends, training costs, and scaling data — the field's quantitative memory. Reach for it when: any hard number about compute growth or model scale; we cite them ourselves. · Research · free
• SemiAnalysis — Dylan Patel's semiconductor-and-datacenter research; the reference for the hardware layer's economics. Reach for it when: the Hardware and Infrastructure layers are your beat. · Research · free/paid
• O'Reilly Learning — the technical library subscription; every AI-engineering book above plus live courses. Reach for it when: your team expenses learning anyway. · Platform
• Khan Academy — free stats, probability, linear algebra, and calculus in short video units; the numeric literacy every model decision rests on. Reach for it when: your math is shaky and you want to close the gap before a course or book loses you. · Course · free
• The Python Tutorial (official) — the language's own tour, covering syntax to standard library with no assumptions. Reach for it when: you need to learn Python and want one authoritative source, not a patchwork of blog posts. · Docs · free
• NumPy Quickstart — the official guide to arrays, broadcasting, and vectorization; the substrate every ML library sits on. Reach for it when: you keep writing Python loops over data and suspect there is a faster way. · Docs · free
• Andrew Ng — Machine Learning Specialization (Coursera) — the canonical intro course; the clearest explanation of how gradient descent, regression, and classification actually work. Reach for it when: you want a mental model of learning algorithms before you touch a framework. · Course [AFFILIATE via Coursera]
• An Introduction to Statistical Learning (ISLR/ISLP) — the readable bridge from statistics to machine learning, with labs in R and Python; free PDF from the authors. Reach for it when: you want to understand why a model behaves the way it does, not just how to run it. · Book · free
• PyTorch Tutorials — the official tutorial sequence for the framework most research and production runs on; start at the 60-minute blitz. Reach for it when: you are ready to write training code and want to follow the path most engineers actually took. · Docs · free
• Anthropic Courses — structured courses on prompt engineering, tool use, and MCP from the team that builds Claude. Reach for it when: you want authoritative guidance on getting the most out of Claude specifically. · Course · free
• OpenAI Cookbook — copy-paste recipes for embeddings, function calling, structured output, and evals, maintained by the API team. Reach for it when: you know what you want to build but need a working code starting point. · Code · free
• Made With ML — an end-to-end production ML curriculum: design, testing, CI/CD, and serving, not just model training. Reach for it when: your model works in a notebook and you need to know what it takes to ship it. · Course · free
• OWASP Top 10 for LLMs — the canonical enumeration of LLM application security risks: prompt injection, insecure output handling, data leakage, and more. Reach for it when: you are about to ship an LLM-powered feature and want to know what you need to harden. · Reference · free
• NIST AI Risk Management Framework — the federal reference standard for identifying, measuring, and governing AI risk; the vocabulary your legal and compliance teams will eventually use. Reach for it when: a stakeholder asks how you are managing AI risk and you need a recognized framework to point to. · Reference · free
• LMArena — crowd-sourced human-preference rankings built from blind head-to-head model comparisons; the closest thing to a neutral scoreboard. Reach for it when: a new model is announced and you want to know where it actually ranks against the alternatives. · Leaderboard · free
• Artificial Analysis — independent benchmarks measuring model quality, speed, and price side by side across providers. Reach for it when: you are choosing between API providers and need apples-to-apples numbers, not vendor claims. · Leaderboard · free
• SWE-bench — the benchmark that evaluates coding agents on real GitHub issues from real open-source repositories. Reach for it when: someone claims their agent can code and you want to know what score that actually maps to. · Benchmark · free
• Stanford HAI — AI Index — the annual, heavily-cited report compiling the field's key statistics on research output, adoption, policy, and capability. Reach for it when: you need citable numbers about where AI is and how fast it is moving. · Report · free
• r/LocalLLaMA — the community of record for running open-weight models on your own hardware; dense with benchmarks, quantization guides, and early hands-on reports. Reach for it when: you want to run a model locally and need real-world setup experience, not documentation. · Community · free

"BEST OF" LISTICLE STUBS (three, ship-ready structure — expand to full pages later)

Listicle 1 — Best GPU cloud for fine-tuning (2026)

Intro (ship-ready): Fine-tuning is the workload that turns GPU-cloud marketing into arithmetic: you

need one to eight serious GPUs, for hours not months, with your data close and your checkpoints safe. You

don't need a hyperscaler contract, and you shouldn't pay hyperscaler prices. Here's the shortlist, ranked

by what a real fine-tune run costs and how much of your evening it eats. Prices move monthly — every number

below is checked at publish ``. Disclosure: some links pay us a commission;

the ranking is ours.

1. RunPod — the value default. Per-second billing, community-cloud pricing, and templates that boot straight into Axolotl/Unsloth. Where most solo fine-tunes should start.

2. Lambda — the quality default. Clean H100/B200 availability, sane networking, no marketplace roulette. When the run matters more than the last dollar.

3. Together AI — fine-tuning as a managed service — upload data, pick a base model, skip the cluster entirely. The "I don't want to see a GPU" option.

4. Vast.ai — the floor on price. Marketplace hardware, variable reliability — checkpoint often. For restartable jobs where cost per hour is everything.

5. Modal — fine-tuning as Python code with serverless scale-to-zero. Best when the fine-tune is one step in a pipeline you're building anyway.

6. CoreWeave — the scale answer. When "fine-tune" means multi-node and a procurement conversation, this is the neocloud with the muscle.

Honest closer: if you're LoRA-tuning a 7-8B model, a single rented consumer-class GPU on RunPod or

Vast with Unsloth will do it for pocket change — start there before renting an H100 you don't need.

Listicle 2 — Best vector DB for RAG (2026)

Intro (ship-ready): The vector database is the most over-shopped decision in RAG. The honest truth:

at under a few million vectors, nearly everything works, and your retrieval quality problems will come

from chunking and embeddings, not the store. So the ranking below optimizes for the thing that actually

differs: operational fit. Disclosure: some links pay us a commission; the ranking is ours.

1. pgvector — the correct first answer for most teams. It's Postgres — you already run it, back it up, and query it. Leave only when scale or latency forces you. (OSS, free)

2. Qdrant — the best self-host-first dedicated engine: fast, Rust-solid, great filtering, and a managed cloud when you tire of operating it. [AFFILIATE cloud]

3. Pinecone — the zero-ops choice. Serverless pricing, nothing to operate, scales without thought. You pay for that, and it's often worth it.

4. Weaviate — hybrid keyword+vector search out of the box — the right default when your queries include names, SKUs, and jargon that pure vectors fumble. [AFFILIATE cloud]

5. Chroma — the prototyping standard. Embedded, pip-installable, in every tutorial. Fine in production small; graduate when you need to. (OSS, free)

6. Milvus / Zilliz — the billion-vector answer. If your corpus has nine-plus digits of vectors, skip the list above and start here. [AFFILIATE cloud]

Honest closer: before switching databases to fix retrieval, add a reranker (Cohere or Voyage) — it's

an afternoon of work and usually a bigger quality jump than any storage migration.

Listicle 3 — Best AI coding assistant (2026)

Intro (ship-ready): "AI coding assistant" now spans three different products: autocomplete that

finishes your line, chat that answers questions about your repo, and agents that take a ticket and return

a diff. The right pick depends on which of those you're actually buying. Ranked below across all three

jobs, with the honest caveat that this category moves faster than any other on the site — we re-test

quarterly. Disclosure: some links pay us a commission; the ranking is ours.

1. Claude Code — the strongest agent. Terminal-native, plans multi-file work, runs your tests, and holds up on real codebases, not demos. If "assistant" means does the work, start here.

2. Cursor — the best AI-native editor experience. Repo-aware chat, fast multi-file edits, and the smoothest inner loop for hands-on-keyboard developers.

3. GitHub Copilot — the enterprise default, and a real bargain at the entry tier. In every editor, approved by every procurement department, better agent features every quarter.

4. Windsurf — the value AI editor. Cascade agent flow at an aggressive price; the strongest "try instead of Cursor" candidate.

5. Aider — the open-source pick. Terminal pair-programmer, BYO API key, git-native. Total cost control and no subscription. (OSS, free + API costs)

6. Replit — the no-setup pick. Agent builds and deploys whole apps in the browser — the right answer for prototypes and for people who don't want a local dev environment.

Honest closer: these are subscriptions with overlapping free tiers — run a two-week trial of your top

two on your own repo, not a toy. The differences show up in your codebase, not in benchmarks.