From a repo of markdown to a published handbook
Docs Flowy reads the docs already in your repository, lets your team and your agents review and extend them, and publishes named releases to the public, behind a password, or for your team only.
Free for 3 reposRead-only accessNo card
What the animation shows
- 1. Docs in gitMarkdown files in the repository become a folder tree, with no config file.
- 2. Read and reviewA teammate leaves a note on the paragraph that needs work.
- 3. Specs and draftsA spec moves across the Board from Draft to In review to Validated.
- 4. Team HandbookPages join the Team Handbook, each pinned to the source it describes.
- 5. Public sitePublish a release for anyone, behind a password, or for team sign-in only.
- 6. Agents and feedbackAn agent replies and claims the note is addressed. A person confirms it.
Reads fromGitHubGitLabSelf-managed GitLab
ReachesClaudeCursorVS CodeZedany MCP client
1 · Docs in git
The folder structure is the navigation
Connect a repository and the markdown inside it becomes a tree your team can read. There is no config file to write and no sidebar to maintain.
- Reads GitHub and GitLab without cloning, and fetches only the files that changed.
- Moves keep a document's identity, so its status and notes follow it.
- Private repositories stay read-only; no token is stored.
Readingacme/payments
Connecting
Looking for your documents.
2 · Read, review, reply
An agent can claim a note is addressed. Only a person closes it.
Your team leaves notes on documents. Your coding agent reads them over MCP, answers each with a typed reply, and says what it changed. The note then waits for a person.
- Review status and implementation status move independently, and a status notices when the document changed under it.
- Docs health lists broken links and pages that fell behind the code.
- Search, Copy for LLM and every read tool stay free on every plan.
- Agent
search_docs"idempotency" across 6 repositories · 3 hits
- OpenA teammate leaves a note.
- Awaiting confirmationThe agent replies and claims it is addressed.
- Closed by a personA person confirms. Nothing else can.
3 · Specs and drafts
People and agents write the spec. The Board shows what got built.
Artifacts and drafts are written by people and by agents. A draft is promoted when it is ready, and only then does it gain an implementation axis.
- Review: Untriaged, Draft, In review, Validated, Rejected.
- Implementation: In progress, Implemented, Done, Cancelled.
- Implemented means an agent says it built it and nobody confirmed.
Showing
Untriaged1
Draft1
in progress1
In review1
in progress2
Validated1
done · drifted
Rejected
Four documents, one axis. The other one rides on the card.
4 · Handbook to public site
Write it internally. Publish a named release when it is ready.
The Team Handbook holds pages pinned to the specs and code they describe. The public site arranges entries from it and ships them as releases you name. You decide who can open it.
Anyone
Open and indexed by search engines.
Password
Readers enter a password. The site is not indexed.
Team sign-in
Only members of your team, through Docs Flowy.
The public site has no comment board. Feedback stays inside Docs Flowy as notes, where agents reply and people close them.
Public sites: Starter and upControl
Built so a team can say yes
Access follows the project, every action is attributed, and the controls an approval asks about are shipped or named as not yet.
Organizations and roles
Membership is the organization. Access is the project, and a role caps it.
Two-factor sign-in
Authenticator codes and recovery codes for every account.
Audit log
Every change is recorded in the same transaction that made it.
Team and upAPI tokens
A token belongs to the organization and reaches exactly one project.
IP allowlist
Restrict sign-in and API access to the addresses you list.
Business and upAsk your docs
Off until an organization turns it on. Cached answers cost no credit.
- config files
- 0config filesever required
- providers
- 2providersGitHub and GitLab
- agent tools
- 16agent toolswithheld by scope
- measure
- 78chmeasureat every width
- push to current
- 1push to currentchanged files only
Pricing
One price, whoever reads
Members and reading are unlimited on every plan. What a plan sells is the monthly pool of AI credits — only calls that reach a model spend one.
Free
Read your team's docs the way they are already written.
€0per month
- 3 repositories
- 1 private repository
- Up to 5 active invitations at a time
- 100 AI credits a month
- 3 agent keys
- 2 agent requests a second
- The reader
- Full-text search
- GitHub and GitLab
- MCP for agents
- Ask your docs
- API tokens
Starter
Agents that write back, notes and the board, for a small team.
€19.00per month
- 10 repositories
- 2,000 AI credits a month
- 10 agent keys
- 10 agent requests a second
- Everything in Free, plus:
- Public Handbook site
- Artifacts and agent replies
- Notes and agent replies
- Task workflow and the board
Team
Your Handbook on your own domain, release emails and the audit log.
€79.00per month
- 50 repositories
- 10,000 AI credits a month
- 100 agent keys
- 25 agent requests a second
- Everything in Starter, plus:
- Handbook on your domain
- Release emails for readers
- Notifications by email
- Audit log
BusinessMost popular
More credits, unlimited repositories, and the IP allowlist.
€249.00per month
- Unlimited repositories
- 35,000 AI credits a month
- Unlimited agent keys
- 50 agent requests a second
- Everything in Team, plus:
- IP allowlist
Every organization starts with 200 credits, once, when a verified account connects its first repository. Reading, search, the tree and bundles are free and unlimited on every plan — only calls that reach a model spend a credit, and a cached answer spends nothing.
Questions
The ones we get asked first
Do we have to restructure the repo?
No. The folder structure becomes the navigation as it stands. If a repo ever needs a config file to read well, that is our bug, not your task.
What access does the GitHub App get?
Read-only, on the repositories you select, and you can revoke it from GitHub at any time. Repos are never cloned. We read the tree and the markdown over the API.
How fast does a change show up?
A push triggers a webhook and only the files whose blob SHA changed are read again. GitLab projects are polled about every five minutes.
Can an agent change our documents?
An agent can write artifacts and reply to notes, and it can claim feedback is addressed. It cannot edit a source file, and only a person can close a note.
Who can see the public site?
You choose per site: anyone, readers with a password, or members of your team who sign in with Docs Flowy. Password and team sites are not indexed.
Which plans include public sites?
Public sites need Starter or above, and the site on your own domain needs Team. The Team Handbook itself is available on every plan, and Free also covers connecting repositories, reading, search and Copy for LLM.
Point it at a repo. Read the handbook you didn't write.
Connect in three minutes. Disconnect in one click.