An LLM-powered chip design assistant that uses GraphRAG — knowledge graphs combined with vector retrieval — to answer technical EDA questions. Originally budgeted at $2,685/month, deployed for $240 total. Here's how.
EDA Copilot is a domain-specific technical assistant for chip design engineers. It ingests PDK documentation, timing reports, tool manuals, and community Q&A into a hybrid retrieval system — a Neo4j knowledge graph for structural relationships (tool → version → known bug) combined with a ChromaDB vector store for semantic search across 847 curated corpus chunks. When an engineer asks a question like "Why does my timing fail after upgrading OpenROAD?" or "What is the metal2 spacing rule in SKY130?", the system retrieves graph facts and text chunks, reranks them with a cross-encoder, and streams a grounded answer via Claude Sonnet with inline citations. The full stack — FastAPI backend, SSE streaming, rate limiting, query logging — runs on a single $12/month VPS.
Nine cost levers were stacked to collapse the budget from $2,685 to $240 — each one independently justified and empirically validated:
The complete cost optimization paper covers methodology, per-technique breakdowns, quality benchmarks (EDABench: 72.2% accuracy), and scaling projections.