Paperless-ngx
Community document management with OCR, full-text search, metadata and ingestion workflows.
7 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Paperless-ngx permissions and MFA defaults review
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.
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.
Primary source · Reviewed 2026-11-17
What lands where
Supplied by
Vendor or project
Official Docker Compose installer; provider tutorial on Vultr or a community Railway application/database/queue template.
Runs in
Documented customer environment
Application, OCR and background worker processes with persistent documents, PostgreSQL and Redis
- Vultr: Customer cloud account
- Railway: Customer platform workspace
- Railway
- Vultr
Servers / containers
Operated by
Your team
Customer operates application permissions, ingestion, backups, secrets and upgrades. Railway manages its platform resources; a Vultr VM also requires customer OS/container maintenance.
Deployment boundaries by provider
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Vultr-hosted Paperless-ngx application deployment guide ↗ · Source checked 2026-11-13
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Community Railway Paperless-ngx stack ↗ · Source checked 2026-11-13
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official Docker Compose installer; provider tutorial on Vultr or a community Railway application/database/queue template. |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core The listed community application is GPL-3.0; optional integrations and container dependencies retain their own terms. |
| License | GPL-3.0; conversion tools and other bundled components have separate licenses. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Upstream self-hosted authentication configuration · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Upstream PostgreSQL-backed recipe; different provider templates may package other releases · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Provider-authored single-server recipe; version and workload qualification required · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Upstream Paperless-ngx core licence · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Upstream paperless-ngx/paperless-ngx release record; commercial editions, LTS branches and provider packages can differ · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
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.
Community & 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.
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.
Compare within Document management
- Adobe Experience Manager 6.5 Forms (Correspondence Management)Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.
- AWS
- Azure
- Alfresco Content Services + Governance ServicesCustomer-operated content and records management with retention and record-declaration workflows.
- AWS
- Apache JSPWikiApache file-based wiki for documentation and knowledge content.
- Hostinger
- Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
- AWS
- Azure
- DocassembleSelf-hosted guided interviews and automated document assembly.
- AWS
- Hostinger
- DocspellSelf-hosted document ingestion, OCR, classification and search.
- Railway
- Hostinger
- DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
- Azure
- eLabFTWOpen-source electronic laboratory notebook for tracked experiments, procedures and attached records.
- Hostinger
Showing 8 of 41 other listings in Document management. These products address related workflows; read their category-fit notes before comparing scope. See all of Document management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Upstream Compose installation and project scope ↗github.com
- Vultr Docker Compose deployment with PostgreSQL and TLS ↗docs.vultr.com
- AI workflow advisory; use current patched releases ↗github.com
- Community Railway Paperless-ngx stack ↗railway.com
- Upstream license ↗github.com
- Reviewed 3.5.0 release and upgrade note ↗github.com
- Contributor history ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Vultr-hosted Paperless-ngx application deployment guide ↗ · Vultr
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Community Railway Paperless-ngx stack ↗ · Railway
Community template · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Vultr-hosted Paperless-ngx application deployment guide ↗ · Vultr
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Reviewed 3.5.0 release and upgrade note ↗github.com
- Contributor history ↗github.com