
# Document management on Railway

Compare documented Document management deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/document-management/
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.


## Provider guidance

- Account boundary: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### Project networking

Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

The listings below have evidence for Railway. Read each cloud evidence note for the applicable package, edition and support qualifications.

7 listings.


## Docspell

Self-hosted document ingestion, OCR, classification and search.

- Listing: https://launchinyourcloud.com/directory/docspell/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: Docspell REST server and job executor sharing PostgreSQL and durable document storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docspell.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Docspell REST server and job executor sharing PostgreSQL and durable document storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted document ingestion, OCR, classification and search.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/docspell (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/docspell-1 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/docspell
  Docspell REST server and job executor sharing PostgreSQL and durable document storage. The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/docspell-1
  Docspell REST server and job executor sharing PostgreSQL and durable document storage. The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes eikek, scala-steward, eikek-scala-steward, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/eikek/docspell/graphs/contributors

- Upstream project: https://github.com/eikek/docspell

### Sources

- Hostinger: https://www.hostinger.com/applications/docspell

- Railway: https://railway.com/deploy/docspell-1

- AGPL-3.0 LICENSE.txt: https://raw.githubusercontent.com/eikek/docspell/master/LICENSE.txt

- GitHub Releases: https://github.com/eikek/docspell/releases

### Licensing sources

- https://raw.githubusercontent.com/eikek/docspell/master/LICENSE.txt

### Infrastructure sources

- https://www.hostinger.com/applications/docspell

- https://railway.com/deploy/docspell-1


### 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. The upstream server supports OIDC/OAuth2 sign-in using a configured external provider; multiple providers are supported and Keycloak configuration is documented. Configure registration, collective mapping and provider settings for the selected release. Scope: Self-hosted Docspell REST server authentication. Source: https://docspell.org/docs/configure/authentication/ (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 project maintains a Compose deployment for the REST server, job executor, PostgreSQL and full-text search. Change the documented secrets, persist data and pin compatible image versions; moving latest/nightly tags are not immutable releases. Scope: Upstream Compose deployment; single-machine default, not HA. Source: https://docspell.org/docs/install/docker/ (reviewed 2026-11-20). Deployment artifact: https://github.com/docspell/docker/tree/master/docker-compose. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. The project recommends 4 GB RAM for a small board running Joex with its database and Solr, with Joex pool size 1. Its example 1-CPU/4-GB VM is a processing illustration, not validated 100-user, 1-TB or HA capacity; OCR languages and classification affect memory. Scope: Upstream low-resource example; not production/HA workload sizing. Source: https://docspell.org/docs/install/rpi/ (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Docspell; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/eikek/docspell/master/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v0.43.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Docspell upstream application; verify compatibility with the selected package. Source: https://github.com/eikek/docspell/releases/tag/v0.43.0 (reviewed 2026-11-19).







## Memos

Self-hosted lightweight notes, documents and knowledge timeline.

- Listing: https://launchinyourcloud.com/directory/memos/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment; Docker / Compose
- Architecture: Memos application, SQLite database and attachment storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://usememos.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Memos application, SQLite database and attachment storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted lightweight notes, documents and knowledge timeline.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/memos.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/memos-3 (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/memos.html
  The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/memos-3
  Memos application, SQLite database and attachment storage. Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes boojack, johnnyjoygh, athurg, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/usememos/memos/graphs/contributors

- Upstream project: https://github.com/usememos/memos

### Sources

- Cloudron Store: https://www.cloudron.io/store/memos.html

- Railway: https://railway.com/deploy/memos-3

- Hostinger: https://www.hostinger.com/applications/memos

- MIT LICENSE: https://raw.githubusercontent.com/usememos/memos/main/LICENSE

- GitHub Releases: https://github.com/usememos/memos/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://raw.githubusercontent.com/usememos/memos/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/memos.html

- https://railway.com/deploy/memos-3


### 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. Memos documents external OAuth2/SSO providers separately from local passwords and API tokens. Providers map a stable external identity to a local user; account linking and registration policy control admission. Password login can be disabled for regular users while retaining an admin recovery path. Scope: Self-hosted Memos current authentication configuration; verify compatibility with the installed release and any provider package. Source: https://usememos.com/docs/configuration/authentication (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 deployment guide provides a Docker container with persistent application data; its README also links Compose, Kubernetes and binary options. Choose a published version and compatible database/configuration, then configure HTTPS, backups and instance authentication. Scope: Self-hosted Memos application/data deployment; not a complete HA cloud stack. Source: https://usememos.com/docs/deploy/docker (reviewed 2026-11-20). Deployment artifact: https://github.com/usememos/memos. Artifact reference: main (moving branch); 26.11.1 release snapshot is recorded separately.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/memos.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Memos; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/usememos/memos/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 26.11.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Memos upstream application; verify compatibility with the selected package. Source: https://github.com/usememos/memos/releases/tag/26.11.1 (reviewed 2026-11-19).







## Nextcloud Server

