Papra Self-Hosted

Lightweight document archive with text extraction, organization sharing, tagging and search.

8 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Upstream Docker/Compose installation or a community Railway template with persistent database storage and a document bucket.

  2. Operated by

    Your team

    Customer manages application access, secrets, storage, backups and updates. Railway operates its underlying platform; the community template runs in the customer project.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodUpstream Docker/Compose installation or a community Railway template with persistent database storage and a document bucket.
InfrastructureServers / containers
Persistent application container with SQLite/libSQL metadata and local or object document storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.
Licensing modelOpen Source / Open Core
The self-hosted Papra application is AGPL-3.0. Hosted Papra service terms are separate; a chart or wrapper license does not replace application terms.
LicenseAGPL-3.0; dependencies and independently maintained packaging retain their own terms.

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.

4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The self-hosted configuration supports GitHub and Google OAuth sign-in and a configurable list of custom OAuth providers through Better Auth. This establishes external sign-in, not SAML support or enterprise provisioning; configure the chosen provider and registration policy.

Self-hosted OAuth provider configuration · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official Docker guide identifies ghcr.io/papra-hq/papra, recommends the rootless variant and documents persistent database/document storage and AUTH_SECRET. The default latest tag moves.

Upstream Papra application image; not the separate CLI package release · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The official Docker guide documents persistent application data and optional extraction components but does not give a validated CPU/RAM minimum. Size document storage, extraction concurrency and any external models separately; a one-container command is not HA sizing.

Self-hosted Docker distribution; numeric production sizing unresolved · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The upstream project is licensed under AGPL-3.0. This records the source licence; it does not price infrastructure, hosted service, optional model providers or support.

Papra upstream core source licence · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Show all fields (8 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.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

The reviewed application release is 26.7.1; Papra fixes only the latest version. Pin a current image and preserve database, documents and encryption keys together. The Railway wrapper adds initial-account setup and storage permissions; Mailpit captures mail until a real relay is configured. Optional OCR/model services, intake email and webhooks can send content outside the installation.

Community & maintenance

The upstream changelog records continuing application releases and fixes, including 26.7.1, and contributions from external participants. The contributor history and community packaging provide participation signals beyond star counts; this does not establish enterprise support or production suitability for every workload.

Category fit

Document management
Stores documents with extracted text, tags, custom properties, organization access and full-text retrieval. This is a lightweight archive, not a formal records-retention or legal-hold system.

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
    Customer-operated · Commercial Only
  • Alfresco Content Services + Governance ServicesCustomer-operated content and records management with retention and record-declaration workflows.
    • AWS
    Customer-operated · Open Source / Open Core
  • Apache JSPWikiApache file-based wiki for documentation and knowledge content.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • DocassembleSelf-hosted guided interviews and automated document assembly.
    • AWS
    • Hostinger
    Customer-operated · Open Source / Open Core
  • DocspellSelf-hosted document ingestion, OCR, classification and search.
    • Railway
    • Hostinger
    Customer-operated · Open Source / Open Core
  • DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
    • Azure
    Customer-operated · Commercial Only
  • eLabFTWOpen-source electronic laboratory notebook for tracked experiments, procedures and attached records.
    • Hostinger
    Customer-operated · Open Source / Open Core

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

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Community Papra application deployment in a Railway project ↗ · Railway

      Community template · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Deploys the application, persistent metadata volume, document bucket and mail-capture service into the customer Railway project. This is independent packaging, not upstream support certification. Review the wrapper and pin a current application image; retain storage/encryption secrets and configure a production mail relay.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory