Docs vs Gollum
Which should you use? A side-by-side look at what each one does, who it suits, what it costs, how hard it is to set up, and where each falls short.
Open source · MIT
Open-source collaborative text editor for teams, with real-time editing and self-hosting.
Open source · MIT
A simple wiki that stores pages as files in a Git repository, editable locally or in the browser.
The short answer
Choose Docs if you need…
- Teams that want a shared wiki or knowledge base they can host themselves
- Public organizations and companies that need control over where their data lives
- Groups who want real-time co-editing with live cursors and comments
- Developers who want to self-host and extend a Django and React application
Choose Gollum if you need…
- Teams that want a wiki whose content lives in Git alongside other project files
- People who already keep GitHub or GitLab wikis and want to view or edit them locally
- Developers who prefer writing docs in a text editor and committing changes
- Users who want to revert or browse page history with familiar Git tools
Side-by-side
| Docs | Gollum | |
|---|---|---|
| Type | App | App |
| Price | Free and open source | Free and open source |
| Licence | MIT | MIT |
| GitHub stars | 17k | 14.3k |
| Setup difficulty | Intermediate | Intermediate |
| How you get it | Run with Docker | Install with a package manager |
| Main language | Python | Ruby |
| Last code update | 4 days ago | 12 months ago |
What each one is
Docs
Docs is a web-based, open-source editor where people write, organize, and share documents together in real time. It lets you nest subpages to build a knowledge base, and it is described as an alternative to tools like Notion or Google Docs. You can use a public instance or host it yourself, which keeps your data under your control.
Gollum
Gollum is a wiki where every page is a text or markup file inside a Git repository. You can edit pages in your own editor and commit them, or use the built-in web interface, and every past version of a page stays available through Git history. It supports several markup languages and can run locally in a browser.
Best for
Docs
- Teams that want a shared wiki or knowledge base they can host themselves
- Public organizations and companies that need control over where their data lives
- Groups who want real-time co-editing with live cursors and comments
- Developers who want to self-host and extend a Django and React application
Gollum
- Teams that want a wiki whose content lives in Git alongside other project files
- People who already keep GitHub or GitLab wikis and want to view or edit them locally
- Developers who prefer writing docs in a text editor and committing changes
- Users who want to revert or browse page history with familiar Git tools
Strengths
Docs
- Real-time collaboration with live cursors and presence, built on Yjs and BlockNote
- Open source under the MIT License with self-hosting options such as Docker Compose and Kubernetes
- Optional AI writing helpers that work with your own model or API provider
Gollum
- Content is plain files in Git, so history, reverts, and branching work with standard tools
- Supports many markup languages and extras such as diagrams, math, and citations
- MIT licensed and actively maintained, with a large community following
Not ideal for
Docs
- People who only want a quick document with no setup: the README points to hosted public instances instead, which you would need to find and trust yourself
- Teams that need a fully self-managed, zero-maintenance service, since self-hosting requires running infrastructure
- Users who need PDF export or certain advanced features if they must avoid GPL-licensed components, because those rely on non-MIT BlockNote XL packages unless built with PUBLISH_AS_MIT=true
Gollum
- People who want a hosted wiki with no setup, since Gollum runs on your machine or server
- Non-technical users who are uncomfortable with Git concepts like repositories and commits
- Teams needing built-in user accounts and permissions, as the README only mentions authentication through a separate CAS server setup
Trade-offs
Docs
- Some advanced features such as PDF export depend on GPL-licensed BlockNote XL packages that are not MIT-compatible
- Self-hosting and local development require Docker, Make, and some technical comfort
- The AI cursor feature is labeled beta in the README
Gollum
- Requires Ruby or JRuby knowledge for installation and some extra renderers need separate gem installs
- On Windows it runs only under JRuby, which adds setup complexity
- Advanced features and install details are mostly documented on an external wiki, so the README alone gives limited detail
Getting started
Docs
Clone the repository
git clone https://github.com/suitenumerique/docsBootstrap the project for local development
make bootstrap FLUSH_ARGS='--no-input'Gollum
Install as a Ruby gem
gem install gollumClone the source
git clone https://github.com/gollum/gollumFrequently asked questions
What is the difference between Docs and Gollum?
Docs: Open-source collaborative text editor for teams, with real-time editing and self-hosting. Gollum: A simple wiki that stores pages as files in a Git repository, editable locally or in the browser. Docs suits teams that want a shared wiki or knowledge base they can host themselves, while Gollum suits teams that want a wiki whose content lives in git alongside other project files.
Are Docs and Gollum free?
Docs: Free and open source. Gollum: Free and open source.
Is Docs or Gollum more popular?
Docs has more GitHub stars (17k) than Gollum (14.3k). Popularity isn't the same as fit — check which one matches your use case above.
What are other alternatives to Docs and Gollum?
Other options people compare them with include BookStack.
Keep comparing
Built from our catalogue entries for both products: open-source details come from each project's README (AI-assisted, refreshed weekly) and GitHub data; AI-tool details are editorial. Spotted something wrong? Let us know from either product's page.