Docmost for Teams: Permissions, Storage and VPS Choice

Last verified: 23 October 2026

Short answer

Self-hosting Docmost removes the hosted platform from the data path, but it does not remove every recurring cost or operating job. The free Community edition covers the core wiki and collaboration workflow. Some controls that organizations often assume are included, such as page-level permissions, SSO and MFA, belong to the paid editions.

Choose the edition before choosing the VPS. A small Community workspace and a Business deployment with identity integration have different operational requirements even when both use the same Docker stack.

Prices and plan boundaries can change. Verify them on the official Docmost pricing page before committing to a license.

Build the access model before inviting users

Docmost has one workspace with multiple spaces. A space is the useful security and organization boundary for a team, project or department. Pages can be nested inside it.

The current space roles are:

• Full Access: manages space settings, permissions and pages;
• Can Edit: creates and changes pages;
• Viewer: reads pages without editing them.

Use groups for repeatable membership. For example, an Engineering group can receive Can Edit access to the Engineering space, while the Everyone group receives Viewer access to a company handbook. This makes onboarding and offboarding less error-prone than adding the same person to many spaces individually.

Page-level restrictions are a separate commercial feature. Docmost’s current documentation says restricted pages are visible only to explicitly permitted users and groups. Restrictions also inherit through the page tree. A child page below a restricted parent is not a shortcut around the parent permission.

Before launch, write down:

1. which spaces exist and who owns each one;
2. which groups receive Full Access, Can Edit or Viewer;
3. whether any content needs page-level restrictions;
4. whether company login, MFA or automated provisioning is required;
5. who removes access when a person leaves.

If page-level restrictions or SSO are mandatory, include the Docmost license in the budget. The old claim that every team pays only for a VPS is not accurate.

Plan the operating stack, not a guessed user count

Docmost’s official Compose stack includes the application, PostgreSQL and Redis. The documentation does not publish a universal rule that a certain RAM value supports a fixed number of people. Editing patterns, attachments, search, imports and other services change the load.

Start with enough headroom for all containers plus the reverse proxy and monitoring. Then record actual memory use, disk growth and response time during normal editing. Resize from those observations rather than from an invented users-per-gigabyte table.

For installation commands, use the separate Docmost installation guide. This page focuses on the team and operations decision.

WebSockets and HTTPS

The real-time editor depends on WebSockets. Docmost says a reverse proxy must forward the Upgrade and Connection headers. If the page loads but the editor is read-only, verify that path before buying a larger server.

The reverse proxy should also terminate HTTPS. Keep the Docmost application port behind the proxy instead of exposing an unencrypted editor directly to the internet.

Invitations and email

Docmost supports SMTP and Postmark email drivers. Email is needed for inviting users. Configure delivery and test an invitation before announcing the workspace to the team.

Files and backups

Local file storage is the default. Docmost also documents S3-compatible storage and Azure Blob Storage. Choose the storage driver deliberately because the backup plan must cover both the PostgreSQL database and uploaded files.

A practical recovery check has three parts:

• restore the database into a clean environment;
• restore or reconnect the file-storage location;
• open representative pages and attachments through the restored application.

Do not call a database dump a complete backup when attachments live elsewhere. Keep at least one recovery copy off the VPS and run a restore drill before the wiki becomes the only copy of important procedures.

Choose a VPS by billing and recovery constraints

Docmost does not need a provider chosen by a synthetic score. The useful distinction is how each server fits the deployment lifecycle, storage plan and location requirement.

Affiliate disclosure: the provider links below are affiliate links. SelfHostVPS may receive compensation if you order through them, at no added cost to you. The technical criteria do not change based on compensation.

Hetzner Cloud

Hetzner documents hourly billing with a monthly price cap. That model can fit a short pilot while still giving a predictable ceiling for a server that remains online. Check the current region, CPU type, public IP, storage, traffic and backup terms before ordering.

Check current Hetzner Cloud options

Contabo

Contabo documents Core, Performance and Storage VPS families with fixed RAM and storage allocations. Its VPS documentation also notes that plan-family changes and some storage moves require a reinstall and data migration. That tradeoff matters when attachments are expected to grow.

Check current Contabo VPS options

Vultr

Vultr Cloud Compute is a shared-CPU virtual machine family with regional deployment and hourly billing. Vultr says a stopped instance continues to bill because its resources remain reserved; destroying it is what ends the compute charge. This makes the teardown and backup procedure part of the cost plan.

Check current Vultr Cloud Compute options

No cross-provider Docmost benchmark was run for this page. The three links are current options to evaluate, not proof that one provider is universally fastest or cheapest. If provider selection is the remaining question, use the separate Docmost VPS comparison and verify every current offer at checkout.

A team-ready launch sequence

1. Decide whether Community contains the access controls the organization needs.
2. Create the workspace, spaces and groups on paper before inviting users.
3. Deploy the official Compose stack behind HTTPS with working WebSockets.
4. Configure email and send a real invitation to a test account.
5. Choose local, S3-compatible or Azure storage and document where files live.
6. Back up PostgreSQL and file storage, then prove a restore in a clean environment.
7. Import a small Markdown or HTML sample before a large migration.
8. Monitor memory, disk growth and application response time during normal use.
9. Assign a named owner and review date to operational pages that must stay current.

This sequence catches edition, permission and recovery mistakes before a large content migration makes them expensive.

When Community is enough

Community is a reasonable fit when space-level roles are sufficient and the team can operate the server, email, storage, backups and upgrades. It still includes the core page editor, real-time collaboration, spaces, groups, page history, search and common import and export paths.

Business becomes relevant when the team needs page-level restrictions, SSO, MFA, API access or other commercial features listed on the current pricing page. Enterprise adds governance controls such as audit logs, SIEM and SCIM. Do not buy a larger VPS to solve a feature boundary that actually belongs to the license.

For a pilot that may become permanent, compare the current server and contract terms here:

• Review current Hetzner Cloud terms
• Review current Contabo VPS terms

Official sources

All source links below were checked on 23 October 2026.

• Docmost pricing and edition comparison
• Docmost license and editions
• Docmost spaces and roles
• Docmost groups
• Docmost page permissions
• Docmost installation
• Docmost reverse proxy and WebSockets
• Docmost email and storage configuration
• Docmost import and export
• Hetzner Cloud billing FAQ
• Contabo VPS documentation
• Vultr server billing