Company knowledge base
A company knowledge base in your own Git repository.
MyGitNotes turns a Git repository into a company knowledge base: handbooks, processes and decisions as Markdown, organised in notebooks, searchable, and versioned with every change.
What you get
A notebook per team
Each team’s own notebook and folders, named and ordered their way.
Find it again
Full-text search, status and tags, and a graph of linked notes.
Views for each job
Read a list, scan cards, or track work on a kanban board, from the same notes.
Every change reviewable
See what changed in the handbook last month, and who changed it.
Onboarding built in
Gather outlines and compilations, or turn pages into flashcards.
No lock-in
It is plain Markdown, readable by any tool.
Questions and answers
How is this different from a wiki?
A wiki usually keeps pages in its own database. MyGitNotes keeps them as Markdown in your repository, so the history, permissions and files are yours, and other tools can use them.
Who can read and edit the knowledge base?
People sign in with GitHub, and MyGitNotes reaches only the repositories granted to it. What each person can do follows their repository access.
Can we bring our existing documentation?
Yes, if it is Markdown or converts to it. Commit the files and MyGitNotes reads them, including frontmatter for status and tags.
What happens if we stop using MyGitNotes?
Nothing. It stays in your repository as Markdown, with its full history.
Can AI assistants use the knowledge base?
Yes. Connect AI agents with read-only or write access; each change is its own commit. See the AI agents page.
Plan your knowledge base with us
Tell us how many teams and repositories you have, and we will suggest a structure and a rollout.