AIToday
Large Language ModelsAI Business & IndustryLangChain BlogPublished: Nov 10, 2026, 10:00 JST

Stripe builds Kai AI agent on Deep Agents in one week

Send on LINE
Stripe builds Kai AI agent on Deep Agents in one week

3 Key Points

  1. What happened

    Stripe built Kai, its company-wide AI productivity agent, in one week on LangChain's open-source Deep Agents harness, per engineering manager Sharadh Krishnamurthy and staff engineer Anupam Upadhyay.

  2. Why it matters

    Kai was purpose-built for non-engineers, and Sharadh said people who had been told to use AI but found earlier tools unapproachable took to it without tuning knobs, so the team could focus on Stripe-specific workflows rather than agent infrastructure.

WHO IT HITSNon-technical Stripe employees such as sellers, finance analysts and business operations staff get a production-ready AI assistant that connects to internal data, Slack and Google Suite without requiring developer tooling.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

Stripe's AI platform team faced a common problem as agentic AI adoption accelerated: engineering teams across the company were building orchestration layers on their own Ruby and Java stacks, but production-quality agent harnesses required performance, evaluation and reliability work beyond simple connectivity. When Claude Code launched in late 2024, every Stripe employee wanted to build agents, but non-engineers hit barriers around the terminal, data access and security. Sharadh Krishnamurthy and Anupam Upadhyay inverted the approach, meeting non-technical employees where they were with a purpose-built assistant rather than pushing them toward developer tooling.

The resulting Knowledge AI Platform, Kai, sits on a layered architecture: Deep Agents as the base handling LLM interaction primitives, a Stripe-specific harness integrating security and internal services, a configuration layer for custom agents, and the Kai UI. Sharadh described the Deep Agents layer as solving all the non-Stripey problems so the team could focus on Stripey agent problems. Anupam built the initial version in one week, and that speed demonstrated the return on Stripe's investment in rebuilding internal service scaffolding around a Python-native stack after more than a decade on Ruby and Java.

Kai's early traction was rapid: it hit the quarterly adoption target in a week and grew more than 16x from 296 users to over 5,000 in roughly four weeks. The bulk of new users were sellers, finance analysts and business operations people who had been told to use AI but had not found a tool that fit how they worked. Today 83% of Stripe uses Kai every week across more than 60k sessions, with Marketing at 95% and GTM teams at 87% adoption by percentage. The team now faces scaling challenges around skill selection, governance and personalization as it moves past product-market fit.

FAQ
What is Kai?
Kai is Stripe's Knowledge AI Platform, a company-wide productivity agent available to every employee. It connects to Stripe's internal data warehouse, Slack and Google Suite and produces artifacts, reports and dashboards alongside the chat.
How did Stripe build Kai so quickly?
One engineer built the initial version in one week using Deep Agents middleware, including filesystem, sandbox and summarization components. Deep Agents provided the tool-calling loop, streaming and state management that would otherwise take months to build.
Which teams use Kai the most?
Business functions show higher adoption by percentage than engineering, with Marketing at 95% and GTM teams at 87%. Sales, finance and business operations roles were the bulk of new users.
LangChain BlogRead Original Article
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleNvidia board probes Jensen Huang over affair with suspected Chinese spy