
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 hotelEvan 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 tradeableRather 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 that make it harder to run a neutral exchange. We also get into the unglamorous engineering: visiting sites, designing clusters, running the backplane, and making infrastructure programmable. Near the end, he describes the ability to subdivide InfiniBand fabric on the fly as one example.Guest: Evan Conrad, CEO of SF Compute. Show notes* Evan’s AI Engineer NYC talk: How Compute Markets Work* Our previous SF Compute conversation* Why oil futures went negative in 2020 — EIA* How SF Compute customers resell unused GPU capacity* SF Compute’s $245M compute sale* Abel: SF Compute’s settlement ledger* CFTC: Barclays and LIBOR manipulation* Elastic InfiniBand partitionsTimestamps* 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* <a tar
Podzilla Summary coming soon
Sign up to get notified when the full AI-powered summary is ready.
Free forever for up to 3 podcasts. No credit card required.

How Anthropic ships the #1 LLM in the World safely: Separating the Brain from the Hands

Supabase’s Plan for a Billion AI-Built Apps

⚡ An Eval for AI Scientists That Knows the Answer Key - Ian Quigley, Leash Bio

Why AI Compute Comes in Rectangles — Erik Bernhardsson, Modal CEO
Free AI-powered recaps of Latent Space: The AI Engineer Podcast and your other favorite podcasts, delivered to your inbox.
Free forever for up to 3 podcasts. No credit card required.