# Data Centers in Orbit by 2028: Baiju Bhatt on His Plans After Robinhood

Page: https://stenobird.com/podcast/grit-606871/data-centers-in-orbit-by-2028-baiju-bhatt-on-his-plans-after-robinhood
Text version: https://stenobird.com/podcast/grit-606871/data-centers-in-orbit-by-2028-baiju-bhatt-on-his-plans-after-robinhood.md
Podcast: [Grit](https://stenobird.com/podcast/grit-606871)
Published: 2026-08-24T09:36:51+00:00
Episode link: https://share.transistor.fm/s/faa70d58
Audio file: https://media.transistor.fm/faa70d58/f12ca533.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/grit-606871/episodes/data-centers-in-orbit-by-2028-baiju-bhatt-on-his-plans-after-robinhood
Duration seconds: 4374

## Resource

What kind of founder walks away from a multi-billion-dollar fintech company to start building rockets? Baiju Bhatt, co-founder of Robinhood, joins Joubin Mirzadegan to talk about life after one of the most consequential companies in modern finance, and why he's now betting on Cowboy Space Corporation, an orbital infrastructure company building AI data centers that ride to space inside its own rockets. "I still have that dog in me," he says. Baiju opens up about building alone for the first time in 15 years and what he learned about product-market fit while scaling Robinhood through its most chaotic years. Connect with Baiju: X LinkedIn Connect with Joubin: X LinkedIn ​ Email: grit@kleinerperkins.com Follow Grit on LinkedIn X ​Learn more about Kleiner Perkins

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/grit-606871/episodes/data-centers-in-orbit-by-2028-baiju-bhatt-on-his-plans-after-robinhood/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/grit-606871/data-centers-in-orbit-by-2028-baiju-bhatt-on-his-plans-after-robinhood.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.