Self-hosted file synchronization and sharing server for team document collaboration.

- Listing: https://launchinyourcloud.com/directory/nextcloud-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 Server core; review selected applications separately
- Licensing model: open-source
- Installation: Official Nextcloud AIO or documented Linux/PHP server installation
- Architecture: Persistent web application, SQL database and file storage; the documented manual installation uses a Linux, Apache, MariaDB and PHP stack.
- Operations: Customer operates the server, storage, backups and upgrades; select a supported release and deployment method.
- Product website: https://nextcloud.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the self-hosted Server and file-sharing capabilities. The installation manual distinguishes official AIO from community Snap, VM and Docker options, which Nextcloud GmbH does not officially support. Review separately selected applications, integrations and enterprise support terms.

This classification covers Nextcloud Server, whose repository provides the GNU Affero GPL version 3. It does not classify every separately installed application or commercial service.

The official manual documents a persistent Linux web/database installation and an official AIO deployment.


### Category fit

- document-management: File synchronization, sharing and collaborative file workspaces; this entry does not establish regulated records-management capabilities.

- collaboration: Shared file workspaces for teams, with additional collaboration applications available in the Nextcloud ecosystem.

### Deployment boundaries


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


### Cloud deployment evidence

- Nextcloud Server community deployment on Railway (railway): https://railway.com/deploy/nextcloud
  The community template deploys the official Nextcloud container with PostgreSQL, a persistent application volume and bucket storage in a customer Railway project. Review the selected release, trusted domains/proxies, background jobs, object-storage configuration and backups. Optional Office, Talk and third-party apps can require additional services; they are not implied by this server deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Official case studies describe self-hosted or on-premise deployments at Milieudefensie, CSIC and Sorbonne University. The official changelog records the 35.0.3 maintenance release on November 12, 2026. These are product adoption and maintenance signals, not a claim that each adopter uses the same edition or installation method.

Reviewed 2026-11-13.

- Organizational deployments and customer stories: https://nextcloud.com/customers/

- Server maintenance releases: https://nextcloud.com/changelog/

### Sources

- Linux installation and deployment options: https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html

- Nextcloud Files capabilities: https://nextcloud.com/files/

- Nextcloud Server license: https://raw.githubusercontent.com/nextcloud/server/master/COPYING

- Nextcloud maintenance changelog: https://nextcloud.com/changelog/

- Official customer implementation stories: https://nextcloud.com/customers/

### Licensing sources

- https://raw.githubusercontent.com/nextcloud/server/master/COPYING

### Infrastructure sources

- https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html


### 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. The Nextcloud-maintained SSO/SAML app supports SAML 2.0 and environment-based authentication. Enable a compatible app release and configure the provider; the repository distinguishes tested providers from theoretical protocol compatibility. Scope: Nextcloud SSO/SAML application; server/app compatibility must be checked. Source: https://github.com/nextcloud/user_saml (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Nextcloud AIO publishes a multi-container application bundle. Review its host/volume/port requirements and enabled optional services; the bundle has a different footprint from a minimal PHP server installation. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/nextcloud/all-in-one (reviewed 2026-11-14). Deployment artifact: https://github.com/nextcloud/all-in-one. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The versioned manual lists 128 MB minimum and 512 MB recommended RAM per PHP process. This is not a total host/AIO minimum: database, concurrent processes, apps, previews and storage need additional resources. Scope: Nextcloud 33 per-process memory, not whole-server sizing. Source: https://docs.nextcloud.com/server/33/admin_manual/installation/system_requirements.html (reviewed 2026-11-14).

- License pricing: Documented. The Server core is AGPL-3.0. This does not price Enterprise support, optional applications, hosting or operating labour; review those separately for the selected deployment. Scope: Nextcloud Server core; applications and commercial subscriptions excluded. Source: https://raw.githubusercontent.com/nextcloud/server/master/COPYING (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v33.0.11, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream nextcloud/server release record; commercial editions and deployment packages may differ. Source: https://github.com/nextcloud/server/releases/tag/v33.0.11 (reviewed 2026-11-14).







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




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







## Safebucket

Open-source on-premises file-sharing software with a community Railway deployment.

- Listing: https://launchinyourcloud.com/directory/safebucket/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Safebucket application, PostgreSQL and MinIO-backed object storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.safebucket.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The template follows moving images. Activity and notifier defaults can use ephemeral filesystem storage; configure durable activity logging and outbound notification services before relying on audit records or external-sharing workflows.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Safebucket application, PostgreSQL and MinIO-backed object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Open-source on-premises file-sharing software with a community Railway deployment.

- data-rooms-ma-document-management: Open-source on-premises file-sharing software with a community Railway deployment.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/safebucket
  Safebucket application, PostgreSQL and MinIO-backed object storage. The template follows moving images. Activity and notifier defaults can use ephemeral filesystem storage; configure durable activity logging and outbound notification services before relying on audit records or external-sharing workflows.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes yohanleb, Renizmy, pedorich-n, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/safebucket/safebucket/graphs/contributors

