HostCritiq
Search ⌘K
Menu

Application hosting

Hosting HedgeDoc

HedgeDoc is a shared Markdown editor for meeting notes, technical documents and presentations. Several people can work on a note at the same time in a browser, with revisions to follow or reverse changes. It fits teams that prefer writing in Markdown and sharing a document link over installing a desktop editor. Diagrams and presentation mode make it useful beyond plain text notes.

Requirements last checked 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 compatible amd64 or arm64 host for the official Docker image.
  • Docker Compose for the documented container setup.
  • A database and persistent uploaded-file storage.

Recommended

Planning guidance

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

Choosing a server for HedgeDoc

Simultaneous editing and attachment uploads are more useful sizing inputs than the number of registered accounts alone. Keep room for the database and uploads, and monitor growth after the team starts using the service.

Deploy with

Supported paths

  • Docker Compose
  • Manual installation

The host must provide

Runtime

Database
PostgreSQL in the official Docker example; follow the selected HedgeDoc 1.x release instructions.

Storage

Persistent data

Back up the database, uploaded files and configuration together. Notes and their attachments live in different parts of the deployment, so keeping only a database dump can leave a restored document without its images.

Step by step

Plan your HedgeDoc deployment

  1. Prepare persistent services

    Use the HedgeDoc 1.x container instructions and set up persistent database and upload volumes.

    Official instructions
  2. Configure the public address

    Set the correct external domain and HTTPS settings, and use a reverse proxy that forwards WebSocket connections.

    Official instructions
  3. Choose team access

    Set the login provider and default note permissions before inviting the team.

    Official instructions

Security

Before you go public

  • Replace example database passwords and keep the database private.
  • Decide whether anonymous note creation is appropriate; restrict it for a private team workspace.
  • Keep operational metrics private if they expose information you do not intend to share.

Cost

Beyond the server price

  • Budget for the web service, database, attachments and recovery copies.
  • The self-hosted project uses AGPL-3.0; identity-provider and hosting costs depend on your deployment.

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