Application hosting

Hosting Docmost

Docmost gives a team a shared wiki for procedures, project notes and internal documentation. Several people can edit together, organise pages into spaces and discuss changes in comments. Page history helps a team follow how an instruction changed instead of passing around competing document copies. Its editor also supports diagrams and file attachments.

Requirements last checked 17 Oct 2026 against the project's documentation.

Compare server plans Size a server

Understand the setup

Find the software and services needed to run the application.

See requirements

Budget your resources

Plan memory, storage and CPU for the way you will use it.

Open resource planner

Build your shortlist

Compare plans for the starting size, then review the provider and billing terms.

See plans

Must have

Installation requirements

A host capable of running the chosen Docmost containers.
PostgreSQL and Redis services reachable by Docmost.
Persistent storage for database contents and uploaded attachments.

Recommended

Planning guidance

Use the resource planner to size a server for your workload.

Choosing a server for Docmost

Team size, simultaneous editing and attachment volume affect the deployment. The database, Redis and file storage need resources alongside the web service; an attachment-heavy wiki is a storage workload as well as an editor.

Deploy with

Supported paths

Docker Compose

The host must provide

Runtime

Database: PostgreSQL; follow the database image and upgrade instructions paired with the selected release.
Cache and coordination: Redis with persistent storage in the Docker Compose setup.

Storage

Persistent data

Back up the PostgreSQL database and attachment storage together. Preserve application configuration and the application secret so recovery does not depend on recreating the original container.

Step by step

Plan a Docmost deployment

Prepare the services

Use the release’s Compose configuration and keep database and attachment paths persistent.
Official instructions
Configure the public address

Set the external application URL, a private application secret and database credentials. Put HTTPS in front of the service.
Official instructions
Organise team access

Create spaces and groups around who should read or edit each collection, then check access using an ordinary member account.
Official instructions

Security

Before you go public

Keep PostgreSQL and Redis off the public internet.
Replace example secrets before use and restrict who can administer the workspace.

Cost

Beyond the server price

Self-hosting includes application compute, database storage and backups.
The core and Enterprise features have different licensing; check the feature set before assuming a paid feature is included.

Want the full monthly bill? Use the hosting cost calculator. Add storage, backups and other costs to your estimate.