Beyond NVIDIA: Mapping AI Infrastructure's True Spend Chain
The narrative around AI capital expenditure (capex) often feels monolithic: NVIDIA, hyperscalers, data centers, power demand—all bundled into a single "AI infrastructure" idea. As fellow developers, we know real-world

The narrative around AI capital expenditure (capex) often feels monolithic: NVIDIA, hyperscalers, data centers, power demand—all bundled into a single "AI infrastructure" idea. As fellow developers, we know real-world systems are rarely that simple. This simplification obscures where the significant investment in AI truly flows, missing crucial layers of the underlying spending chain.
Instead of a single idea, AI capex is a complex, multi-stage process. When a cloud provider decides to boost AI infrastructure spending, that money doesn't just materialize as usable compute. It traverses a chain: from chips and semiconductor equipment to servers, networking, data centers, and even further down to power systems, cooling, and construction. Understanding this chain is crucial for anyone trying to grasp the actual economic impact and technical demands of the AI boom.
Deconstructing the AI Infrastructure Trade
To move beyond the headlines, we need a granular view. Our goal here isn't to build a stock recommendation engine, but to analytically separate the AI infrastructure theme into its component layers. We'll examine how business fundamentals align with market recognition across this diverse landscape, revealing where the AI infrastructure trade is already making a tangible impact.
Our investigation begins by establishing a comprehensive AI capex universe. This universe is categorized into distinct layers, ensuring we capture the breadth of the spending chain. These layers include:
- Demand-side hyperscalers: The major cloud and AI infrastructure spenders.
- AI compute and chips: Core GPU and accelerator suppliers.
- Semiconductor equipment: Companies providing tools for advanced chip manufacturing.
- Servers and storage: Hardware providers for AI servers and data centers.
- Networking: Suppliers for data center networking and AI cluster buildouts.
- Data centers: Physical data center and interconnection infrastructure.
- Power and electrification: Electrical systems, power management, and grid infrastructure.
- Cooling and industrial systems: Thermal and climate control solutions essential for high-density AI compute.
- Construction and engineering: Firms involved in building and outfitting infrastructure.
This structured universe, initially drafted with AI assistance and then manually refined, serves as our map for tracing capital flow.
Building Our Analytical Framework
Once our universe is defined, the next step involves collecting empirical data to understand each company's performance and market standing. We leverage the EODHD API to pull two critical types of data:
-
Fundamentals Data: This provides insight into a company's business strength. Key metrics include quarterly revenue growth year-over-year, profit margin, operating margin, return on equity, and P/E ratios. We use a function like
get_fundamentalsto fetch this data:python def get_fundamentals(ticker): url = f'https://eodhd.com/api/fundamentals/{ticker}?api_token={api_key}&fmt=json' data = requests.get(url).json() return data
-
Historical Prices Data: This helps us gauge market recognition by analyzing stock performance. We retrieve one year of daily adjusted close prices to calculate metrics like 1-year, 6-month, and 3-month returns, 1-year volatility, and maximum drawdown. The
get_price_historyfunction facilitates this:python def get_price_history(ticker): price_start = date.today() - timedelta(days=365) price_end = date.today() url = f'https://eodhd.com/api/eod/{ticker}?api_token={api_key}&fmt=json&from={price_start.isoformat()}&to={price_end.isoformat()}&period=d' data = requests.get(url).json() prices = pd.DataFrame(data) if prices.empty: return pd.DataFrame()
... (data cleaning and sorting)
return prices[['date', 'adjusted_close']]
After gathering this raw data, we normalize selected metrics using a min-max scaling function. This ensures that diverse financial figures (e.g., revenue growth vs. profit margin) can be compared on a consistent 0-1 scale.
From these normalized metrics, we construct two composite signals:
- Fundamental Signal: A weighted average of normalized revenue growth, operating margin, profit margin, and return on equity. This signal indicates the underlying business strength and growth profile.
- Market Recognition Signal: A weighted average of normalized 1-year, 6-month, and 3-month returns, combined with the inverse of the maximum drawdown. This signal quantifies how much the market has already rewarded the company's stock.
Insights from the AI Capex Matrix
The most revealing part of this analysis is mapping companies onto an "AI Capex Matrix" where the x-axis represents Market Recognition and the y-axis represents Fundamental Signal. Companies are plotted as bubbles, with their size corresponding to market capitalization.
While NVIDIA predictably stands out as a fundamental outlier due to its extraordinary growth and margins, the broader picture is far more nuanced. Companies like AMD, Marvell, Vertiv, Comfort Systems, Dell, Lam Research, Applied Materials, and Quanta Services show strong market recognition. This mix includes not just chip-related and equipment companies, but crucially, also physical infrastructure names.
This observation signals a significant shift: the AI capex trade is extending beyond the well-known tech giants and into the foundational physical infrastructure required to build out AI capabilities. The market is not exclusively rewarding the developers of AI, but also the builders of its physical habitat.
Layer-by-Layer Performance
To further dissect this trend, we can examine the median 1-year return for each infrastructure layer. Surprisingly, the "Construction and Engineering" layer often ranks highly, closely followed by "Semiconductor Equipment" and "AI Compute and Chips." This contrasts sharply with the popular narrative that focuses almost solely on the top-tier chip and hyperscaler companies.
The strong performance of these underlying physical layers demonstrates that the demand from hyperscalers and chip manufacturers propagates throughout the entire supply chain. As AI models grow and data centers expand, the need for robust power, efficient cooling, and specialized construction becomes paramount, and the market has begun to reflect this reality.
Practical Takeaways
For developers and engineers working in or alongside the AI space, these insights are crucial. The AI infrastructure boom is far more distributed than commonly perceived. While the performance of AI models is captivating, the foundational physical infrastructure enabling them represents a massive, complex buildout. Understanding this intricate spending chain can inform career choices, project planning, and even strategic technology investments. The real trade isn't just in the chips; it's in the full stack from silicon to concrete.
FAQ
Q: Why is it important to separate "Fundamental Signal" from "Market Recognition Signal"?
A: Separating these signals helps distinguish between a company's underlying business health and growth (fundamentals) and how the stock market is currently valuing or reacting to it. A strong market recognition signal without robust fundamentals might indicate overvaluation, while strong fundamentals with low market recognition could suggest an overlooked opportunity, or simply that the market hasn't caught up yet.
Q: What is the significance of using adjusted_close for price calculations instead of close?
A: adjusted_close accounts for corporate actions such as stock splits, dividends, and other distributions. This provides a more accurate representation of the true value of an investment over time, making it essential for calculating reliable historical returns and drawdowns.
Q: How does the min_max_score function contribute to the analysis?
A: The min_max_score function normalizes diverse financial metrics into a consistent range, typically 0 to 1. This is crucial for combining metrics with different scales (e.g., revenue growth percentages vs. dollar-denominated profit margins) into a single, meaningful composite signal without any single metric disproportionately dominating the score.
Related articles
Build Your Own Local NMT App with React Native and QVAC
This article explores how Neural Machine Translation (NMT), powered by the Transformer architecture, revolutionized translation by understanding context. We then delve into QVAC, a local-first AI development platform, and its Bergamot engine, enabling private, on-device translation. Learn to set up a React Native app with QVAC and manage model lifecycles for efficient local translation.
ASML Low-NA EUV Pricing: Value Capture or Cost Burden
The Industry Reacts: ASML's EUV Pricing Shift Verdict: ASML’s strategic move to broaden its value-based pricing for Low-NA EUV tools, looking beyond mere wafer throughput, marks a significant shift in the semiconductor
Unpacking Roman Concrete's Durability: Carbonation and Self-Healing
The Enduring Legacy: Roman Concrete's Millennia-Long Stand As software developers, we're familiar with the ephemeral nature of technology; systems evolve, frameworks deprecate, and codebases undergo constant
PayPal in Microservices: NestJS, gRPC, and Docker Blueprint
Integrating payment logic directly into every microservice within a distributed system often leads to significant challenges. Scattering PayPal API calls across services like user-service, order-service, or
Wolverine's Latest Trailer: Lady Deathstrike Delivers a Brutal
Wolverine's Latest Trailer: Lady Deathstrike Delivers a Brutal Beatdown! Alright, True Believers, buckle up! We're now less than two months away from Marvel’s Wolverine slicing its way onto PlayStation 5, and Insomniac
Demystifying Dijkstra's Algorithm: The Shortest Path Pioneer
Explore Dijkstra's Algorithm, the foundational pathfinding technique conceived by Edsger W. Dijkstra. This guide explains how it solves shortest path problems using graphs, nodes, edges, and weights. Learn its greedy approach and the critical role of data structures like adjacency lists and priority queues in its efficient Python implementation.





