
# Software on Vultr

Explore software with documented Vultr deployment, customer-account guidance, licensing qualifications and source evidence.

Canonical page: https://launchinyourcloud.com/clouds/vultr/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde



## Related questions

- [What open-source apps can I deploy on a VPS like DigitalOcean, Hetzner or Vultr?](https://launchinyourcloud.com/questions/apps-on-vps/)


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: Vultr account and compute instances
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.vultr.com/products/compute/instances/cloud-compute/provisioning (checked 2026-11-20).
- Network: Instance networks and firewall rules
- Identity and access: Cloud account access and server SSH keys
- Installation guidance: Provision compute through the console, API, CLI or Terraform, then install and operate the documented application.
- Guidance source: https://docs.vultr.com/products/compute/instances/cloud-compute/provisioning
- Guidance reviewed: 2026-11-12


### VPC provisioning

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.
Source: https://docs.vultr.com/products/network/vpc-networks/provisioning (reviewed 2026-11-14).

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

30 listings.


## Apache Answer

Self-hosted community questions, answers and knowledge content.

- Listing: https://launchinyourcloud.com/directory/apache-answer/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, 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: Cloudron package; Application platform deployment
- Architecture: Apache Answer application and persistent database/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://answer.apache.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 SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database.

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

Apache Answer application and persistent database/storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted community questions, answers and knowledge content.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/apache-answer.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/apache-answer
  Apache Answer application and persistent database/storage. The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database. 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 LinkinStars, aichy126, kumfo, 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/apache/answer/graphs/contributors

- Upstream project: https://github.com/apache/answer

### Sources

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

- Railway: https://railway.com/deploy/apache-answer

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

- Releases v2.0.3: https://github.com/apache/answer/releases

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

### Licensing sources

- https://github.com/apache/answer/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/apache-answer.html

- https://railway.com/deploy/apache-answer


### 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 plugin guide demonstrates building Answer with GitHub and Google OAuth connector plugins. Include and configure compatible plugins in the deployed binary/image; this is not a claim that the default image includes enterprise SAML/OIDC. Scope: Official plugin-based application-user OAuth authentication. Source: https://answer.apache.org/docs/plugins (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 installation guide supplies Docker/Compose and binary installation options. Persist the data directory, configure the selected database and include required authentication plugins in the built image; default standalone examples do not supply production HA. Scope: Apache Answer application installation; plugin/custom-image build may be required. Source: https://answer.apache.org/docs/installation (reviewed 2026-11-20). Deployment artifact: https://answer.apache.org/docs/installation. Artifact reference: Current official deployment examples; pin binary/container and plugin versions.

- 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/apache-answer.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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







## BookStack Self-Hosted

Self-hosted wiki and documentation organized into books, chapters and pages.

- Listing: https://launchinyourcloud.com/directory/bookstack/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT application; third-party components retain their licenses.
- Licensing model: open-source
- Installation: Cloudron package on a customer VM; upstream also documents native PHP/MySQL installation.
- Architecture: Persistent PHP web application with MySQL, uploaded media, attachments, configuration and themes
- Operations: Customer manages administrators, registration roles, identity, content permissions, mail, database and file backups, recovery and upgrades. Cloudron manages package services on the customer server.
- Product website: https://www.bookstackapp.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Reviewed Cloudron 2.3.1 contains upstream 26.09.3 and its access-control fixes. Change the initial local administrator credentials. With Cloudron SSO, change the default registration role before admitting users: the package initially grants administrator status. Back up the database, configuration, uploads, storage and custom themes. Only the latest upstream release is supported. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.

MIT application; third-party components retain their licenses. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.

Persistent PHP web application with MySQL, uploaded media, attachments, configuration and themes. Cloudron provides a persistent server application, not event-driven application functions.


### Category fit

- collaboration: Collaborative wiki documentation with books, chapters, pages, revisions, attachments and role-based access.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (checked 2026-11-13). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/cloudron (checked 2026-11-13). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.linode.com/docs/marketplace-docs/guides/cloudron/ (checked 2026-11-13). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudron.io/installation/ (checked 2026-11-13). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-13). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://lumadock.com/vps-hosting/cloudron (checked 2026-11-13). 


### Cloud deployment evidence

- Cloudron EC2 AMI and application installation (aws): https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Droplet deployment (digitalocean): https://marketplace.digitalocean.com/apps/cloudron
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Linode deployment (linode): https://www.linode.com/docs/marketplace-docs/guides/cloudron/
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron named-provider installation and Marketplace availability (vultr): https://docs.cloudron.io/installation/
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
  Source type: package-platform-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Hostinger customer VPS Cloudron template (hostinger): https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- LumaDock customer VPS Cloudron template (lumadock): https://lumadock.com/vps-hosting/cloudron
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

BookStack has been maintained since 2015 with sustained development, translations and substantive code contributions from multiple participants. The project FAQ and contributor history establish participation beyond popularity counts; the reviewed release addresses access-control defects.

Reviewed 2026-11-13.

- Project maintenance and participation: https://www.bookstackapp.com/about/project-faq/

- Contributor history: https://github.com/BookStackApp/BookStack/graphs/contributors

- Maintained release: https://github.com/BookStackApp/BookStack/releases/tag/v26.09.3

### Sources

- Upstream installation: https://www.bookstackapp.com/docs/admin/installation/

- Database, configuration and file recovery: https://www.bookstackapp.com/docs/admin/backup-restore/

- Upstream upgrades: https://www.bookstackapp.com/docs/admin/updates/

- Project maintenance, edition and support policy: https://www.bookstackapp.com/about/project-faq/

- Cloudron BookStack configuration and administrator roles: https://docs.cloudron.io/packages/bookstack/

- Reviewed access-control fixes: https://github.com/BookStackApp/BookStack/releases/tag/v26.09.3

- MIT application license: https://github.com/BookStackApp/BookStack/blob/v26.09.3/LICENSE

- Contributor history: https://github.com/BookStackApp/BookStack/graphs/contributors

- Cloudron application packages and persistent data: https://docs.cloudron.io/apps/

- Cloudron application updates: https://docs.cloudron.io/updates/

- Cloudron database and application-data backups: https://docs.cloudron.io/backups/

- Cloudron platform plans: https://www.cloudron.io/pricing.html

- Cloudron account and platform terms: https://www.cloudron.io/legal/terms.html

- Cloudron account and installation metadata: https://www.cloudron.io/legal/privacy.html

- Exact Cloudron application package versions: https://www.cloudron.io/store/index.html

- Cloudron EC2 AMI and application installation: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

- Cloudron customer Droplet deployment: https://marketplace.digitalocean.com/apps/cloudron

- Cloudron customer Linode deployment: https://www.linode.com/docs/marketplace-docs/guides/cloudron/

- Cloudron named-provider installation and Marketplace availability: https://docs.cloudron.io/installation/

- Hostinger customer VPS Cloudron template: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/

- LumaDock customer VPS Cloudron template: https://lumadock.com/vps-hosting/cloudron

### Licensing sources

- https://github.com/BookStackApp/BookStack/blob/v26.09.3/LICENSE

- https://www.bookstackapp.com/about/project-faq/

- https://www.cloudron.io/legal/terms.html

- https://www.cloudron.io/pricing.html

### Infrastructure sources

- https://docs.cloudron.io/packages/bookstack/

- https://docs.cloudron.io/installation/


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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: Documented. AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate. Scope: Cloudron platform plus separate application package. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (reviewed 2026-11-14). Supporting source: Cloudron application package — https://docs.cloudron.io/packages/bookstack/. Offer prodview-aep3gt5elubci: Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application); https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. BookStack documents SAML 2.0 and OpenID Connect as primary authentication alternatives to its email/password login. Reconcile these settings with any packaged distribution and its identity integration. Scope: Upstream BookStack; packaged Cloudron configuration may differ. Source: https://www.bookstackapp.com/docs/admin/saml2-auth/ (reviewed 2026-11-14). Supporting source: BookStack OpenID Connect authentication — https://www.bookstackapp.com/docs/admin/oidc-auth/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation page links Ubuntu installation scripts that provision the application and supporting PHP/web-server/database stack. Review the script before execution and use a supported matching OS; this is a single-server installer, not provider IaC or HA automation. Scope: Official Ubuntu 24.04 installer option; other distributions/packages have separate instructions. Source: https://www.bookstackapp.com/docs/admin/installation/ (reviewed 2026-11-20). Deployment artifact: https://codeberg.org/bookstack/devops/raw/branch/main/scripts/installation-ubuntu-24.04.sh. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The reviewed Cloudron BookStack package declares a 256 MB application-memory minimum. Cloudron itself additionally needs at least 2 GB RAM and 20 GB disk. These package limits do not size database, attachments, backups, concurrency or HA, and are not a whole-system VM requirement. Scope: Cloudron BookStack 26.09.3 package, not a universal upstream host floor. Source: https://www.cloudron.io/store/bookstack.html (reviewed 2026-11-20). Supporting source: Cloudron platform installation requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. The upstream BookStack software is MIT-licensed. This license does not include a hosting platform subscription, managed operation, implementation or a commercial support service. Packaged distributions and their supporting services can charge separately. Scope: Upstream BookStack core software terms. Source: https://raw.githubusercontent.com/BookStackApp/BookStack/development/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Collabora Online (CODE)

Community office editing server for integration with a document platform.

- Listing: https://launchinyourcloud.com/directory/collabora-online/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hetzner, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package
- Architecture: Collabora Online Development Edition server and a separate WOPI-compatible file platform.
- 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://collaboraonline.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

CODE is the development/community edition, separate from commercially supported Collabora Online. Helm chart versions and CODE application versions are separate; production support must not be inferred from a working package.

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

Collabora Online Development Edition server and a separate WOPI-compatible file platform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Community office editing server for integration with a document platform.

### Deployment boundaries


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

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

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

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

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/ (checked 2026-11-19). 

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/collabora-online.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.

- Hetzner Tutorial (hetzner): https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/
  Collabora Online Development Edition server and a separate WOPI-compatible file platform. CODE is the development/community edition, separate from commercially supported Collabora Online. Helm chart versions and CODE application versions are separate; production support must not be inferred from a working package. 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 Ashod, eszkadev, timar, 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/CollaboraOnline/online/graphs/contributors

- Upstream project: https://github.com/CollaboraOnline/online

### Sources

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

- Hetzner Tutorial: https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/

- MPL-2.0 COPYING: https://github.com/CollaboraOnline/online/blob/master/COPYING

- Releases 2026: https://github.com/CollaboraOnline/online/releases

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

### Licensing sources

- https://github.com/CollaboraOnline/online/blob/master/COPYING

### Infrastructure sources

- https://www.cloudron.io/store/collabora-online.html

- https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/


### 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: Sources checked — unresolved. The reviewed CODE material describes an embedded editing service and integrations, but does not establish standalone corporate SAML/OIDC user login in the listed development edition. Confirm the identity-providing document host, connector and edition instead of assigning its SSO to the editing engine. Scope: CODE engine identity versus external document-platform authentication. Source: https://www.collaboraonline.com/code/ (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. Collabora publishes the collabora/code container image for the CODE development/small-team edition, which the vendor does not recommend for production. Pin a suitable image and configure a document host/connector. Active source development moved to Gerrit; the retained GitHub build/chart artifacts do not make a nightly or commercial build equivalent to CODE. Scope: Listed CODE development edition; not Collabora Online commercial production support. Source: https://www.collaboraonline.com/code/ (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/collabora/code. Artifact reference: Select a supported version-tagged CODE image; distinguish nightly and commercial builds. Supporting source: Upstream source/build repository locations — https://raw.githubusercontent.com/CollaboraOnline/online/master/README.md.

- Minimum footprint / sizing: Documented. The Cloudron package declares 1024MB 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/collabora-online.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Collabora Online (CODE); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/CollaboraOnline/online/blob/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Discourse

Self-hosted discussion and community platform for workplace collaboration and customer support communities.

- Listing: https://launchinyourcloud.com/directory/discourse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, linode, vultr, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-2.0 core; review extensions separately
- Licensing model: open-source
- Installation: Official Docker installer on a Linux cloud or local server
- Architecture: Persistent Docker server; the standalone template includes web, PostgreSQL and Redis services with host-mounted data volumes.
- Operations: Customer maintains the Linux host, Docker deployment, backups, updates and configured messaging services; choose an actively supported release channel.
- Product website: https://www.discourse.org/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosted Discourse. The official cloud installation guide explicitly lists AWS EC2 and Google Cloud as supported Docker hosts; customers provision the Linux server, rather than using a bundled cloud-specific infrastructure template. The installer offers an external Discourse ID login option when SMTP is skipped. Review authentication, email and other integrations for outbound data flows. Supported-series updates published November 10, 2026 include 2026.10.1 and 2026.7.5 ESR; the 2026.10.1 changelog records 38 security fixes. Self-hosted operators should upgrade on their selected supported release channel.

The listed self-hosted core has a GNU GPL version 2 license. Official paid hosting is a separate service; review the licenses of selected extensions separately.

The official installer requires a Linux server and Docker. Its standalone configuration mounts persistent host storage and includes PostgreSQL and Redis; this is a server workload.


