Build Production-Ready Agentic-RAG Applications From Scratch Course: What we are going to build
A newsletter announces a course starting September 27th that builds a production-ready agentic RAG application from scratch. The project takes a GitHub repository URL, crawls and indexes the files, then lets users chat with the code through a React frontend, FastAPI backend, and LangGraph orchestration, with Pinecone for storage. Sessions are live hands-on coding covering indexing, basic RAG, making it agentic, and horizontal scaling. Another promo for the same course.
Notes
Build Production-Ready Agentic-RAG Applications From Scratch — course announcement
Launch date: Saturday, September 27, 2025 (per source date). Fully hands-on, "live, hands-on coding session" per component, taught from scratch as on-the-job build.
The app: a web app that takes a GitHub repo URL, scrapes/indexes its files into a vector DB, then answers questions about that code.
Stack:
- React (frontend)
- FastAPI (backend)
- LangGraph (agentic orchestration)
- Pinecone (vector DB)
- Langsmith (observability)
- Deployed to Google Cloud (GCP)
Backend endpoints: (1) indexing endpoint — takes repo URL + "crawl" action to start crawl/index; (2) chat endpoint — responds to chatbot messages. Frontend has two pages: an indexing page (URL input + crawl trigger) and a chatbot page.
Course structure (project-based):
- Introduction — what we build, environment setup
- The RAG Application — data parsing pipeline → indexing pipeline → basic RAG pipeline → add Langsmith observability → going agentic
- The Backend Application — indexing API endpoint, adding memory, administering DB data
- The Frontend Application — indexing page, chatbot page
- Deploying to GCP
"Going agentic" definition (quoted): "we are going to use an LLM as a decision engine to enhance the quality of our pipeline." Deliberate trade-off: improves accuracy "at the cost of latency and cost," with discussion of offsetting those with small language models and fine-tuning. Three subagents, one per component: intent router (entry point, decides if RAG is needed), retriever (extracts the right data), generator (produces the response).
Scaling up: target is deploying to 1M users — all endpoints designed asynchronous, indexing requests queued, elastic load balancing for horizontal scaling.
Caveat/limitation stated: none given beyond the latency/cost trade-off; no pricing or prerequisites mentioned in the announcement.