Webinar-Lottie.svg

lakeFS Acquires DVC, Uniting Data Version Control Pioneers to Accelerate AI-Ready Data

webcros.svg
Webinar: The Adoption Playbook for AI-Ready Data

Introducing the Periodic Table of Agent Infrastructure

John NoonanJohn Noonan
Last updated on July 16, 2026

Table of Contents

Watch how lakeFS works!

In 1869, chemistry was a growing field, with a growing problem: 63 known elements and no organizing system that worked. Dmitri Mendeleev solved it by inventing the periodic table, which brought order to a field that had outgrown anyone’s ability to track it.

Agentic AI is at its 1869 moment, though our challenge is even more daunting due to the breakneck speed things are evolving. Agents went from demo to production in about a year, and the infrastructure scene exploded behind them. Sandboxes, harnesses, memory layers, gateways, catalogs, eval platforms. Hundreds of vendors, dozens of overlapping claims, and no shared structure for any of it.

So we built the structure. Today we’re launching the Periodic Table of Agent Infrastructure: 118 technologies, 15 categories, one map of the agent infrastructure stack.

What is the agent infrastructure stack?

The agent infrastructure stack is the set of layers that sit between a model and a working production agent. The sandboxes, memory, gateways, catalogs, eval platforms, and other building blocks that let agents keep state, recover from failure, control costs, and touch enterprise data safely. The Periodic Table of Agent Infrastructure maps this stack across 15 categories.

What is the Periodic Table of Agent Infrastructure?

The Periodic Table of Agent Infrastructure

An interactive table at periodic-table.ai. Every category is clickable and every tool has a plain-language description of what it does and where it fits. Scan the whole landscape in two minutes or go deep on the one category you’re evaluating right now.

The Periodic Table of Agent Infrastructure

A detailed report with our take on the industry: why this stack exists, what each of the 15 categories actually does, the key technologies in each, what differentiates each technology, and finally, which layers we think survive as models absorb more of the stack natively.

Why we built it

Anyone can converse with a chatbot or call a model API. However, running agents in production is another story. They have to keep state across long sessions, recover from failures, control costs, and touch enterprise data without breaking anything. Each of those problems has spawned its own set of vendors, and the result is a market that’s genuinely hard to navigate. Category names overlap, products span multiple layers, and every vendor describes the stack with themselves at the center.

We kept running into this in our own conversations with AI and data platform teams. So we built the reference we wished existed: one neutral frame that shows every layer of the stack, what each one is for, and who plays where.

Who it’s for

Engineers building agents get a fast way to orient: what category solves your problem, what the real options are, and how they differ.

Platform and data teams get a stack audit tool. Fifteen categories, one pass, and you know exactly which layers you’ve covered and which ones you’ve been quietly assuming someone else owns.

Leaders making build-vs-buy calls get a shared vocabulary. For instance, when “memory” means one thing to the product manager and another to the engineer wiring a vector store, fixed category definitions get everyone arguing about the same thing.

And anyone trying to keep up gets a quick, easy-to-understand glimpse of an AI landscape that changes by the week. No jargon decoder required.

How we put it together

lakeFS created the table based on expert interviews and secondary market research. It’s a quick reference to the building blocks from which modern agentic systems are assembled. It includes the most relevant example technologies in each category. It is not exhaustive, and it isn’t meant to be. Our goal is that it is useful.

One more thing: this space moves exceptionally fast, so the table will move with it. Expect frequent updates as categories shift, tools merge, and new building blocks emerge. Mendeleev left gaps in his table for elements not yet discovered. We’re planning for the same flexibility, while keeping it manageable with the self-imposed limit of 118 elements.

Where is it all going?

Want to know where we think the agentic stack is heading? Head to periodic-table.ai to explore the interactive table and download the full report.

Frequently Asked Questions

It’s an interactive map of the technologies behind production agentic systems, 118 tools organized into 15 categories, created by lakeFS. Each category is clickable and each tool has a plain-language description of what it does and where it fits in the stack.

Agent infrastructure is the set of layers between a model and a working production agent: sandboxes, memory, gateways, catalogs, eval platforms, and more. These building blocks let agents keep state, recover from failure, control costs, and access enterprise data safely.

