Deployment
Docker & GPU
Docker support: Yes
GPU: Not required
Check the source notes below before assuming a GPU, transcoding workload or machine-learning feature is included in the baseline deployment.
Productivity / Finance
Document management system that scans indexes and archives documents with OCR
Requirements
Badges are attached to each value. An estimate is never presented as an official project requirement.
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | 2 GB Estimated | 4 GB Estimated |
| CPU | 2 vCPU Estimated | 2-4 vCPU Estimated |
| Disk | 10 GB + archive size Estimated | Not stated Not stated |
Disk figures describe the application footprint recorded in the dataset. Personal media, documents, backups and other user data can require substantially more storage.
RunOnVPS sizing suggestion
4 GB RAM tier
This is our sizing suggestion, derived from Paperless-ngx’s recommended RAM of 4 GB. It is not an official requirement and it does not guarantee that every workload, plug-in set or media library will fit comfortably.
Affiliate link placeholder — no provider selectedThis placeholder intentionally has no URL or affiliate ID in the Day 2 build.
Deployment
Docker support: Yes
GPU: Not required
Check the source notes below before assuming a GPU, transcoding workload or machine-learning feature is included in the baseline deployment.
Commercial alternative
Google Drive / Dropbox
Paperless-ngx is catalogued here as a self-hosted alternative to Google Drive / Dropbox. Feature parity varies, so compare your required workflow before migrating.
Source check
Official docs do not publish a hardware minimum (checked 2026-10-24); estimates based on the official Docker Compose stack (webserver + PostgreSQL + Redis; optional Tika/Gotenberg add overhead). OCR is CPU-intensive and disk use scales with the document archive. Stars approximate as of 2026-10-24.
Data source: https://docs.paperless-ngx.com/
Project repository: https://github.com/paperless-ngx/paperless-ngx
Keep comparing