The Programmable Data Center — Evan Conrad, SF Compute
October 20, 2026
AI Summary
5 min readThe Programmable Data Center — Evan Conrad, SF Compute
Evan Conrad started SF Compute (originally called June Arc) by trying to sublease a single GPU cluster. The experience was like running a hotel: a customer asks for a room, then wants it cleaned, then wants room service, then security. Eventually you're running the whole hotel. That's what happened to SF Compute over the last several years — they built the entire operating capacity of a cloud in order to reliably deliver compute. Conrad calls this "physical settlement," borrowing a term from futures markets. In oil, physical settlement means you get delivered the actual barrels. In compute, it means you get delivered working GPUs with all the infrastructure around them. The company now handles everything from supply chain consulting and cluster architecture to backplane management and site visits — without owning the hardware themselves.
The State of Compute Markets
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of Latent Space: The AI Engineer Podcast
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 Timestamped Outline: The Programmable Data Center — Evan Conrad, SF Compute
- 2 (00:00) **NVIDIA's Role** - Why NVIDIA didn't build SF Compute and why it benefits from the market existing
- 3 (00:27) **Welcome and Context** - Evan Conrad returns to discuss compute trading markets
- 4 (02:14) **SF Compute Status Update** - From subleasing clusters to full physical settlement operations
- 5 (03:49) **Physical Settlement Explained** - Borrowing the term from futures markets
- 6 (05:46) **Market Maturity and Liquidity** - Current state of compute market depth
- 7 (07:11) **Contract Standardization** - Progress on standardizing compute contracts
+ Full timestamped outline available in the app
Guests on this episode
Show Notes
This was recorded on the sidelines of the new Compute Trading track at AIE NYC. Catch us next at AIE CODE, our last flagship for the top agentic engineers in the world.
In the early days of cloud, former guest Martin Casado made something so disruptive that Cisco was threatened enough to pay $600m for it, and VMware outbid for $1.3B:
That concept was software-defined networking, which virtualized the routing network by separating the control plane from the data plane. That revolution is now coming for GPUs - where previously running your own supercompute cluster required $50-100m upfront to get commitments and do the entire stack from hardware to firmware to kernels, SF Compute is now enabling you to not only buy or sell GPU hours now and in the future, but also to programmatically control everything from your network to memory.
We last spoke with Evan about commoditizing compute. At AI Engineer New York, we went deeper: what does it take to physically deliver a GPU contract, and what has to be true before a market in compute can become liquid?
From selling a room to running the hotel
Evan describes SF Compute’s expansion with a hotel analogy. A customer wants a room, then asks for cleaning, room service, and security. Eventually you discover that delivering the room means operating the hotel. SF Compute began by trying to sublease a cluster; the company has since built much of the operating capacity of a cloud to deliver the compute traded on its market.
That work is physical settlement: the buyer gets usable compute, rather than simply a cash payment against an index. It brings the physical constraints of a cluster into the market itself. Can a workload be interrupted? How quickly can it recover from storage? Which GPU generation, networking and software configuration does it need? Those details affect both the contract and the price.
Making compute tradeable
Rather than waiting for every GPU cluster to become interchangeable, SF Compute matches orders with different constraints. Evan argues that this makes trading possible while the technology changes, at the cost of spreading liquidity across more variants. We also discuss spot and forward pricing, batch versus live inference, and why an index can become disconnected from the cost of actually buying compute.
Independence is central to Evan’s case for a market operator. He argues that companies with large hardware or inference businesses have incentives tha