{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","category":{"description":"Document platforms, repositories and APIs.","id":"document-management","name":"Document management"},"cloud":{"boundary":"Vultr account and compute instances","classificationReview":{"reviewed":"2026-11-20","source":"https://docs.vultr.com/products/compute/instances/cloud-compute/provisioning","summary":"Navigation group for the documented infrastructure offering; read each application path for its actual account boundary."},"defaultBoundary":"cloud-account","diligence":[{"reviewed":"2026-11-14","source":"https://docs.vultr.com/products/network/vpc-networks/provisioning","summary":"Vultr documents isolated IPv4 VPC networks with console, API, CLI and Terraform provisioning. Configure the selected location, address ranges and routes; private application access is separate from public ingress.","topic":"VPC provisioning"}],"id":"vultr","identity":"Cloud account access and server SSH keys","install":"Provision compute through the console, API, CLI or Terraform, then install and operate the documented application.","name":"Vultr","network":"Instance networks and firewall rules","providerType":"cloud-infrastructure","reviewed":"2026-11-12","short":"Vultr","source":"https://docs.vultr.com/products/compute/instances/cloud-compute/provisioning"},"kind":"cloud-category","listings":[{"architecture":"Joplin Server, database and persistent attachment storage.","categories":["document-management"],"category":"Document management","categoryFit":{"document-management":"Personal-use self-hosted synchronization server for Joplin notes."},"cloudEvidence":[{"clouds":["aws","digitalocean","linode","vultr","hostinger","lumadock"],"notes":"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.","reviewed":"2026-11-19","sourceType":"package-platform-documentation","title":"Cloudron Store","url":"https://www.cloudron.io/store/joplin-server.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","digitalocean","linode","vultr","hostinger","lumadock"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"linode","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"vps-account","cloud":"hostinger","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"vps-account","cloud":"lumadock","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Personal-use self-hosted synchronization server for Joplin notes.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Joplin Server Business self-hosted baseline; provider-package allocations, external content storage and redundancy are separate","source":"https://joplinapp.org/help/apps/joplin_server_business/","status":"documented","summary":"The Server Business guide lists two CPU cores/four threads, at least 4 GB RAM (8 GB recommended) and 50 GB SSD plus content growth. These are moderate-load deployment requirements, not the smaller Cloudron package allocation or a validated 100-user, 1 TB HA topology.","supportingSources":[{"title":"Previously reviewed Cloudron app package allocation","url":"https://www.cloudron.io/store/joplin-server.html"}]},"iac":{"artifactRef":"dev (moving branch); use a compatible published server image tag","artifactUrl":"https://github.com/laurent22/joplin/blob/dev/docker-compose.server.yml","reviewed":"2026-11-20","scope":"Joplin Server application plus separately provisioned production database and persistent content storage","source":"https://github.com/laurent22/joplin/blob/dev/packages/server/README.md","status":"documented","summary":"The official server README provides versioned Docker images and a production PostgreSQL/Compose setup; the SQLite example is for testing. Configure public URL, database, credentials and reverse proxy before use. Select the appropriate commercial licence for an organisation."},"licensePricing":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"Joplin Server; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md","status":"documented","summary":"Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted Joplin Server SAML; supported clients, session policy and business licensing must be checked","source":"https://joplinapp.org/help/apps/server/saml/","status":"documented","summary":"Joplin Server documents SAML user authentication using SP/IdP configuration and server environment settings. Its API and website must use the same base URL for SAML. Commercial organisational use requires the appropriate Server Business rights; this does not establish hosted Cloud plan entitlements.","supportingSources":[{"title":"Server Business and self-hosted licensing context","url":"https://joplinapp.org/help/apps/joplin_server_business/"}]}},"id":"joplin-server","infrastructure":["servers"],"infrastructureNotes":"Joplin Server, database and persistent attachment storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://www.cloudron.io/store/joplin-server.html"],"install":"Cloudron package; Docker / Compose","installMethods":["cloudron","docker"],"kind":"product","license":"Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.","licenseModel":"source-available","licenseModelNotes":"Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.","licenseModelSources":["https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Joplin Server","notes":"The Server Personal Use License permits personal non-commercial use and restricts use by business entities and commercial sharing without written permission. This is not a default option for a 100-user business deployment. Desktop/client licences and releases do not establish server rights or Server 3.7.6 publication dates.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Cloudron Store","url":"https://www.cloudron.io/store/joplin-server.html"},{"title":"Hostinger","url":"https://www.hostinger.com/applications/joplin-server"},{"title":"Joplin Server Personal Use License","url":"https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md"},{"title":"GitHub Releases","url":"https://github.com/laurent22/joplin/releases"},{"title":"Cloudron customer-server and named-provider installation","url":"https://docs.cloudron.io/installation/"}],"url":"https://launchinyourcloud.com/directory/joplin-server/","website":"https://joplinapp.org"},{"architecture":"Memos application, SQLite database and attachment storage.","categories":["document-management"],"category":"Document management","categoryFit":{"document-management":"Self-hosted lightweight notes, documents and knowledge timeline."},"cloudEvidence":[{"clouds":["aws","digitalocean","linode","vultr","hostinger","lumadock"],"notes":"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.","reviewed":"2026-11-19","sourceType":"package-platform-documentation","title":"Cloudron Store","url":"https://www.cloudron.io/store/memos.html","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"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.","reviewed":"2026-11-19","sourceType":"community-template","title":"Railway","url":"https://railway.com/deploy/memos-3","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","digitalocean","linode","vultr","hostinger","lumadock","railway"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/usememos/memos/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/usememos/memos"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"linode","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"vps-account","cloud":"hostinger","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"vps-account","cloud":"lumadock","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Self-hosted lightweight notes, documents and knowledge timeline.","diligence":{"footprint":{"reviewed":"2026-11-19","scope":"Selected Cloudron application package; add database, files, backups and concurrent workload requirements","source":"https://www.cloudron.io/store/memos.html","status":"documented","summary":"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.","supportingSources":[{"title":"Cloudron platform requirements","url":"https://docs.cloudron.io/installation/"}]},"iac":{"artifactRef":"main (moving branch); 26.11.1 release snapshot is recorded separately","artifactUrl":"https://github.com/usememos/memos","reviewed":"2026-11-20","scope":"Self-hosted Memos application/data deployment; not a complete HA cloud stack","source":"https://usememos.com/docs/deploy/docker","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-19","scope":"Memos; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://raw.githubusercontent.com/usememos/memos/main/LICENSE","status":"documented","summary":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-11-16T01:12:25Z","releaseTag":"26.11.1","reviewed":"2026-11-19","scope":"Memos upstream application; verify compatibility with the selected package","source":"https://github.com/usememos/memos/releases/tag/26.11.1","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted Memos current authentication configuration; verify compatibility with the installed release and any provider package","source":"https://usememos.com/docs/configuration/authentication","status":"documented","summary":"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."}},"id":"memos","infrastructure":["servers"],"infrastructureNotes":"Memos application, SQLite database and attachment storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://www.cloudron.io/store/memos.html","https://railway.com/deploy/memos-3"],"install":"Cloudron package; Application platform deployment; Docker / Compose","installMethods":["cloudron","platform-template","docker"],"kind":"product","license":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://raw.githubusercontent.com/usememos/memos/main/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Memos","notes":"Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Cloudron Store","url":"https://www.cloudron.io/store/memos.html"},{"title":"Railway","url":"https://railway.com/deploy/memos-3"},{"title":"Hostinger","url":"https://www.hostinger.com/applications/memos"},{"title":"MIT LICENSE","url":"https://raw.githubusercontent.com/usememos/memos/main/LICENSE"},{"title":"GitHub Releases","url":"https://github.com/usememos/memos/releases"},{"title":"Cloudron customer-server and named-provider installation","url":"https://docs.cloudron.io/installation/"}],"url":"https://launchinyourcloud.com/directory/memos/","website":"https://usememos.com"},{"architecture":"NirvaShare application services on a customer VM with configured object-storage and identity-provider access.","categories":["document-management","data-rooms-ma-document-management"],"category":"Document management","categoryFit":{"data-rooms-ma-document-management":"Commercial self-hosted gateway for controlled sharing of customer object storage.","document-management":"Commercial self-hosted gateway for controlled sharing of customer object storage."},"cloudEvidence":[{"clouds":["aws"],"notes":"NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.","reviewed":"2026-11-19","sourceType":"marketplace-offer","title":"AWS Marketplace CFT","url":"https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.","reviewed":"2026-11-19","sourceType":"marketplace-offer","title":"DO Marketplace","url":"https://marketplace.digitalocean.com/apps/nirvashare","vendorSupport":"not-assessed"},{"clouds":["vultr"],"notes":"NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Cloud Platforms","url":"https://nirvashare.com/docs/deployment/cloud-platforms/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","digitalocean","vultr"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial self-hosted gateway for controlled sharing of customer object storage.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Vendor Linux server baseline; workload and HA sizing excluded","source":"https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/","status":"documented","summary":"The vendor specifies at least 2 CPU cores, 4 GB RAM and 100 GB disk, recommending 8 GB RAM or more on a supported Linux distribution. Object/file storage, optional services and HA are additional; this is a baseline, not validated 100-user capacity."},"iac":{"artifactRef":"Documentation updated 2025-01-10; not executed","artifactUrl":"https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/","reviewed":"2026-11-20","scope":"Legacy vendor CloudFormation example; conflicts with current sizing and requires review","source":"https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/","status":"documented","summary":"The vendor publishes inline CloudFormation YAML that creates EC2, security rules and an installation bootstrap. Its 2025 example uses a fixed AMI, t2.medium and 40-GB disk, below the current 100-GB requirement, and exposes SSH/application ports publicly. Update region/image, storage, ingress and bootstrap pinning before use; it is not a hardened production template.","supportingSources":[{"title":"Current minimum disk requirement","url":"https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"NirvaShare; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://nirvashare.com/pricing/","status":"documented","summary":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation."},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"CloudFormation Template (CFT)","id":"prodview-k6zpjoiopyrzs","publisher":"Nirvato Software Pvt Ltd","url":"https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs","version":"6.4.1"}],"reviewed":"2026-11-19","scope":"NirvaShare selected AWS public offer; infrastructure and support charges are separate","source":"https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs","status":"documented","summary":"The reviewed AWS offer delivers CloudFormation Template (CFT) from Nirvato Software Pvt Ltd. Its package version is 6.4.1; verify the contained application and required entitlements separately."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted share access; admin console configured separately","source":"https://nirvashare.com/docs/tutorials/share-files-from-smb-storage-with-entra-id-active-directory-users-using-sso/","status":"documented","summary":"SAML 2.0 identity providers can protect shares using external-SSO login profiles. The vendor documents metadata exchange with Entra ID and separate admin-console SSO configuration; review entitlement, claim mapping and enforcement for each surface.","supportingSources":[{"title":"Admin-console SSO configuration properties","url":"https://nirvashare.com/docs/deployment/nirvashare-config-properties/"}]}},"id":"nirvashare","infrastructure":["servers"],"infrastructureNotes":"NirvaShare application services on a customer VM with configured object-storage and identity-provider access. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs","https://marketplace.digitalocean.com/apps/nirvashare","https://nirvashare.com/docs/deployment/cloud-platforms/"],"install":"CloudFormation; VM image","installMethods":["cloudformation","vm-image"],"kind":"product","license":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModel":"commercial-only","licenseModelNotes":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModelSources":["https://nirvashare.com/pricing/"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"NirvaShare","notes":"The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"AWS Marketplace CFT","url":"https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs"},{"title":"DO Marketplace","url":"https://marketplace.digitalocean.com/apps/nirvashare"},{"title":"Cloud Platforms","url":"https://nirvashare.com/docs/deployment/cloud-platforms/"},{"title":"AWS CFT Docs","url":"https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/"},{"title":"Pricing","url":"https://nirvashare.com/pricing/"},{"title":"Release Notes","url":"https://nirvashare.com/release-notes/"}],"url":"https://launchinyourcloud.com/directory/nirvashare/","website":"https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs"},{"advisories":[{"action":"Pin the selected image, back up documents and the database, review PAPERLESS_ALLOWED_HOSTS and verify permissions and MFA configuration after upgrading.","conditions":"Authentication mode, tag inheritance and configuration permissions determine applicability. Provider templates may use different image tags.","id":"paperless-ngx-3-5-0-security-review","listingIds":["paperless-ngx"],"reviewed":"2026-11-17","scope":"Upstream Paperless-ngx 3.5.0 release fixes; no CVE or complete affected-version range is established by this release record.","source":"https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0","summary":"Release 3.5.0 fixes configuration/tag permissions and the default trusted-authentication behavior for MFA, and adds session cleanup.","title":"Paperless-ngx permissions and MFA defaults review","type":"security-advisory"}],"architecture":"Application, OCR and background worker processes with persistent documents, PostgreSQL and Redis","categories":["document-management"],"category":"Document management","categoryFit":{"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."},"cloudEvidence":[{"clouds":["vultr"],"notes":"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.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"Vultr-hosted Paperless-ngx application deployment guide","url":"https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"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.","reviewed":"2026-11-13","sourceType":"community-template","title":"Community Railway Paperless-ngx stack","url":"https://railway.com/deploy/paperless-ngx","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["vultr","railway"],"communityAcceptance":{"reviewed":"2026-11-17","sources":[{"title":"Reviewed 3.5.0 release and upgrade note","url":"https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0"},{"title":"Contributor history","url":"https://github.com/paperless-ngx/paperless-ngx/graphs/contributors"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Community document management with OCR, full-text search, metadata and ingestion workflows.","diligence":{"footprint":{"reviewed":"2026-11-20","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","status":"documented","summary":"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."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/paperless-ngx/paperless-ngx/blob/main/docker/compose/docker-compose.postgres.yml","reviewed":"2026-11-14","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","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream Paperless-ngx core licence","source":"https://raw.githubusercontent.com/paperless-ngx/paperless-ngx/main/LICENSE","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-11-17T03:36:20Z","releaseTag":"v3.5.0","reviewed":"2026-11-17","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","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Upstream self-hosted authentication configuration","source":"https://raw.githubusercontent.com/paperless-ngx/paperless-ngx/main/docs/configuration.md","status":"documented","summary":"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."}},"id":"paperless-ngx","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-13","infrastructureSources":["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"],"install":"Official Docker Compose installer; provider tutorial on Vultr or a community Railway application/database/queue template.","installMethods":["docker","package","platform-template"],"kind":"product","license":"GPL-3.0; conversion tools and other bundled components have separate licenses.","licenseModel":"open-source","licenseModelNotes":"The listed community application is GPL-3.0; optional integrations and container dependencies retain their own terms.","licenseModelSources":["https://github.com/paperless-ngx/paperless-ngx/blob/main/LICENSE"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Paperless-ngx","notes":"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.","operations":"Customer operates application permissions, ingestion, backups, secrets and upgrades. Railway manages its platform resources; a Vultr VM also requires customer OS/container maintenance.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Upstream Compose installation and project scope","url":"https://github.com/paperless-ngx/paperless-ngx"},{"title":"Vultr Docker Compose deployment with PostgreSQL and TLS","url":"https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system"},{"title":"AI workflow advisory; use current patched releases","url":"https://github.com/paperless-ngx/paperless-ngx/security/advisories/GHSA-c8f3-pqr2-rr24"},{"title":"Community Railway Paperless-ngx stack","url":"https://railway.com/deploy/paperless-ngx"},{"title":"Upstream license","url":"https://github.com/paperless-ngx/paperless-ngx/blob/main/LICENSE"},{"title":"Reviewed 3.5.0 release and upgrade note","url":"https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0"},{"title":"Contributor history","url":"https://github.com/paperless-ngx/paperless-ngx/graphs/contributors"}],"url":"https://launchinyourcloud.com/directory/paperless-ngx/","website":"https://docs.paperless-ngx.com/"},{"architecture":"TriliumNext server with persistent database and attachments.","categories":["document-management"],"category":"Document management","categoryFit":{"document-management":"Self-hosted hierarchical personal notes and document knowledge base."},"cloudEvidence":[{"clouds":["aws","digitalocean","linode","vultr","hostinger","lumadock"],"notes":"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.","reviewed":"2026-11-19","sourceType":"package-platform-documentation","title":"Cloudron Store","url":"https://www.cloudron.io/store/triliumnext-notes.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","digitalocean","linode","vultr","hostinger","lumadock"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/TriliumNext/Trilium/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/TriliumNext/Trilium"}],"summary":"The reviewed upstream contributor history includes eliandoran, zadam, adoriandoran, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"linode","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"vps-account","cloud":"hostinger","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"vps-account","cloud":"lumadock","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-hosted hierarchical personal notes and document knowledge base.","diligence":{"footprint":{"reviewed":"2026-11-19","scope":"Selected Cloudron application package; add database, files, backups and concurrent workload requirements","source":"https://www.cloudron.io/store/triliumnext-notes.html","status":"documented","summary":"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.","supportingSources":[{"title":"Cloudron platform requirements","url":"https://docs.cloudron.io/installation/"}]},"iac":{"artifactRef":"v0.107.0 upstream source reviewed; choose its matching published image tag, not an unpinned latest upgrade","artifactUrl":"https://hub.docker.com/r/triliumnext/trilium","reviewed":"2026-11-20","scope":"TriliumNext self-hosted server; upstream and Cloudron package versions/allocations are separate","source":"https://docs.triliumnotes.org/user-guide/setup/server/installation/docker","status":"documented","summary":"The project publishes Docker images and Compose instructions with a persistent Trilium data directory. Select a version matching the desktop/sync clients rather than automatically following latest; configure proxy/authentication, ownership, backups and upgrades for the installed server."},"licensePricing":{"reviewed":"2026-11-19","scope":"TriliumNext Notes; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/TriliumNext/Trilium/blob/main/LICENSE","status":"documented","summary":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-11-08T22:06:59Z","releaseTag":"v0.107.0","reviewed":"2026-11-19","scope":"TriliumNext Notes upstream application; verify compatibility with the selected package","source":"https://github.com/TriliumNext/Trilium/releases/tag/v0.107.0","status":"documented","summary":"Reviewed upstream v0.107.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"TriliumNext v0.107.0 server authentication; verify the packaged server version and provider algorithm/settings","source":"https://github.com/TriliumNext/Trilium/blob/v0.107.0/README.md","status":"documented","summary":"TriliumNext documents external OpenID Connect login and links the integration from its published v0.107.0 README. OIDC replaces the local web password login and delegates MFA to the provider. Configure the identity accepted by this personal-notes instance; this does not make it a multi-tenant team repository.","supportingSources":[{"title":"OpenID Connect configuration","url":"https://docs.triliumnotes.org/user-guide/setup/server/openid-connect"}]}},"id":"triliumnext-notes","infrastructure":["servers"],"infrastructureNotes":"TriliumNext server with persistent database and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://www.cloudron.io/store/triliumnext-notes.html"],"install":"Cloudron package","installMethods":["cloudron"],"kind":"product","license":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/TriliumNext/Trilium/blob/main/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"TriliumNext Notes","notes":"The server is primarily a single-user knowledge base; published notes and sharing do not establish a multi-user enterprise collaboration suite.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Cloudron Store","url":"https://www.cloudron.io/store/triliumnext-notes.html"},{"title":"AGPL-3.0 LICENSE","url":"https://github.com/TriliumNext/Trilium/blob/main/LICENSE"},{"title":"Releases v0.107.0","url":"https://github.com/TriliumNext/Trilium/releases"},{"title":"Cloudron customer-server and named-provider installation","url":"https://docs.cloudron.io/installation/"}],"url":"https://launchinyourcloud.com/directory/triliumnext-notes/","website":"https://triliumnotes.org"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/clouds/vultr/document-management/"}