### Category fit

- collaboration: Public or private discussion communities with searchable topics, chat and shared knowledge.

- customer-support: Customer and peer-support communities; this is a discussion platform rather than an agent-ticket helpdesk.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 


### Cloud deployment evidence

- Discourse supported cloud server installation (aws, gcp, digitalocean, linode, vultr, hetzner): https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md
  The official cloud installation guide explicitly names DigitalOcean, AWS EC2, Google Cloud, Linode/Akamai, Vultr and Hetzner as supported hosts, then provides a complete server installation workflow. This is provider compatibility for the customer-operated Discourse application, not its separate hosted SaaS; configure the supported OS, DNS, email, HTTPS and recovery.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official customer directory identifies Docker, Elastic and GitLab support communities as Discourse users, without establishing their hosting model. The official release service records security-maintenance updates on November 10, 2026 for the latest, monthly and ESR channels; the supported 2026.10.1 release includes 38 security fixes.

Reviewed 2026-11-14.

- Named support-community adopters: https://www.discourse.org/customers

- Current releases and support timelines: https://releases.discourse.org/

- 2026.10.1 security-maintenance changelog: https://releases.discourse.org/changelog/v2026.10.1/

### Sources

- Official self-hosting installation guide: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

- Official standalone Docker service and storage template: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml

- Discussion, chat and administration features: https://www.discourse.org/features

- Discourse core license: https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt

- Official releases and support timelines: https://releases.discourse.org/

- Official customer community directory: https://www.discourse.org/customers

- Discourse 2026.10.1 security-maintenance changelog: https://releases.discourse.org/changelog/v2026.10.1/

### Licensing sources

- https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt

- https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

### Infrastructure sources

- https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

- https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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. DiscourseConnect is the official SSO protocol for connecting Discourse to an external identity provider through a signed shared-secret exchange. It is distinct from a generic SAML entitlement; configure account/email mapping and callback security for the actual identity service. Scope: Official DiscourseConnect self-hosted forum authentication. Source: https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045 (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 discourse_docker repository supplies launcher scripts and a standalone configuration example with application, PostgreSQL and Redis templates. Configure mail, TLS, secrets, volumes and backups, and pin compatible releases; a standalone container is not a clustered HA topology. Scope: Official self-hosted launcher and standalone container installation. Source: https://raw.githubusercontent.com/discourse/discourse_docker/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml. Artifact reference: main (moving branch). Supporting source: Standalone configuration template — https://raw.githubusercontent.com/discourse/discourse_docker/main/samples/standalone.yml.

- Minimum footprint / sizing: Documented. The upstream cloud guide lists 1 CPU core, 1 GB RAM with swap and 10 GB disk as minima; 2+ cores, 2 GB+ RAM and 20 GB+ disk are recommended. Plugins, traffic and data growth change sizing. Scope: Upstream standalone cloud install baseline. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (reviewed 2026-11-14).

- License pricing: Documented. The upstream Discourse software is GPL version 2. Hosted subscription prices on discourse.org are for separately operated hosting/services and should not be presented as the license cost of the self-hosted core. Infrastructure, implementation and optional services are separate. Scope: Upstream self-hosted core license; hosted plan pricing is a different offering. Source: https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## DocuSeal Self-Hosted

Self-hosted document forms and electronic-signature workflows with API and webhook integration.

- Listing: https://launchinyourcloud.com/directory/docuseal/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, azure, gcp, railway, heroku, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.
- Licensing model: open-source
- Installation: Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM.
- Architecture: Rails web application and document-processing jobs with a database, attachments and signing configuration
- Operations: Customer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment.
- Product website: https://www.docuseal.com/
- Source review: 2026-11-19; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.

AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.

Web application containers and document-processing jobs with durable database and attachment storage on Cloudron or managed application platforms. Cloud Run container hosting does not establish event-driven function deployment support.


### Category fit

- workflow-automation: Automates document form filling, signature collection and completion workflows through a self-hosted application, API and webhooks. This does not establish full contract lifecycle management or regulated-record compliance.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (checked 2026-11-13). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/cloudron (checked 2026-11-13). Source: https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml (checked 2026-11-13). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.linode.com/docs/marketplace-docs/guides/cloudron/ (checked 2026-11-13). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudron.io/installation/ (checked 2026-11-13). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-13). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://lumadock.com/vps-hosting/cloudron (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run (checked 2026-11-13). 

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

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/docusealco/docuseal-heroku/blob/master/app.json (checked 2026-11-13). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/docusealco/docuseal-render/blob/master/render.yaml (checked 2026-11-13). 


### Cloud deployment evidence

- Cloudron EC2 AMI and application installation (aws): https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Droplet deployment (digitalocean): https://marketplace.digitalocean.com/apps/cloudron
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Linode deployment (linode): https://www.linode.com/docs/marketplace-docs/guides/cloudron/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron named-provider installation and Marketplace availability (vultr): https://docs.cloudron.io/installation/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
  Source type: package-platform-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Hostinger customer VPS Cloudron template (hostinger): https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- LumaDock customer VPS Cloudron template (lumadock): https://lumadock.com/vps-hosting/cloudron
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Azure Web Apps deployment (azure): https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps
  Installs the actual application container in a customer Azure resource group with PostgreSQL and Blob Storage. Configure secrets, storage and production database network restrictions rather than retaining permissive example firewall rules.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Google Cloud Run deployment (gcp): https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run
  Installs the actual application container in a customer project with Cloud SQL and Google Cloud Storage. Configure keys, bucket access and production database network restrictions. This is application hosting, not a storage-only integration.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor DigitalOcean application specification (digitalocean): https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml
  Creates the vendor application container and PostgreSQL in a customer App Platform account. Database persistence does not preserve attachments: configure durable object storage and back up both. Pin the application image and configure real mail.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor-linked Railway application template (railway): https://railway.com/deploy/IGoDnc
  Installs the vendor application and PostgreSQL in a customer Railway project. The database volume alone does not preserve attachments: configure an application volume at the image data path or durable object storage. Review secrets, SMTP and backups.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Heroku application specification (heroku): https://github.com/docusealco/docuseal-heroku/blob/master/app.json
  Creates a container application and PostgreSQL add-on in a customer Heroku account. Dyno filesystems are ephemeral: configure durable object storage for documents, retain encryption keys and back up the database.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Render application blueprint (render): https://github.com/docusealco/docuseal-render/blob/master/render.yaml
  Creates the application and PostgreSQL in a customer Render account. The example selects free services; Render does not recommend those for production and the free database expires after 30 days. Use suitable paid compute/database, durable attachment storage, secrets and working outbound mail.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

The current core has sustained work by two principal maintainers, external code contributions and continuing security releases. Public contributor and release histories establish ongoing maintenance; they do not independently validate every paid feature or customer deployment.

Reviewed 2026-11-19.

- Contributor history: https://github.com/docusealco/docuseal/graphs/contributors

- Reviewed maintenance and security release 3.3.8: https://github.com/docusealco/docuseal/releases/tag/3.3.8

- Release history: https://www.docuseal.com/changelog

### Sources

- Self-hosted edition and boundaries: https://www.docuseal.com/on-premises

- Vendor installation options: https://www.docuseal.com/install

- Production runtime requirements: https://www.docuseal.com/docs/on-premises-server-requirements

- Configuration, secrets and storage: https://www.docuseal.com/docs/configuring-docuseal-via-environment-variables

- Cloudron application operations: https://docs.cloudron.io/packages/docuseal/

- Core application and installation: https://github.com/docusealco/docuseal/blob/3.3.6/README.md

- Attachment storage configuration: https://github.com/docusealco/docuseal/blob/3.3.6/config/storage.yml

- Default storage selection: https://github.com/docusealco/docuseal/blob/3.3.6/config/environments/production.rb

- Pro image, licensing and usage connection: https://www.docuseal.com/docs/on-premises-pro-installation

- Qualified signature edition limitation: https://www.docuseal.com/faq/how-to-use-qes-signing-with-docuseal-on-premises

- Current security release: https://github.com/docusealco/docuseal/releases/tag/3.3.7

- Release and security history: https://www.docuseal.com/changelog

- Core AGPL license: https://github.com/docusealco/docuseal/blob/3.3.6/LICENSE

- Contributor history: https://github.com/docusealco/docuseal/graphs/contributors

- Cloudron application packages and persistent data: https://docs.cloudron.io/apps/

- Cloudron application updates: https://docs.cloudron.io/updates/

- Cloudron database and application-data backups: https://docs.cloudron.io/backups/

- Cloudron platform plans: https://www.cloudron.io/pricing.html

- Cloudron account and platform terms: https://www.cloudron.io/legal/terms.html

- Cloudron account and installation metadata: https://www.cloudron.io/legal/privacy.html

- Exact Cloudron application package versions: https://www.cloudron.io/store/index.html

- Cloudron EC2 AMI and application installation: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

- Cloudron customer Droplet deployment: https://marketplace.digitalocean.com/apps/cloudron

- Cloudron customer Linode deployment: https://www.linode.com/docs/marketplace-docs/guides/cloudron/

- Cloudron named-provider installation and Marketplace availability: https://docs.cloudron.io/installation/

- Hostinger customer VPS Cloudron template: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/

- LumaDock customer VPS Cloudron template: https://lumadock.com/vps-hosting/cloudron

- Vendor Azure Web Apps deployment: https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps

- Vendor Google Cloud Run deployment: https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run

- Vendor DigitalOcean application specification: https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml

- Vendor-linked Railway application template: https://railway.com/deploy/IGoDnc

- Vendor Heroku application specification: https://github.com/docusealco/docuseal-heroku/blob/master/app.json

- Vendor Render application blueprint: https://github.com/docusealco/docuseal-render/blob/master/render.yaml

- Railway application Docker source: https://github.com/docusealco/docuseal-railway

- Railway volume persistence: https://docs.railway.com/volumes/reference

- Heroku ephemeral dyno filesystem: https://devcenter.heroku.com/articles/dyno-isolation

- Render free-service production limitations: https://render.com/docs/free

- Vendor application upgrade instructions: https://www.docuseal.com/docs/update-docuseal-to-the-latest-version

- Security-hardening changes in 3.3.7: https://github.com/docusealco/docuseal/compare/3.3.6...3.3.7

- DocuSeal 3.3.8 security release: https://github.com/docusealco/docuseal/releases/tag/3.3.8

- GHSA-78g6-f52x-q3jx: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx

### Licensing sources

- https://github.com/docusealco/docuseal/blob/3.3.6/LICENSE

- https://www.docuseal.com/docs/on-premises-pro-installation

- https://www.cloudron.io/legal/terms.html

- https://www.cloudron.io/pricing.html

### Infrastructure sources

- https://docs.cloudron.io/packages/docuseal/

- https://docs.cloudron.io/installation/

- https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps

- https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run


### Buyer diligence


Research coverage: 7/12 fields (58%); 7 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: Documented. AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate. Scope: Cloudron platform plus separate application package. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (reviewed 2026-11-14). Supporting source: Cloudron application package — https://docs.cloudron.io/packages/docuseal/. Offer prodview-aep3gt5elubci: Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application); https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML SSO appears in the self-hosted Pro feature list. It is not established here for the free edition. Scope: Self-hosted Pro. Source: https://www.docuseal.com/on-premises (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. GHSA-78g6-f52x-q3jx affects DocuSeal before 3.3.8. A single unauthenticated request can crash a Ruby application worker before routing or authentication. No workaround is documented; update and restart every web and background process. Scope: DocuSeal versions earlier than 3.3.8. Source: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx (reviewed 2026-11-19). Supporting source: 3.3.8 security release — https://github.com/docusealco/docuseal/releases/tag/3.3.8.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose example defines DocuSeal, PostgreSQL and Caddy with persistent storage. It uses moving application/proxy images and example database credentials; pin compatible versions and replace credentials before deployment. Scope: Upstream Compose example; not a hardened production baseline. Source: https://github.com/docusealco/docuseal/blob/master/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/docusealco/docuseal/blob/master/docker-compose.yml. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. The vendor sizes examples for 10,000 signed documents. For one-off templates with one signer and 500-KB average files it lists 1 vCPU, 1 GB RAM and 12 GB disk; larger files, reused templates and multiple signers have different storage needs. PostgreSQL is recommended for heavy production/API use. Scope: Approximate document-based examples, not a 1-TB or HA installation baseline. Source: https://www.docuseal.com/docs/on-premises-server-requirements (reviewed 2026-11-20).

- License pricing: Documented. The 3.3.8 core is AGPLv3. The on-premises page offers free self-hosting and separately prices Pro at $240 per user/year plus $0.20 per document signed through API or embedding. Confirm billable user/document definitions, currency and current terms before quoting. Scope: Self-hosted core versus paid Pro; advertised amounts are not a 100-user total or infrastructure cost. Source: https://www.docuseal.com/on-premises (reviewed 2026-11-20). Supporting source: Versioned core licence — https://github.com/docusealco/docuseal/blob/3.3.8/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. DocuSeal 3.3.8 was published November 19, 2026. It updates Ruby to address GHSA-78g6-f52x-q3jx; all web and background processes must be restarted so the fixed runtime is active. Scope: Upstream DocuSeal core release; separately packaged provider images may lag. Source: https://github.com/docusealco/docuseal/releases/tag/3.3.8 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/docusealco/docuseal/releases/tag/3.3.7. Supporting source: Security advisory — https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx.



