The Company Brain: Stripe’s Architecture for Autonomy
Moving beyond off-the-shelf AI to build internal intelligence
Most companies approach artificial intelligence like a consumer. They buy a subscription, give their employees a login, and hope for the best. Stripe took a different path. Instead of relying on external tools that lack context, they built Kai, an internal AI agent used by over 10,000 employees. This wasn't an exercise in vanity; it was a necessity born from the realization that generic models cannot navigate the specific, high-stakes environment of a global payments processor. To make AI work at scale, you cannot simply layer it on top of your business; you must weave it into the very fabric of your data and governance.
Governance via Projects
One of the most significant hurdles in enterprise AI is not the intelligence of the model, but the control of the data. Stripe solved this by treating 'projects' as a governance mechanism. Rather than giving an agent unfettered access to the entire company's knowledge base, access is scoped to specific projects. This creates a sandbox where agents can operate without the risk of leaking sensitive information or making unauthorised queries. It turns a chaotic flood of data into a structured library that an agent can navigate safely. This structure is what allows a non-technical employee to ask a question and receive a reliable answer without needing to understand the underlying SQL queries.
The infrastructure built for human developers turned out to be exactly what agents needed.
The engineering team discovered a surprising synergy: the tools designed to help human developers—such as robust documentation, testing suites, and clear API structures—were precisely what AI agents required to function. When an agent can query a data layer that is already clean and well-documented, its utility skyrockets. Stripe didn't just build an AI; they realised that their existing developer experience (DX) was the foundation for an entirely new category of 'engineering intelligence.' This shift moves the focus from writing code to managing the systems that generate and execute work.
- Scoped data access through project-based governance
- Leveraging existing developer infrastructure for agentic queries
- Building a skills platform to package repeatable workflows
- Implementing telemetry to monitor agent performance and errors
As Stripe scales Kai, the challenge shifts from technical feasibility to managing a fleet of agents. They are moving toward a 'hyperagent' model, where fleets of specialised agents handle specific, repetitive tasks. This requires a new kind of oversight—not just checking if the code works, but checking if the agent's logic remains aligned with company goals as it encounters new, edge-case scenarios. The goal is to create a system where the AI doesn't just answer questions, but actively participates in the company's operational rhythm.
Enterprise AI succeeds when it is built as a core piece of infrastructure rather than a bolted-on utility.