Reference: Mid-Scale RAG Over Internal Docs
referencerag-over-docs
model
Model
framework
Agent Framework
retrieval
Retrieval / Vector Store
eval
Eval
observability
Observability / Tracing
prompt_management
Prompt Management
deployment
Deployment Target
mcp_servers
MCP Servers
guardrails
Guardrails / Safety
Architectural notes
Reference architecture for an internal "ask the docs" agent over Notion, GitHub READMEs, and a docs site. Why these picks: - Mastra for orchestration because the team is already TypeScript-first. - turbopuffer for hybrid (vector + BM25) search over ~100k chunks. - Voyage embeddings over OpenAI for retrieval quality at this scale. - Langfuse for self-hosted observability where doc content is sensitive. - Braintrust for golden-question eval gated in CI. Common gotchas: - Chunking strategy dominates retrieval quality more than embedding choice. - Notion MCP can return inconsistent results when pages are reorganized.
Embed this stack
Show off your stack on your engineering blog or company page.
<iframe src="http://testserver/embed/stacks/rag-over-docs-midscale" width="100%" height="380" frameborder="0" style="border: 1px solid #334155; border-radius: 8px;"></iframe>