- Upstream project: https://github.com/safebucket/safebucket

### Sources

- Railway Template: https://railway.com/deploy/safebucket

- GitHub README: https://github.com/safebucket/safebucket

- Apache-2.0 LICENSE: https://github.com/safebucket/safebucket/blob/main/LICENSE

- GitHub Releases: https://github.com/safebucket/safebucket/releases

### Licensing sources

- https://github.com/safebucket/safebucket/blob/main/LICENSE

### Infrastructure sources

- https://railway.com/deploy/safebucket


### 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. The official README documents user SSO through an external OpenID Connect provider, with local accounts for external users. Provider, redirect/origin and role settings must be configured for the installed release; this is not a SAML or SCIM support claim. Scope: Safebucket v0.8.1 upstream user authentication; match the selected provider package and OIDC configuration. Source: https://github.com/safebucket/safebucket/blob/v0.8.1/README.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 official full-stack local recipe publishes Compose definitions for Safebucket, PostgreSQL, RustFS, Valkey, NATS, Loki and Mailpit. It is a production-like local environment with sample credentials and test email, so production secrets, storage, email, HTTPS and resilience require separate configuration. Scope: Safebucket complete local stack; distinguish the full recipe from the lighter deployment and a production HA design. Source: https://docs.safebucket.io/getting-started/local-full-deployment (reviewed 2026-11-20). Deployment artifact: https://github.com/safebucket/safebucket/blob/main/deployments/local/full/docker-compose.yml. Artifact reference: main (moving branch); match the selected application release.

- Minimum footprint / sizing: Documented. The full local Compose guide asks for at least 1 GB RAM available to its containers. This is a local-startup allowance, not a whole-host production or HA minimum; database, object storage, caching, events, logs, files and backup growth need separate workload sizing. Scope: Safebucket production-like local recipe; no validated 100-user, 1 TB or redundant topology is established. Source: https://docs.safebucket.io/getting-started/local-full-deployment (reviewed 2026-11-20).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Safebucket; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/safebucket/safebucket/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v0.8.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Safebucket upstream application; verify compatibility with the selected package. Source: https://github.com/safebucket/safebucket/releases/tag/v0.8.1 (reviewed 2026-11-19).







## XWiki

Self-hosted enterprise wiki and structured knowledge application platform.

- Listing: https://launchinyourcloud.com/directory/xwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL-2.1 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: XWiki application, PostgreSQL, persistent files and search components.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.hostinger.com/applications/xwiki
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.

GNU LGPL-2.1 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

XWiki application, PostgreSQL, persistent files and search components. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted enterprise wiki and structured knowledge application platform.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/xwiki (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/xwiki-1 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/xwiki
  XWiki application, PostgreSQL, persistent files and search components. The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/xwiki-1
  XWiki application, PostgreSQL, persistent files and search components. The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes tmortagne, vmassol, mflorea, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/xwiki/xwiki-platform/graphs/contributors

- Upstream project: https://github.com/xwiki/xwiki-platform

### Sources

- Hostinger: https://www.hostinger.com/applications/xwiki

- Railway: https://railway.com/deploy/xwiki-1

- LGPL-2.1 LICENSE: https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE

- GitHub Releases: https://github.com/xwiki/xwiki-platform/releases

### Licensing sources

- https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/xwiki

- https://railway.com/deploy/xwiki-1


### 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. The OpenID Connect Authenticator extension provides OIDC sign-in and synchronization. It is installed through Extension Manager, is LGPL-2.1 licensed, and requires XWiki 14.10.2 or later; commercial support is separate. Scope: XWiki with separately installed OIDC Authenticator extension. Source: https://extensions.xwiki.org/xwiki/bin/view/Extension/OpenID%20Connect/OpenID%20Connect%20Authenticator/ (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. Official installation options include a production-capable Docker image, Debian packages or a WAR distribution. Production requires a supported database, persistent application data and compatible Java/container versions; the standalone HSQLDB demo is not the production baseline. Scope: Official XWiki distribution options. Source: https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/ (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/_/xwiki. Artifact reference: Select an explicit compatible image tag; no artifact is installed by this review.

- Minimum footprint / sizing: Documented. The Tiny guideline is 2 CPU cores, 2 GB RAM and 5 GB disk for up to 25 active users; Small is 2 cores, 4 GB and 20 GB for up to 250. These single-machine application/database profiles depend on document and request volume and do not establish HA or 1-TB capacity. Scope: Upstream single-machine sizing profiles; workload dimensions must all be checked. Source: https://www.xwiki.org/xwiki/bin/view/documentation/xs/admin/installation/xwiki-instance-sizing/ (reviewed 2026-11-20).

- License pricing: Documented. GNU LGPL-2.1 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: XWiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream xwiki-platform-17.10.15 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: XWiki upstream application; verify compatibility with the selected package. Source: https://github.com/xwiki/xwiki-platform/releases/tag/xwiki-platform-17.10.15 (reviewed 2026-11-19).






