Stripe's Knowledge AI Platform

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.

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

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.

> 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.

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!

Dang it, I just named my newborn son Kai. At least I didn’t go with Alexa..

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.

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

Cool to see, but wondering what the upside of this is vs what notion is building with their own agents. I can imagine notion agents can do something very similar to this (and with the same amount of control / security) and at what point would it make sense for a company to build their own vs buying into one..

TIL people still fall for eh I mean use Langchain. Sorry, low value comment; I don’t know how to do that differently; it is such bad garbage since day one and strangely it did not improve. Sorry anyway for the comment, at least it was not LLM generated?

Somebody probably mentioned this already or maybe its just me but: The "endless scroll" this page does is neat, to say the least.-

Can anyone recommend something self-hosted that does this?

reminds me of Cloudflare OS: https://blog.cloudflare.com/cloudflare-os/

It's very close to the direction we're taking for windmill.dev, we call it "operator builders" rather than focus on "knowledge graph" which the article is very light on details of.

What I'm mostly reading is a developer platform and runtime where users can build agents that can run tools and for that you need a secure code runtime, ACL/permissions, easy way to build apps or what cloudflare OS call gadgets. We're betting on this too at https://github.com/windmill-labs/windmill, very curious to see if that's the future for most enterprise and if a model where everyone vibe-code/fork cloudflare OS to their enterprise need is the future, or a more exhaustive/enterprise platform like ours does.

so is it like CloudflareOS ? https://github.com/cloudflare/cloudflare-os

seems every company that has spare engineering resource all builds such thing internally

I love the design, I'm sure there will be more knowledge framework coming in the near future.

> Within two weeks of our April launch, most of Stripe was using Stripe's Knowledge AI Platform, also known as Kai.

By force or by choice?

This is the same as AWS's new quickSuite platform?

This site could use a bit more line height, more paragraphs, or less text overall.

They don't really say why they built their own rather than using one of the open source solutions like https://github.com/bionic-gpt/bionic-gpt

Somewhat interesting how the design of Stripe's developer-focused landing pages used to be the "cream of the crop," so to speak, but now they just look like Claude run amok. I wonder if the web design "skills" for Claude, and other LLMs, were overly trained on Stripe.

Dammit, I just named my newborn son Kai.

But no darkmode support? … :D

The article reads like slop, to be honest.

haha stripe's example prompt is "Create an event"

Has tl;dr been replaced by ai;dr?

The whole piece is mostly AI slop.

"Sharing the substrate forces discipline and creates a flywheel: improvements to the execution environment benefit both internal and product agents simultaneously."

No human would write that.

Hope this comes over as constructive criticism:

  1. The whole interface feels way too vibe coded with tons of unneeded stuff. Why does it have a console and snake game built in? Why does it have annoying sounds? Why is it full of AI slop writing? The latter is especially confusing because the first person listed under authors is a "Technical Writer". I guess the interface is the general stripe.dev page not exactly related to Kai but the post definitely is pure AI slop writing.
  2. It seems to claim things that might not be substantiated like the following: "When Account Executives use Kai, they produce 2x the sales activity, create 17% more opportunities, generate 26% more revenue opportunities, and close 39% more deals when compared to the same sellers in weeks they don't use it." Correlation is not causation. If sales people have less activity (vacations or sick days etc) then they also wont use this tool much, it doesn't mean all the increase in sales is because of the tool.
  3. the post talks a lot about how great this tool is but it describes nearly nothing of value to the outsider who can't access it. What were the valuable lessons learned? What's neat about it? There is not much meat imho.

[dead]

[dead]

[flagged]

[flagged]

[dead]

[flagged]