English
Docmost Hosting
Create a collaborative team wiki with rich editing, spaces, permissions, and real-time updates.
No setup fees-
One click deploy -
2 GB RAM Memory needed -
25 GB Disk Space Needed -
From 5 € Price
Official links
Docmost’s official links and original website
Docmost Website
More
Tech
- Docker image
- docmost/docmost:latest
- Default port
- 3000
- Database
- postgres
How Docmost works
Docmost divides a workspace into spaces, then stores related knowledge as pages inside each space. Team members write through a rich editor, build nested page structures, link related material, and use search to recover information across the workspace. Several people can edit the same page in real time, with presence and changes visible during the session.
Permissions can separate public, private, or team-specific areas. Comments provide a discussion layer around the written content, while page history supports reviewing earlier changes. The catalogue stack also includes Redis for application coordination alongside PostgreSQL for persistent workspace records.
Key Docmost features
Spaces give departments or projects their own knowledge areas without creating separate installations. Nested pages make longer manuals easier to navigate, and the editor supports tables, media, code blocks, links, and other structured content used in internal documentation.
Real-time editing is useful when a team is writing requirements, meeting notes, runbooks, or onboarding material together. Search, comments, page history, and granular access controls help the workspace remain useful after the initial drafting session ends.
Docmost vs Confluence
Docmost focuses on a self-hosted team wiki with spaces, pages, live editing, comments, search, and permissions. Confluence is a commercial connected workspace that combines documentation with the wider Atlassian product family and its integration ecosystem.
Confluence may suit organisations that want Atlassian-hosted cloud plans, close Jira integration, vendor support, and a large Marketplace catalogue. Docmost is more attractive when the priority is an independently hosted collaborative wiki with direct control of the application and its stored content.
Who uses Docmost
Product teams maintain specifications and decision records in Docmost, while operations groups use it for procedures, service notes, and onboarding. Engineering organisations can document systems and incidents, and support teams can build a private reference library for recurring customer questions.
The community deployment should be evaluated around its documented core wiki functions. Organisations that depend on advanced enterprise identity, vendor-managed administration, or paid extensions should compare the required edition and integration scope before choosing it.
Self-hosting Docmost: requirements and cost
Resource use grows with active editors, page count, search activity, uploaded files, comments, and revision history. PostgreSQL stores workspace data, while Redis supports the application stack. AvaHost provisions both supporting containers, but the PostgreSQL database remains unmanaged. Application email delivery is disabled, so email invitations and notifications must not be presented as part of the hosted service.
Docmost has no separate software charge for the hosted core image, and the database-adjusted recommendation is Plan 3 at €10. The Docmost package provides one-click setup, a custom domain, automated HTTPS, automatic application updates, and scheduled backups. The owner account should be created on first visit before the installation address is shared with a wider team.
F.A.Q
Docmost starts at €10 on Plan 3 after accounting for the application, PostgreSQL, and Redis services in the catalogue stack. Docmost hosting includes one-click setup, a custom domain, automated HTTPS, application updates, and scheduled backups. Active editors, revision history, uploaded files, and workspace search determine when more capacity may be appropriate.
AvaHost provisions PostgreSQL with Docmost and connects the application during deployment. Spaces, pages, users, permissions, comments, and revision records depend on that database, while Redis supports application coordination. PostgreSQL is included but unmanaged, so its data and the persistent Docmost files should be considered together during maintenance or recovery.
A custom domain can be attached to the Docmost workspace, and automated HTTPS is applied after DNS points to the hosted application. Choose the final address before distributing page links widely, then test owner access, shared pages, embedded media, and any integrations that may still contain the original platform hostname.
No. Application email delivery is disabled across AvaHost hosted applications, so the Docmost page must not promise invitation, notification, or password-delivery messages. Create the owner account directly on first visit, configure access inside the application, and share the final HTTPS address through another approved communication channel when users are ready to join.