Question 1

What is Kleio?

Accepted Answer

Kleio is an engineering memory and provenance platform for AI-assisted development. It captures decisions, checkpoints, and work signals across humans, agents, and code so you can understand not just what changed, but why it changed.

Question 2

How does Kleio fit into my existing workflow?

Accepted Answer

Kleio is designed to slot into how you already work. It integrates with tools like Cursor, Claude, and your Git workflow through a CLI, MCP server, and GitHub App. You can start it locally, use provided templates for rules, and capture context directly from your normal development flow without changing how you build.

Question 3

Why not just use markdown files in my repo?

Accepted Answer

Markdown files are useful, but they rely on people remembering to write, organize, and maintain them. In fast-moving projects, context ends up fragmented across commits, chats, PRs, terminals, and AI sessions. Kleio helps capture that context as it happens, structure it, and connect it back to the actual work.

Question 4

Who is Kleio for?

Accepted Answer

Kleio is built for engineers and teams working in high-velocity environments, especially where AI tools are part of the development workflow. It is most useful when decisions are happening quickly and context is otherwise easy to lose across sessions, contributors, and systems.

Question 5

What does Kleio capture?

Accepted Answer

Kleio captures engineering context such as decisions, checkpoints, todos, and related signals tied to your codebase and workflow. Over time, this builds a structured history of how work evolved and what led to the current state.

Question 6

Do I need the CLI, or can I just use the web app?

Accepted Answer

The web app lets you review and work with captured context, but the CLI and integrations are what enable automatic capture. They run alongside your existing tools and let Kleio observe and structure work directly from your development flow.

Question 7

Is my data secure?

Accepted Answer

Kleio is built with security fundamentals in mind, including authenticated access and tenant-aware data separation. As the product matures, security and deployment options will expand for teams with stricter requirements.

Question 8

How does billing work?

Accepted Answer

Kleio has three plans — Free, Pro (€19/mo), and Team (€49/mo) — with discounted yearly billing. Checkout and subscription management are handled through Stripe inside the app. You can upgrade, downgrade, or switch billing intervals at any time from your workspace settings.

Question 9

Where do I get support?

Accepted Answer

Support is hands-on. If you are onboarding with Kleio, you can reach out through the product contact channels or links provided on the site. For technical ecosystem questions, GitHub may also be used where applicable.

Question 10

Why is it called Kleio?

Accepted Answer

Kleio is named after Clio (also spelled Kleio), the muse of history in ancient Greek mythology. The name reflects the product's purpose: preserving the context behind engineering work so important decisions are not lost.

Engineering context,
decisions, and the future of code review.

See it in action

Coming soon

How AI Agents Are Creating a New Kind of Technical Debt

ADRs Are Dead. Long Live Engineering Memory.

The Real Cost of Context Loss in AI-Assisted Development

Don't wait for the blog

Engineering context,decisions, and the future of code review.