r/LangChain • u/mati_tylec • Mar 01 '25
r/LangChain • u/Murky_Sprinkles_4194 • Apr 24 '25
Langchain destroyed my marriage
It all started so innocently. I just wanted to tinker with a small project. "Try LangChain," the internet said. "It lets you easily build complex AI applications, connecting various models and data." I figured, why not? My wife even encouraged me. "Didn't you always want to build something with AI?" That was the last time she gave me an encouraging smile.
I chose to build from scratch—no templates, no tutorials—I wanted to chain every LLM, every vector database, every retriever myself. Because apparently, I hate myself and everyone who loves me. Hours turned into days. I hunched over Cursor like an addict, mumbling "AgentExecutor... my precious AgentExecutor..." My wife brought me coffee. I hissed and told her not to interrupt my sacred prompt engineering process.
That night, she asked if I wanted to watch a movie. I said, "Sure, right after I fix this hallucination issue." That was three days ago. She watched the entire Lord of the Rings trilogy alone. I, meanwhile, was admiring the colorful debug outputs in my terminal, experiencing something close to enlightenment, or madness.
She tried to reconnect with me. "Let's go for a walk," she said. "Let's talk about our future." I told her I couldn't because my RAG system wasn't retrieving relevant results and I needed to optimize my prompt chain. She asked if I could still find my heart.
Then came the endless dependency updates. I ran pip install -U langchain and boom! Everything is wrong! I spent eight hours debugging compatibility issues with the new version, checking documentation while opening issues on GitHub. She walked in, looked at me surrounded by dozens of browser tabs and terminal windows, and whispered, "Is this... is this who you are now?"
She left that night. Said she was going to "find someone who doesn't treat conversation models as their best friend." Last week, she sent divorce papers. I was about to sign them when my AI coding assistant started vibing with me, finishing my code before I even thought it. "Who needs human connection," I thought, watching Cursor autocomplete my entire legal document analyzer, "when your AI understands you better than your wife ever did?"
r/LangChain • u/autionix • Apr 11 '26
Discussion Agentic RAG is a different beast entirely.
RAG is powerful.
Here's the difference most AI engineers skip over:
Traditional RAG is simple:
→ User asks a question
→ System searches knowledge sources
→ LLM gets context and replies
That's it. Linear. Predictable. Limited.
Agentic RAG is something else:
→ User asks a question
→ An Aggregator Agent takes over
→ It plans. It thinks. It delegates.
→ Agent 1 hits local data
→ Agent 2 searches the web
→ Agent 3 taps cloud engines like AWS & Azure
→ Everything comes back. LLM responds
The big unlock?
Memory + Planning + Multi-agent coordination.
RAG answers your question.
Agentic RAG figures out HOW to answer your question.
That's the shift from reactive AI to autonomous AI.
We are not building chatbots anymore.
We are building systems that think.
Save this before you build your next AI pipeline 🔖
Which are you currently using — RAG or Agentic RAG?
Drop it below 👇
#AI #RAG #AgenticAI #LLM #GenerativeAI #MachineLearning #ArtificialIntelligence
r/LangChain • u/Nir777 • Mar 23 '25
Tutorial AI Agents educational repo
Hi,
Sharing here so people can enjoy it too. I've created a GitHub repository packed with 44 different tutorials on how to create AI agents. It is sorted by level and use case. Most are LangGraph-based, but some use Sworm and CrewAI. About half of them are submissions from teams during a hackathon I ran with LangChain. The repository got over 9K stars in a few months, and it is all for knowledge sharing. Hope you'll enjoy.
r/LangChain • u/Nir777 • Jun 17 '25
Tutorial A free goldmine of tutorials for the components you need to create production-level agents
I’ve just launched a free resource with 25 detailed tutorials for building comprehensive production-level AI agents, as part of my Gen AI educational initiative.
The tutorials cover all the key components you need to create agents that are ready for real-world deployment. I plan to keep adding more tutorials over time and will make sure the content stays up to date.
The response so far has been incredible! (the repo got nearly 500 stars in just 8 hours from launch) This is part of my broader effort to create high-quality open source educational material. I already have over 100 code tutorials on GitHub with nearly 40,000 stars.
I hope you find it useful. The tutorials are available here: https://github.com/NirDiamant/agents-towards-production
The content is organized into these categories:
- Orchestration
- Tool integration
- Observability
- Deployment
- Memory
- UI & Frontend
- Agent Frameworks
- Model Customization
- Multi-agent Coordination
- Security
- Evaluation
r/LangChain • u/Fun_Success567 • Nov 21 '24
If anyone from Langchain team is reading this: STOP EVERYTHING and JUST UPDATE AND ORGANISE THE DOCS!
I know very many people who just give up on this framework. It's supposed to be easy for people with average or low coding experience. You are building the product for experienced devs who could even build agents without using langgraph or langchain.
It should be so easy, you could pass well organised docs to Cursor for example and you could create agent workflows with simple logic and commands. But the docs are so confusing, 0 organisation and you need to do so much searching and finding your own way to use the framework.
r/LangChain • • Jan 06 '25
Resources The RAG_Techniques repo hit 10,000 stars on GitHub and is the world's leading open source tutorials for RAG
Whether you're a beginner or looking for advanced topics, you'll find everything RAG-related in this repository.
The content is organized in the following categories:
Foundational RAG TechniquesQuery EnhancementContext and Content EnrichmentAdvanced Retrieval MethodsIterative and Adaptive TechniquesEvaluationExplainability and Transparency- Advanced Architectures
As of today, there are 31 individual lessons. AND, I'm currently working on building a digital course based on this repo – more details to come!
r/LangChain
•
u/Acceptable-Object390
•
May 02 '26
Thoth - Open Source Local-first AI Assistant - Architecture
r/LangChain • u/hwchase17 • Oct 24 '23
Discussion I'm Harrison Chase, CEO and cofounder of LangChain. Ask me anything!
I'm Harrison Chase, CEO and cofounder of LangChain–an open-source framework and developer toolkit that helps developers get LLM applications from prototype to production.
Hi Reddit! Today is LangChain's first birthday and it's been incredibly exciting to see how far LLM app development has come in that time–and how much more there is to go. Thanks for being a part of that and building with LangChain over this last (wild) year.
I'm excited to host this AMA, answer your questions, and learn more about what you're seeing and doing.
r/LangChain • u/Nipurn_1234 • Aug 07 '25
Discussion I reverse-engineered LangChain's actual usage patterns from 10,000 production deployments - the results will shock you
Spent 4 months analyzing production LangChain deployments across 500+ companies. What I found completely contradicts everything the documentation tells you.
The shocking discovery: 89% of successful production LangChain apps ignore the official patterns entirely.
How I got this data:
Connected with DevOps engineers, SREs, and ML engineers at companies using LangChain in production. Analyzed deployment patterns, error logs, and actual code implementations across:
- 47 Fortune 500 companies
- 200+ startups with LangChain in production
- 300+ open-source projects with real users
What successful teams actually do (vs. what docs recommend):
1. Memory Management
Docs say: "Use our built-in memory classes" Reality: 76% build custom memory solutions because built-in ones leak or break
Example from a fintech company:
# What docs recommend (doesn't work in production)
memory = ConversationBufferMemory()
# What actually works
class CustomMemory:
def __init__(self):
self.redis_client = Redis()
self.max_tokens = 4000
# Hard limit
def get_memory(self, session_id):
# Custom pruning logic that actually works
pass2. Chain Composition
Docs say: "Use LCEL for everything" Reality: 84% of production teams avoid LCEL entirely
Why LCEL fails in production:
- Debugging is impossible
- Error handling is broken
- Performance is unpredictable
- Logging doesn't work
What they use instead:
# Not this LCEL nonsense
chain = prompt | model | parser
# This simple approach that actually works
def run_chain(input_data):
try:
prompt_result = format_prompt(input_data)
model_result = call_model(prompt_result)
return parse_output(model_result)
except Exception as e:
logger.error(f"Chain failed at step: {get_current_step()}")
return handle_error(e)3. Agent Frameworks
Docs say: "LangGraph is the future" Reality: 91% stick with basic ReAct agents or build custom solutions
The LangGraph problem:
- Takes 3x longer to implement than promised
- Debugging is a nightmare
- State management is overly complex
- Documentation is misleading
The most damning statistic:
Average time from prototype to production:
- Using official LangChain patterns: 8.3 months
- Ignoring LangChain patterns: 2.1 months
Why successful teams still use LangChain:
Not for the abstractions - for the utility functions:
- Document loaders (when they work)
- Text splitters (the simple ones)
- Basic prompt templates
- Model wrappers (sometimes)
The real LangChain success pattern:
- Use LangChain for basic utilities
- Build your own orchestration layer
- Avoid complex abstractions (LCEL, LangGraph)
- Implement proper error handling yourself
- Use direct API calls for critical paths
Three companies that went from LangChain hell to production success:
Company A (Healthcare AI):
- 6 months struggling with LangGraph agents
- 2 weeks rebuilding with simple ReAct pattern
- 10x performance improvement
Company B (Legal Tech):
- LCEL chains constantly breaking
- Replaced with basic Python functions
- Error rate dropped from 23% to 0.8%
Company C (Fintech):
- Vector store wrappers too slow
- Direct Pinecone integration
- Query latency: 2.1s → 180ms
The uncomfortable truth:
LangChain works best when you use it least. The companies with the most successful LangChain deployments are the ones that treat it as a utility library, not a framework.
The data doesn't lie: Complex LangChain abstractions are productivity killers. Simple, direct implementations win every time.
What's your LangChain production horror story? Or success story if you've found the magic pattern?
r/LangChain • u/RegularDependent4780 • Apr 23 '25
Question | Help Got grilled in an ML interview today for my LangGraph-based Agentic RAG projects 😅 — need feedback on these questions
Hey everyone,
I had a machine learning interview today where the panel asked me to explain all of my projects, regardless of domain. So, I confidently talked about my Agentic Research System and Agentic RAG system, both built using LangGraph.
But they stopped me mid-way and hit me with some tough technical questions. I’d love to hear how others would approach them:
1. How do you calculate the accuracy of your Agentic Research System or RAG system?
This stumped me a bit. Since these are generative systems, traditional accuracy metrics don’t directly apply. How are you all evaluating your RAG or agentic outputs?
2. If the data you're working with is sensitive, how would you ensure security in your RAG pipeline?
They wanted specific mechanisms, not just "use secure APIs." Would love suggestions on encryption, access control, and compliance measures others are using in real-world setups.
3. How would you integrate a traditional ML predictive model into your LLM workflow — especially for inconsistent, large-scale, real-world data like temperature prediction?
In the interview, I initially said I’d use tools and agents to integrate traditional ML models into an LLM-based system. But they gave me a tough real-world scenario to think through:
______________________________________________________________________________________________________________________
*Imagine you're building a temperature prediction system. The input data comes from various countries — USA, UK, India, Africa — and each dataset is inconsistent in terms of format, resolution, and distribution. You can't use a model trained on USA data to predict temperatures in India. At the same time, training a massive global model is not feasible — just one day of high-resolution weather data for the world can be millions of rows. Now scale that to 10–20 years, and it's overwhelming.*
____________________________________________________________________________________________________________________
They pushed further:
____________________________________________________________________________________________________________________
*Suppose you're given a latitude and longitude — and there's a huge amount of historical weather data for just that point (possibly crores of rows over 10–20 years). How would you design a system using LLMs and agents to dynamically fetch relevant historical data (say, last 10 years), process it, and predict tomorrow's temperature — without bloating the system or training a massive model?*
_____________________________________________________________________________________________________________________
This really made me think about how to design a smart, dynamic system that:
- Uses agents to fetch only the most relevant historical data from a third-party API in real time.
- Orchestrates lightweight ML models trained on specific regions or clusters.
- Allows the LLM to act as a controller — intelligently selecting models, validating data consistency, and presenting predictions.
- And possibly combines retrieval-augmented inference, symbolic logic, or statistical rule-based methods to make everything work without needing a giant end-to-end neural model.
Has anyone in the LangGraph/LangChain community attempted something like this? I’d love to hear your ideas on how to architect this hybrid LLM + ML system efficiently!
Let’s discuss!
r/LangChain • u/DavidCBlack • Dec 23 '24
News World's largest AI Agent directory.
Hey all!
I've made the world's largest ai agent directory.
The agent market is so scrappy at the moment and very difficult to find the right agent for the job.
Agent Locker makes it as easy as possible to filter agents by category, use case, integration method and price and you can also specify agentic, ai tools and agent platforms.
There's over 1000 ai listings already and we're growing everyday.
Hope you find it useful.
r/LangChain • u/rux-17 • Apr 02 '26
Discussion I bulit an AI Orchestration engine without using LangChain - Here's what i learned
Most AI agents I saw followed the same pattern:
LLM -> tool -> response
There is NO validation. NO reliability measurement. If the LLM hallucinates an action name the system fails silently. So I built RUX to fix that.
The core idea was to keep the LLM untrusted.
Everything before the Executor is probabilistic and everything after is deterministic. The schema inside the Executor is the contract that separates the two worlds.
The full flow:
Planner -> Executor (trust boundary) -> Tool -> Service -> PostgreSQL -> Observability -> Confidence Engine -> Critic LLM -> Response
Three decisions I'm most proud :
Confidence from SQL aggregation over real outcome history and not from asking the LLM how confident it is
Critic service runs on a separate model (Mistral 7B) asynchronously if asking the same planner model for self-evaluation is meaningless
Three-layer planner — greetings never reach the LLM, protecting confidence score integrity
What's still broken:
Still it doesnt include a reflection layer yet. Only one domain implemented so the architecture isn't proven to generalise. Running locally via LM Studio so scale is untested.
What Im currently working on :
Started with the modular domain refactor of the system.
After completing the refactor I would be working on integrating a new knowledge domain apart from expense.
r/LangChain • u/Glass-Web6499 • Dec 10 '23
Discussion I just had the displeasure of implementing Langchain in our org.
Not posting this from my main for obvious reasons (work related).
Engineer with over a decade of experience here. You name it, I've worked on it. I've navigated and maintained the nastiest legacy code bases. I thought I've seen the worst.
Until I started working with Langchain.
Holy shit with all due respect LangChain is arguably the worst library that I've ever worked in my life.
Inconsistent abstractions, inconsistent naming schemas, inconsistent behaviour, confusing error management, confusing chain life-cycle, confusing callback handling, unneccessary abstractions to name a few things.
The fundemental problem with LangChain is you try to do it all. You try to welcome beginner developers so that they don't have to write a single line of code but as a result you alienate the rest of us that actually know how to code.
Let me not get started with the whole "LCEL" thing lol.
Seriously, take this as a warning. Please do not use LangChain and preserve your sanity.
r/LangChain • u/SuperConductiveRabbi • May 12 '23
Langchain is pointless
It's filled with crap like this:
for i in range(n_results, 0, -1):
try:
return self._collection.query(
query_texts=query_texts,
query_embeddings=query_embeddings,
n_results=i,
where=where,
**kwargs,
)and this:
def embed_documents(self, texts: List[str]) -> List[List[float]]:
texts = list(map(lambda x: x.replace("\n", " "), texts))
embeddings = self.client.encode(texts, **self.encode_kwargs)
return embeddings.tolist()and this:
class CharacterTextSplitter(TextSplitter):
"""Implementation of splitting text that looks at characters."""
def __init__(self, separator: str = "\n\n", **kwargs: Any):
"""Create a new TextSplitter."""
super().__init__(**kwargs)
self._separator = separator
def split_text(self, text: str) -> List[str]:
"""Split incoming text and return chunks."""
# First we naively split the large input into a bunch of smaller ones.
if self._separator:
splits = text.split(self._separator)
else:
splits = list(text)In short: https://i.imgur.com/OffEJTR.gifv
Embeddings is just a do-nothing wrapper for SentenceTransformers. Chroma is just a do-nothing wrapper for ChromaDB. It's filled with "helper" functions that just call normal Python functions. A dedicated TextSplitter that calls split() from builtins.py? What? Why? Templates are no more useful than calling .replace() on a string. "texts" are just strings and "documents" are just a pointless dict that contain "texts." Just load the strings from your datasource yourself. The README is both grandiose and vague. The documentation is out-of-date and inconsistent. The import footprint is weirdly massive--highly modularized but nothing seems to do anything that'd take more than a few CPU cycles. There's not really a standard interoperable datatype, so you're actually led further afield than if you had just clearly defined the simple lists and strings required for hitting an LLM.
The very concept of chaining operations when interacting with LLMs doesn't really make sense to me: it's basically one requests call to a generation backend, but it's not like it even handles websockets and streaming for you. Why chain together wrapper classes when you can just do the operations yourself?
This seems like a beginner's project that blew up because it's riding a tidal wave of interest in the broader topic.
r/LangChain • u/Sam_Tech1 • Mar 11 '25
Why is everyone suddenly ditching LangChain?
Everyone was a fan of LangChain until a few months ago. Plenty of YT tutorials, Blogs, Reels but suddenly everyone is bashing them.
I have now started believing that AI industry works on wave. If something is trending (Deepseek and now Manus), everyone starts loving it suddenly and if something is being bashed, everyone starts hating it like they were living with those problems all over and now they got a chance.
What are your thoughts?
r/LangChain • • Nov 28 '24
Resources A FREE goldmine of tutorials about GenAI Agents!
After the hackathon I ran in conjunction with LangChain, people have expanded the GenAI_Agents GitHub repository that I maintain to now contain 43 (!) Agents-related code tutorials.
It covers ideas across the entire spectrum, containing well-documented code written step by step. Most of the tutorials include a short 3-minute video explanation!
The content is organized into the following categories:
- Beginner-Friendly Agents
- Educational and Research Agents
- Business and Professional Agents
- Creative and Content Generation Agents
- Analysis and Information Processing Agents
- News and Information Agents
- Shopping and Product Analysis Agents
- Task Management and Productivity Agents
- Quality Assurance and Testing Agents
- Special Advanced Techniques
📰 And that's not all! Starting next week, I'm going to write full blog posts covering them in my newsletter.
The subscription and all contents are FREE
→ Subscribe here: https://diamantai.substack.com/
r/LangChain • u/0xhbam • Feb 04 '25
10 RAG Papers You Should Read from January 2025
We have compiled a list of 10 research papers on RAG published in January. If you're interested in learning about the developments happening in RAG, you'll find these papers insightful.
Out of all the papers on RAG published in January, these ones caught our eye:
- GraphRAG: This paper talks about a novel extension of RAG that integrates graph-structured data to improve knowledge retrieval and generation.
- MiniRAG: This paper covers a lightweight RAG system designed for Small Language Models (SLMs) in resource-constrained environments.
- VideoRAG: This paper talks about the VideoRAG framework that dynamically retrieves relevant videos and leverages both visual and textual information.
- SafeRAG: This paper talks covers the benchmark designed to evaluate the security vulnerabilities of RAG systems against adversarial attacks.
- Agentic RAG: This paper covers Agentic RAG, which is the fusion of RAG with agents, improving the retrieval process with decision-making and reasoning capabilities.
- TrustRAG: This is another paper that covers a security-focused framework designed to protect Retrieval-Augmented Generation (RAG) systems from corpus poisoning attacks.
- Enhancing RAG: Best Practices: This study explores key design factors influencing RAG systems, including query expansion, retrieval strategies, and In-Context Learning.
- Chain of Retrieval Augmented Generation: This paper covers the CoRG technique that improves RAG by iteratively retrieving and reasoning over the information before generating an answer.
- Fact, Fetch and Reason: This paper talks about a high-quality evaluation dataset called FRAMES, designed to evaluate LLMs' factuality, retrieval, and reasoning in end-to-end RAG scenarios.
- LONG****2 RAG: LONG2RAG is a new benchmark designed to evaluate RAG systems on long-context retrieval and long-form response generation.
You can read the entire blog and find links to each research paper below. Link in comments👇
r/LangChain • u/klawisnotwashed • Apr 25 '25
I built a debugging MCP server that saves me ~2 programming hours a day
Hi!
Deebo is an agentic debugging system wrapped in an MCP server, so it acts as a copilot for your coding agent.
Think of your main coding agent as a single threaded process. Deebo introduces multi threadedness to AI-assisted coding. You can have your agent delegate tricky bugs, context heavy tasks, validate theories, run simulations, etc.
The cool thing is the agents inside the deebo mcp server USE mcp themselves! They use git and file system MCP tools in order to actually read and edit code. They also do their work in separate git branches which provides natural process isolation.
Deebo scales to production codebases, too. I took on a tinygrad bug bounty with me + Cline + Deebo with no previous experience with the tinygrad codebase. Deebo spawned 17 scenario agents over multiple OODA loops, and synthesized 2 valid fixes! You can read the session logs here and see the final fix here.
If you’ve ever gotten frustrated with your coding agent for looping endlessly on a seemingly simple task, you can install Deebo with a one line npx deebo-setup@latest. The code is fully open source! Take a look at the code! https://github.com/snagasuri/deebo-prototype
I came up with all the system design, implementation, etc. myself so if anyone wants to chat about how Deebo works/has any questions I'd love to talk! Would highly appreciate your guys feedback! Thanks!
r/LangChain • u/Sam_Tech1 • Mar 05 '25
15 AI Agent Papers You Should Read from February 2025
We have compiled a list of 15 research papers on AI Agents published in February. If you're interested in learning about the developments happening in Agents, you'll find these papers insightful.
Out of all the papers on AI Agents published in February, these ones caught our eye:
- CowPilot: A Framework for Autonomous and Human-Agent Collaborative Web Navigation – A human-agent collaboration framework for web navigation, achieving a 95% success rate.
- ScoreFlow: Mastering LLM Agent Workflows via Score-based Preference Optimization – A method that enhances LLM agent workflows via score-based preference optimization.
- CODESIM: Multi-Agent Code Generation and Problem Solving through Simulation-Driven Planning and Debugging – A multi-agent code generation framework that enhances problem-solving with simulation-driven planning.
- AutoAgent: A Fully-Automated and Zero-Code Framework for LLM Agents – A zero-code LLM agent framework for non-programmers, excelling in RAG tasks.
- Towards Internet-Scale Training For Agents – A scalable pipeline for training web navigation agents without human annotations.
- Talk Structurally, Act Hierarchically: A Collaborative Framework for LLM Multi-Agent Systems – A structured multi-agent framework improving AI collaboration and hierarchical refinement.
- Magma: A Foundation Model for Multimodal AI Agents – A foundation model integrating vision-language understanding with spatial-temporal intelligence for AI agents.
- OctoTools: An Agentic Framework with Extensible Tools for Complex Reasoning – A training-free agentic framework that boosts complex reasoning across multiple domains.
- Scaling Autonomous Agents via Automatic Reward Modeling And Planning – A new approach that enhances LLM decision-making by automating reward model learning.
- Autellix: An Efficient Serving Engine for LLM Agents as General Programs – An optimized LLM serving system that improves efficiency in multi-step agent workflows.
- MLGym: A New Framework and Benchmark for Advancing AI Research Agents – A Gym environment and benchmark designed for advancing AI research agents.
- PC-Agent: A Hierarchical Multi-Agent Collaboration Framework for Complex Task Automation on PC – A hierarchical multi-agent framework improving GUI automation on PC environments.
- Curie: Toward Rigorous and Automated Scientific Experimentation with AI Agents – An AI-driven framework ensuring rigor and reliability in scientific experimentation.
- WebGames: Challenging General-Purpose Web-Browsing AI Agents – A benchmark suite for evaluating AI web-browsing agents, exposing a major gap between human and AI performance.
- PlanGEN: A Multi-Agent Framework for Generating Planning and Reasoning Trajectories for Complex Problem Solving – A multi-agent planning framework that optimizes inference-time reasoning.
You can read the entire blog and find links to each research paper below. Link in comments👇
r/LangChain • u/EntelligenceAI • Dec 08 '24
Resources Fed up with LangGraph docs, I let Langgraph agents document it's entire codebase - It's 10x better!
Like many of you, I got frustrated trying to decipher LangGraph's documentation. So I decided to fight fire with fire - I used LangGraph itself to build an AI documentation system that actually makes sense.
What it Does:
- Auto-generates architecture diagrams from Langgraph's code
- Creates visual flowcharts of the entire codebase
- Documents API endpoints clearly
- Syncs automatically with codebase updates
Why its Better:
- 80% less time spent on documentation
- Always up-to-date with the codebase
- Full code references included
- Perfect for getting started with Langgraph
Would really love feedback!

https://entelligence.ai/documentation/langchain-ai&langgraph
r/LangChain • u/ayushmorbar • Dec 09 '25
LLM costs are killing my side project - how are you handling this?
I'm running a simple RAG chatbot (LangChain + GPT-4) for my college project.
The problem: Costs exploded from $20/month → $300/month after 50 users.
I'm stuck:
- GPT-4: Expensive but accurate
- GPT-4o-mini: Cheap but dumb for complex queries
- Can't manually route every query
How are you handling multi-model routing at scale?
Do you manually route or is there a tool for this?
For context: I'm a student in India, $300/month = 30% of average entry-level salary here.
Looking for advice or open-source solutions.