HedgeDoc Hosting Live In 5 Minutes

HedgeDoc is a free, open-source collaborative Markdown editor. Multiple people can edit the same note in real time, with revision history, configurable sharing permissions, and support for meeting notes, runbooks, technical plans and shared documentation. This template deploys version 1.11.1.

Yes — that is exactly what this is. HedgeDoc is AGPL-3.0 licensed and designed to be self-hosted. On xCloud it is a OneClick app, so the pinned HedgeDoc 1.11.1 container, its own PostgreSQL sidecar, the private container network, the domain and the SSL certificate are provisioned for you in about five minutes instead of assembled by hand.

Pinned, verified images rather than a floating latest tag: the HedgeDoc application image pinned to 1.11.1, and a private PostgreSQL sidecar HedgeDoc alone can reach. The HedgeDoc origin (container port 3000) is bound to localhost and reverse-proxied by xCloud nginx, so the container is never directly exposed to the internet. Existing servers stay on their installation snapshot until you choose to upgrade.

On two named persistent volumes: hedgedoc_db, the PostgreSQL data directory holding accounts, notes, revisions and permissions, and hedgedoc_uploads, the files attached to notes. Both survive a container restart or redeploy, and both need to be captured together for a restore to make sense.

A database name and user prefixed hedgedoc_, a random 32-character database password, and a 64-byte session secret — generated once at install and shown in your xCloud credential panel alongside the site URL. PostgreSQL only reads its POSTGRES_DB, POSTGRES_USER and POSTGRES_PASSWORD environment variables when hedgedoc_db is empty; editing them later does not update the existing database or role, so PostgreSQL and the HedgeDoc database URL have to be changed together, and the session secret should stay stable once notes exist.

"Allow email registration" is enabled by default so you can create the first account. Once your team is onboarded, open the xCloud Environment editor, set email registration to disabled, and redeploy. Existing accounts and notes are unaffected — this only closes new public sign-ups.

Not out of the box for local accounts — HedgeDoc's built-in username/password login has no self-service password reset and no native two-factor authentication. If you need either, configure an external identity provider (OAuth2, LDAP, SAML or similar) that HedgeDoc supports, rather than relying on the local login alone.

The template manifest asks for 1024 MB of RAM, 1 CPU core and 5 GB of disk as a floor. This page sells the 6 GB tier, comfortably above that. A small team with light note volume can start near the floor; an active team with a longer history should size RAM and disk with headroom, and upload-heavy teams should size disk and backup storage around expected attachment growth.

Back up hedgedoc_db and hedgedoc_uploads from the same window — a database dump alone loses attachments, and uploads alone lose every account, note and revision. Use PostgreSQL's own pg_dump for an application-consistent database copy, preserve the uploads volume alongside it, keep tested copies off the application server, and exercise a restore on a schedule. A server snapshot by itself is not proof of a restorable, application-consistent backup.

Backups in xCloud

No. The template pins HedgeDoc 1.11.1 so new installations stay deterministic; a catalog re-sync affects new installs only; existing sites keep their install snapshot until you choose to update. Before updating, read HedgeDoc's upstream release notes, back up both persistent volumes, preserve the Compose project identity and both volume names, recreate containers without deleting volumes, and test login, note history, uploads and collaboration afterward. Treat a PostgreSQL major-version change as a separate migration to plan for, not something an app update does for you.

No. We claim no official partnership, endorsement or upstream support relationship with the HedgeDoc project. This is a deployment and server-management option for the open-source, AGPL-3.0-licensed application.

Yes. It is a dedicated Cloud VPS, not a locked appliance, so you can deploy other OneClick apps or your own sites beside it as long as the resources are there.

Yes. There is no lock-in — cancel any time. Hosting is billed monthly and charged for what you actually use, so when you delete the server the unused balance is refunded to your account, less up to 10% in payment-processing fees.