
# Paperless-ngx



Canonical page: https://launchinyourcloud.com/directory/paperless-ngx/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Paperless-ngx

Community document management with OCR, full-text search, metadata and ingestion workflows.

- Listing: https://launchinyourcloud.com/directory/paperless-ngx/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-3.0; conversion tools and other bundled components have separate licenses.
- Licensing model: open-source
- Installation: Official Docker Compose installer; provider tutorial on Vultr or a community Railway application/database/queue template.
- Architecture: Application, OCR and background worker processes with persistent documents, PostgreSQL and Redis
- Operations: Customer operates application permissions, ingestion, backups, secrets and upgrades. Railway manages its platform resources; a Vultr VM also requires customer OS/container maintenance.
- Product website: https://docs.paperless-ngx.com/
- Source review: 2026-11-17; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Review used upstream 3.5.0. Pin a current image before importing documents and coordinate database/document backups. The canonical Railway template uses a mutable latest tag; its setup text does not certify production readiness. An older separately reviewed 3.0.5 template predates an AI-permission fix and is not the recommended package. Optional email, document converters and AI integrations need separate access and data-flow review. Release 3.5.0 moves bulk operations to asynchronous processing, adds manual workflow triggers, tightens configuration-view and descendant-tag permissions, clears sessions automatically, and fixes the default MFA trusted-authentication setting. Some installations must adjust PAPERLESS_ALLOWED_HOSTS before upgrading.

The listed community application is GPL-3.0; optional integrations and container dependencies retain their own terms.

Application, OCR and background worker processes with persistent documents, PostgreSQL and Redis. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- document-management: Scans, OCRs, classifies and searches documents with tags, correspondents, metadata and processing workflows. Do not equate personal/team archiving with regulated retention or legal hold.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system (checked 2026-11-13). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/paperless-ngx (checked 2026-11-13). 


### Cloud deployment evidence

- Vultr-hosted Paperless-ngx application deployment guide (vultr): https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system
  Provider documentation installs the application, database, queue and HTTPS reverse proxy on an operator-controlled Linux server. Pin compatible current images, protect persistent document/database paths and manage VM updates. This establishes hosting guidance, not upstream vendor support.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Community Railway Paperless-ngx stack (railway): https://railway.com/deploy/paperless-ngx
  The template provisions the application with PostgreSQL, Redis and a persistent volume in the customer project. Railway operates the platform. Pin and verify a current patched application image and volume paths against upstream instructions; the template documentation is not a tested deployment guarantee.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

The community maintains repeated releases, a public security-advisory process, and substantial contributions from multiple maintainers. The reviewed 3.5.0 release adds workflow improvements and permission, session, and MFA fixes from distinct contributors; admission does not depend on popularity counts.

Reviewed 2026-11-17.

- Reviewed 3.5.0 release and upgrade note: https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0

- Contributor history: https://github.com/paperless-ngx/paperless-ngx/graphs/contributors

### Sources

- Upstream Compose installation and project scope: https://github.com/paperless-ngx/paperless-ngx

- Vultr Docker Compose deployment with PostgreSQL and TLS: https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system

- AI workflow advisory; use current patched releases: https://github.com/paperless-ngx/paperless-ngx/security/advisories/GHSA-c8f3-pqr2-rr24

- Community Railway Paperless-ngx stack: https://railway.com/deploy/paperless-ngx

- Upstream license: https://github.com/paperless-ngx/paperless-ngx/blob/main/LICENSE

- Reviewed 3.5.0 release and upgrade note: https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0

- Contributor history: https://github.com/paperless-ngx/paperless-ngx/graphs/contributors

### Licensing sources

- https://github.com/paperless-ngx/paperless-ngx/blob/main/LICENSE

### Infrastructure sources

- https://github.com/paperless-ngx/paperless-ngx

- https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system

- https://railway.com/deploy/paperless-ngx


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. OIDC sign-in is documented through django-allauth providers. Configure the provider application and PAPERLESS_SOCIALACCOUNT_PROVIDERS; group mapping and trusted-proxy settings require separate review. Scope: Upstream self-hosted authentication configuration. Source: https://raw.githubusercontent.com/paperless-ngx/paperless-ngx/main/docs/configuration.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream PostgreSQL Compose example records required environment files, persistent data/import/export storage and application services. Review the matching release and credentials before deploying. Scope: Upstream PostgreSQL-backed recipe; different provider templates may package other releases. Source: https://github.com/paperless-ngx/paperless-ngx/blob/main/docker/compose/docker-compose.postgres.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/paperless-ngx/paperless-ngx/blob/main/docker/compose/docker-compose.postgres.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. Vultr's deployment example requires at least 2 CPU cores and 4 GB RAM for its application, PostgreSQL, Redis and reverse-proxy stack. It uses an older application image; this provider example is not an upstream HA minimum or a sizing guarantee for the current release. Scope: Provider-authored single-server recipe; version and workload qualification required. Source: https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system (reviewed 2026-11-20).

- License pricing: Documented. The upstream core uses GPL-3.0. This records source-code licensing, not an infrastructure, support or managed-hosting price. Bundled conversion tools have their own terms. Scope: Upstream Paperless-ngx core licence. Source: https://raw.githubusercontent.com/paperless-ngx/paperless-ngx/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is v3.5.0, published 2026-11-17. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream paperless-ngx/paperless-ngx release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0 (reviewed 2026-11-17).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Paperless-ngx permissions and MFA defaults review (security-advisory): Release 3.5.0 fixes configuration/tag permissions and the default trusted-authentication behavior for MFA, and adds session cleanup. Scope: Upstream Paperless-ngx 3.5.0 release fixes; no CVE or complete affected-version range is established by this release record. Conditions: Authentication mode, tag inheritance and configuration permissions determine applicability. Provider templates may use different image tags. Action: Pin the selected image, back up documents and the database, review PAPERLESS_ALLOWED_HOSTS and verify permissions and MFA configuration after upgrading. Source: https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0; reviewed 2026-11-17.



