Why Stripe Puts AI Agents in Isolated Cloud Sandboxes
Stripe engineering manager Sharadh Krishnamurthy explains why AI agents threaten core infrastructure and how sandboxes prevent total outages.
40 hours of podcasts, in 5 minutes.
Sharadh Krishnamurthy, engineering manager at Stripe, joins Claire Vo to break down Kai, Stripe's internal AI agent used by over 10,000 employees weekly. He explains why Stripe decided to build rather than buy their company agent, how pre-existing developer and data infrastructure enabled rapid enterprise deployment, and how they use project-level governance, secure cloud sandboxes, and a self-serve skills platform to scale AI safely across both technical and non-technical teams.
Stripe engineering manager Sharadh Krishnamurthy explains why AI agents threaten core infrastructure and how sandboxes prevent total outages.
Stripe scaled Kai to 10,000 weekly users by letting staff build 2,000 skills. Here is how they prune dead tools to stop context rot.
Stripe processes internal data requests across 10,000 employees using a 3-layer triage architecture that protects data warehouses from rogue agents.
Stripe built Kai with 1.5 engineers in two weeks. Today 10,000 employees use it weekly. Here is why buying off-the-shelf AI failed.
Sharadh Krishnamurthy explains how Stripe uses project-level tool policies and human-in-the-loop controls to govern 10,000 weekly AI agent users.
40 hours of podcasts, distilled into one 5-minute read. Free, every Sunday morning.
One email a week. Unsubscribe with one click.