The Periodic Table organizes the stack into 15 categories

  • Compute and Infrastructure: the GPU vendors and clouds that run the models, spanning hyperscalers, neoclouds, and on-demand marketplaces.
  • Foundation Models: the reasoning engine of an agent, deciding what to do next, when to use tools, and how to interpret results.
  • Coding Agents: commercial, vendor-managed products for software development, where model, tools, and agent logic ship bundled together.
  • Agent Harnesses: open-source systems you run yourself that wrap a raw model with tool access, memory, and control flow.
  • Agent Frameworks: developer libraries for building agents from scratch, providing primitives for orchestration, state, and multi-agent coordination.
  • Workflow and Orchestration: the deterministic layer that connects agents to the rest of the stack and keeps long-running processes reliable.
  • Agent Sandboxes: isolated environments (compute and data) where agents can execute code and touch data without risking production.
  • Memory Management: systems that give agents continuity over time, storing what happened, what was decided, and what context matters later.
  • Data Connectors and Tool Integrations: the bridge between an agent and external apps, APIs, and business systems where work actually happens.
  • Data Storage: where an agent’s information physically lives: object stores, relational and vector databases, caches, and versioned data layers.
  • Data Query and Analytics Engines: the compute-over-data layer agents delegate to for scanning, joining, and analyzing more than fits in context.
  • Metadata Management and Data Catalogs: the layer defining what data exists, what it means, where it lives, and whether an agent should use it.
  • AI Gateways and Cost Control: the layer between agents and model providers that routes requests, enforces budgets, and handles failover.
  • Observability and Evaluation: tracing what an agent did step by step, then judging whether those actions were correct or useful.
  • Governance and Compliance: the guardrails, security controls, and audit trail that keep agents within organizational and regulatory limits.

The table currently includes 118 technologies across 15 categories. The limit of 118 is deliberate, mirroring the number of elements in the chemical periodic table.

The tools included are:

  • Compute and Infrastructure: NVIDIA, AWS, Azure, Google Cloud, CoreWeave, Lambda Labs, Red Hat, Nebius, RunPod, Crusoe, Nscale
  • Foundation Models: OpenAI (ChatGPT), Anthropic (Claude), Google (Gemini), xAI (Grok), Meta (Llama), DeepSeek, Mistral, Alibaba (Qwen)
  • Coding Agents: Antigravity, Augment, Claude Code, Codex, Cursor, Copilot, Devin, TRAE
  • Agent Harnesses: Aider, Cline, Goose, NanoClaw, OpenClaw, OpenCode
  • Agent Frameworks: Anthropic Claude Agent SDK, CrewAI, Google ADK, LangGraph, LlamaIndex, Microsoft Agent Framework, OpenAI Agents SDK, PydanticAI
  • Workflow and Orchestration: Airflow, n8n, Dagster, Prefect, Inngest, Restate, Seqera (NextFlow), Temporal, Zapier
  • Agent Sandboxes: Browserbase, E2B, Fly.io, lakeFS, Cloudflare Sandbox, Daytona, Modal
  • Memory Management: Cognee, Letta, Mem0, Zep
  • Data Connectors and Tool Integrations:</strong> Anthropic Connectors, MCP, Arcade, OpenAI Connectors, Composio, Stagehand
  • Data Storage: Amazon S3, Azure Blob Storage, Cloudian, Dell ObjectScale, Google Cloud Storage, lakeFS, Milvus, MinIO, NetApp, Pinecone, MongoDB, PostgreSQL, Neo4j, Redis, Seagate, VAST, SQLite, WEKA
  • Data Query and Analytics Engines: BigQuery, DuckDB, ClickHouse, Elasticsearch, Databricks, lakeFS, Snowflake
  • Metadata Management and Data Catalogs: Alation, Atlan, AWS Glue Data Catalog, Collibra, Apache Gravitino, lakeFS, Apache Polaris, Databricks Unity Catalog
  • AI Gateways and Cost Control: Cloudflare AI Gateway, OpenRouter, Kong AI Gateway, Portkey, LiteLLM
  • Observability and Evaluation: Arize Phoenix, Laminar, Braintrust, Langfuse, lakeFS, LangSmith, Patronus AI, W&B Weave
  • Governance and Compliance: Credo AI, Guardrails AI, lakeFS, Lakera, Robust Intelligence

Engineers building agents, platform and data teams auditing their stack, and leaders making build-vs-buy calls, plus anyone trying to keep up with a landscape that changes weekly.

Frequently. The space moves fast, so the table is updated as categories shift, tools merge, and new building blocks emerge, with gaps left for what hasn’t arrived yet.

We use cookies to improve your experience and understand how our site is used.

Learn more in our Privacy Policy