The Programmable Data Center — Evan Conrad, SF Compute @LatentSpacePod
The Programmable Data Center — Evan Conrad, SF Compute  @LatentSpacePod
Uploaded October 2026 | Updated November 2026, 1 day ago
GPU compute is bought and sold like a commodity, but delivering it is a lot messier than trading a contract. Evan Conrad of SF Compute joins swyx at AI Engineer New York to explain the market they’re building—and why he thinks it needs an independent operator.

We cover:
• Why SF Compute had to build cloud operations to deliver the GPUs it trades
• How interruptions, storage and hardware generations affect compute prices
• Why batch and live inference need different contract terms
• Physical versus cash settlement, and the risk of trading a price disconnected from actual GPUs
• Why NVIDIA and the big clouds have different incentives from an independent market
• How to turn a data center into a programmable GPU cluster

Chapters:
0:00 Why can’t NVIDIA build this?
0:25 Welcome back to Latent Space
2:23 From selling a room to running the hotel
3:47 Physical settlement: actually delivering compute
6:00 Liquidity and the GPU order book
8:42 Trading nonstandard compute
10:00 Interrupting and moving workloads
12:20 Why hardware cohorts matter
14:32 How far out do compute contracts go?
16:19 Batch versus live inference leases
17:58 The shape of compute prices
20:33 GPU generations, specifications and SKUs
23:30 Physical versus cash settlement
27:00 The emerging compute market ecosystem
29:03 What it takes to deliver a GPU cluster
32:24 Sovereign compute
33:26 Why NVIDIA can’t build this market
34:48 A programmable data center

SF Compute: sfcompute.com
Latent Space: https://www.latent.space
Sponsorship and business inquiries: business@latent.space
The Programmable Data Center — Evan Conrad, SF ComputeHow We Mapped 125 Million Human Cells: The Story Behind the Human Cell AtlasThe AI Frontier: from Gemini 3 Deep Think distilling to Flash — Jeff DeanRepeating High Quality Data SetsFuture of Doctors AIs Role in HealthcareQuantum Observer Effect on Training Runs⚡️ The State of AI Engineer Hiring: Cheating, AI Adoption,Junior Devs — Vivek Ravisankar, HackerRankAIs Typo Dilemma⚡️ Googles Open AI Strategy — Omar Sanseviero, Google DeepMindClaude Code’s Bitter Lesson: Prompts, Harnesses, Mods, and Agents — Thariq Shihipar, AnthropicWhy AI Compute Comes in Rectangles — Erik Bernhardsson, Modal⚡️ OpenClaws Memory Sucks and the fix is simple — Dhravya Shah, Supermemory
Latent Space |

The Programmable Data Center — Evan Conrad, SF Compute

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER