Docmost: a self-hosted wiki that takes on Confluence and Notion
Docmost is an open-source collaborative wiki and documentation software. It is an open-source alternative to Confluence and Notion.
At a glance
- What is it?
- Docmost is an AGPL-3.0 collaborative wiki written in TypeScript, shipped as a Docker image with Postgres and Redis. It covers real-time editing, spaces, permissions and diagrams, but its install documentation lives off-site and part of the codebase is under a separate enterprise licence.
- Who is it for?
- Adopt Docmost if you want a self-hosted wiki with real-time editing, spaces and page history, and you are comfortable running Postgres and Redis behind a Docker Compose file. Do not adopt it if you need a permissively licensed codebase end to end, or if you will not read the self-hosting docs before you commit.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- docmost/docmost22,341 ★ · +593
| Repository | 2026-09-21 | 2026-11-15 |
|---|---|---|
| docmost/docmost | 21.7k | 22.3k |
593 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What Docmost solves, and for whom
Docmost is documentation software you host yourself. The README calls it an open-source collaborative wiki and documentation software, and the repository description calls it an open-source alternative to Confluence and Notion. The target reader is a team that wants a shared knowledge base with a page tree, comments and permissions, but does not want the content sitting in a vendor account.
The feature list in the README is the clearest statement of scope: real-time collaboration, diagrams through Draw.io, Excalidraw and Mermaid, spaces, permissions management, groups, comments, page history, search, file attachments, embeds for Airtable, Loom and Miro, and translations in more than ten languages. That is a product aimed at internal documentation, not at public-facing publishing. Spaces and groups suggest the intended unit of adoption is a company with several teams, each wanting its own area with its own access rules.
It is a poor fit for a single writer keeping personal notes. Page history, permissions and groups exist to coordinate people; if there is only one person, those features are overhead you still have to operate. A static site generator or a local note app would ask less of you.
How the pieces fit: pnpm workspace, Postgres, Redis, Hocuspocus
The repository is a pnpm workspace with an Nx build graph. The root package.json defines scripts that fan out across apps and packages: build runs nx run-many -t build, and dev runs the client and server together through pnpm concurrently. The workspace holds apps/ and packages/, and the editor lives in its own package, @docmost/editor-ext, which is referenced as a workspace dependency.
The editor is Tiptap. The dependency list pins @tiptap/core and a set of extensions at 3.31.3, including collaboration and collaboration-caret. Real-time collaboration is not a Docmost invention: the project depends on the Hocuspocus packages at 4.5.0, @hocuspocus/server, @hocuspocus/provider and @hocuspocus/transformer. That is the mechanism behind simultaneous editing. The server component also has a separate collab process, exposed through the collab and collab:dev scripts in the root package.json.
State lives in two places. Postgres holds the application data; the DATABASE_URL in .env.example points at a docmost database with a schema parameter. Redis runs alongside it, and the Compose file starts it with appendonly yes and maxmemory-policy noeviction, which tells you the project expects Redis to keep its data rather than treat it as a throwaway cache. File attachments go to the local filesystem by default, or to S3 or Azure when STORAGE_DRIVER is changed.
One consequence of the Tiptap and Hocuspocus stack is worth stating plainly: the editor is Tiptap-based, with conversion helpers such as @joplin/turndown and @joplin/turndown-plugin-gfm present for turning content into Markdown. That is a different storage philosophy from a wiki that keeps Markdown files on disk as the source of truth.
Installing Docmost with Docker Compose
The README does not carry install steps. It points at the documentation site for getting started and at the cloud version for a hosted option. The repository does ship a docker-compose.yml and a .env.example, so the self-hosted path is visible in the code even though the prose lives elsewhere.
The Compose file defines three services. The docmost service uses the image docmost/docmost:latest, depends on db and redis, publishes port 3000, and mounts a named volume at /app/data/storage. Postgres runs as postgres:18 with a docmost database and user, and Redis runs as redis:8. Before starting it, replace the placeholder secrets. The .env.example gives the rule for APP_SECRET: a minimum of 32 characters, generated with openssl rand -hex 32.
openssl rand -hex 32Paste that value into APP_SECRET and set a real database password in DATABASE_URL. The Compose file ships APP_URL as http://localhost:3000, which is the address you will open in a browser once the containers are up.
docker compose up -dAfter the containers start, the application is reachable on port 3000. The Dockerfile confirms how the image is built: Node 26 slim, pnpm 12.16.1 installed globally, a build stage, then an installer stage that runs pnpm install --frozen-lockfile --prod with the client filtered out. The server process listens on the port given by PORT, which .env.example sets to 3000.
For a source build rather than the image, the root scripts are the entry point. pnpm install --frozen-lockfile followed by pnpm build produces the server and client bundles, and pnpm start runs the production server. Development uses pnpm dev, which starts the client and server concurrently. The README points contributors at a development page in the documentation rather than describing the workflow inline.
Configuration you will actually touch
The .env.example is the honest inventory of what an operator has to decide. Storage is the first: STORAGE_DRIVER takes local, s3 or azure, and each has its own block of keys. The S3 block includes AWS_S3_FORCE_PATH_STYLE, which matters for S3-compatible services rather than AWS itself. Azure has account name, key and container.
Mail is the second. MAIL_DRIVER accepts smtp or postmark. The SMTP block carries host, port, username, password, SMTP_SECURE and SMTP_IGNORETLS; Postmark needs only POSTMARK_TOKEN. Invitations and notifications depend on this working, so a self-hosted deployment without a mail path is half-configured.
Two settings are easy to miss. FILE_UPLOAD_SIZE_LIMIT defaults to 50mb according to the comment in the file. GOTENBERG_URL is described as the Gotenberg URL for server-side PDF export, which means PDF export is not self-contained: you point Docmost at a separate Gotenberg instance, or that feature has nowhere to go. DRAWIO_URL exists for a custom Draw.io server, so the diagram integration can also be pointed away from the default.
Telemetry is on unless you turn it off. DISABLE_TELEMETRY defaults to false. Iframe embedding is off by default too: IFRAME_EMBED_ALLOWED is false, and when you enable it, IFRAME_ALLOWED_ORIGINS restricts which origins may embed the app, with an empty value allowing any origin. Debug logging is controlled by DEBUG_MODE, DEBUG_DB and LOG_HTTP, all defaulting to false.
Where Docmost is the wrong tool
The licence boundary is the first limitation. The README states that Docmost core is AGPL 3.0, and that enterprise features are available under an enterprise licence. It then names the directories covered by that enterprise licence: apps/server/src/ee, apps/client/src/ee and packages/ee, with the licence text at packages/ee/License. The README does not enumerate which features live in those directories. If you are evaluating Docmost on the assumption that everything in the repository is AGPL, that assumption is wrong, and the only way to know what is carved out is to read the code in those three paths.
AGPL itself is a consideration for anyone embedding the software in a service. This is not legal advice, but the licence choice is a deliberate one and it shapes who can adopt the project without a conversation with their lawyers.
Operationally, the dependency on Postgres and Redis is not optional in the Compose setup, and Redis is configured with appendonly and noeviction rather than as a disposable cache. A single-container deployment is not what the shipped files describe. PDF export depends on an external Gotenberg service, so an air-gapped install loses that feature unless you run Gotenberg too. Mail needs an SMTP server or Postmark.
Finally, the README does not document backup, restore or rollback. The Compose file declares three volumes, docmost, db_data and redis_data, so the data to preserve is identifiable, but the procedure for restoring it is not in the repository's README.
Docmost vs Outline, Notion and Obsidian: the real difference
The comparison that matters is storage and licensing, not feature checklists.
Outline is the closest analogue: a self-hosted team wiki with real-time collaboration. The practical difference for an adopter is the licence. Docmost core is AGPL 3.0 with enterprise directories under a separate licence, and the README points at the enterprise licence file for those paths. Anyone choosing between the two should compare the licence terms of each project directly rather than rely on a repository description.
Notion is the hosted product Docmost is positioned against. The difference is where the data lives and who operates the service. Docmost gives you a Docker Compose file, a Postgres database and a storage volume you control; Notion gives you an account. That trade is the whole point of the project, and it also means you own the backup problem, which the README does not solve for you.
Obsidian is a different shape entirely: local Markdown files, no server, no Postgres, no collaboration layer. Docmost runs a server with Postgres and a Tiptap and Hocuspocus collaboration stack, which is what makes simultaneous editing work. If your priority is plain files you can grep and version in Git, Docmost is the wrong end of that spectrum.
The honest summary is that Docmost competes on being a self-hosted Confluence-style wiki with a modern editor, and the deciding factors for most teams will be the licence carve-out and the operational surface of Postgres plus Redis plus optional Gotenberg.
Editorial conclusion
Adopt Docmost if you want a self-hosted wiki with real-time editing, spaces and page history, and you are comfortable running Postgres and Redis behind a Docker Compose file. Do not adopt it if you need a permissively licensed codebase end to end, or if you will not read the self-hosting docs before you commit. Verify first that the enterprise directories under apps/server/src/ee, apps/client/src/ee and packages/ee do not cover the features you need, and confirm the SMTP or Postmark settings in .env.example match the mail provider you actually run.
Frequently asked questions
What is Docmost used for?
It is an open-source collaborative wiki and documentation software, positioned as an alternative to Confluence and Notion. The README lists real-time collaboration, spaces, permissions, groups, comments, page history, search, attachments and diagrams as its features.
How do I install Docmost?
The README points to the documentation site for getting started. The repository ships a docker-compose.yml with docmost, Postgres 18 and Redis 8 services, so the self-hosted path is to set APP_SECRET and the database password, then run docker compose up -d. The application listens on port 3000.
Is Docmost free and open source?
Docmost core is licensed under AGPL 3.0, and enterprise features are available under a separate enterprise licence. The README names apps/server/src/ee, apps/client/src/ee and packages/ee as the directories covered by the enterprise licence.
How much does Docmost cost?
The repository does not state prices. The README links to a cloud version and a pricing page on the project website, which is where cost information would live.
How does Docmost compare with Notion?
Docmost is software you host, with a Docker Compose file, a Postgres database and a storage volume you control. Notion is a hosted product reached through an account. The README positions Docmost as an open-source alternative to Notion and Confluence.
Official sources
Where this project is recommended
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/docmost-docmost)Star history chart for your README
[](https://hysenlabs.com/projects/docmost-docmost)Was this useful?