Command Palette
Search for a command to run...

for projects

A home for your docs that credits you.

Your README is scraped by a dozen models and surfaced with no link back, and your best answers elsewhere were licensed off to an AI lab. Point docolin at your repo and get a canonical, attributed home: community contributions and verification on top, while your issues, pull requests, and merge rights stay exactly where they are.


two ways in

Bring docs however you keep them.

Sync from git

Point docolin at any repo. It syncs on every push, and your issues and pull requests stay in the GitHub workflow you already use.

Import what you have

Bring MkDocs, Mintlify, or Docusaurus docs in one pass. Plain content imports cleanly; platform-specific components are mapped where they can be and flagged where they can't.

Or write in the app

An in-app editor is on the way for authors who don't live in Git. No repo required.


what stays yours

Community input, your editorial control.

Merge rights stay with you

Anyone can open a pull request or a discussion. Merging stays with you and your invited maintainers; lock a branch and the community can still propose, just not overwrite.

Attribution everywhere

Your name rides into every citation, including when an AI agent serves your guide through MCP. Credit by construction, not by courtesy.

Every version kept

Each version stays addressable forever with its own verification record. A guide that worked on 22.04 doesn't vanish when 24.04 lands.


Give your docs a home that can't be taken away.

docolin's platform is AGPL, so it can't be bought and locked down, and a company reading your docs through MCP doesn't inherit AGPL, it just has to keep your name on your work. Free forever, funded by sponsors.