### Vendor alternative positioning

Positioning is not a finding of feature parity.

- docusign: The publisher positions DocuSeal as an alternative for document-signing workflows. Source: https://www.docuseal.com/; reviewed 2026-11-16.

- pandadoc: The publisher positions DocuSeal as an alternative for document-signing workflows. Source: https://www.docuseal.com/; reviewed 2026-11-16.


### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- DocuSeal 3.3.8 unauthenticated denial-of-service fix (security-advisory): GHSA-78g6-f52x-q3jx allows one unauthenticated request to crash a Ruby application worker before routing or authentication. Scope: DocuSeal versions earlier than 3.3.8. Conditions: Every web and background process still using the affected Ruby runtime remains exposed; the advisory documents no workaround. Action: Upgrade to 3.3.8 or later, restart every Ruby process and verify the active runtime. Source: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx; reviewed 2026-11-19. Supporting source: 3.3.8 security release — https://github.com/docusealco/docuseal/releases/tag/3.3.8.




## DokuWiki

File-based wiki for documentation and shared knowledge.

- Listing: https://launchinyourcloud.com/directory/dokuwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: DokuWiki web application with persistent wiki pages, configuration and attachments.
- 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://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version.

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

DokuWiki web application with persistent wiki pages, configuration and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: File-based wiki for documentation and shared knowledge.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/dokuwiki.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/dokuwiki
  DokuWiki web application with persistent wiki pages, configuration and attachments. Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version. 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 splitbrain, selfthinker, Klap-in, 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/dokuwiki/dokuwiki/graphs/contributors

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

### Sources

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

- Railway: https://railway.com/deploy/dokuwiki

- AWS Marketplace: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg

- GPL-2.0 COPYING: https://github.com/dokuwiki/dokuwiki/blob/master/COPYING

- Releases 2026-07-14c: https://github.com/dokuwiki/dokuwiki/releases

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

### Licensing sources

- https://github.com/dokuwiki/dokuwiki/blob/master/COPYING

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from TurnKey GNU/Linux. Its package version is 19.0.3; verify the contained application and required entitlements separately. Scope: DokuWiki selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg (reviewed 2026-11-19). Offer prodview-h7wozgfyl3vfg: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The maintainer-provided oauth plugin implements login through OAuth services. It is a separately installed authentication plugin, not a guarantee that the default wiki has corporate SAML/OIDC configured; validate provider-plugin and DokuWiki release compatibility. Scope: CosmoCode DokuWiki OAuth plugin integration. Source: https://raw.githubusercontent.com/cosmocode/dokuwiki-plugin-oauth/master/README (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 DokuWiki container repository documents a non-root image, persistent /storage volume and a Compose example. Configure the initial wiki securely, set writable storage ownership and pin a supported release rather than a moving tag. Scope: Official DokuWiki application container packaging; not cloud-account HA IaC. Source: https://raw.githubusercontent.com/dokuwiki/docker/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/dokuwiki/docker. Artifact reference: master (moving repository); choose a supported version-tagged image.

- 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/dokuwiki.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: DokuWiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/dokuwiki/dokuwiki/blob/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Etherpad

Self-hosted real-time collaborative text editor.

- Listing: https://launchinyourcloud.com/directory/etherpad/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, 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: Cloudron package; Application platform deployment
- Architecture: Etherpad application, database and persistent plugins and settings.
- 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://etherpad.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version.

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

Etherpad application, database and persistent plugins and settings. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted real-time collaborative text editor.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/etherpad.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/etherpad
  Etherpad application, database and persistent plugins and settings. Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. 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 JohnMcLear, rhansen, Pita, 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/ether/etherpad/graphs/contributors

- Upstream project: https://github.com/ether/etherpad

### Sources

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

- Railway: https://railway.com/deploy/etherpad

- Apache-2.0 LICENSE: https://github.com/ether/etherpad-lite/blob/develop/LICENSE

- Releases v3.3.19: https://github.com/ether/etherpad-lite/releases

- Etherpad | Cloudron Docs: https://docs.cloudron.io/packages/etherpad/

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

- Etherpad authentication and author-token advisories: https://github.com/ether/etherpad/security/advisories/GHSA-62cj-9j72-mfrh

### Licensing sources

- https://github.com/ether/etherpad-lite/blob/develop/LICENSE

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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: Sources checked — unresolved. The reviewed configuration includes an embedded OIDC issuer with admin/user clients, and the API supports mapping a host application’s users and permissions. This does not establish login federation to an existing corporate SAML/OIDC IdP for the selected pad/admin deployment. Confirm the supported external-auth plugin or portal integration. Scope: Embedded identity issuer and host API integration are distinct from external-IdP federation. Source: https://raw.githubusercontent.com/ether/etherpad/develop/settings.json.template (reviewed 2026-11-20). Supporting source: Official host-user/API integration design — https://docs.etherpad.org/api/http_api.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker documentation provides container/environment configuration and persistent data/plugin handling. Pin compatible application/plugins, supply a production database and secrets, and configure the reverse proxy. A standalone container does not by itself supply durable clustered operation or external-user SSO. Scope: Upstream Etherpad container deployment and configuration. Source: https://docs.etherpad.org/docker.html (reviewed 2026-11-20). Deployment artifact: https://github.com/ether/etherpad/blob/develop/doc/docker.md. Artifact reference: develop (moving branch); pin application and compatible plugins.

- Minimum footprint / sizing: Documented. The Cloudron package declares 768MB 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/etherpad.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Etherpad authentication and author-token advisories (security-advisory): Upstream documents an OIDC login bypass and an author-token isolation correction in separate advisories. Scope: GHSA-62cj-9j72-mfrh and GHSA-746x-9w89-7xv6; consult each notice for its own affected and fixed versions. Conditions: OIDC/password configuration and clients without author tokens change exposure; plugin/package versions must be checked separately. Action: Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version. Source: https://github.com/ether/etherpad/security/advisories/GHSA-62cj-9j72-mfrh; reviewed 2026-11-19. Supporting source: Author-token isolation advisory — https://github.com/ether/etherpad/security/advisories/GHSA-746x-9w89-7xv6.




## Grav

Self-hosted flat-file content management system.

- Listing: https://launchinyourcloud.com/directory/grav/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: linode, aws, digitalocean, vultr, hostinger, lumadock
- 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
- Architecture: Grav PHP application and persistent content, configuration and plugins.
- 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://getgrav.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

No relational database is required by the base system; plugins and themes can introduce their own dependencies and licences. Cloudron package and upstream versions can differ.

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

Grav PHP application and persistent content, configuration and plugins. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted flat-file content management system.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (linode, aws, digitalocean, vultr, hostinger, lumadock): https://www.cloudron.io/store/grav.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.


### Community and maintenance

The reviewed upstream contributor history includes rhukster, flaviocopes, w00fz, 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/getgrav/grav/graphs/contributors

- Upstream project: https://github.com/getgrav/grav

### Sources

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

- Akamai Quick Deploy: https://techdocs.akamai.com/quick-deploy-apps/docs/grav

- MIT LICENSE.txt: https://github.com/getgrav/grav/blob/develop/LICENSE.txt

- Releases v2.2.30: https://github.com/getgrav/grav/releases

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

### Licensing sources

- https://github.com/getgrav/grav/blob/develop/LICENSE.txt

### Infrastructure sources

- https://www.cloudron.io/store/grav.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 Grav project documents the Trilby Media login-oauth2 plugin for third-party OAuth2 login, extending the core Login plugin with named and custom providers. Validate plugin/core compatibility and the intended login surface; the old announcement is not proof that every current Admin deployment supports every provider. Scope: Official project announcement plus maintained plugin implementation; OAuth2 Login integration. Source: https://getgrav.org/blog/oauth2-and-ldap-login-plugins (reviewed 2026-11-20). Supporting source: Login OAuth2 maintainer repository — https://github.com/trilbymedia/grav-plugin-login-oauth2.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide supplies version-addressable ZIP packages, Composer installation and source installation. The Admin package includes the Admin plugin. This establishes a deployable application artifact, not a cloud-infrastructure or HA template. Scope: Versioned Grav 1.7 guide; verify current major-version compatibility. Source: https://learn.getgrav.org/17/basics/installation (reviewed 2026-11-20). Deployment artifact: https://getgrav.org/downloads. Artifact reference: Choose a tagged Grav/Core-plus-Admin package; do not assume current downloads match 1.7 instructions.

- 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/grav.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: Grav; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/getgrav/grav/blob/develop/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Infisical Self-Hosted

Self-hosted secrets-management platform with application and machine-identity access workflows.

- Listing: https://launchinyourcloud.com/directory/infisical-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core outside enterprise directories; enterprise features and third-party components have separate terms.
- Licensing model: open-source
- Installation: Official AWS ECS/Fargate and Google GKE deployment guides, or a Vultr Docker Compose guide; configure PostgreSQL, Redis, TLS and encryption keys.
- Architecture: Persistent application containers with PostgreSQL, Redis and cloud networking/secrets services
- Operations: Customer owns the AWS account, Google project or Vultr instance and manages application identity, encryption keys, database recovery and upgrades. Providers operate selected managed infrastructure services.
- Product website: https://infisical.com/
- Source review: 2026-11-19; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Review used upstream 0.167.10. Vendor AWS/GCP examples contain older version placeholders; pin a current compatible image/chart and use the complete installation steps, not the abbreviated infrastructure snippets alone. Preserve encryption keys independently of database backups. Configure telemetry, mail and external secret/infrastructure connections for the intended boundary. Infisical Cloud and agent-only integrations are separate. Infisical v0.167.13 tightens delegated OAuth-token authorization: scope-narrowed tokens no longer pass role-only administration checks, approval/rejection/bypass operations are denied, and workspace listing checks organization permission. Previously accepted delegated-token calls may return 403; retest automation with least-privilege scopes.

The repository licenses code outside ee directories under MIT, enterprise directories under their own license and incorporated third-party components under their original terms. Paid enterprise entitlements must be checked separately.

Persistent application containers with PostgreSQL, Redis and cloud networking/secrets services. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- identity-access-management: Centralizes application secrets and related access/configuration workflows. Certificate, privileged-access and enterprise features depend on the licensed edition and selected components.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx (checked 2026-11-13). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform (checked 2026-11-13). 


### Cloud deployment evidence

- Vendor ECS/Fargate installation in the customer AWS account (aws): https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx
  Includes application task definition and service creation, RDS PostgreSQL, ElastiCache, load balancing, IAM/secrets and upgrade steps. The optional Terraform/CloudFormation summaries are incomplete examples. Use current pinned application versions and review networking, database transport and credentials.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor GKE installation in the customer Google Cloud project (gcp): https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx
  Provisions GKE, Cloud SQL and Memorystore and installs the application Helm release in the operator project. Review supported chart/image versions, VPC access, TLS, key backup and database migrations. This is an application deployment, distinct from connecting Infisical to Google secrets APIs.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vultr application deployment with Docker Compose (vultr): https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform
  Provider instructions install the application, PostgreSQL, Redis and TLS proxy on an operator-controlled Ubuntu server. Customer manages OS, application updates and data/key recovery; generic cloud integrations are not additional hosting evidence.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

Upstream has sustained participation from multiple substantive contributors and frequent maintained releases, including 0.167.10 on the review date. This is a maintained community/commercial project, not a configuration-only Terraform provider.

Reviewed 2026-11-13.

- Reviewed application release: https://github.com/Infisical/infisical/releases/tag/v0.167.10

- Contributor history: https://github.com/Infisical/infisical/graphs/contributors

### Sources

- Official AWS application deployment source: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx

- Official GKE application deployment source: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx

- Standalone runtime requirements: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/standalone-infisical.mdx

- Vultr application deployment with Docker Compose: https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform

- Exact upstream license boundaries: https://github.com/Infisical/infisical/blob/main/LICENSE

- Reviewed application release: https://github.com/Infisical/infisical/releases/tag/v0.167.10

- Contributor history: https://github.com/Infisical/infisical/graphs/contributors

- Infisical v0.167.13 release: https://github.com/Infisical/infisical/releases/tag/v0.167.13

- Delegated-token authorization hardening: https://github.com/Infisical/infisical/pull/9607

### Licensing sources

- https://github.com/Infisical/infisical/blob/main/LICENSE

### Infrastructure sources

- https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx

- https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx

- https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform


### Buyer diligence


Research coverage: 7/12 fields (58%); 6 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: Edition-dependent. The detailed SSO guide explicitly includes free Google/GitHub login on self-hosted instances. SAML and OIDC require a self-hosted Enterprise licence, with organization email-domain verification and provider configuration. The Enterprise guide explains licence activation; Cloud Pro prices do not establish a self-hosted quote or SCIM entitlement. Scope: Explicit self-hosted protocol/edition boundary; resolves the earlier Cloud-matrix-only question. Source: https://infisical.com/docs/documentation/platform/sso/overview (reviewed 2026-11-20). Supporting source: Published v0.167.13 SSO guide — https://github.com/Infisical/infisical/blob/v0.167.13/docs/documentation/platform/sso/overview.mdx. Supporting source: Self-hosted Enterprise licence activation — https://github.com/Infisical/infisical/blob/v0.167.13/docs/self-hosting/ee.mdx.

