Who's building Stele,
and why.
I'm Serkan Yersen, and I build Stele. I've spent 19+ years building software, most recently at Meta, where I worked on WhatsApp Web, shipped release infrastructure used by more than three billion people, and built agentic AI workflows for developers. Before that I was a founding engineer at JotForm, where I built the first drag-and-drop form builder, and the frontend architect behind Home Depot's online workflows. Stele came out of that last stretch. Once agents were doing real engineering, the thing slowing them down wasn't capability, it was memory: every session started cold, re-learned the project, and every so often confidently rebuilt something we had already tried and thrown out. Nothing carried over, between one session and the next, one tool and another, one person and the rest. So I built the record I wanted my own agents to have, where the project itself holds the decisions, the dead ends, and the reasons behind them, and everyone who works on it, human or agent, starts from what is already known. That is the whole product. It exists because I needed it, well before I ever tried to sell it.
You're trusting Stele with your project's memory, so here's where to check who that is:
Stele is a shared, persistent record for a software project, the knowledge and the work together, kept by the people and the agents building it. It captures what a project decides, what it learns, and what it is working on, keeps those linked, and serves the relevant history back on demand, to a teammate or to an agent mid-task.
The direction is for Stele to become the place agentic work starts from: where you follow tasks as they move, watch the knowledge your team and their agents build up in real time, and see the project taking shape alongside the code instead of buried inside it.