
# Papra Self-Hosted



Canonical page: https://launchinyourcloud.com/directory/papra/
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.


## Papra Self-Hosted

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

- Listing: https://launchinyourcloud.com/directory/papra/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0; dependencies and independently maintained packaging retain their own terms.
- Licensing model: open-source
- Installation: Upstream Docker/Compose installation or a community Railway template with persistent database storage and a document bucket.
- Architecture: Persistent application container with SQLite/libSQL metadata and local or object document storage
- Operations: Customer manages application access, secrets, storage, backups and updates. Railway operates its underlying platform; the community template runs in the customer project.
- Product website: https://papra.app/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

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.

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.

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.


### 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.

### Deployment boundaries


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


### Cloud deployment evidence

- Community Papra application deployment in a Railway project (railway): https://railway.com/deploy/papra-dms
  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.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-13.

- Application changelog and external contributions: https://docs.papra.app/changelog/

- Upstream contributor history: https://github.com/papra-hq/papra/graphs/contributors

### Sources

- Official Docker installation and persistence: https://docs.papra.app/self-hosting/using-docker/

- Application configuration: https://docs.papra.app/self-hosting/configuration/

- Internal and external content extraction: https://docs.papra.app/guides/content-extraction/

- Railway wrapper source and initialization: https://github.com/gridalpha/papra-railway

- Community Papra application deployment in a Railway project: https://railway.com/deploy/papra-dms

- Upstream application license: https://github.com/papra-hq/papra/blob/main/LICENSE

- Application changelog and external contributions: https://docs.papra.app/changelog/

- Upstream contributor history: https://github.com/papra-hq/papra/graphs/contributors

### Licensing sources

- https://github.com/papra-hq/papra/blob/main/LICENSE

### Infrastructure sources

- https://docs.papra.app/self-hosting/using-docker/

- https://railway.com/deploy/papra-dms


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 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. 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. Scope: Self-hosted OAuth provider configuration. Source: https://docs.papra.app/self-hosting/configuration/ (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 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. Scope: Upstream Papra application image; not the separate CLI package release. Source: https://docs.papra.app/self-hosting/using-docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. 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. Scope: Self-hosted Docker distribution; numeric production sizing unresolved. Source: https://docs.papra.app/self-hosting/using-docker/ (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Papra upstream core source licence. Source: https://raw.githubusercontent.com/papra-hq/papra/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






