From Code to Understanding.

Understand
what AI built.

Doklo reads the code and organizes it by feature, like login and checkout. Developers and non-developers read the same explanation, and can open the related code whenever they need to.

Explore the live demo without signing up.

An app built by AI should come with a way to understand it.

Doklo explains what an AI-built service does and how it works, feature by feature.

Like a colleague who reads it first and explains it calmly beside you.

Dok

See what was built.

A Dok explains one feature: the order a login or a checkout happens in, and what happens when a payment fails.

CHKT-CHECKOUTApproved
Checkout
Purpose
Let a signed-in customer pay for their cart without leaving the store.
1
People
customer · system
2
Flow
Provide address → pay with Stripe → system holds stock → webhook confirms the order.
3
Rules
Stock is held for 10 minutes. An order is created only when the webhook arrives.
4
Works when
✓ a failed payment releases the held stock and keeps the cart intact.
5
Related code
app/checkout/actions.ts · lib/stripe/client.ts · +5 files
6
  • 1
    What it is for

    The explanation starts with the purpose of the feature.

  • 2
    Who uses it

    The roles come from the code, not from memory.

  • 3
    How it runs

    The order a checkout runs in, step by step.

  • 4
    What the rules are

    The limits and policies that explain why something is not allowed.

  • 5
    How you know it works

    The criteria that show the feature works as intended.

  • 6
    Where the code is

    The explanation is linked to its code, so you can check what it was written from.

Code→Dok→Hub→UnderstandingDoks are stored as JSON in your git repository. The Hub is where the Doks for login, checkout, shipping and the rest come together.

How it works

Understand how it works.

01

Connect the repository to analyze.

A repository is where a product's code lives. Doklo reads the connected code and organizes the explanation by feature.

$ doklo scan
✓ 312 files · 23 routes · 87 components
02

Analyzing the code.

Doklo looks at which features exist and how they connect. Scanning the code is free; writing one Dok costs one credit.

$ doklo generate
● CHKT-CHECKOUT draft · 7 related files
03

Review the explanation.

Check that the explanation matches the related code. Fix what needs fixing, then approve it. Your edits stay even when the Dok is regenerated.

Needs review→ you →Approved
Approved in Studio.
04

Live Docs are published.

Live Docs are built from Doks a person approved. When the code changes, Doklo tells you which explanation to check again.

help-page · CHKT-CHECKOUT
built from 1 approved Dok
Live Docs

Share the Same Understanding.

Live Docs are help pages for your users, built from explanations a person checked and approved. They tell users where to click and what to enter.

Help pagethe guide you hand to users, per featurehtml · mdstable
Release noteswhat changed, written so users understand ithtmlexperimental
Help indexevery feature's help in one listhtmlexperimental
Ops manualthe procedures an admin checksmdexperimental
Traceability matrixrequirement, code and test in one tablexlsxexperimental

Of the 16 templates in the engine, the help page is the one promised stable today; the rest are opt-in. When the code changes, Doklo tells you which explanation to check again.

help-page · CHKT-CHECKOUTApproved
Help · Checkout

Checkout

Pay for your cart in three steps. Your items are held for 10 minutes while payment completes.

Steps
  1. Enter your shipping address and pick a delivery speed.
  2. Pay with card. Extra verification appears right on the page.
  3. Your confirmation email arrives within a minute.
If you cannot continue
  1. Checkout needs a verified email. Check your inbox first.
built from 1 approved Dok · 7 related files
What Doklo cares about

Built by AI. Understood by people.

Doklo helps people understand what AI built.

01

You should be able to understand how it works.

Doklo explains AI-built results plainly, so a person can look and decide.

02

You should be able to check where an explanation comes from.

Every explanation shows the code it was written from.

03

People with different technical knowledge should be able to talk about it.

Doklo uses words that planners and customers understand, not only developers.

04

A freshly made Dok is a draft, not yet reviewed.

Read it, fix what needs fixing, then approve it. Live Docs are built only from Doks a person approved.

Doklo reads your code only while an analysis runs and does not store it. The copy is deleted when the analysis ends.

MCPcoming

People and AI read
the same product explanation.

MCP is how AI tools look up what Doklo knows. The connection that lets Cursor and Claude Code read approved Doks comes after Live Docs.

CursorClaude Codeany MCP client
agent › doklo.search_doks("refund hold")
← CHKT-CHECKOUT · approved
  rule: an order is created only when the webhook arrives
  related code: 7 files · approved by a person

Understand what AI built.

Look around first, no sign-up needed.

Get started free

No card is required to explore the demo.