"Why didn't you just use a hosted RAG service? Because the honest answer isn't 'building is better' — it's 'none of my constraints were on their list.'"
The Question That Deserves a Real Answer
Anyone looking at a hand-built corpus engine asks it immediately: there are dozens of hosted retrieval services, some excellent — why build? The self-flattering answers are available and all bad. "Building is always better." "I don't trust vendors." "It's more fun." None of those would survive a serious review, and none of them is why this engine exists. The real answer is duller and much stronger.
Renting Is Usually Right
Start by conceding the general case, because it's true: for most projects, most of the time, using a hosted retrieval service is the correct engineering decision. You get a maintained system, someone else's operational burden, and a working product in an afternoon. If your requirements are generic — index some docs, answer some questions — building your own is usually a slow way to arrive somewhere you could have started. A build decision that can't admit this isn't a decision; it's a preference wearing a justification.
The Honest Answer Is Constraint Mismatch
So the case for building has to be specific. Line up the actual constraints this engine had to honor: a private, lifelong corpus that is nobody else's business. No model in the retrieval path, so search works with the model server down. Fully offline determinism. Originals that stay untouched exactly where they live. Citations that must still resolve in ten years. An evidence layer holding judgments that no re-ingest can regenerate. Now ask which hosted service optimizes for that list. None — not because they're bad, but because they're built for generic hosted RAG, and not one of those constraints is on that list. That's not a knock on them; it's a mismatch.
The Decade Test
The durability half is what tips this one. A corpus of personal writing accumulates over decades — it will outlive most companies, most products, and certainly most pricing models. Rent your ability to find your own words and you've made your intellectual history dependent on someone else's continued interest in serving you: a deprecation, a price change, a shutdown, or a quiet policy shift and your archive is a hostage. For a system whose entire job is to still work in twenty years, ownership isn't ideology. It's the requirement.