MCP standardized how an agent calls a tool. It said almost nothing about how the agent logs in as you — and that gap is the whole product these three are selling.
The real divide in open-source RAG isn't which library to import — it's whether to build with one at all, or deploy a finished engine. Three engines, three very different bets.
GRPO is now a commodity all three ship. The thing that actually sorts them is who owns the distributed orchestration — and how you keep one starving inference engine fed.
Three ways to serve embeddings at scale that look like rivals but answer a different question: should embeddings be a dedicated specialist, or ride on the GPU already running your LLM?
The new realtime models hear and speak in one step, no text in the middle. That deletes the seam where you used to read, log, and control everything. Here's the real trade.
The frameworks that get the most attention disagree on something basic — what an agent's action even is. One writes code, one wires a graph, one casts a team.
The listicle treats these as three flavors of the same choice. They aren't — two are ends of one axis, and the third sits on a different axis entirely. Pick by your environment, not your vibe.
The benchmark you compare on today expires in three weeks. The license you build on doesn't. Pick an open-weight family the way it will still matter next quarter — by what you're allowed to do with it, and what it costs to serve.
Forcing a model to emit valid JSON is a solved problem. Doing it without slowing generation to a crawl is the one that produced three new engines — and your serving stack probably already picked one for you.
Three self-hosted chat UIs that look interchangeable on a feature checklist — but each one is really built for a different person, and picking the wrong one means fighting the grain forever.
An MoE model computes like a small model and remembers like a giant one. That split is great for a token factory and a trap for a single self-hosted agent.
One agent, twenty MCP servers, and a context window drowning in tool definitions. The gateway is the layer that puts a single governed door in front of all of them.
Three open tools for making synthetic fine-tuning data. The model that generates it stopped being the hard part — the part that decides whether your dataset helps or quietly poisons your model is what happens after.
The four tools map to four architectural postures — and in a year when the companies keep getting acquired out from under their users, the posture is what you're actually choosing.
Two ways to build an agent that drives software: send it screenshots and let it move the cursor, or hand it the page's structure and let it act on elements. The split isn't old vs new — it's general vs reliable.
Three repos for retrieving over PDFs as images instead of parsed text — and why the real choice between them is who owns the multi-vector storage problem, not who has the best model.
They get pitched as competitors. They're not even the same kind of thing — and the difference that actually decides your architecture is what each one costs you in tokens.
They aren't ranked by capability. They differ on where the agent runs and who holds the steering wheel — and that decides your blast radius, not your benchmark score.
Three engines, one job: turn a model into a high-throughput endpoint. The feature gaps are closing — what's left is portability, vendor lock-in, and which project is still being built.
Speculative decoding makes a single LLM response 2–6x faster without changing a token of the output. The reason it works — and why the newest method wins — is a fact about your GPU, not your model.
Three open-source tools promise to catch prompt injection before it reaches your agent. Their GitHub status pages tell you more about whether detection works than any benchmark does.
Three ways to scrub names, card numbers, and patient IDs out of a prompt before it reaches a model provider. The hard part isn't detection — it's whether you can ever put the data back.
They get listed as three competing ways to do vector search in Postgres. They are not competitors — they are three rungs of one ladder, and one rung just fell off.
A new wave of vision-model OCR turns PDFs into clean Markdown. For RAG the leaderboard everyone quotes measures the wrong thing — and is published by the people who make the tools.
Once you've fine-tuned a model, you need a GPU to serve it from. The four serverless platforms developers reach for disagree about one thing that follows you for years — the format you package the model in.
Three popular repos all build a knowledge graph for your LLM. They were built for three different jobs, and the one axis that decides between them is whether your corpus sits still.
Teams pick a multimodal embedder by its ImageNet zero-shot score. For retrieval that is the wrong number — and chasing it lands you with two models and two indexes instead of one.
Three ways to put a model behind an endpoint — and they increasingly run the same engine underneath, so the thing you are actually choosing is not speed.