- SCIM provisioning: Sources checked — unresolved. The pricing page advertises Enterprise SCIM, but explicitly separates self-hosted pricing from Cloud. This pass did not establish the exact self-hosted license and provisioning entitlement; obtain the deployment-specific matrix. Scope: Self-hosted commercial scope unresolved; Cloud tier names are not a substitute. Source: https://infisical.com/pricing (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Documented. v0.167.13 denies delegated OAuth-token approval, rejection and bypass operations, enforces scope checks ahead of role-only administration checks and adds an organization-permission check to workspace listing. Retest delegated automation. Scope: Infisical delegated OAuth tokens; the vendor did not publish a complete affected-version range. Source: https://github.com/Infisical/infisical/pull/9607 (reviewed 2026-11-19). Supporting source: v0.167.13 release — https://github.com/Infisical/infisical/releases/tag/v0.167.13.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official self-hosting guide documents Compose with PostgreSQL and Redis. Configure the required encryption/authentication secrets, persistence and HTTPS; commercial features require their own license entitlement. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://infisical.com/docs/self-hosting/deployment-options/docker-compose (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The small-deployment guide specifies at least two application instances, each 2 CPU cores/4 GB RAM, plus PostgreSQL at 2 vCPU/8 GB/100 GB disk and Redis at 2 vCPU/4 GB/30 GB SSD. Redis is a persistent required datastore, not a disposable cache. These component baselines need additional replication/storage planning for your throughput, audit retention and HA targets. Scope: Current self-hosted application, PostgreSQL and Redis resource guidance; not a total operating-cost estimate. Source: https://infisical.com/docs/self-hosting/configuration/requirements (reviewed 2026-11-20).

- License pricing: Documented. The pricing FAQ explicitly says self-hosted pricing differs from Infisical Cloud and directs buyers to contact the vendor. Public Cloud per-identity prices must not be used as a self-hosted quote. Scope: Vendor self-hosted pricing policy; no infrastructure or labor estimate. Source: https://infisical.com/pricing (reviewed 2026-11-14).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Infisical v0.167.13 was published November 19, 2026. It tightens delegated OAuth-token authorization and may cause formerly accepted scope-narrowed administration calls to return 403. Scope: Upstream Infisical self-hosted release; cloud packages and commercial editions may differ. Source: https://github.com/Infisical/infisical/releases/tag/v0.167.13 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/Infisical/infisical/releases/tag/v0.167.10. Supporting source: Authorization change — https://github.com/Infisical/infisical/pull/9607.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Infisical v0.167.13 delegated-token authorization hardening (security-advisory): Infisical now enforces delegated OAuth-token scopes ahead of role-only administration checks and denies approval, rejection and bypass operations. Scope: Delegated OAuth tokens and workspace listing; no complete affected-version range was published. Conditions: Scope-narrowed delegated tokens and automation using administration or workspace-list operations are affected; some calls may newly return 403. Action: Upgrade to v0.167.13 or later and retest least-privilege delegated automation. Source: https://github.com/Infisical/infisical/pull/9607; reviewed 2026-11-19. Supporting source: v0.167.13 release — https://github.com/Infisical/infisical/releases/tag/v0.167.13.




## Joomla!

Customer-operated content management and website publishing platform.

- Listing: https://launchinyourcloud.com/directory/joomla/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci, digitalocean, linode, vultr, northflank
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-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: Joomla web application, database, web server and persistent site assets.
- 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.joomla.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 Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.

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

