Stripe's internal AI platform hits 83% weekly active users in two weeks
Stripe built its internal AI platform
Stripe built Kai, an internal knowledge AI platform, after coding agents left non-engineers behind. Two weeks after launch, most of the company was using it; today 83% are weekly active users. Kai runs on surface-agnostic APIs, AgentStudio for domain owners, and a shared execution environment that enforces data-isolation guardrails. It has shifted 25,000 hours per year from administrative work to revenue-generating work.
The isolation boundary isn't "what can this person access based on their authorization token?", but instead "what should this task be allowed to view given this context?"
- quadrifoliate
Stripe is the company I usually hold up as the exemplar of polished internal tools. Hopefully this is taken the right way and I don't want to be negative towards the teams working on this, but I see a distinct lack of polish in these tools and presentations. Some examples:
- Unnecessary AI copy throughout the interfaces like "Browse, discover, and manage skils for your agents", "No favorites yet — hover a card and click the star to pin it here", "One execution environment, shared across agents". These instantly read as AI copy and decrease my enthusiasm.
- Inconsistent, AI-sloppy look-and-feel with different typefaces spattered across the interface.
- The session metrics slide looks busy and AI-generated. It repeats 360,014 sessions in one of the cells at the top, but also has a "360K sessions" in the heading.
I don't know if I'm the only one that notices this stuff, or whether others see it too.
- lukebuehler
Very cool demonstration of managed agents built for the needs of their own business.
I think this is where a lot of companies are going to go: on-prem platforms that give various teams access to agents that are as powerful as coding agents, but much more managed and governed.
I'm betting on this with my open source project, Lightspeed: https://github.com/smartcomputer-ai/lightspeed
- hek2sch
I read a buzz word "Knowledge AI Platform" but I did not see any specific feature helpful for knowledge management like verification or transparency. It is more like any generic Agent builder. Maybe it meant to justify building something internally.
- bob1029
> Building a standalone agent product wouldn't work. Instead, it would force users out of their natural workflows and into a new app.
I am finding the opposite to be true with one of my clients. They explicitly want a new channel. The chat-style UI/UX is vastly preferred over their poorly maintained internal tooling.
I suppose if you are Stripe actual, most things would be well designed and more difficult to abandon. Most places aren't like Stripe.
The hard part is bringing everything that matters to the new channel, but it's certainly feasible to do this. I am doing it right now. We will soon be able to delete hundreds of wildly inconsistent cshtml views and related controllers in favor of a single agent tool that applies json patches. This will easily cover 99.9% of use cases. A manual json editor is retained for the rare case where we need some multi-megabyte merge operation.
- atonse
Ahhh I built an internal set of agents to run our company (finances, all info in the karpathy-style LLMWiki and a database of clients, contracts, billing, time tracking, all managed by MCPs, etc) and it's also called Kai (company name is Kaizen)
Happy to be in such good company!
- olliebrkr
Dang it, I just named my newborn son Kai. At least I didn’t go with Alexa..
- godzillafarts
I want to read this, but the ever-changing linear gradient of the background is too visually distracting. I tried to get around it by highlighting text I want to read, but since the background is changing underneath it, so is the highlight. My eyes hurt.
- naw103
I feel like every time I launch a new feature in GPTree one of these big players follows up with the same functionality within a few weeks :-(
https://gp-tree.com/enterprise
Our developer docs for GPTree knowledge engine here https://gp-tree.com/docs/knowledge-api