DocManFu

Deploy guide

Private document management on a VPS.

A small virtual private server gives you a document archive reachable from anywhere, without handing your files to a document SaaS.

Installation stepsDeployment guide

Why it fits

Why run DocManFu on a VPS

  • Access your archive from any browser
  • Predictable monthly infrastructure cost, no per-seat fees
  • No hardware to maintain at home

Before you install

Setup notes

  1. 1Choose a server with at least 2 GB of RAM and enough disk for your archive
  2. 2Put DocManFu behind HTTPS with Caddy, Traefik, or another reverse proxy
  3. 3Use strong unique secrets and keep Docker and the OS updated
  4. 4Back up PostgreSQL and document storage to a separate provider

What you get

The full DocManFu stack on a VPS

DocManFu runs as one Docker Compose stack: web app, API, PostgreSQL, Redis, and a background OCR worker. Anywhere Docker Engine and Docker Compose v2 run, DocManFu can run. OCR happens locally, AI is optional and can run locally with Ollama, and your documents stay on storage you control.

git clone https://github.com/DocManFu/DocManFu.git
cd DocManFu
cp .env.production.example .env   # set POSTGRES_PASSWORD and JWT_SECRET_KEY
./prod up -d

Other ways to self-host

Synology NASUnraidTrueNAS SCALEProxmoxHome serverDocker Desktop

What will you store?

BillsTax documentsMedical recordsReceiptsInsurance documentsBank statementsWarranties and manualsPay stubsHome and property documentsSchool records

Your documents. Your rules.

Ready to master the paper pile?

One Docker Compose command puts a private, searchable document vault on hardware you control. Prefer not to self-host? A hosted version is coming soon—ask @DustinDavis on X.

Start self-hostingView on GitHub ↗