Joomla web application, database, web server and persistent site assets. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Customer-operated content management and website publishing platform.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/joomla-with-mds/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/openlitespeed-joomla (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application (checked 2026-11-19). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/deploy-joomla-on-northflank (checked 2026-11-19). 


### Cloud deployment evidence

- OCI Architecture (oci): https://docs.oracle.com/en/solutions/joomla-with-mds/
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/openlitespeed-joomla
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Akamai Quick Deploy (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/joomla
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Vultr Docs (vultr): https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Northflank Guide (northflank): https://northflank.com/guides/deploy-joomla-on-northflank
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes brianteeman, wilsonge, infograf768, 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/joomla/joomla-cms/graphs/contributors

- Upstream project: https://github.com/joomla/joomla-cms

### Sources

- OCI Architecture: https://docs.oracle.com/en/solutions/joomla-with-mds/

- DO Marketplace: https://marketplace.digitalocean.com/apps/openlitespeed-joomla

- Akamai Quick Deploy: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla

- Vultr Docs: https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application

- Northflank Guide: https://northflank.com/guides/deploy-joomla-on-northflank

- GPL-2.0 LICENSE.txt: https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt

- Releases v6.2.1-rc1: https://github.com/joomla/joomla-cms/releases

### Licensing sources

- https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt

### Infrastructure sources

- https://docs.oracle.com/en/solutions/joomla-with-mds/

- https://marketplace.digitalocean.com/apps/openlitespeed-joomla

- https://techdocs.akamai.com/quick-deploy-apps/docs/joomla

- https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application

- https://northflank.com/guides/deploy-joomla-on-northflank


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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: Edition-dependent. miniOrange publishes a SAML service-provider extension and explicitly states Joomla 3/4/5/6 compatibility. This is a third-party extension with its own plan and support terms, not an included Joomla-core feature; validate the exact site version, provider and purchased plugin capabilities. Scope: Extension vendor documentation for Joomla 6-compatible SAML; not upstream Joomla support. Source: https://plugins.miniorange.com/joomla-single-sign-on-sso (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. Akamai documents deploying its Joomla Quick Deploy application through Cloud Manager, API, CLI or Terraform using StackScript 985372. This is a provider-maintained package/recipe; verify the installed Joomla version and upgrade path separately from the upstream release. Scope: Akamai/Linode Joomla application deployment recipe; not a Joomla upstream HA template. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla (reviewed 2026-11-20). Deployment artifact: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla. Artifact reference: Current provider StackScript 985372 examples; package/application versions can differ.

- Minimum footprint / sizing: Sources checked — unresolved. The current Joomla 6.x technical requirements recommend a PHP memory limit of at least 256 MB and specify supported PHP, database and web-server versions. That limit is per PHP process, not a VM/RAM or HA capacity floor; whole-deployment sizing remains unconfirmed. Scope: Joomla 6.x software requirements; no complete host footprint established. Source: https://manual.joomla.org/docs/next/get-started/technical-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Joomla!; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Joplin Server

Personal-use self-hosted synchronization server for Joplin notes.

- Listing: https://launchinyourcloud.com/directory/joplin-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.
- Licensing model: source-available
- Installation: Cloudron package; Docker / Compose
- Architecture: Joplin Server, database and persistent 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://joplinapp.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 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.

Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.

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


### Category fit

- document-management: Personal-use self-hosted synchronization server for Joplin notes.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/joplin-server.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.


### Sources

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

- Hostinger: https://www.hostinger.com/applications/joplin-server

- Joplin Server Personal Use License: https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md

- GitHub Releases: https://github.com/laurent22/joplin/releases

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

### Licensing sources

- https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md

### Infrastructure sources

- https://www.cloudron.io/store/joplin-server.html


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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. 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. Scope: Self-hosted Joplin Server SAML; supported clients, session policy and business licensing must be checked. Source: https://joplinapp.org/help/apps/server/saml/ (reviewed 2026-11-20). Supporting source: Server Business and self-hosted licensing context — https://joplinapp.org/help/apps/joplin_server_business/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. 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 (reviewed 2026-11-20). Deployment artifact: https://github.com/laurent22/joplin/blob/dev/docker-compose.server.yml. Artifact reference: dev (moving branch); use a compatible published server image tag.

- Minimum footprint / sizing: Documented. 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. 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/ (reviewed 2026-11-20). Supporting source: Previously reviewed Cloudron app package allocation — https://www.cloudron.io/store/joplin-server.html.

- License pricing: Edition-dependent. Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization. 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 (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Lychee

Self-hosted photo gallery, albums and image sharing.

- Listing: https://launchinyourcloud.com/directory/lychee/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- 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; Docker / Compose
- Architecture: Lychee application, database and persistent originals and thumbnails.
- 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://lycheeorg.dev
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Public, protected and private album modes must be configured deliberately; hosting the server does not make every gallery private.

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

Lychee application, database and persistent originals and thumbnails. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted photo gallery, albums and image sharing.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/lychee.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.


### Community and maintenance

The reviewed upstream contributor history includes ildyria, kamil4, nagmat84, 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/LycheeOrg/Lychee/graphs/contributors

- Upstream project: https://github.com/LycheeOrg/Lychee

### Sources

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

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

- MIT LICENSE: https://raw.githubusercontent.com/LycheeOrg/Lychee/master/LICENSE

- GitHub Releases: https://github.com/LycheeOrg/Lychee/releases

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

### Licensing sources

- https://raw.githubusercontent.com/LycheeOrg/Lychee/master/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/lychee.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. Lychee v7.13.0 implements configured OAuth provider redirects/callbacks and signs users into the gallery through linked provider accounts. Optional first-login user creation is separately configurable. Configure a supported provider, credentials, callback and account-linking policy; this does not establish arbitrary SAML/SCIM support or inclusion in every Cloudron package. Scope: Upstream Lychee v7.13.0 gallery-user OAuth login; packaging and configured-provider scope. Source: https://github.com/LycheeOrg/Lychee/blob/v7.13.0/app/Actions/Oauth/Oauth.php (reviewed 2026-11-21). Supporting source: OAuth redirect/callback controller — https://github.com/LycheeOrg/Lychee/blob/v7.13.0/app/Http/Controllers/OauthController.php.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream v7.13.0 repository provides a Docker Compose configuration for the gallery, persistent uploads and supporting services. The example defaults to a moving latest application image: pin a compatible image, configure database/secrets and storage, and review its security and worker settings before production. The current install guide also links a minimal quick start. Scope: Versioned upstream Compose example; example image tags and current online quick start require explicit release selection. Source: https://github.com/LycheeOrg/Lychee/blob/v7.13.0/docker-compose.yaml (reviewed 2026-11-21). Deployment artifact: https://github.com/LycheeOrg/Lychee/blob/v7.13.0/docker-compose.yaml. Artifact reference: v7.13.0. Supporting source: Installation guide — https://lycheeorg.dev/docs/getting-started/installation/.

- 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/lychee.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: Lychee; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/LycheeOrg/Lychee/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v7.13.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Lychee upstream application; verify compatibility with the selected package. Source: https://github.com/LycheeOrg/Lychee/releases/tag/v7.13.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).







## NirvaShare

Commercial self-hosted gateway for controlled sharing of customer object storage.

- Listing: https://launchinyourcloud.com/directory/nirvashare/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: CloudFormation; VM image
- Architecture: NirvaShare application services on a customer VM with configured object-storage and identity-provider access.
- 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://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

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.


### Category fit

- document-management: Commercial self-hosted gateway for controlled sharing of customer object storage.

- data-rooms-ma-document-management: Commercial self-hosted gateway for controlled sharing of customer object storage.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/nirvashare (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nirvashare.com/docs/deployment/cloud-platforms/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace CFT (aws): https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs
  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.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/nirvashare
  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.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Cloud Platforms (vultr): https://nirvashare.com/docs/deployment/cloud-platforms/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Marketplace CFT: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs

- DO Marketplace: https://marketplace.digitalocean.com/apps/nirvashare

- Cloud Platforms: https://nirvashare.com/docs/deployment/cloud-platforms/

- AWS CFT Docs: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/

- Pricing: https://nirvashare.com/pricing/

- Release Notes: https://nirvashare.com/release-notes/

### Licensing sources

- https://nirvashare.com/pricing/

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs

- https://marketplace.digitalocean.com/apps/nirvashare

- https://nirvashare.com/docs/deployment/cloud-platforms/


### 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: Documented. 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. Scope: NirvaShare selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs (reviewed 2026-11-19). Offer prodview-k6zpjoiopyrzs: Nirvato Software Pvt Ltd; CloudFormation Template (CFT); package 6.4.1; https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. 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/ (reviewed 2026-11-20). Supporting source: Admin-console SSO configuration properties — https://nirvashare.com/docs/deployment/nirvashare-config-properties/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. 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/ (reviewed 2026-11-20). Deployment artifact: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/. Artifact reference: Documentation updated 2025-01-10; not executed. Supporting source: Current minimum disk requirement — https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/.

- Minimum footprint / sizing: Documented. 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. Scope: Vendor Linux server baseline; workload and HA sizing excluded. Source: https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: NirvaShare; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://nirvashare.com/pricing/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Omeka S

Digital collections publishing for libraries, archives, museums and research institutions.

- Listing: https://launchinyourcloud.com/directory/omeka-s/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3 application; the packaged OIDC module is GPL-3.0-or-later.
- Licensing model: open-source
- Installation: Cloudron package on a customer VM; upstream also documents a PHP/MySQL installation.
- Architecture: Persistent PHP application with MySQL, collection files, configuration, themes and extension modules
- Operations: Customer manages collection access, researcher/editor roles, modules and themes, mail, database and file backups, restoration and coordinated upgrades.
- Product website: https://omeka.org/s/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Reviewed Cloudron 1.6.1 contains Omeka S 4.2.1 and OIDC module 1.2.0, whose declared compatibility covers Omeka S 4.x. The current package uses OIDC although its package manual still describes LDAP. Change initial administrator credentials, review identity/account linking and researcher defaults, and check extension compatibility before upgrades. Preserve the database, configuration, collection files, modules and themes. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.

GPLv3 application; the packaged OIDC module is GPL-3.0-or-later. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.

Persistent PHP application with MySQL, collection files, configuration, themes and extension modules. Cloudron provides a persistent server application, not event-driven application functions.


### Category fit

- archives-collections-management: Describes digital collection items and media with shared metadata, item sets, linked data and independently curated public exhibits. This does not establish formal retention or legal-hold controls.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (checked 2026-11-13). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/cloudron (checked 2026-11-13). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.linode.com/docs/marketplace-docs/guides/cloudron/ (checked 2026-11-13). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudron.io/installation/ (checked 2026-11-13). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-13). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://lumadock.com/vps-hosting/cloudron (checked 2026-11-13). 


### Cloud deployment evidence

- Cloudron EC2 AMI and application installation (aws): https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Droplet deployment (digitalocean): https://marketplace.digitalocean.com/apps/cloudron
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Linode deployment (linode): https://www.linode.com/docs/marketplace-docs/guides/cloudron/
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron named-provider installation and Marketplace availability (vultr): https://docs.cloudron.io/installation/
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
  Source type: package-platform-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Hostinger customer VPS Cloudron template (hostinger): https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- LumaDock customer VPS Cloudron template (lumadock): https://lumadock.com/vps-hosting/cloudron
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

The Corporation for Digital Scholarship maintains Omeka S with an institutional community. Its showcase documents library and university collections, including Yale and the University of Utah, alongside continuing upstream releases. These establish real collection use, not provider certification.

Reviewed 2026-11-13.

- Institutional deployments: https://omeka.org/s/showcase/

- Project stewardship: https://omeka.org/s/

- Maintained release: https://github.com/omeka/omeka-s/releases/tag/v4.2.1

### Sources

- Official application scope and stewardship: https://omeka.org/s/

- Installation, requirements and upgrades: https://omeka.org/s/docs/user-manual/install/

- Extension compatibility: https://omeka.org/s/docs/user-manual/modules/

- Application user roles: https://omeka.org/s/docs/user-manual/admin/users/

- Cloudron package operations; identity manual lags current manifest: https://docs.cloudron.io/packages/omekas/

- Reviewed upstream release: https://github.com/omeka/omeka-s/releases/tag/v4.2.1

- Core GPL license: https://github.com/omeka/omeka-s/blob/v4.2.1/LICENSE

- Packaged OIDC module: https://github.com/cloudron-io/OmekaS-OIDC

- OIDC 1.2.0 compatibility: https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/config/module.ini

- OIDC module license: https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/composer.json

- Institutional collection deployments: https://omeka.org/s/showcase/

- Cloudron application packages and persistent data: https://docs.cloudron.io/apps/

- Cloudron application updates: https://docs.cloudron.io/updates/

- Cloudron database and application-data backups: https://docs.cloudron.io/backups/

- Cloudron platform plans: https://www.cloudron.io/pricing.html

- Cloudron account and platform terms: https://www.cloudron.io/legal/terms.html

- Cloudron account and installation metadata: https://www.cloudron.io/legal/privacy.html

- Exact Cloudron application package versions: https://www.cloudron.io/store/index.html

- Cloudron EC2 AMI and application installation: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

- Cloudron customer Droplet deployment: https://marketplace.digitalocean.com/apps/cloudron

- Cloudron customer Linode deployment: https://www.linode.com/docs/marketplace-docs/guides/cloudron/

- Cloudron named-provider installation and Marketplace availability: https://docs.cloudron.io/installation/

- Hostinger customer VPS Cloudron template: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/

- LumaDock customer VPS Cloudron template: https://lumadock.com/vps-hosting/cloudron

### Licensing sources

- https://github.com/omeka/omeka-s/blob/v4.2.1/LICENSE

- https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/composer.json

- https://www.cloudron.io/legal/terms.html

- https://www.cloudron.io/pricing.html

### Infrastructure sources

- https://docs.cloudron.io/packages/omekas/

- https://docs.cloudron.io/installation/


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 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: Documented. AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate. Scope: Cloudron platform plus separate application package. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (reviewed 2026-11-14). Supporting source: Cloudron application package — https://docs.cloudron.io/packages/omekas/. Offer prodview-aep3gt5elubci: Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application); https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The optional OIDC 1.2.0 module documents institutional user login, PKCE, claim/group-based roles and just-in-time provisioning, with PHP 8.1+ and Omeka S ^4.0 compatibility. Install and configure the module and IdP deliberately; this does not establish that every Cloudron or VPS image includes it. Scope: Third-party module-maintainer evidence for Omeka S user OIDC, distinct from the upstream core and packaged defaults. Source: https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/README.md (reviewed 2026-11-21). Supporting source: Versioned module compatibility declaration — https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/config/module.ini.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream manual documents a PHP application distribution with MySQL/MariaDB, writable files and configuration. These requirements describe upstream Omeka S, not the separately maintained Cloudron package. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://omeka.org/s/docs/user-manual/install/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The upstream installation manual identifies PHP extensions, database, web-server and filesystem requirements, while Cloudron documents its separate package configuration. Neither reviewed page establishes a quantitative production CPU/RAM/storage baseline for the repository, media derivatives, indexing and HA. Scope: Omeka S upstream requirements; no verified whole-host or Cloudron application memory minimum. Source: https://omeka.org/s/docs/user-manual/install/ (reviewed 2026-11-21). Supporting source: Cloudron package documentation — https://docs.cloudron.io/packages/omekas/.

- License pricing: Documented. The v4.2.1 core is GPLv3 licensed. Modules, themes, hosting and Cloudron or other packaged-platform subscriptions have separate terms; their charges are not an Omeka S core software licence fee. Scope: Versioned upstream Omeka S core; no packaged-platform or optional-module entitlement inferred. Source: https://github.com/omeka/omeka-s/blob/v4.2.1/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

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







## ONLYOFFICE Docs (Community Edition)

Community browser-based office document editing and co-authoring server.

- Listing: https://launchinyourcloud.com/directory/onlyoffice-docs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hetzner, hostinger, lumadock
- 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: Cloudron package
- Architecture: ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform.
- 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.onlyoffice.com/see-it-in-action
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. The supplied Vultr article installs DocSpace rather than Docs; the Vultr badge here comes from the reviewed Cloudron Docs package instead.

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

ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Community browser-based office document editing and co-authoring server.

### Deployment boundaries


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

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

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice (checked 2026-11-19). 

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

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/ (checked 2026-11-19). 

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, vultr, hostinger, lumadock): https://www.cloudron.io/store/onlyoffice-docs.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.

- Akamai Quick Deploy (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice
  ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. This source is distinct from the Cloudron package.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Hetzner Tutorial (hetzner): https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/
  ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. 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 agolybev, ShockwaveNN, trofim24, 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/ONLYOFFICE/DocumentServer/graphs/contributors

- Upstream project: https://github.com/ONLYOFFICE/DocumentServer

### Sources

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

- Akamai Quick Deploy: https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice

- Hetzner Tutorial: https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/

- AGPL-3.0 LICENSE: https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE

- Releases v10.0.0: https://github.com/ONLYOFFICE/DocumentServer/releases

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

### Licensing sources

- https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/onlyoffice-docs.html

- https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice

- https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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: Sources checked — unresolved. The reviewed Docs integration uses a host platform and signed JWT requests to the editor service. This does not establish standalone SAML/OIDC user login in the listed Docs Community engine. Confirm the identity-providing host and connector instead of transferring DocSpace SSO claims. Scope: Docs Community editor engine; host-platform identity is a separate layer. Source: https://helpcenter.onlyoffice.com/docs/installation/docs-community-install-docker.aspx (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 Community guide installs the DocumentServer container with persistent data and configuration, including the JWT secret used by host integrations. The editor service still needs a document-management host/connector; deploying it alone does not supply a complete authenticated collaboration portal. Scope: ONLYOFFICE Docs Community editor-engine container, not DocSpace/Workspace. Source: https://helpcenter.onlyoffice.com/docs/installation/docs-community-install-docker.aspx (reviewed 2026-11-20). Deployment artifact: https://github.com/ONLYOFFICE/Docker-DocumentServer. Artifact reference: Current official Community Docker guide; pin an application-compatible image.

- Minimum footprint / sizing: Documented. The Cloudron package declares 2048MB 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/onlyoffice-docs.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: ONLYOFFICE Docs (Community Edition); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Overleaf Community Edition

Community collaborative LaTeX document authoring server.

- Listing: https://launchinyourcloud.com/directory/overleaf-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr
- 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: Docker / Compose
- Architecture: Overleaf web application, MongoDB, Redis, TeX toolchain and 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://github.com/overleaf/overleaf
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Community and Server Pro have different security and support entitlements. Treat TeX input as executable content and review compiler isolation; obsolete 2015 GitHub Releases are not current application snapshots. Sandboxed Compiles is documented as a Server Pro feature; do not expose Community to untrusted TeX authors on the assumption it has equivalent isolation.

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

Overleaf web application, MongoDB, Redis, TeX toolchain and document storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Community collaborative LaTeX document authoring server.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-overleaf-open-source-latex-collaboration-platform (checked 2026-11-19). 


### Cloud deployment evidence

- Vultr Docs (vultr): https://docs.vultr.com/how-to-deploy-overleaf-open-source-latex-collaboration-platform
  Overleaf web application, MongoDB, Redis, TeX toolchain and document storage. Community and Server Pro have different security and support entitlements. Treat TeX input as executable content and review compiler isolation; obsolete 2015 GitHub Releases are not current application snapshots. Sandboxed Compiles is documented as a Server Pro feature; do not expose Community to untrusted TeX authors on the assumption it has equivalent isolation.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes das7pad, briangough, aeaton-overleaf, 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/overleaf/overleaf/graphs/contributors

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

### Sources

- Vultr Docs: https://docs.vultr.com/how-to-deploy-overleaf-open-source-latex-collaboration-platform

- AGPL-3.0 LICENSE: https://github.com/overleaf/overleaf/blob/main/LICENSE

- Commits 2026-09: https://github.com/overleaf/overleaf/commits/main

- Sandboxed Compiles | On-premises | Overleaf docsGitBook AssistantGitBook AssistantGitBook AssistantGitBook AssistantGitBook AssistantGitBook Assistant: https://docs.overleaf.com/on-premises/configuration/overleaf-toolkit/server-pro-only-configuration/sandboxed-compiles

### Licensing sources

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

### Infrastructure sources

- https://docs.vultr.com/how-to-deploy-overleaf-open-source-latex-collaboration-platform


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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: Explicitly unsupported. The upstream edition comparison explicitly excludes SAML 2/LDAP SSO from Community Edition and includes it in separately licensed Server Pro. A hosted Professional subscription does not grant Server Pro rights. Scope: Listed Overleaf Community Edition; Server Pro is a different edition. Source: https://docs.overleaf.com/on-premises/welcome/server-pro-vs.-community-edition (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 Overleaf Toolkit wraps Docker Compose and manages application, MongoDB and Redis containers for Community Edition or separately licensed Server Pro. Its default single-server topology does not provide Server Pro entitlements, sandboxed compiles or HA. Scope: Official on-premises Toolkit; Community edition restrictions remain applicable. Source: https://docs.overleaf.com/on-premises/getting-started/what-is-the-overleaf-toolkit (reviewed 2026-11-20). Deployment artifact: https://github.com/overleaf/toolkit. Artifact reference: Moving Toolkit repository; pin compatible configuration/application versions.

- Minimum footprint / sizing: Documented. The shared on-premises guide lists a basic minimum of 2 CPU cores and 3 GB RAM for roughly five concurrent users. Document size and compilation concurrency drive growth; its larger Server Pro examples and horizontal-scaling features are not Community HA guarantees. Scope: Basic on-premises baseline, with edition-specific scaling limitations. Source: https://docs.overleaf.com/on-premises/getting-started/requirements/hardware-requirements (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: Overleaf Community Edition; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/overleaf/overleaf/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## PeerTube

Self-hosted video publishing and federated media platform.

- Listing: https://launchinyourcloud.com/directory/peertube/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- 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: Cloudron package; Docker / Compose
- Architecture: PeerTube application, PostgreSQL, Redis, video storage and processing workers.
- 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://joinpeertube.org/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

PeerTube 8.3.2 includes a sharp/libvips security update. Federation and optional peer-to-peer playback share metadata or traffic outside the host; review those settings for confidential media. Update PeerTube and its bundled image-processing dependencies through the compatible 8.3.2-or-later upgrade process.

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

PeerTube application, PostgreSQL, Redis, video storage and processing workers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted video publishing and federated media platform.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/peertube.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.


### Community and maintenance

The reviewed upstream contributor history includes Chocobozzz, rigelk, s8321414, 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/Chocobozzz/PeerTube/graphs/contributors

- Upstream project: https://github.com/Chocobozzz/PeerTube

### Sources

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

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

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/Chocobozzz/PeerTube/develop/LICENSE

- GitHub Releases: https://github.com/Chocobozzz/PeerTube/releases

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

- PeerTube image-processing dependency update: https://github.com/Chocobozzz/PeerTube/releases/tag/v8.3.2

### Licensing sources

- https://raw.githubusercontent.com/Chocobozzz/PeerTube/develop/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/peertube.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. PeerTube documents external authentication plugins, and Framasoft maintains an official OIDC plugin that adds provider login to the user form, with a callback, role mapping and optional group restrictions. Configure a compatible plugin release and account-migration policy. This is user federation via an optional plugin, not the core API password-token flow or a guarantee for every packaged installation. Scope: Self-hosted PeerTube external user authentication; optional official plugin and deployment/version compatibility. Source: https://docs.joinpeertube.org/admin/managing-users (reviewed 2026-11-21). Supporting source: Official OIDC plugin documentation — https://framagit.org/framasoft/peertube/official-plugins/-/blob/master/peertube-plugin-auth-openid-connect/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. PeerTube supplies a versioned production Docker Compose example and an installation guide covering the application, reverse proxy, PostgreSQL, Redis, configuration and persistent volumes. Match the example to the application image, set domains/secrets and TLS, and size transcoding/storage and backup arrangements separately; a single Compose host does not establish HA. Scope: Upstream PeerTube v8.3.2 production container example; platform packaging and HA are separate concerns. Source: https://github.com/Chocobozzz/PeerTube/blob/v8.3.2/support/docker/production/docker-compose.yml (reviewed 2026-11-21). Deployment artifact: https://github.com/Chocobozzz/PeerTube/blob/v8.3.2/support/docker/production/docker-compose.yml. Artifact reference: v8.3.2. Supporting source: Docker installation — https://docs.joinpeertube.org/install/docker.

- Minimum footprint / sizing: Documented. The Cloudron package declares 1024MB 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/peertube.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- PeerTube image-processing dependency update (security-advisory): PeerTube 8.3.2 includes security maintenance for its image-processing dependency. Scope: PeerTube 8.3.2 release and its sharp/libvips change; check the actual dependency build rather than inferring all older versions are affected. Conditions: Exposure depends on the installed image-processing libraries and enabled input paths. Action: Update PeerTube and its bundled image-processing dependencies through the compatible 8.3.2-or-later upgrade process. Source: https://github.com/Chocobozzz/PeerTube/releases/tag/v8.3.2; reviewed 2026-11-19.




## Penpot

Self-hosted collaborative interface design and prototyping platform.

- Listing: https://launchinyourcloud.com/directory/penpot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public 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: Penpot frontend, backend, exporter, PostgreSQL, cache and 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://penpot.app
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.

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

Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted collaborative interface design and prototyping platform.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform (checked 2026-11-19). 

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


### Cloud deployment evidence

- Vultr Docs (vultr): https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform
  Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/penpot
  Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes niwinz, Alotor, superalex, 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/penpot/penpot/graphs/contributors

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

### Sources

- Vultr Docs: https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform

- Railway: https://railway.com/deploy/penpot

- MPL-2.0 LICENSE: https://github.com/penpot/penpot/blob/develop/LICENSE

- Releases v2.19.3: https://github.com/penpot/penpot/releases

### Licensing sources

- https://github.com/penpot/penpot/blob/develop/LICENSE

### Infrastructure sources

- https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform

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


### 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 self-hosted configuration guide documents generic OIDC and named OAuth providers. Configure the backend credentials, enabled-login flags and callback URL; LDAP and the application admin surface are separate considerations. Scope: Penpot self-hosted application-user identity configuration. Source: https://help.penpot.app/technical-guide/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 self-hosting guide supplies a Compose file with frontend, backend, exporter, PostgreSQL and persistent assets. Replace the example master secret/database credentials and pin compatible images. A single PostgreSQL container is not database HA. Scope: Upstream Penpot Compose deployment; verify compatibility with the selected provider package. Source: https://help.penpot.app/technical-guide/getting-started/docker/ (reviewed 2026-11-20). Deployment artifact: https://raw.githubusercontent.com/penpot/penpot/develop/docker/images/docker-compose.yaml. Artifact reference: develop (moving branch).

- Minimum footprint / sizing: Documented. The upstream settings guide describes 4 CPUs/16 GB RAM as a reference and recommends an elastic 50–100 GB database starting point for up to ten editors, with growth driven by files and usage. These are vendor guidelines, not a validated 100-user/1-TB HA configuration; add database/asset backups and replicas separately. Scope: Upstream reference settings and elastic database guidance; not a guaranteed capacity benchmark. Source: https://help.penpot.app/technical-guide/getting-started/recommended-settings/ (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## phpBB

Customer-operated discussion forum and community application.

- Listing: https://launchinyourcloud.com/directory/phpbb/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Package / binary installer
- Architecture: phpBB application, 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://www.phpbb.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AWS TurnKey and the Vultr installation are separate delivery paths; the appliance label is not the phpBB release version.

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

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


### Category fit

- collaboration: Customer-operated discussion forum and community application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-lrm7kmwtmipne (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-phpbb-on-ubuntu-22-04 (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-lrm7kmwtmipne
  phpBB application, database and attachment storage. AWS TurnKey and the Vultr installation are separate delivery paths; the appliance label is not the phpBB release version.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Vultr Docs (vultr): https://docs.vultr.com/how-to-deploy-phpbb-on-ubuntu-22-04
  phpBB application, database and attachment storage. AWS TurnKey and the Vultr installation are separate delivery paths; the appliance label is not the phpBB release version.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes marc1706, nickvergessen, bantu, 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/phpbb/phpbb/graphs/contributors

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

### Sources

- AWS Marketplace: https://aws.amazon.com/marketplace/pp/prodview-lrm7kmwtmipne

- Vultr Docs: https://docs.vultr.com/how-to-deploy-phpbb-on-ubuntu-22-04

- GPL-2.0 LICENSE: https://github.com/phpbb/phpbb/blob/master/LICENSE

- Releases v3.3.19: https://github.com/phpbb/phpbb/releases

### Licensing sources

- https://github.com/phpbb/phpbb/blob/master/LICENSE

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-lrm7kmwtmipne

- https://docs.vultr.com/how-to-deploy-phpbb-on-ubuntu-22-04


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from TurnKey GNU/Linux. Its package version is 19.0.3; verify the contained application and required entitlements separately. Scope: phpBB selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-lrm7kmwtmipne (reviewed 2026-11-19). Offer prodview-lrm7kmwtmipne: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-lrm7kmwtmipne.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The upstream 3.3.x OAuth authentication provider implements external-provider login and configurable provider services. This confirms OAuth integration, not a generic SAML/OIDC entitlement; configure a supported provider on a patched release and validate any additional extension separately. Scope: Upstream phpBB 3.3 OAuth user authentication implementation. Source: https://raw.githubusercontent.com/phpbb/phpbb/3.3.x/phpBB/phpbb/auth/provider/oauth/oauth.php (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 3.3.x installation guide documents deploying the application archive and running its installer with a supported database/web server. Restore restrictive file permissions after installation and remove the installer directory. This is an application package, not cloud-infrastructure or HA automation. Scope: Official phpBB 3.3 application installation instructions. Source: https://raw.githubusercontent.com/phpbb/phpbb/3.3.x/phpBB/docs/INSTALL.html (reviewed 2026-11-20). Deployment artifact: https://github.com/phpbb/phpbb/tree/3.3.x. Artifact reference: 3.3.x source/installation guide; select a supported packaged release for deployment.

- Minimum footprint / sizing: Sources checked — unresolved. The 3.3.x installation document establishes web-server/PHP/database dependencies but does not establish a quantitative production CPU/RAM/storage floor for the selected forum workload. Attachment volume, extensions and concurrency need separate sizing. Scope: Upstream installation prerequisites; quantitative production/HA sizing remains open. Source: https://raw.githubusercontent.com/phpbb/phpbb/3.3.x/phpBB/docs/INSTALL.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Piwigo

Self-hosted photo management, albums and media gallery.

- Listing: https://launchinyourcloud.com/directory/piwigo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Docker / Compose
- Architecture: Piwigo application, database, originals and generated images.
- 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://piwigo.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Plugins, storage and published album permissions require separate review; package versions and upstream releases can differ.

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

Piwigo application, database, originals and generated images. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted photo management, albums and media gallery.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/piwigo.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.


### Community and maintenance

The reviewed upstream contributor history includes Piwigo-TranslationTeam, plegall, ddtddt, 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/Piwigo/Piwigo/graphs/contributors

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

### Sources

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

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

- GPL-2.0 COPYING.txt: https://raw.githubusercontent.com/Piwigo/Piwigo/master/COPYING.txt

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

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

### Licensing sources

- https://raw.githubusercontent.com/Piwigo/Piwigo/master/COPYING.txt

### Infrastructure sources

- https://www.cloudron.io/store/piwigo.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 Piwigo extension catalog lists OpenIDConnectNext with Piwigo 16 compatibility. Its maintained plugin documents OIDC login, provider/client configuration and account linking, and reports testing with Piwigo 16.5/PHP 8.4. Install a compatible plugin release and choose the authorization-code flow; this is an optional integration, not automatic federation in every gallery image. Scope: Piwigo 16.x with the maintained ProximApp OpenIDConnectNext plugin; extension evidence rather than universal package inclusion. Source: https://piwigo.org/ext/index.php?eid=1049 (reviewed 2026-11-21). Supporting source: Plugin documentation — https://github.com/ProximApp/PiwigoOpenIdConnectNext/blob/master/README.md. Supporting source: Plugin release v2.2.0 — https://github.com/ProximApp/PiwigoOpenIdConnectNext/releases/tag/v2.2.0.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Piwigo documents downloading the full application archive, uploading it to a PHP web server and running the browser installer with MySQL credentials and a webmaster account. This is a maintained manual installation path, not a cloud provisioning template; select the application release and separately configure hosting, TLS, backups and upgrades. Scope: Upstream self-hosted manual installer; cloud hosting/package automation remains a separate layer. Source: https://github.com/Piwigo/piwigo-docs-en/blob/main/docs/self-hosting-piwigo/install-guides/manual-install.md (reviewed 2026-11-21). Deployment artifact: https://github.com/Piwigo/piwigo-docs-en/blob/main/docs/self-hosting-piwigo/install-guides/manual-install.md. Artifact reference: Current upstream self-hosting manual reviewed on this date. Supporting source: Versioned core release — https://github.com/Piwigo/Piwigo/tree/16.5.0.

- 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/piwigo.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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







## Rallly

Self-hosted group scheduling polls and meeting coordination.

- Listing: https://launchinyourcloud.com/directory/rallly/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, 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: Cloudron package; Application platform deployment
- Architecture: Rallly application, PostgreSQL, persistent storage and outbound email.
- 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://rallly.co
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery.

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

Rallly application, PostgreSQL, persistent storage and outbound email. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted group scheduling polls and meeting coordination.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/rallly.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/rallly
  Rallly application, PostgreSQL, persistent storage and outbound email. Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery. 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 lukevella, snyk-bot, jonas-hoebenreich, 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/lukevella/rallly/graphs/contributors

- Upstream project: https://github.com/lukevella/rallly

### Sources

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

- Railway: https://railway.com/deploy/rallly

- AGPL-3.0 LICENSE: https://github.com/lukevella/rallly/blob/main/LICENSE

- Releases v4.17.1: https://github.com/lukevella/rallly/releases

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

### Licensing sources

- https://github.com/lukevella/rallly/blob/main/LICENSE

### Infrastructure sources

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

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


### 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 self-hosting guide documents Google, Microsoft Entra ID and generic OIDC login from v3.4 onward. Configure callback URLs, verified email claims and linking policy; multi-user licence entitlements are a separate consideration. Scope: Rallly self-hosted user identity; review the selected v4 deployment and license. Source: https://support.rallly.co/self-hosting/single-sign-on (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 installer provisions a Compose stack, generates secrets and supports external database, object storage and reverse-proxy settings. Review the downloaded script before execution, pin compatible images and plan backups; this is not a production HA template. Scope: Current official self-hosting stack and installer. Source: https://support.rallly.co/self-hosting/installation/docker (reviewed 2026-11-20). Deployment artifact: https://get.rallly.co. Artifact reference: Moving official installer; inspect and pin the selected application/stack release.

- Minimum footprint / sizing: Documented. The Cloudron package declares 2048MB 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/rallly.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. The current self-hosting guide states free personal use and asks multi-user installations to purchase a licence key. It lists Plus at $49, Organization at $499 and Enterprise from $999; keys cover Rallly v4.x with tier/user/space limits. Activation requires the licensing service. These runtime-plan terms add detail beyond the repository’s AGPL notice. Scope: Published Rallly v4 self-hosting licence-key tiers; confirm applicable user/space allocation and quote. Source: https://support.rallly.co/self-hosting/licensing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Squidex

Self-hosted headless CMS with structured content, APIs and assets.

- Listing: https://launchinyourcloud.com/directory/squidex/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, render, heroku, vultr
- 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: Application platform deployment
- Architecture: Squidex application, database and asset storage using provider-specific instructions.
- 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://squidex.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 application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.

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

Squidex application, database and asset storage using provider-specific instructions. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted headless CMS with structured content, APIs and assets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2 (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp (checked 2026-11-19). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render (checked 2026-11-19). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EC2 Guide (aws): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Guide (gcp): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Render Guide (render): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Install on Heroku | Squidex (heroku): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Install on Vultr | Squidex (vultr): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes SebastianStehle, kamushadenes, seamys, 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/Squidex/squidex/graphs/contributors

- Upstream project: https://github.com/Squidex/squidex

### Sources

- AWS EC2 Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2

- Azure Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure

- GCP Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp

- Render Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render

- Install on Heroku | Squidex: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku

- Install on Vultr | Squidex: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr

- MIT LICENSE: https://github.com/Squidex/squidex/blob/master/LICENSE

- Releases v7.24.0: https://github.com/Squidex/squidex/releases

### Licensing sources

- https://github.com/Squidex/squidex/blob/master/LICENSE

### Infrastructure sources

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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 official external-identity guide documents configuring an external Azure AD/OAuth identity provider for self-hosted Squidex. The Compose example also exposes Google/GitHub/Microsoft credentials. The separately documented Squidex.Identity project is deprecated and must not be presented as a maintained SSO service. Scope: Self-hosted Squidex external-provider configuration; not the deprecated Squidex.Identity server. Source: https://docs.squidex.io/id-01-getting-started/installation/external-identity-providers (reviewed 2026-11-20). Supporting source: Upstream Compose identity configuration — https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream hosting repository supplies a Compose stack with Squidex 7, MongoDB 6 and a Caddy proxy, persistent mounts and environment-based identity settings. These moving examples need compatible supported image versions, secrets and backups; the stack is not a replicated database/HA design. Scope: Upstream Squidex 7 Compose example; assess database support and image versions separately. Source: https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml (reviewed 2026-11-20). Deployment artifact: https://github.com/Squidex/squidex-hosting/tree/master/docker-compose. Artifact reference: master (moving branch); Squidex major 7 / MongoDB major 6 in reviewed example.

- Minimum footprint / sizing: Sources checked — unresolved. The official Compose stack establishes application, MongoDB and proxy dependencies, but no quantitative CPU/RAM/storage production floor was established in the reviewed installation materials. Confirm content volume, database replication, caches and concurrency before sizing. Scope: Upstream deployment topology; no workload-tested minimum established. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-docker (reviewed 2026-11-20). Supporting source: Reviewed Compose services — https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml.

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

- Operating cost estimate: Not researched.

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







## Supabase Self-Hosted

Self-hosted PostgreSQL application backend with authentication, storage, APIs and realtime services.

- Listing: https://launchinyourcloud.com/directory/supabase/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, railway, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0
- Licensing model: open-source
- Installation: Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server image
- Architecture: Customer-operated PostgreSQL database and containerized backend services
- Operations: Customer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
- Product website: https://supabase.com/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.

The listed self-hosted distribution uses open-source components; the Supabase platform repository is Apache-2.0. Managed-cloud features and paid support are separate from this public self-hosted distribution, and bundled components retain their own licenses.

The official installation runs PostgreSQL and supporting services through Docker Compose on a Linux server or VPS. This is persistent application infrastructure, even when it exposes functions.


### Category fit

- backend-platforms: PostgreSQL-based application backend with authentication, APIs, storage, realtime and functions; self-hosting does not include every managed-platform feature.

- databases-vector: A PostgreSQL-based application data platform with database APIs, authentication and storage services. This entry covers the self-hosted stack.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/supabase-community/supabase-on-aws (checked 2026-11-21). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/guides/supabase (checked 2026-11-21). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application (checked 2026-11-21). 


### Cloud deployment evidence

- Supabase community AWS CloudFormation/CDK deployment (aws): https://github.com/supabase-community/supabase-on-aws
  This project-community template deploys Supabase containers on ECS Fargate with Aurora and Studio on Amplify Hosting. It is an alternative to the upstream Compose layout and does not support pg_graphql/GraphQL. Harden Studio access, review feature differences and operate the AWS resources yourself; this is not managed Supabase.
  Source type: community-template; reviewed: 2026-11-21; vendor support: not-assessed.

- Self-host Supabase in a Railway project (railway): https://railway.com/guides/supabase
  Railway documents a community template for PostgreSQL, authentication, REST, storage, and Studio. The services communicate over private networking in the customer’s Railway project. Railway operates the underlying platform.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.

- Deploy the Supabase Marketplace application on Vultr Compute (vultr): https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application
  Vultr documents selecting the Supabase application while provisioning a Compute server in the customer’s account. The customer chooses the region and plan and administers the installed stack.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Self-hosting scope and responsibilities: https://supabase.com/docs/guides/self-hosting

- Official Docker deployment: https://supabase.com/docs/guides/self-hosting/docker

- Platform repository license: https://raw.githubusercontent.com/supabase/supabase/master/LICENSE

- Self-host Supabase in a Railway project: https://railway.com/guides/supabase

- Deploy the Supabase Marketplace application on Vultr Compute: https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application

### Licensing sources

- https://raw.githubusercontent.com/supabase/supabase/master/LICENSE

- https://supabase.com/docs/guides/self-hosting

### Infrastructure sources

- https://supabase.com/docs/guides/self-hosting/docker


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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 self-hosted Auth service supports external OAuth providers, including a configurable Keycloak issuer. This serves end users of applications built on Supabase; it does not establish organizational SSO for the self-hosted Studio/admin dashboard. Review provider, redirect, signup and administrative access separately. Scope: Self-hosted application-user Auth service; Studio federation excluded. Source: https://raw.githubusercontent.com/supabase/auth/master/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 upstream docker directory contains the multi-service Compose stack and related environment/configuration files. Follow the self-hosting guide for a matching deployment version and replace secrets. Scope: Self-hosted multi-service stack; not the monthly developer newsletter version. Source: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. For all components, the guide gives 2 CPU cores, 4 GB RAM and 40 GB SSD as a minimum; 4 cores, 8 GB+ and 80 GB+ SSD are recommended. Optional analytics increases requirements. Scope: Docker stack for development and small-to-medium production; not every workload. Source: https://supabase.com/docs/guides/self-hosting/docker (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/supabase/supabase/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Taiga

Open-source agile project, issue and team planning application.

- Listing: https://launchinyourcloud.com/directory/taiga/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: Taiga frontend, backend, database, task workers and persistent media.
- 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://github.com/taigaio/taiga-back
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials.

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

Taiga frontend, backend, database, task workers and persistent media. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Open-source agile project, issue and team planning application.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/taiga.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/taiga
  Taiga frontend, backend, database, task workers and persistent media. Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials. 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 bameda, superalex, jespino, 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/taigaio/taiga-back/graphs/contributors

- Upstream project: https://github.com/taigaio/taiga-back

### Sources

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

- Railway: https://railway.com/deploy/taiga

- MPL-2.0 LICENSE: https://github.com/taigaio/taiga-back/blob/main/LICENSE

- Releases v6.10.2: https://github.com/taigaio/taiga-back/releases

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

### Licensing sources

- https://github.com/taigaio/taiga-back/blob/main/LICENSE

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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 self-hosting guide documents GitHub and GitLab OAuth user login, disabled by default. Both backend and frontend settings, registered OAuth clients and public-registration settings must align. This establishes those social/provider login paths, not general SAML/OIDC or Cloudron-package SSO support. Scope: Upstream Taiga user login configuration; packaged distributions may differ. Source: https://docs.taiga.io/setup-production.html (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 taiga-docker repository supplies Compose, initialization configuration and environment settings for application, async worker, database, events and supporting services. Configure secrets, TLS, email and persistent volumes, and align all component image versions before use. Scope: Official self-hosted Compose stack; not the source-development quickstart. Source: https://docs.taiga.io/setup-production.html (reviewed 2026-11-20). Deployment artifact: https://github.com/taigaio/taiga-docker/blob/main/docker-compose.yml. Artifact reference: main (moving branch); choose compatible component release tags.

- Minimum footprint / sizing: Documented. The Cloudron package declares 300MB 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/taiga.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## TriliumNext Notes

Self-hosted hierarchical personal notes and document knowledge base.

- Listing: https://launchinyourcloud.com/directory/triliumnext-notes/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- 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: Cloudron package
- Architecture: TriliumNext server with persistent database and attachments.
- 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://triliumnotes.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 server is primarily a single-user knowledge base; published notes and sharing do not establish a multi-user enterprise collaboration suite.

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

TriliumNext server with persistent database and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted hierarchical personal notes and document knowledge base.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/triliumnext-notes.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.


### Community and maintenance

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.

Reviewed 2026-11-19.

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

- Upstream project: https://github.com/TriliumNext/Trilium

### Sources

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

- AGPL-3.0 LICENSE: https://github.com/TriliumNext/Trilium/blob/main/LICENSE

- Releases v0.107.0: https://github.com/TriliumNext/Trilium/releases

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

### Licensing sources

- https://github.com/TriliumNext/Trilium/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/triliumnext-notes.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. 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. 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 (reviewed 2026-11-20). Supporting source: OpenID Connect configuration — https://docs.triliumnotes.org/user-guide/setup/server/openid-connect.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: TriliumNext self-hosted server; upstream and Cloudron package versions/allocations are separate. Source: https://docs.triliumnotes.org/user-guide/setup/server/installation/docker (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/triliumnext/trilium. Artifact reference: v0.107.0 upstream source reviewed; choose its matching published image tag, not an unpinned latest upgrade.

- 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/triliumnext-notes.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: TriliumNext Notes upstream application; verify compatibility with the selected package. Source: https://github.com/TriliumNext/Trilium/releases/tag/v0.107.0 (reviewed 2026-11-19).







## Typebot

Self-hosted visual conversation and form builder.

- Listing: https://launchinyourcloud.com/directory/typebot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr, hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion.
- Licensing model: source-available
- Installation: Application platform deployment; Docker / Compose
- Architecture: Typebot builder and viewer, database, object storage and mail configuration.
- 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://typebot.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.

FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion.

Typebot builder and viewer, database, object storage and mail configuration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted visual conversation and form builder.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder (checked 2026-11-19). 

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

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production (checked 2026-11-19). 


### Cloud deployment evidence

- Vultr Docs (vultr): https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Hostinger (hostinger): https://www.hostinger.com/applications/typebot
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Vultr Docs: https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder

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

- Railway: https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production

- GitHub LICENSE (FSL-1.1-Apache-2.0): https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE

- GitHub Releases: https://github.com/baptisteArno/typebot.io/releases

### Licensing sources

- https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE

### Infrastructure sources

- https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder

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

- https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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. Self-hosted builder authentication supports named social providers, Microsoft Entra ID, Keycloak and a custom OIDC provider. Published v3.19.1 code registers these providers with its login/session flow. Configure issuer/callback URLs, trusted identity/email and workspace admission policy; this authenticates editors, not every bot respondent, and does not establish SCIM. Scope: Self-hosted builder/editor login, checked against published v3.19.1 implementation. Source: https://docs.typebot.com/self-hosting/configuration.md (reviewed 2026-11-20). Supporting source: Published provider configuration — https://github.com/baptisteArno/typebot.io/blob/v3.19.1/packages/auth/src/lib/providers.ts. Supporting source: Published authentication/session wiring — https://github.com/baptisteArno/typebot.io/blob/v3.19.1/packages/auth/src/lib/nextAuth.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide links a Compose stack for separate builder/viewer applications, PostgreSQL and Redis. The v3.19.1 file still selects latest application images and a sample database password; pin compatible images, replace credentials, and configure the encryption secret, login provider, URLs, TLS and optional object storage. Scope: Vendor Docker recipe with versioned source; source-file tag alone does not pin container images. Source: https://docs.typebot.com/self-hosting/deploy/docker.md (reviewed 2026-11-20). Deployment artifact: https://github.com/baptisteArno/typebot.io/blob/v3.19.1/docker-compose.yml. Artifact reference: v3.19.1 (recipe uses moving latest application image tags).

- Minimum footprint / sizing: Sources checked — unresolved. The Docker guide establishes builder, viewer, database and cache roles, with optional object storage, but does not specify whole-stack production CPU/RAM/storage minima. Size editor sessions, concurrent conversations, uploads and integrations separately; provider tutorial/demo allocations do not validate a 100-user, 1 TB HA deployment. Scope: Current upstream deployment topology; numeric workload and HA sizing remains unconfirmed. Source: https://docs.typebot.com/self-hosting/deploy/docker.md (reviewed 2026-11-20).

- License pricing: Documented. FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion. Scope: Typebot; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## WBO (Whitebophir)

Self-hosted multi-user collaborative whiteboard.

- Listing: https://launchinyourcloud.com/directory/wbo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- 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: Cloudron package; Docker / Compose
- Architecture: WBO application with persistent board 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://wbo.ophir.dev
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Review board visibility and authentication before exposing it. A private VPS does not automatically make every board private or give the app enterprise SSO.

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

WBO application with persistent board storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted multi-user collaborative whiteboard.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/wbo.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.


### Community and maintenance

The reviewed upstream contributor history includes lovasoa, finnboeger, h2Entwicklung, 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/lovasoa/whitebophir/graphs/contributors

- Upstream project: https://github.com/lovasoa/whitebophir

### Sources

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

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

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/lovasoa/whitebophir/master/LICENSE

- GitHub Releases (v2.18.44): https://github.com/lovasoa/whitebophir/releases

- Commits: https://github.com/lovasoa/whitebophir/commits/master.atom

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

### Licensing sources

- https://raw.githubusercontent.com/lovasoa/whitebophir/master/LICENSE

### Infrastructure sources

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


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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: Sources checked — unresolved. The reviewed application supports signed JWT board access when AUTH_SECRET_KEY is configured; otherwise a board URL permits access. This establishes token authorization, not an integrated SAML/OIDC login flow. Confirm the external identity service and token-issuance integration separately. Scope: WBO board authorization; no turnkey federated user-login path established. Source: https://raw.githubusercontent.com/lovasoa/whitebophir/master/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 upstream README provides an official Docker run deployment with a persistent server-data volume and an alternative Node.js installation. Its example uses latest; pin a compatible image, protect board data and configure the proxy/trusted IP source. It is a single-instance application recipe. Scope: Official Whitebophir/WBO Docker and Node installation. Source: https://raw.githubusercontent.com/lovasoa/whitebophir/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/lovasoa/whitebophir. Artifact reference: master (moving branch); pin the selected Docker image or release.

- 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/wbo.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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







## WordPress Self-Hosted

Open-source content management system with documented customer-account deployments across major clouds and application-provider images.

- Listing: https://launchinyourcloud.com/directory/wordpress-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, oci, linode, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv2 or later; themes, plugins and provider packaging may have separate terms.
- Licensing model: open-source
- Installation: Provider application images/blueprints, Azure App Service quickstart, OCI Resource Manager template, or Akamai StackScript; package and topology vary by provider
- Architecture: PHP application with a customer-controlled MySQL or MariaDB database and persistent media storage.
- Operations: Customer manages WordPress core, themes and plugins, application security, identities, content, database, media, backups, scaling and upgrades.
- Product website: https://wordpress.org/
- Source review: 2026-11-19; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers WordPress.org self-hosting, not WordPress.com SaaS. Provider blueprints accelerate installation but do not replace application hardening, backup, patching and plugin review. Provider packages can lag upstream. The current recommended PHP/database versions and application/plugin stack need a separate patch and HA review. WordPress 7.1.5 is a security release fixing multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Security fixes were backported to eligible older branches. Update immediately, and verify provider images that still advertise 7.1.4 or earlier rather than assuming the platform package is current.

WordPress core is released under GPLv2 or later. Themes, plugins and provider images can add separate licenses or charges.

WordPress runs on provisioned application and database capacity with durable media and database state, even when a provider manages parts of the substrate.


### Category fit

- content-management: Publishes websites, blogs and extensible structured content with themes, plugins and a browser-based editorial interface.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://cloud.google.com/wordpress (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/ (checked 2026-11-18). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm (checked 2026-11-18). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress (checked 2026-11-18). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/one-click-wordpress (checked 2026-11-18). 


### Cloud deployment evidence

- WordPress in the customer's Amazon Lightsail account (aws): https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html
  AWS documents selecting a region, launching the WordPress blueprint and operating the instance in the customer's Lightsail account.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Azure App Service (azure): https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress
  Microsoft's quickstart deploys the WordPress Marketplace item and backing Azure resources into the customer's selected subscription and resource group.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Google Cloud (gcp): https://cloud.google.com/wordpress
  Google documents customer deployments of WordPress on Google Cloud, including a Compute Engine path. Provider packaging and support scope must be reviewed.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress DigitalOcean 1-Click application (digitalocean): https://docs.digitalocean.com/products/marketplace/catalog/wordpress/
  DigitalOcean installs the full WordPress application and database on a customer Droplet. Confirm the resolved image version and production/HA design.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- OCI Resource Manager WordPress template (oci): https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm
  Oracle lists a Resource Manager quickstart that deploys a WordPress instance into OCI. It is a provider application template, not a WordPress support contract or HA guarantee.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Akamai Cloud (Linode) (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress
  Akamai documents full application/database deployment on a customer Compute Instance using StackScript 401697, with Cloud Manager and API/CLI inputs.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- Vultr One-Click WordPress (vultr): https://docs.vultr.com/one-click-wordpress
  Vultr documents launching the full WordPress application on the customer’s selected server size/location and configuring its administrator, domain and TLS.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

The project maintains a dated core release history and documents NASA’s WordPress-based web properties. This establishes maintained software and named adoption, not the cloud account or suitability of a particular plugin stack.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://wordpress.org/documentation/article/wordpress-versions/

- Official maintenance and adoption evidence: https://wordpress.org/showcase/nasa/

### Sources

- Launch and configure WordPress on Amazon Lightsail: https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html

- Create a WordPress site on Azure App Service: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress

- WordPress on Google Cloud: https://cloud.google.com/wordpress

- WordPress GPL license: https://wordpress.org/about/license/

- WordPress DigitalOcean 1-Click application: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/

- OCI Resource Manager WordPress template: https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm

- WordPress on Akamai Cloud (Linode): https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress

- Vultr One-Click WordPress: https://docs.vultr.com/one-click-wordpress

- WordPress 7.1.5 security release: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/

- WordPress 7.1.5 documentation: https://wordpress.org/documentation/wordpress-version/version-7-1-5/

### Licensing sources

- https://wordpress.org/about/license/

### Infrastructure sources

- https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html

- https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress


### Buyer diligence


Research coverage: 12/12 fields (100%); 8 documented, 4 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: Documented. DigitalOcean offers a WordPress 1-Click Droplet, currently including WordPress 7.1.4, PHP 8.3.36 and MySQL 8.0.46. That database version is below WordPress’s current MySQL 8.4 recommendation. Microsoft also documents an App Service Marketplace item. Packaging and infrastructure charges are separate from WordPress.com. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/ (reviewed 2026-11-18). Supporting source: Microsoft WordPress deployment — https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress. Supporting source: Lightsail WordPress blueprint — https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html. Supporting source: Upstream runtime/database recommendations — https://wordpress.org/about/requirements/. Offer wordpress: DigitalOcean; Droplet 1-Click application; package WordPress 7.1.4; package label latest; https://marketplace.digitalocean.com/apps/wordpress.

- Cloud commitment eligibility: Sources checked — unresolved. The Azure quickstart creates App Service and database resources, but does not establish software-offer commitment credit. Check the selected provider charges and the buyer’s agreement; WordPress core’s free license is not a transactable commitment claim. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. OpenID Connect Generic Client 3.11.4 provides authorization-code SSO and optional account creation/linking for WordPress logins. It is a separately installed community plugin, not bundled core or a provider-image entitlement. It requires PHP 8.0+; configure the IdP, redirect URI and linking policy. Version 3.11.4 changes state/nonce validation and requires review of PKCE and existing-user linking settings. Scope: Optional OpenID Connect Generic Client 3.11.4; WordPress user login, not every theme/plugin or external application. Source: https://wordpress.org/plugins/daggerhart-openid-connect-generic/ (reviewed 2026-11-18). Deployment artifact: https://downloads.wordpress.org/plugin/daggerhart-openid-connect-generic.3.11.4.zip. Artifact reference: OpenID Connect Generic Client 3.11.4.

- SCIM provisioning: Edition-dependent. miniOrange supplies an optional inbound SCIM endpoint: the IdP sends users to WordPress using a base URL and bearer token. Free creation is documented; profile updates, deletion/deactivation and reactivation require Premium. Enhanced group push/import are listed as future work. Soft deactivation retains the account and blocks login, but the guides do not establish revocation of existing sessions. Public package 1.2.0 is separate from the licensed Premium delivery. Scope: Third-party miniOrange WordPress provisioning plugin; inbound users, with Premium lifecycle operations; not native core SCIM. Source: https://wordpress.org/plugins/scim-user-provisioning/ (reviewed 2026-11-18). Supporting source: Provisioning operations, Premium boundary and group limitations — https://plugins.miniorange.com/wordpress-scim-user-provisioning.

- Compliance attestations: Sources checked — unresolved. The WordPress security paper describes project practices, not an independent attestation covering the buyer’s site, plugins, hosting and operations. Obtain the deployment-specific control and audit scope. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/security/ (reviewed 2026-11-18).

- Security controls: Documented. The hardening guide covers restricted database privileges, file permissions, protecting wp-config.php, disabling dashboard file editing, backups and logging. Core, theme and plugin updates remain customer responsibilities; a provider image does not complete this work. Current review: WordPress 7.1.5 fixes multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Update immediately or use the corresponding supported backport, and verify the exact provider image version. Scope: WordPress core 7.1 and eligible backported branches; third-party themes and plugins are outside this advisory. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/ (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://developer.wordpress.org/advanced-administration/security/hardening/. Supporting source: Optional OIDC plugin 3.11.4 security settings and upgrade behavior — https://wordpress.org/plugins/daggerhart-openid-connect-generic/.

- Air-gapped operation: Sources checked — unresolved. WordPress documents manual updates and WP_HTTP_BLOCK_EXTERNAL for requests made through its HTTP API. The latter allows local/site requests and does not govern arbitrary PHP networking by plugins. These controls do not validate a disconnected lifecycle for a selected theme/plugin stack. Confirm offline packages, licences, mail, IdP, media/CDN and update dependencies for that stack. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://developer.wordpress.org/reference/classes/wp_http/block_request/ (reviewed 2026-11-18). Supporting source: Manual core update procedure — https://wordpress.org/documentation/article/updating-wordpress/.

- Deployment artifact / IaC: Documented. Akamai documents WordPress StackScript 401697 and maps its database, administrator and web-server inputs to Cloud Manager and API/CLI deployment. AWS supplies a Lightsail blueprint and OCI lists a Resource Manager WordPress template. These are provider-managed moving packages, not a pinned upstream application release. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress (reviewed 2026-11-18). Supporting source: Lightsail blueprint — https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html. Supporting source: OCI Resource Manager application templates — https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm.

- Minimum footprint / sizing: Documented. The project recommends PHP 8.3+, MariaDB 10.11+ or MySQL 8.4+, and HTTPS; Apache or Nginx is recommended. It does not give a universal CPU/RAM minimum. PHP 7.4/MySQL 5.5.5 compatibility is a legacy fallback, not a recommendation to use those EOL runtimes. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/requirements/ (reviewed 2026-11-18).

- License pricing: Documented. WordPress core is GPLv2 or later, without a core software subscription. Themes, plugins, commercial support and provider packaging may introduce separate terms and charges. Hosting and operations are additional. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/license/ (reviewed 2026-11-18).

- Operating cost estimate: Sources checked — unresolved. 100 internal users and 1 TB do not determine page requests, PHP workers, database I/O or media delivery. Specify traffic/concurrency, plugin stack, cache/CDN, media versus database storage, HA database and application design, backups, egress and paid extensions before estimating AWS us-east-1 operations. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://wordpress.org/about/requirements/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. WordPress 7.1.5 was released November 18, 2026. It is a security release fixing multisite privilege escalation, stored and reflected XSS paths and media-type hardening. Eligible older branches received backports; provider packages may lag. Scope: WordPress.org self-hosted core; themes, plugins and provider images require separate version review. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/ (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://wordpress.org/documentation/article/wordpress-versions/. Supporting source: Version-specific documentation — https://wordpress.org/documentation/wordpress-version/version-7-1-5/.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Optional WordPress OIDC plugin security settings need review (security-advisory): OpenID Connect Generic Client 3.11.4 changes login state, nonce and verified-email linking checks. PKCE defaults on for new installs but stays off on existing sites until enabled. Scope: Only WordPress sites using the optional OpenID Connect Generic Client plugin; this is not a WordPress core or every-provider-image advisory. Conditions: Existing sites that link users have Link Users Without Verified Email enabled during upgrade and receive an admin notice. The changelog provides no universal affected-version range or CVE. Action: Use the current reviewed plugin, enable PKCE after IdP testing and review linking without verified email. Check callback, account linking and recovery behavior rather than assuming upgrade changes all existing settings. Source: https://wordpress.org/plugins/daggerhart-openid-connect-generic/; reviewed 2026-11-18.

- WordPress 7.1.5 security release (security-advisory): WordPress 7.1.5 fixes multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Scope: WordPress core 7.1 and eligible supported backport branches; themes and plugins remain separate. Conditions: Multisite administration, block-editor/media workflows and the installed core branch determine applicability. Action: Update immediately to 7.1.5 or the corresponding supported backport and verify the exact provider-image version. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/; reviewed 2026-11-19.



