Elizabeth Hayes

𝗠𝗼𝘀𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝘁𝗵𝗶𝗻𝗸 𝗔𝗜 = 𝗖𝗵𝗮𝘁𝗚𝗣𝗧. Not even close. ChatGPT is what you see. The real AI revolution is the massive ecosystem being built underneath it. This AI Stack Map captures 100+ tools powering modern AI applications. 𝗧𝗵𝗲 𝗺𝗼𝗱𝗲𝗿𝗻 𝗔𝗜 𝘀𝘁𝗮𝗰𝗸 𝗹𝗼𝗼𝗸𝘀 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗹𝗶𝗸𝗲 𝘁𝗵𝗶𝘀: LLMs → OpenAI, Claude, Gemini, Llama, Mistral Agentic AI → LangGraph, CrewAI, AutoGen, CAMEL, Agno RAG → LangChain, LlamaIndex, Haystack, GraphRAG Embeddings → OpenAI, Voyage, Cohere, BGE MCP → Connecting models with tools, data and systems AI Security → Guardrails, Presidio, Lakera, Prompt Security Observability & Evals → LangSmith, Langfuse, Phoenix, Ragas Memory → Redis, Mem0, Zep, Neo4j, Chroma Agent Frameworks → OpenAI SDK, Semantic Kernel, Google ADK, Bedrock Automation → n8n, Zapier, Make, Airflow, Prefect Vector Databases → Pinecone, Weaviate, Qdrant, Milvus, pgvector But here’s the part that matters more than the logos. 𝗧𝗵𝗶𝘀 𝗶𝘀 𝗻𝗼𝘁 𝗮 𝘀𝗵𝗼𝗽𝗽𝗶𝗻𝗴 𝗹𝗶𝘀𝘁. It’s a dependency graph. Your RAG is only as good as your retrieval + embeddings. Your agent is only as reliable as its tools + evaluations + guardrails. Your memory is useless if you can’t observe when context becomes stale or wrong. Your MCP layer becomes dangerous if permissions and governance are an afterthought. And a “best-in-class” stack can still become a terrible production system. Why? Because AI systems rarely fail only inside one component. 𝗧𝗵𝗲𝘆 𝗳𝗮𝗶𝗹 𝗮𝘁 𝘁𝗵𝗲 𝗵𝗮𝗻𝗱𝗼𝗳𝗳𝘀. Model → Retrieval Retrieval → Context Context → Agent Agent → Tool Tool → Memory Memory → Evaluation That’s where latency compounds, context gets lost, permissions leak, hallucinations propagate and reliability starts falling apart. 𝗧𝗵𝗲 𝗿𝗲𝗮𝗹 𝗺𝗼𝗮𝘁 𝗶𝘀𝗻’𝘁 𝗵𝗮𝘃𝗶𝗻𝗴 𝗺𝗼𝗿𝗲 𝗔𝗜 𝘁𝗼𝗼𝗹𝘀. It’s designing how they work together. A stack map tells you 𝗪𝗛𝗔𝗧 exists. Production engineering decides 𝗛𝗢𝗪 it all survives contact with reality. Which tool in your AI stack has become indispensable? Save this map for your next AI build. Repost it for someone designing an AI architecture. #AI #ArtificialIntelligence #GenAI