One line · 24 words
Stele gives software teams and their AI coding agents a shared record of project knowledge and work, so context carries across sessions and tools.
Press kit
Everything you need to write about Stele.
Approved copy, a fact sheet, logo files, current product screenshots and the brand rules that keep them looking right. Take what you need. Write to us for anything else.
Fact sheet
Fact sheet · MarkdownStele at a glance
- What it is
- Shared memory for AI coding agents and the people who work with them
- Works with
- Claude Code, Cursor, Codex and any MCP client
- Made of
- A hosted record, an agent plugin, a command-line tool and a web app
- Founder
- Serkan Yersen
- Pricing
- Free to start · Indie $5.99/mo · Pro $12/mo · Team $20 per person/mo
- Public projects
- Free, and readable by anyone at app.stele-ai.dev/explore
- Social
- @stele_dev · github.com/Stele-Dev
- Press contact
- serkan@stele-ai.dev
Approved copy
Describe Stele in your own length
Quote any of these as written, or trim them. Each one is accurate as of the date on this page.
Short · 57 words
Stele is persistent project memory for people and AI coding agents. It keeps decisions, lessons, documents and tasks linked in one shared record. When an agent starts work, Stele brings forward the relevant history, including what the team tried before and why it changed direction. People can read and steer the same record in the web app.
Long · 111 words
AI coding agents start every session with no memory of the project. They repeat mistakes the team already fixed and undo decisions they never heard about. Stele gives them a shared record to read first.
Agents in Claude Code, Cursor, Codex and other MCP clients read what the project decided, what is in progress and what went wrong before, then write back what they learn. Tasks and knowledge live in one linked graph, so a new session or a different tool picks up where the last one stopped. People see the same record in a web app, where they can correct it, assign work and publish it as a public project.
Founder
Serkan Yersen
Serkan is a software engineer with more than 19 years of experience. At Meta he worked on WhatsApp Web, release infrastructure and developer AI workflows. Before that he was a founding engineer at JotForm.
He started Stele after watching agent sessions start cold, relearn the project and rebuild things the team had already tried and thrown out.
Logo
Logo rules ↓Logo files
Use the light files on light backgrounds and the dark files on dark ones. Keep the logo as supplied: same shape, same colors, room to breathe.
Every file also comes as a transparent PNG in the full kit.
Product
Screenshots
Captured on October 9, 2026 from DotState, an open-source project whose memory is public on Stele. They show real project data. The interface may have changed since.
Editorial art
Illustrations
From the story on our homepage. Credit them as “Illustration: Stele”. They are drawings, so please don't caption them as screenshots of the product.
Brand
Full guidelines · MarkdownUsing the brand
Logo
- Leave clear space on every side equal to half the height of the mark.
- Keep the mark at 24 px or larger. Below that, use the small mark.
- Don't stretch, rotate, recolor, outline or add effects.
- Don't place it over photos, illustrations or busy screenshots.
Color
Paper#FEFDFC
Ink#1E212B
Knowledge#2B6DC8
Task#C08838
Blue marks knowledge and ochre marks work. Paper and ink do everything else.
Name
Stele
Write it with a capital S and the rest lowercase, in the same typeface as the text around it. Avoid STELE in running text, “Stele AI” and “the Stele”.
Writing about Stele?
For an interview, a demo, or a file in another format, email Serkan directly. Ask before using the logo on merchandise, in a partnership or in a way that suggests endorsement.