
# Software on Hostinger

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

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




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Hostinger account and VPS
- Provider group: vps-hosting
- Provider classification: The documented route uses a customer VPS and application administrator; the hosting provider operates its physical infrastructure. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-20).
- Network: Customer server networking, DNS and firewall rules
- Identity and access: Cloud account access, server root/SSH access and application administrators
- Installation guidance: Provision the documented Cloudron VPS template in your account, complete domain and administrator setup, then install and operate the reviewed application package.
- Guidance source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
- Guidance reviewed: 2026-11-13


### VPS hardening

The provider recommends SSH hardening, firewall configuration and patching for VPS hosts. A preinstalled application template does not transfer these operating responsibilities away from the customer.
Source: https://www.hostinger.com/tutorials/vps-security/ (reviewed 2026-11-14).

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

52 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).







## Apache JSPWiki

Apache file-based wiki for documentation and knowledge content.

- Listing: https://launchinyourcloud.com/directory/apache-jspwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: JSPWiki Java application, persistent page files 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://jspwiki.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

Current repository maintenance is distinct from the older GitHub release snapshot; validate the chosen Tomcat/Java and wiki version combination.

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

JSPWiki Java application, persistent page files and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Apache file-based wiki for documentation and knowledge content.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/apache-jspwiki
  JSPWiki Java application, persistent page files and attachments. Current repository maintenance is distinct from the older GitHub release snapshot; validate the chosen Tomcat/Java and wiki version combination.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes juanpablo-santos, ajaquith, spyhunter99, 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/jspwiki/graphs/contributors

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

### Sources

- Hostinger: https://www.hostinger.com/applications/apache-jspwiki

- Apache-2.0 LICENSE: https://raw.githubusercontent.com/apache/jspwiki/master/LICENSE

- GitHub Releases: https://github.com/apache/jspwiki/releases

- Official upstream releases: https://jspwiki.apache.org/

### Licensing sources

- https://raw.githubusercontent.com/apache/jspwiki/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/apache-jspwiki


### Buyer diligence


Research coverage: 5/12 fields (42%); 2 documented, 3 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 upstream documentation establishes JAAS and servlet-container security integration, but this review did not establish a complete version-matched external SAML/OIDC user-login configuration for JSPWiki 3.0. Generic Java/container authentication alone is not proof of a supported federation path. Scope: Apache JSPWiki application user federation; optional login modules and external servlet/proxy integration require specific evidence. Source: https://github.com/apache/jspwiki/blob/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: Sources checked — unresolved. JSPWiki documents WAR/container installation, but the current Apache index exposes a 3.0.1 distribution while the project homepage still announces 3.0.0. This review did not reconcile the current release status and exact production binary selection. Verify the announcement, package/checksums and servlet compatibility rather than assuming an archived package or provider image is current. Scope: JSPWiki upstream artifact/release-channel reconciliation; the documented self-hosted installation path remains established. Source: https://downloads.apache.org/jspwiki/ (reviewed 2026-11-20). Deployment artifact: https://downloads.apache.org/jspwiki/. Artifact reference: Mutable Apache distribution index; observed 3.0.1 directory is not used to invent a publication date. Supporting source: Project release announcements — https://jspwiki.apache.org/. Supporting source: Observed versioned binary directory — https://downloads.apache.org/jspwiki/3.0.1/binaries/. Supporting source: Application installation and runtime requirements — https://github.com/apache/jspwiki/blob/master/README.md.

- Minimum footprint / sizing: Sources checked — unresolved. The installation README specifies Java and servlet-container prerequisites but does not establish a quantitative whole-host CPU/RAM/storage minimum. Size the wiki content, attachments, search/indexing, runtime and replicas for the intended use rather than treating Java heap settings as host capacity. Scope: JSPWiki 3.0 application/container deployment; quantitative production and HA sizing remains unconfirmed. Source: https://github.com/apache/jspwiki/blob/master/README.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The official site announces JSPWiki 3.0.0 and maintained-line 2.12.5 on August 22, 2026. GitHub Releases does not list all current Apache distributions; check Java/Tomcat and plugin compatibility. Scope: Official Apache upstream application releases, not the provider image. Source: https://jspwiki.apache.org/ (reviewed 2026-11-19).







## ArchiveBox

Open-source web archiving application for retained, searchable copies of web content.

- Listing: https://launchinyourcloud.com/directory/archivebox/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, 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: Application platform deployment; Docker / Compose
- Architecture: Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service.
- 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://archivebox.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Web snapshots are distinct from retiring a transactional application's business schema or implementing statutory records disposition. Keep the archive volume, browser isolation, chosen image version and backup process under operator control.

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

Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- legacy-system-archive-access: Open-source web archiving application for retained, searchable copies of web content.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger ArchiveBox (hostinger): https://www.hostinger.com/applications/archivebox
  Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service. Web snapshots are distinct from retiring a transactional application's business schema or implementing statutory records disposition. Keep the archive volume, browser isolation, chosen image version and backup process under operator control.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway Template (railway): https://railway.com/deploy/archivebox-2
  Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service. Web snapshots are distinct from retiring a transactional application's business schema or implementing statutory records disposition. Keep the archive volume, browser isolation, chosen image version and backup process under operator control.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes pirate, cdvv7788, claude, 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/ArchiveBox/ArchiveBox/graphs/contributors

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

### Sources

- Hostinger ArchiveBox: https://www.hostinger.com/applications/archivebox

- Railway Template: https://railway.com/deploy/archivebox-2

- MIT LICENSE: https://raw.githubusercontent.com/ArchiveBox/ArchiveBox/main/LICENSE

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

### Licensing sources

- https://raw.githubusercontent.com/ArchiveBox/ArchiveBox/main/LICENSE

### Infrastructure sources

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

- https://railway.com/deploy/archivebox-2


### 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 versioned guide supports reverse-proxy authentication using a configured username header and a tightly restricted trusted-proxy IP/CIDR; the application middleware consumes it for user login. Configure a compatible upstream identity proxy and strip spoofed headers. This is a specific trusted-proxy integration rather than proof that merely enabling LDAP establishes federation. Scope: ArchiveBox v0.9.77 reverse-proxy application-user SSO boundary. Source: https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/docs/Setting-up-Authentication.md (reviewed 2026-11-21). Supporting source: User authentication middleware — https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/archivebox/core/middleware.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The versioned repository supplies Compose configuration and upstream setup guidance for persistent archive data and application services. Pin compatible application/extractor images, configure access, storage and backups, and validate optional workers/dependencies; provider templates are separately packaged. Scope: ArchiveBox v0.9.77 upstream Compose artifact; provider package versions separate. Source: https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/docker-compose.yml (reviewed 2026-11-21). Deployment artifact: https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/docker-compose.yml. Artifact reference: v0.9.77.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed current release README and Compose reference do not establish a quantitative whole-production-host CPU/RAM/storage baseline. Browser/extractor concurrency, captured sites, media, index retention, workers and storage/backup growth drive capacity. Scope: ArchiveBox v0.9.77 complete production sizing remains unconfirmed. Source: https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/README.md (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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







## AureusERP

Customer-operated ERP for business, inventory, purchasing and financial records.

- Listing: https://launchinyourcloud.com/directory/aureuserp/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, azure
- 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: VM image; Docker / Compose
- Architecture: Laravel application, PostgreSQL, file storage and 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://aureuserp.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Hostinger and cloudimg provide separate packages. Check the installed application version and licence before applying upstream changes.

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

Laravel application, PostgreSQL, file storage and workers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated ERP for business, inventory, purchasing and financial records.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/aureuserp
  Laravel application, PostgreSQL, file storage and workers. Hostinger and cloudimg provide separate packages. Check the installed application version and licence before applying upstream changes.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04
  Laravel application, PostgreSQL, file storage and workers. Hostinger and cloudimg provide separate packages. Check the installed application version and licence before applying upstream changes.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jitendra-webkul, suraj-webkul, sandeep-webkul, 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/aureuserp/aureuserp/graphs/contributors

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

### Sources

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

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/aureuserp/aureuserp/master/LICENSE

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

### Licensing sources

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

### Infrastructure sources

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

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04


### Buyer diligence


Research coverage: 7/12 fields (58%); 5 documented, 2 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 official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: AureusERP selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.aureuserp-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.aureuserp-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.aureuserp-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.aureuserp-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed AureusERP README documents local administration and role/permission setup, but does not establish an external SAML/OIDC user-login provider for the self-hosted core. Laravel, Filament and role-management dependencies alone do not establish SSO support. Scope: AureusERP self-hosted core; optional plugins require their own supported-version and entitlement evidence. Source: https://github.com/aureuserp/aureuserp/blob/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 a Composer/source installation and php artisan erp:install to create the environment, schema, roles and admin account. Its quick start and Sail Compose file are development-oriented; they do not establish a hardened production or HA deployment. Scope: Reviewed AureusERP application bootstrap; provision production web/database services separately. Source: https://github.com/aureuserp/aureuserp/blob/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/aureuserp/aureuserp. Artifact reference: master (moving branch). Supporting source: Sail development Compose configuration — https://github.com/aureuserp/aureuserp/blob/master/docker-compose.yml.

- Minimum footprint / sizing: Sources checked — unresolved. The README specifies PHP, database and web-server compatibility, but no quantitative whole-stack CPU/RAM/storage floor. Its development requirements and Sail configuration do not validate the selected modules for the proposed production workload. Scope: AureusERP application, selected plugins, database, queues and storage; production sizing remains unconfirmed. Source: https://github.com/aureuserp/aureuserp/blob/master/README.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Bigcapital

Self-hosted accounting, invoicing and financial reporting application.

- Listing: https://launchinyourcloud.com/directory/bigcapital/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Application services, database and persistent accounting documents.
- 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://bigcapital.app
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Accounting software does not by itself establish local tax certification or payroll compliance.

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

Application services, database and persistent accounting documents. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Self-hosted accounting, invoicing and financial reporting application.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/bigcapital
  Application services, database and persistent accounting documents. Accounting software does not by itself establish local tax certification or payroll compliance.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes abouolia, elforjani13, jsoref, 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/bigcapitalhq/bigcapital/graphs/contributors

- Upstream project: https://github.com/bigcapitalhq/bigcapital

### Sources

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

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/bigcapitalhq/bigcapital/develop/LICENSE

- GitHub Releases: https://github.com/bigcapitalhq/bigcapital/releases

### Licensing sources

- https://raw.githubusercontent.com/bigcapitalhq/bigcapital/develop/LICENSE

### Infrastructure sources

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


### 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 upstream Google authentication guide implements server-side OAuth 2.0 sign-in and sign-up, with the button enabled only when the backend provider is configured. This establishes Google login, not generic SAML federation or SCIM. Scope: Reviewed Bigcapital develop branch; Google OAuth client, backend settings and correct redirect origin required. Source: https://github.com/bigcapitalhq/bigcapital/blob/develop/docs/google-auth.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker deployment guide uses a production Compose file and pre-built registry images, with environment configuration and database migration steps. Pin compatible code/images and provide secrets, durable data, TLS and backups; the recipe does not establish HA. Scope: Self-hosted Bigcapital production Compose deployment; guide and moving source branches must be version-matched. Source: https://docs.bigcapital.app/deployment/docker (reviewed 2026-11-20). Deployment artifact: https://github.com/bigcapitalhq/bigcapital/blob/develop/docker-compose.prod.yml. Artifact reference: develop (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The production Compose recipe identifies multiple application and data services but does not specify quantitative CPU/RAM/storage reservations or a tested full-stack minimum. Size its databases, queues, workers and durable data together for the intended accounting workload. Scope: Reviewed Bigcapital production Compose source; service count alone is not a 100-user or HA capacity claim. Source: https://github.com/bigcapitalhq/bigcapital/blob/develop/docker-compose.prod.yml (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: Bigcapital; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/bigcapitalhq/bigcapital/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Chevereto Self-Hosted

Self-hosted image hosting and gallery management application.

- Listing: https://launchinyourcloud.com/directory/chevereto/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Chevereto application, database and persistent image 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://chevereto.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The reviewed source is AGPL-3.0; historical Free/commercial naming is not a substitute for the actual selected version licence.

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

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


### Category fit

- digital-asset-management: Self-hosted image hosting and gallery management application.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/chevereto
  Chevereto application, database and persistent image storage. The reviewed source is AGPL-3.0; historical Free/commercial naming is not a substitute for the actual selected version licence.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes rodber, antropolouco, tomny-dev, 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/chevereto/chevereto/graphs/contributors

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

### Sources

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

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/chevereto/chevereto/4.2/LICENSE

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

### Licensing sources

- https://raw.githubusercontent.com/chevereto/chevereto/4.2/LICENSE

### Infrastructure sources

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


### 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. The vendor documents OAuth2 social login with named providers such as Google and Discord. Its current self-hosted edition table excludes social/OAuth2 login from Free and includes it in Lite and Pro. This is named-provider social authentication, not a claim of generic enterprise SAML/OIDC or SCIM. Scope: Chevereto self-hosted edition/feature entitlements; verify the selected package and plan. Source: https://chevereto.com/pricing (reviewed 2026-11-20). Supporting source: Supported social-login feature description — https://chevereto.com/features. Supporting source: Published 4.5.9 provider-login implementation — https://github.com/chevereto/chevereto/blob/4.5.9/app/src/Legacy/Classes/Login.php.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes Docker recipes and ready-built image links for Chevereto V4. Select the free or entitled paid edition and matching release, configure database/persistent media and secrets, and apply the documented ingress/HTTPS setup. Paid image builds and redistribution have separate licence conditions. Scope: Chevereto self-hosted application/container packaging; not a complete Hostinger or HA infrastructure template. Source: https://github.com/chevereto/docker/blob/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/chevereto/docker/tree/master. Artifact reference: master (moving branch); choose a compatible application/image release and edition. Supporting source: Current self-hosted edition entitlements — https://chevereto.com/pricing.

- Minimum footprint / sizing: Sources checked — unresolved. The stack guide specifies PHP/database compatibility and a recommended 512 MB PHP memory limit, but that is a process setting, not a whole-host resource minimum. The reviewed installation material does not establish complete CPU/RAM/storage sizing for image processing, database, media growth and HA. Scope: Chevereto self-hosted web/database/image-processing stack; workload and selected edition require sizing. Source: https://github.com/chevereto/v4-docs/blob/main/application/stack/php.md (reviewed 2026-11-20). Supporting source: Docker installation requirements — https://github.com/chevereto/docker/blob/master/README.md.

- License pricing: Documented. The reviewed 4.5.9 source is AGPLv3, while vendor self-hosted packages have Free, Lite and Pro tiers. Lite is a monthly subscription; Pro/Pro Max are annual, with different features/support. OAuth2 social login is excluded from Free. Hosted Cloud pricing, checkout taxes and infrastructure costs are separate. Scope: Chevereto upstream source licence versus vendor self-hosted feature/support entitlements; confirm the applicable package agreement and checkout currency. Source: https://chevereto.com/pricing (reviewed 2026-11-20). Supporting source: Published 4.5.9 source licence — https://github.com/chevereto/chevereto/blob/4.5.9/LICENSE.

- Operating cost estimate: Not researched.

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







## ChiefOnboarding

Self-hosted employee onboarding tasks, documents and workflows.

- Listing: https://launchinyourcloud.com/directory/chiefonboarding/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: ChiefOnboarding application, database, persistent files and background jobs.
- 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://chiefonboarding.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Slack and mail integrations are external dependencies when enabled; onboarding workflows do not by themselves certify HR compliance.

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

ChiefOnboarding application, database, persistent files and background jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- hr-employee-records-management: Self-hosted employee onboarding tasks, documents and workflows.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/chiefonboarding
  ChiefOnboarding application, database, persistent files and background jobs. Slack and mail integrations are external dependencies when enabled; onboarding workflows do not by themselves certify HR compliance.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes GDay, matehsan, floschoepfer, 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/chiefonboarding/ChiefOnboarding/graphs/contributors

- Upstream project: https://github.com/chiefonboarding/ChiefOnboarding

### Sources

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

- AGPL-3.0 LICENSE.md: https://raw.githubusercontent.com/chiefonboarding/ChiefOnboarding/master/LICENSE.md

- GitHub Releases: https://github.com/chiefonboarding/ChiefOnboarding/releases

### Licensing sources

- https://raw.githubusercontent.com/chiefonboarding/ChiefOnboarding/master/LICENSE.md

### Infrastructure sources

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


### 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 application documents OIDC provider configuration and role mapping through SSO_PROVIDERS and OIDC role settings, with separate Google login instructions. Verified-email handling, automatic account creation and administrator-role mappings require deliberate configuration. Scope: Self-hosted application-user OIDC; role mapping is not evidence of SCIM provisioning. Source: https://docs.chiefonboarding.com/config/oidc.html (reviewed 2026-11-21). Supporting source: Google user login and callback setup — https://docs.chiefonboarding.com/config/google-sso.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v2.5.2 deployment guide supplies a published-image Compose example with PostgreSQL and an optional Caddy reverse proxy, persistent database storage and environment settings. Replace sample secrets and moving/old images. The repository-root Compose file uses a development build and local AWS emulation; it is a different workflow. Scope: Versioned deployment-guide example, not the repository development stack. Source: https://github.com/chiefonboarding/ChiefOnboarding/blob/v2.5.2/docs/deployment/docker.md (reviewed 2026-11-21). Deployment artifact: https://github.com/chiefonboarding/ChiefOnboarding/blob/v2.5.2/docs/deployment/docker.md. Artifact reference: v2.5.2 documentation; example application/database latest tags require release selection.

- Minimum footprint / sizing: Sources checked — unresolved. The versioned deployment guide documents the application, PostgreSQL, proxy and persistent storage, but gives no quantitative production CPU/RAM or user-concurrency baseline. The development stack and its local AWS emulator are not a production capacity recommendation. Scope: Deployment prerequisites confirmed; full production/HA sizing remains unconfirmed. Source: https://github.com/chiefonboarding/ChiefOnboarding/blob/v2.5.2/docs/deployment/docker.md (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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







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







## Combodo iTop (Community)

Community IT service-management application with tickets, configuration records and service workflows.

- Listing: https://launchinyourcloud.com/directory/itop/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: PHP application, database, attachments and scheduled jobs.
- 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://combodo.com/features/
- 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 commercially licensed extensions have different capabilities and entitlements.

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

PHP application, database, attachments and scheduled jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Community IT service-management application with tickets, configuration records and service workflows.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/itop
  PHP application, database, attachments and scheduled jobs. Community and commercially licensed extensions have different capabilities and entitlements.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes Molkobain, piRGoif, eespie, 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/Combodo/iTop/graphs/contributors

- Upstream project: https://github.com/Combodo/iTop

### Sources

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

- GitHub license.txt (AGPL-3.0): https://raw.githubusercontent.com/Combodo/iTop/develop/license.txt

- GitHub Releases: https://github.com/Combodo/iTop/releases

### Licensing sources

- https://raw.githubusercontent.com/Combodo/iTop/develop/license.txt

### Infrastructure sources

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


### 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 separately installed Combodo SAML extension authenticates pre-existing iTop ExternalUser accounts; it does not provision them. The vendor store offers free AGPL versions, while the current manual describes 1.2.6 requiring iTop 3.2+. Confirm the downloadable extension/version compatibility for Community 3.3 before installation. Scope: Optional SAML extension for self-hosted iTop; not an assertion that every Community package bundles it. Source: https://www.itophub.io/wiki/page?id=extensions:combodo-saml (reviewed 2026-11-20). Supporting source: Vendor extension store and available packages — https://store.itophub.io/en_US/products/combodo-saml.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The iTop 3.3 guide documents installing a Community distribution on a PHP/database host and running its web setup. Pin the application package and compatible extensions, configure web-server access and protect the setup directory; a third-party provider image is a separate artifact. Scope: Versioned upstream Community installation; distinct from a marketplace image. Source: https://www.itophub.io/wiki/page?id=3_3_0:install:start (reviewed 2026-11-20). Deployment artifact: https://github.com/Combodo/iTop/releases/tag/3.3.0-1. Artifact reference: 3.3.0-1.

- Minimum footprint / sizing: Documented. The 3.3 table recommends an all-in-one 2-vCPU, 4 GB RAM server with 10 GB database disk for under 20 console users, 200 monthly tickets and 50k CIs. Larger tiers split web/database servers; its >50-user tier lists 8 vCPU, 16 GB and 50 GB database disk. Validate per-server allocation, attachments and HA for your actual workload. Scope: Versioned workload tiers; database-disk figures are not total data capacity or a validated 100-user HA design. Source: https://www.itophub.io/wiki/page?id=3_3_0:install: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: Combodo iTop (Community); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/Combodo/iTop/develop/license.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Corteza

Low-code platform for business records, workflows and configurable CRM applications.

- Listing: https://launchinyourcloud.com/directory/corteza/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: Corteza server, web applications, database and object or file 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://cortezaproject.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

CRM workflows require configuration; a general platform is not a packaged vertical business solution.

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

Corteza server, web applications, database and object or file storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- internal-tools: Low-code platform for business records, workflows and configurable CRM applications.

- workflow-automation: Low-code platform for business records, workflows and configurable CRM applications.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/corteza
  Corteza server, web applications, database and object or file storage. CRM workflows require configuration; a general platform is not a packaged vertical business solution.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes darh, Fajfa, tjerman, 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/cortezaproject/corteza/graphs/contributors

- Upstream project: https://github.com/cortezaproject/corteza

### Sources

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

- GitHub LICENSE (Apache-2.0): https://raw.githubusercontent.com/cortezaproject/corteza/2024.9.x/LICENSE

- GitHub Releases: https://github.com/cortezaproject/corteza/releases

### Licensing sources

- https://raw.githubusercontent.com/cortezaproject/corteza/2024.9.x/LICENSE

### Infrastructure sources

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


### 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 2026.9 authentication guide documents SAML setup with IdP metadata, service-provider credentials and Admin-panel configuration, alongside separate external login providers. Replace the example keys and validate the selected IdP rather than treating generic OAuth integration as user SSO. Scope: Versioned Corteza user SAML configuration. Source: https://docs.cortezaproject.org/corteza-docs/2026.9/integrator-guide/authentication/external/saml/index.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 2026.9 guide publishes a Compose example with Corteza, PostgreSQL, persistent data directories and an external reverse-proxy network. Set the application version, database DSN and secrets, and replace sample database credentials; proxy/TLS and backups require configuration. Scope: Versioned multi-container installation example, not a hardened HA deployment. Source: https://docs.cortezaproject.org/corteza-docs/2026.9/devops-guide/examples/deploy-online/multi-pgsql.html (reviewed 2026-11-20). Deployment artifact: https://docs.cortezaproject.org/corteza-docs/2026.9/devops-guide/examples/deploy-online/multi-pgsql.html. Artifact reference: 2026.9 documentation example; pin compatible container release tags.

- Minimum footprint / sizing: Documented. The 2026.9 requirements give 1 vCPU/core and 2 GB RAM for the 1–500-user tier, with larger tiers and a storage formula based on user count, upload volume, time and a safety factor. These broad guidelines do not establish concurrency, database sizing or HA capacity for a 1-TB deployment. Scope: Published user-tier starting guidance; validate the actual workload and supported database versions. Source: https://docs.cortezaproject.org/corteza-docs/2026.9/devops-guide/system-requirements.html (reviewed 2026-11-20).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Corteza; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/cortezaproject/corteza/2024.9.x/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Decidim

Open-source civic participation, proposal, participatory-budgeting and accountability platform.

- Listing: https://launchinyourcloud.com/directory/decidim/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Provider-packaged Decidim application stack on a customer-controlled VPS.
- 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://decidim.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 provider page does not pin an application version. Verify the deployed image and apply current upstream security maintenance before use. Budget voting and accountability reporting are distinct from a general grant-contract management system. Check the installed Decidim version and follow the 0.32.0, 0.32.1 and 0.32.2 upgrade sequence with database, application and static-file backups.

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

Provider-packaged Decidim application stack on a customer-controlled VPS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- public-participation: Open-source civic participation, proposal, participatory-budgeting and accountability platform.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger Decidim (hostinger): https://www.hostinger.com/applications/decidim
  Provider-packaged Decidim application stack on a customer-controlled VPS. The provider page does not pin an application version. Verify the deployed image and apply current upstream security maintenance before use. Budget voting and accountability reporting are distinct from a general grant-contract management system.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes andreslucena, alecslupu, mrcasals, 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/decidim/decidim/graphs/contributors

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

### Sources

- Hostinger Decidim: https://www.hostinger.com/applications/decidim

- Decidim Budgets Docs: https://docs.decidim.org/en/develop/admin/components/budgets.html

- Decidim Projects Docs: https://docs.decidim.org/en/develop/admin/components/budgets/projects.html

- Decidim Accountability Docs: https://docs.decidim.org/en/develop/admin/components/accountability.html

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/decidim/decidim/develop/LICENSE-AGPLv3.txt

- GitHub Releases (`v0.32.2`): https://github.com/decidim/decidim/releases

- Commits: https://github.com/decidim/decidim/commits/develop.atom

- Decidim patch-release security fixes: https://github.com/decidim/decidim/releases/tag/v0.32.2

### Licensing sources

- https://raw.githubusercontent.com/decidim/decidim/develop/LICENSE-AGPLv3.txt

### Infrastructure sources

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


### 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 v0.32.2 application registers configured OmniAuth providers such as Google and implements verified user registration/identity linking. Provider settings are organisation-specific. This confirms the configured social/OAuth path, not generic SAML/OIDC plugins or identity verification of every participant. Scope: Upstream Decidim v0.32.2 configured provider login; package/organisation scope. Source: https://github.com/decidim/decidim/blob/v0.32.2/decidim-core/config/initializers/omniauth.rb (reviewed 2026-11-21). Supporting source: User creation and identity handling — https://github.com/decidim/decidim/blob/v0.32.2/decidim-core/app/commands/decidim/create_omniauth_registration.rb.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The versioned installation manual documents creating and configuring a Rails/Decidim application, database, migrations, assets and deployment prerequisites. This is an upstream manual installation path; provider one-click images, TLS, background jobs, storage and upgrades require separate release/configuration review. Scope: Decidim v0.32.2 upstream manual installation, separate from provider packages. Source: https://github.com/decidim/decidim/blob/v0.32.2/docs/modules/install/pages/manual.adoc (reviewed 2026-11-21). Deployment artifact: https://github.com/decidim/decidim/blob/v0.32.2/docs/modules/install/pages/manual.adoc. Artifact reference: v0.32.2.

- Minimum footprint / sizing: Sources checked — unresolved. The versioned installation manual/checklist identifies software and operational prerequisites but does not establish numeric production CPU/RAM/storage sizing. Size application/database/search, background jobs, attachments, participation peaks and HA for the selected modules. Scope: Decidim v0.32.2 complete production sizing remains unconfirmed. Source: https://github.com/decidim/decidim/blob/v0.32.2/docs/modules/install/pages/checklist.adoc (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Decidim patch-release security fixes (security-advisory): Decidim 0.32.2 lists five upstream security advisories and ordered upgrade steps. Scope: Decidim 0.32.x patch sequence; consult each linked GHSA for its own affected range. Conditions: Provider templates can use a different application version; a new deployment date does not establish patch level. Action: Check the installed Decidim version and follow the 0.32.0, 0.32.1 and 0.32.2 upgrade sequence with database, application and static-file backups. Source: https://github.com/decidim/decidim/releases/tag/v0.32.2; reviewed 2026-11-19.




## Dittofeed

Self-hosted customer engagement and messaging orchestration platform.

- Listing: https://launchinyourcloud.com/directory/dittofeed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: render, railway, hostinger
- 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; Docker / Compose
- Architecture: Dittofeed application, PostgreSQL, ClickHouse and supporting services.
- 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://dittofeed.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.

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

Dittofeed application, PostgreSQL, ClickHouse and supporting services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted customer engagement and messaging orchestration platform.

### Deployment boundaries


- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.dittofeed.com/deployment/self-hosted/render.md (checked 2026-11-19). 

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

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


### Cloud deployment evidence

- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil (render): https://docs.dittofeed.com/deployment/self-hosted/render.md
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/dittofeed-2
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.

- Hostinger (hostinger): https://www.hostinger.com/applications/dittofeed
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes maxgurewitz, chandlercraig, neo773, 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/dittofeed/dittofeed/graphs/contributors

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

### Sources

- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil: https://docs.dittofeed.com/deployment/self-hosted/render.md

- Railway: https://railway.com/deploy/dittofeed-2

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

- Render Guide: https://docs.dittofeed.com/deployment/self-hosted/render

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/dittofeed/dittofeed/main/LICENSE

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

### Licensing sources

- https://raw.githubusercontent.com/dittofeed/dittofeed/main/LICENSE

### Infrastructure sources

- https://docs.dittofeed.com/deployment/self-hosted/render.md

- https://railway.com/deploy/dittofeed-2

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


### 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: Edition-dependent. OIDC-based multi-tenant authentication is documented, but the detailed guide restricts that mode to dittofeed-ee and Dittofeed Cloud. The community lite deployment instead offers a shared-password single-tenant mode. Obtain the Enterprise image/entitlement and configure provider claims and workspace access; anonymous demo mode is unsuitable for production. Scope: Self-hosted Enterprise OIDC versus community/lite authentication; detailed mode restrictions override the general overview. Source: https://docs.dittofeed.com/deployment/self-hosted/auth-modes/multi-tenant.md (reviewed 2026-11-20). Supporting source: Authentication-mode overview — https://docs.dittofeed.com/deployment/self-hosted/auth-modes.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide links the lite Compose stack and documents replacing default credentials, secrets and dashboard URLs. It includes PostgreSQL, ClickHouse and workflow services; the vendor also publishes a Helm chart. Choose a compatible pinned release and configure storage, TLS, authentication and backups; Enterprise uses a separately entitled image. Scope: Vendor community/lite deployment recipe, distinct from Enterprise image delivery. Source: https://docs.dittofeed.com/deployment/self-hosted/docker-compose.md (reviewed 2026-11-20). Deployment artifact: https://github.com/dittofeed/dittofeed/blob/main/docker-compose.lite.yaml. Artifact reference: main (moving branch; pin compatible application and dependency versions). Supporting source: Official Kubernetes/Helm recipe — https://docs.dittofeed.com/deployment/self-hosted/kubernetes.md.

- Minimum footprint / sizing: Documented. The Helm guide lists application-container requests/limits of 1 CPU and 512 MiB RAM and ClickHouse memory requests/limits of 1 GiB. These are component configuration defaults, not a whole-stack minimum: PostgreSQL, Temporal, storage, replicas and traffic need separate capacity. They do not size 100 users, 1 TB or HA. Scope: Documented chart component allocations, not total host or production capacity. Source: https://docs.dittofeed.com/deployment/self-hosted/kubernetes.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Docassemble

Self-hosted guided interviews and automated document assembly.

- Listing: https://launchinyourcloud.com/directory/docassemble/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, aws
- 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: Docker / Compose
- Architecture: Docassemble Docker application, database, persistent interviews and generated documents.
- 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://docassemble.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 vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.

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

Docassemble Docker application, database, persistent interviews and generated documents. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted guided interviews and automated document assembly.

### Deployment boundaries


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

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docassemble.org/docs/installation.html (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/docassemble
  Docassemble Docker application, database, persistent interviews and generated documents. The vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Docassemble EC2 Docs (aws): https://docassemble.org/docs/installation.html
  Docassemble Docker application, database, persistent interviews and generated documents. The vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jhpyle, jpylephilalegal, BryceStevenWilley, 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/jhpyle/docassemble/graphs/contributors

- Upstream project: https://github.com/jhpyle/docassemble

### Sources

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

- Docassemble EC2 Docs: https://docassemble.org/docs/installation.html

- MIT LICENSE.txt: https://raw.githubusercontent.com/jhpyle/docassemble/master/LICENSE.txt

- GitHub Releases: https://github.com/jhpyle/docassemble/releases

### Licensing sources

- https://raw.githubusercontent.com/jhpyle/docassemble/master/LICENSE.txt

### Infrastructure sources

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

- https://docassemble.org/docs/installation.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. The server documents external OAuth sign-in with providers including Auth0, Keycloak, Authentik and Azure. Configure each provider and account-linking/admin policies. The guide warns that external authentication affects its optional server-side answer-encryption model. Scope: Self-hosted server external authentication. Source: https://docassemble.org/docs/config.html#oauth (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project recommends the jhpyle/docassemble Docker distribution, including for production, with persistent configuration/data and optional external database or object storage. Select a versioned image and review production settings rather than using the minimal demonstration command unchanged. Scope: Official Docker distribution; infrastructure provisioning and HA not supplied by the one-line example. Source: https://docassemble.org/docs/installation.html (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/jhpyle/docassemble. Artifact reference: Select an explicit image tag for deployment.

- Minimum footprint / sizing: Documented. The project reports roughly 800–900 MB RAM during normal operation but recommends at least 4 GB because updates can use substantially more. This is a baseline server recommendation, not tested capacity for 100 users, 1 TB or HA. Scope: Upstream single-machine memory recommendation. Source: https://docassemble.org/docs/installation.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Docspell

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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


### Cloud deployment evidence

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

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


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The upstream server supports OIDC/OAuth2 sign-in using a configured external provider; multiple providers are supported and Keycloak configuration is documented. Configure registration, collective mapping and provider settings for the selected release. Scope: Self-hosted Docspell REST server authentication. Source: https://docspell.org/docs/configure/authentication/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project maintains a Compose deployment for the REST server, job executor, PostgreSQL and full-text search. Change the documented secrets, persist data and pin compatible image versions; moving latest/nightly tags are not immutable releases. Scope: Upstream Compose deployment; single-machine default, not HA. Source: https://docspell.org/docs/install/docker/ (reviewed 2026-11-20). Deployment artifact: https://github.com/docspell/docker/tree/master/docker-compose. Artifact reference: master (moving branch).

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

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

- Operating cost estimate: Not researched.

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







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







## eLabFTW

Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

- Listing: https://launchinyourcloud.com/directory/elabftw/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: eLabFTW application containers, database and persistent uploaded records on a customer VPS.
- 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.elabftw.net
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Verify the actual provider image and current upstream security fixes. Laboratory record controls are not an automatic clinical-validation, GLP or regulatory-certification claim; institutional procedures and supported dependencies remain separate.

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

eLabFTW application containers, database and persistent uploaded records on a customer VPS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

- clinical-regulatory-document-management: Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger VPS (hostinger): https://www.hostinger.com/applications/elabftw
  eLabFTW application containers, database and persistent uploaded records on a customer VPS. Verify the actual provider image and current upstream security fixes. Laboratory record controls are not an automatic clinical-validation, GLP or regulatory-certification claim; institutional procedures and supported dependencies remain separate.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes NicolasCARPi, MoustaphaCamara, MarcelBolten, 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/elabftw/elabftw/graphs/contributors

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

### Sources

- Hostinger VPS: https://www.hostinger.com/applications/elabftw

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

- Releases: https://github.com/elabftw/elabftw/releases

### Licensing sources

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

### Infrastructure sources

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


### 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 system-administrator guide documents SAML user sign-in with one or more identity providers, separately from LDAP and trusted-header external authentication. Account-creation and local-login settings control how users are admitted. Configure the chosen IdP and team mapping for the selected release. Scope: Self-hosted eLabFTW SAML login; LDAP, local login and middleware-header paths are distinct. Source: https://doc.elabftw.net/docs/install/post-install/authentication/saml (reviewed 2026-11-20). Supporting source: Authentication and account policies — https://doc.elabftw.net/sysadmin-guide.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The version-6 installation guide uses the official elabctl management script or a downloadable Docker Compose configuration, then separate configuration/TLS/start steps. The default includes MySQL; the current guide explicitly distinguishes it from MariaDB. Configure secrets, durable data, backups and matching application/database versions. Scope: eLabFTW version-6 container installation path; provision the host and production operations separately. Source: https://github.com/elabftw/elabftw/blob/release/6.0/documentation/docs/install/installation/1-elabctl.md (reviewed 2026-11-20). Deployment artifact: https://get.elabftw.net/. Artifact reference: Official elabctl/configuration download URL is unversioned; guide branch release/6.0 is moving. Supporting source: Runtime and database prerequisites — https://doc.elabftw.net/docs/install/prerequisites.

- Minimum footprint / sizing: Sources checked — unresolved. The current prerequisites identify a 64-bit Linux container host and a MySQL-backed stack, but do not establish a quantitative whole-host CPU/RAM/storage minimum for this laboratory workload. Attachments, database growth, backups, integrations and replicas require a version- and workload-specific design. Scope: eLabFTW application, database and persistent experiment data; container/package allowances are not whole-system HA sizing. Source: https://doc.elabftw.net/docs/install/prerequisites (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: eLabFTW; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/elabftw/elabftw/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Ente Photos

Self-hosted encrypted photo backup and sharing backend with web clients.

- Listing: https://launchinyourcloud.com/directory/ente-photos/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway, azure
- 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: VM image; Application platform deployment; Docker / Compose
- Architecture: Ente Museum API, Photos/Albums web apps, PostgreSQL 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://ente.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.

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

Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted encrypted photo backup and sharing backend with web clients.

### Deployment boundaries


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

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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.ente-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/ente
  Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/ente-1
  Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.ente-ubuntu-24-04
  Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes mnvr, ua741, abhinavkgrd, 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/ente/ente/graphs/contributors

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

### Sources

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

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

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.ente-ubuntu-24-04

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/ente-io/ente/main/LICENSE

- GitHub Releases: https://github.com/ente-io/ente/releases

### Licensing sources

- https://raw.githubusercontent.com/ente-io/ente/main/LICENSE

### Infrastructure sources

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

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

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.ente-ubuntu-24-04


### Buyer diligence


Research coverage: 6/12 fields (50%); 4 documented, 2 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 official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: Ente Photos selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.ente-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.ente-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.ente-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.ente-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.ente-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed Museum/self-hosting material establishes Ente account/client setup but does not establish a supported external SAML/OIDC enterprise sign-in path for self-hosted Photos. Ente Auth, account MFA/passkeys and another website's hosted login are not evidence of Photos federation. Scope: Ente Photos clients with a customer-operated Museum backend; product-specific external user federation remains unconfirmed. Source: https://ente.io/help/self-hosting/ (reviewed 2026-11-20). Supporting source: Museum server and client architecture — https://github.com/ente-io/ente/blob/main/server/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Ente publishes a quickstart script that generates Compose/configuration with instance credentials for Museum, PostgreSQL and object storage. This deploys the backend; Photos clients must connect to that instance, and self-hosting a web client is a separate step. Preserve configuration and data volumes when upgrading. Scope: Ente Museum backend supporting Photos; not a complete public web-client or HA deployment. Source: https://github.com/ente-io/ente/blob/main/server/docs/quickstart.md (reviewed 2026-11-20). Deployment artifact: https://github.com/ente-io/ente/blob/main/server/quickstart.sh. Artifact reference: main (moving branch); generated configuration and image versions must be retained. Supporting source: Self-hosted client and server guidance — https://ente.io/help/self-hosting/.

- Minimum footprint / sizing: Sources checked — unresolved. The quickstart specifies Docker and creates Museum, PostgreSQL and object-storage services, but does not give a quantitative whole-stack CPU/RAM/storage minimum. Size original media, encrypted objects, database, backups, clients and any separately hosted web front end for the intended workload. Scope: Ente Photos backend and selected client deployment; lightweight binary claims are not validated production/HA sizing. Source: https://github.com/ente-io/ente/blob/main/server/docs/quickstart.md (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: Ente Photos; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/ente-io/ente/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## Flarum

Self-hosted discussion forum and community workspace.

- Listing: https://launchinyourcloud.com/directory/flarum/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, azure
- 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: VM image; Docker / Compose
- Architecture: Flarum PHP application, database, attachments and extension 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://www.hostinger.com/applications/flarum
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The maintained 1.8 stable series and 2.x preview series are separate. Extensions may have different licences and upgrade compatibility.

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

Flarum PHP application, database, attachments and extension configuration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted discussion forum and community workspace.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.flarum-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/flarum
  Flarum PHP application, database, attachments and extension configuration. The maintained 1.8 stable series and 2.x preview series are separate. Extensions may have different licences and upgrade compatibility.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.flarum-ubuntu-24-04
  Flarum PHP application, database, attachments and extension configuration. The maintained 1.8 stable series and 2.x preview series are separate. Extensions may have different licences and upgrade compatibility.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes tobyzerner, franzliedke, flarum-bot, 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/flarum/framework/graphs/contributors

- Upstream project: https://github.com/flarum/framework

### Sources

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

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.flarum-ubuntu-24-04

- MIT LICENSE: https://github.com/flarum/framework/blob/2.x/LICENSE.md

- Releases v1.8.21: https://github.com/flarum/framework/releases

### Licensing sources

- https://github.com/flarum/framework/blob/2.x/LICENSE.md

### Infrastructure sources

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

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.flarum-ubuntu-24-04


### 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: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: Flarum selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.flarum-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.flarum-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.flarum-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.flarum-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.flarum-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Documented. The published fof/oauth 2.0.2 extension requires flarum/core ^2.0.0 and provides external OAuth-provider login. Use the 2.x-compatible release; the older master/1.x metadata requiring ^1.8.1 must not be used for a Flarum 2 deployment. Configure and test the chosen provider and extension permissions separately. Scope: Third-party FriendsOfFlarum OAuth 2.0.2 for Flarum 2.x; not core-native SAML. Source: https://raw.githubusercontent.com/FriendsOfFlarum/oauth/7a4d395d077a459e937dc9e88c3513fcf0eca0b8/composer.json (reviewed 2026-11-20). Supporting source: Published maintainer package/version metadata — https://repo.packagist.org/p2/fof/oauth.json. Supporting source: Matching release provider documentation — https://raw.githubusercontent.com/FriendsOfFlarum/oauth/7a4d395d077a459e937dc9e88c3513fcf0eca0b8/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official 2.x guide provides archive and Composer-based application installation, database configuration and update instructions. It requires compatible PHP/database extensions and maintenance access; an extension or marketplace image built for 1.x is not automatically compatible with 2.x. Scope: Upstream Flarum 2.x application installation. Source: https://docs.flarum.org/install/ (reviewed 2026-11-20). Deployment artifact: https://docs.flarum.org/install/. Artifact reference: Current 2.x release/archive or Composer application; pin core and extension versions.

- Minimum footprint / sizing: Sources checked — unresolved. The 2.x installation guide specifies PHP 8.3+, web-server and supported database requirements, but no quantitative production CPU/RAM/storage minimum was established. Confirm database, extension, search and active-user requirements for the intended deployment. Scope: Current 2.x software prerequisites; numeric production host floor remains open. Source: https://docs.flarum.org/install/ (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







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







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







## Krayin CRM

Self-hosted CRM for leads, contacts, sales pipelines and activity records.

- Listing: https://launchinyourcloud.com/directory/krayin-crm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: Laravel application, database, persistent files and scheduled jobs.
- 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://krayincrm.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Hostinger template is a provider package; apply upstream upgrades and configure delivery, TLS and backups separately.

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

Laravel application, database, persistent files and scheduled jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Self-hosted CRM for leads, contacts, sales pipelines and activity records.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/krayin-crm
  Laravel application, database, persistent files and scheduled jobs. The Hostinger template is a provider package; apply upstream upgrades and configure delivery, TLS and backups separately.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jitendra-webkul, suraj-webkul, devansh-webkul, 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/krayin/laravel-crm/graphs/contributors

- Upstream project: https://github.com/krayin/laravel-crm

### Sources

- Hostinger: https://www.hostinger.com/applications/krayin-crm

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/krayin/laravel-crm/master/LICENSE

- GitHub Releases: https://github.com/krayin/laravel-crm/releases

### Licensing sources

- https://raw.githubusercontent.com/krayin/laravel-crm/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/krayin-crm


### 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 Krayin core documentation establishes application login and roles, but does not establish an external SAML/OIDC provider integration for this self-hosted edition. Laravel authentication or an unverified extension is not sufficient evidence of supported user SSO. Scope: Krayin core; third-party modules and paid customization need their own version-specific evidence. Source: https://github.com/krayin/laravel-crm/blob/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. Krayin 2.0 documents the webkul/krayin:2.0.1 image and a GitHub Docker/Compose setup. The guide describes persistent application/database volumes. Pin the selected package, replace defaults and configure production networking, backups and TLS; this is not an HA infrastructure template. Scope: Krayin 2.0 Docker installation; image and source versions must match. Source: https://devdocs.krayincrm.com/2.0/introduction/docker.html (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/webkul/krayin. Artifact reference: webkul/krayin:2.0.1.

- Minimum footprint / sizing: Documented. The upstream README specifies at least 3 GB RAM, PHP 8.2+, Composer 2.5+ and MySQL 8.0.32+ with Apache or Nginx. It does not provide a validated 100-user, 1 TB or HA topology. Scope: Reviewed Krayin master requirements; database, storage, backups and redundancy need workload sizing. Source: https://github.com/krayin/laravel-crm/blob/master/README.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## LibreDesk

Self-hosted shared inbox and customer support desk.

- Listing: https://launchinyourcloud.com/directory/libredesk/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: LibreDesk application, PostgreSQL, cache and persistent 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://libredesk.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.

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

LibreDesk application, PostgreSQL, cache and persistent attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted shared inbox and customer support desk.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/libredesk
  LibreDesk application, PostgreSQL, cache and persistent attachments. Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/libredesk
  LibreDesk application, PostgreSQL, cache and persistent attachments. Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes abhinavxd, csr4422, jleroy, 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/abhinavxd/libredesk/graphs/contributors

- Upstream project: https://github.com/abhinavxd/libredesk

### Sources

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

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

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/abhinavxd/libredesk/main/LICENSE

- GitHub Releases: https://github.com/abhinavxd/libredesk/releases

### Licensing sources

- https://raw.githubusercontent.com/abhinavxd/libredesk/main/LICENSE

### Infrastructure sources

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

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


### 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. Agents can use Google, Microsoft or a custom OpenID Connect provider. Create local agent accounts first: LibreDesk matches the provider email to an existing agent and does not create accounts through SSO. Configure the issuer, credentials and registered callback URL. Scope: Current upstream agent-login configuration, also described by published v2.9.2 source. Source: https://docs.libredesk.io/configuration/sso (reviewed 2026-11-20). Supporting source: Published v2.9.2 feature and installation reference — https://github.com/abhinavxd/libredesk/blob/v2.9.2/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The published v2.9.2 recipe supplies Compose and configuration files for LibreDesk, PostgreSQL and Redis, or a standalone release binary. Set encryption material and the initial administrator password, pin compatible images and configure TLS, persistence and backups. Scope: Published upstream release recipe; the quickstart image tags still require an explicit pin. Source: https://github.com/abhinavxd/libredesk/blob/v2.9.2/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/abhinavxd/libredesk/blob/v2.9.2/docker-compose.yml. Artifact reference: v2.9.2. Supporting source: Current installation and encryption-key guide — https://docs.libredesk.io/getting-started/installation.

- Minimum footprint / sizing: Sources checked — unresolved. The installation guide identifies the application, PostgreSQL and Redis but does not establish a whole-stack CPU/RAM/storage minimum for the selected workload. Size ticket/message throughput, attachments, retention, database and redundancy separately; a single binary does not imply a tiny HA deployment. Scope: Upstream topology confirmed; numeric production sizing remains unconfirmed. Source: https://docs.libredesk.io/getting-started/installation (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: LibreDesk; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/abhinavxd/libredesk/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## LibrePhotos

Self-hosted photo library with search and recognition.

- Listing: https://launchinyourcloud.com/directory/librephotos/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: LibrePhotos application, database, workers and original photo storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.librephotos.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Local recognition does not establish disconnected support for downloading models, updates or optional external services.

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

LibrePhotos application, database, workers and original photo storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted photo library with search and recognition.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/librephotos
  LibrePhotos application, database, workers and original photo storage. Local recognition does not establish disconnected support for downloading models, updates or optional external services.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes derneuere, sickelap, 5m4u66y, 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/LibrePhotos/librephotos/graphs/contributors

- Upstream project: https://github.com/LibrePhotos/librephotos

### Sources

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

- MIT LICENSE: https://raw.githubusercontent.com/LibrePhotos/librephotos/dev/LICENSE

- GitHub Releases: https://github.com/LibrePhotos/librephotos/releases

### Licensing sources

- https://raw.githubusercontent.com/LibrePhotos/librephotos/dev/LICENSE

### Infrastructure sources

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


### 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 current upstream application documents OpenID Connect user sign-in. Its deployment configuration requires a correct external application URL for provider redirects and secure cookie/proxy settings when HTTPS terminates in front of the backend. API tokens are a separate mechanism. Scope: LibrePhotos self-hosted OIDC; match the application, backend and reverse-proxy configuration. Source: https://github.com/LibrePhotos/librephotos/blob/1.6.0/README.md (reviewed 2026-11-20). Supporting source: Deployment environment and proxy requirements — https://docs.librephotos.com/docs/installation/environment-variables.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official standard deployment uses the repository's deploy/compose directory, an environment file and Docker Compose. Application, database and volume paths must match the selected release; PostgreSQL 18 changes the documented mount path. Pulling images alone does not update the Compose configuration. Scope: LibrePhotos standard self-hosted Compose deployment; alternative unified-container packaging has a separate recipe. Source: https://docs.librephotos.com/docs/installation/standard-install (reviewed 2026-11-20). Deployment artifact: https://github.com/LibrePhotos/librephotos/tree/1.6.0/deploy/compose. Artifact reference: 1.6.0 application release; match Compose configuration and container tags.

- Minimum footprint / sizing: Documented. The upstream requirements list two CPU cores, 4 GB RAM and 10 GB storage plus the photo library; four or more cores and 8 GB or more RAM are recommended. ML features are memory-intensive. These are application baselines, not sizing for 1 TB, concurrent indexing or HA. Scope: Reviewed LibrePhotos self-hosted requirements; original photos, thumbnails, database, backups and replicas add capacity needs. Source: https://github.com/LibrePhotos/librephotos/blob/1.6.0/README.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







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







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







## Open Archiver

Open-source email archive with provider-packaged VPS deployment and retention-oriented workflows.

- Listing: https://launchinyourcloud.com/directory/open-archiver/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker Compose application, PostgreSQL, Valkey, Meilisearch and persistent local or S3-compatible archive 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://openarchiver.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Hostinger supplies the named VPS deployment; the customer operates the complete stateful stack. Upstream's installation baseline is 4 GB RAM, or 2 GB with external data services. Those minima do not size the agreed HA workload or a complete retention budget. Recreate containers from a compatible v0.6.2-or-later image containing the runtime correction; updating application files alone does not replace the runtime.

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

Docker Compose application, PostgreSQL, Valkey, Meilisearch and persistent local or S3-compatible archive storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- records-management: Open-source email archive with provider-packaged VPS deployment and retention-oriented workflows.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger Open Archiver (hostinger): https://www.hostinger.com/applications/open-archiver
  Docker Compose application, PostgreSQL, Valkey, Meilisearch and persistent local or S3-compatible archive storage. Hostinger supplies the named VPS deployment; the customer operates the complete stateful stack. Upstream's installation baseline is 4 GB RAM, or 2 GB with external data services. Those minima do not size the agreed HA workload or a complete retention budget.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes weishest, tilwegener, axeldunkel, 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/LogicLabs-OU/OpenArchiver/graphs/contributors

- Upstream project: https://github.com/LogicLabs-OU/OpenArchiver

### Sources

- Hostinger Open Archiver: https://www.hostinger.com/applications/open-archiver

- Install Docs: https://docs.openarchiver.com/user-guides/installation.html

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/LogicLabs-OU/OpenArchiver/main/LICENSE

- GitHub Releases: https://github.com/LogicLabs-OU/OpenArchiver/releases

- OpenArchiver runtime security rebuild: https://github.com/LogicLabs-OU/OpenArchiver/releases/tag/v0.6.2

### Licensing sources

- https://raw.githubusercontent.com/LogicLabs-OU/OpenArchiver/main/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/open-archiver


### 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: Edition-dependent. The vendor documents OIDC and SAML2 user SSO with provider discovery/metadata, callbacks, JIT/account linking and group roles, requiring an Enterprise licence with SSO enabled. Local MFA and mailbox-connector OAuth are separate. Do not apply this entitlement to the unactivated open-source build. Scope: Open Archiver Enterprise user SSO feature entitlement. Source: https://docs.openarchiver.com/enterprise/sso/guide.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream guide supplies Docker Compose for the application and dependencies, with environment configuration, persistent storage and optional S3. Pin compatible images, protect keys/secrets and plan database/Redis/search upgrades, backups and TLS; one Compose host does not establish HA. Scope: Open Archiver upstream Compose deployment; Enterprise activation and hosting packages separate. Source: https://docs.openarchiver.com/user-guides/installation.html (reviewed 2026-11-21). Deployment artifact: https://docs.openarchiver.com/user-guides/installation.html. Artifact reference: Current upstream installation guide reviewed on this date.

- Minimum footprint / sizing: Documented. The installation guide requires at least 4 GB RAM with bundled services, or 2 GB when PostgreSQL, Redis/Valkey and Meilisearch run externally. That application-host baseline excludes the external services, retained mail/attachments, indexes, ingestion peaks and HA replicas. Scope: Open Archiver host RAM baseline with bundled versus external dependency distinction. Source: https://docs.openarchiver.com/user-guides/installation.html (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- OpenArchiver runtime security rebuild (security-advisory): Upstream 0.6.2 rebuilds the image with a corrected Node.js Brotli runtime. Scope: OpenArchiver v0.6.2 image update for CVE-2026-111497; custom source installations must inspect their actual Node.js runtime. Conditions: The release changes the container runtime rather than application code; a custom image may have a different runtime. Action: Recreate containers from a compatible v0.6.2-or-later image containing the runtime correction; updating application files alone does not replace the runtime. Source: https://github.com/LogicLabs-OU/OpenArchiver/releases/tag/v0.6.2; reviewed 2026-11-19.




## OTOBO

Self-hosted service desk for tickets, queues, service workflows and customer records.

- Listing: https://launchinyourcloud.com/directory/otobo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Perl application, database, search, web server and background jobs.
- 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/RotherOSS/otobo
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

OTOBO is maintained separately from historical OTRS editions; extensions and support contracts have their own scope.

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

Perl application, database, search, web server and background jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted service desk for tickets, queues, service workflows and customer records.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/otobo
  Perl application, database, search, web server and background jobs. OTOBO is maintained separately from historical OTRS editions; extensions and support contracts have their own scope.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes bschmalhofer, stefanhaerter, MichaelThumes, 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/RotherOSS/otobo/graphs/contributors

- Upstream project: https://github.com/RotherOSS/otobo

### Sources

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

- GitHub LICENSE (GPL-3.0): https://raw.githubusercontent.com/RotherOSS/otobo/rel-11_1/LICENSE

- GitHub Releases: https://github.com/RotherOSS/otobo/releases

### Licensing sources

- https://raw.githubusercontent.com/RotherOSS/otobo/rel-11_1/LICENSE

### Infrastructure sources

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


### 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 OTOBO 11.1 Docker guide documents Kerberos SSO through its Nginx proxy with an Active Directory service principal/keytab and browser configuration. Enable the application HTTP authentication backend and map existing users; LDAP password checks and mailbox OAuth alone are different paths. Scope: Versioned OTOBO 11.1 Kerberos/Nginx setup; not a generic SAML/OIDC claim. Source: https://doc.otobo.org/manual/installation/11.1/en/content/sso-kerberos.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 11.1 guide recommends Docker Compose and links the otobo-docker repository. Select the patch-matched tag, configure .env, passwords, persistent volumes and TLS, then run the application installer. The base stack and HTTP/HTTPS overrides are separate files; do not treat the moving branch as a fixed application version. Scope: Versioned OTOBO 11.1 installation with patch-matched Compose configuration. Source: https://doc.otobo.org/manual/installation/11.1/en/content/installation/installation-docker.html (reviewed 2026-11-20). Deployment artifact: https://github.com/RotherOSS/otobo-docker/tree/rel-11_1. Artifact reference: rel-11_1 (moving branch; guide requires selecting the matching patch tag).

- Minimum footprint / sizing: Documented. The 11.1 guide gives a test baseline of 4 GB RAM and 10 GB storage, and a production starting point of a 3 GHz Xeon-class CPU, 8 GB RAM (16 GB recommended) and 40 GB storage. Ticket volume and attachments drive sizing; these are not a replicated 1 TB HA specification. Scope: Versioned production-versus-test host guidance; configure database and attachment storage separately. Source: https://doc.otobo.org/manual/installation/11.1/en/content/requirements.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Papermerge DMS

Self-hosted scanned-document management, OCR and metadata repository.

- Listing: https://launchinyourcloud.com/directory/papermerge/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: Papermerge application, database, processing workers and persistent documents.
- 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://papermerge.dev
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

OCR and preview processing add compute and temporary storage; a base provider template is not a capacity plan for a 1 TB HA repository.

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

Papermerge application, database, processing workers and persistent documents. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted scanned-document management, OCR and metadata repository.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/papermerge
  Papermerge application, database, processing workers and persistent documents. OCR and preview processing add compute and temporary storage; a base provider template is not a capacity plan for a 1 TB HA repository.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ciur, dl3sm, bl1nkker, 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/papermerge/papermerge-core/graphs/contributors

- Upstream project: https://github.com/papermerge/papermerge-core

### Sources

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

- Apache-2.0 LICENSE: https://raw.githubusercontent.com/papermerge/papermerge-core/master/LICENSE

- GitHub Releases: https://github.com/papermerge/papermerge-core/releases

### Licensing sources

- https://raw.githubusercontent.com/papermerge/papermerge-core/master/LICENSE

### Infrastructure sources

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


### 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 3.5 documentation describes OIDC sign-in, with Keycloak and Authentik examples, plus a separately configured remote-user option. Configure the identity provider and token/group mapping; do not trust unfiltered public headers. Scope: Papermerge DMS 3.5 self-hosted OIDC. Source: https://docs.papermerge.io/3.5/sso/oidc/overview/ (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 vendor publishes Compose YAML for PostgreSQL, persistent media and optional OCR, S3 and indexing workers. Examples pin the web image to 3.5.3; replace sample secrets and reconcile component versions before production. SQLite examples are demos. Scope: Papermerge 3.5 progressive Compose examples; not a complete HA architecture. Source: https://docs.papermerge.io/3.5/setup/docker-compose/ (reviewed 2026-11-20). Deployment artifact: https://docs.papermerge.io/3.5/setup/docker-compose/#persistent-media-storage. Artifact reference: 3.5 documentation; example web image 3.5.3.

- Minimum footprint / sizing: Documented. The vendor gives 1 GB RAM as the absolute minimum for the web application alone. Database, OCR, indexing, other workers and Kubernetes require additional resources; this is not the full application or HA footprint. Scope: Papermerge 3.5 web-only minimum; optional services and production capacity excluded. Source: https://docs.papermerge.io/3.5/setup/requirements/ (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







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




## PhotoPrism

Self-hosted photo library indexing, search and album management.

- Listing: https://launchinyourcloud.com/directory/photoprism/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean, hostinger
- 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: VM image; Docker / Compose
- Architecture: PhotoPrism application, database and persistent original photos and previews.
- 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.photoprism.app
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Community AGPL-3.0 and paid editions have different features. External maps or configured services may receive requests; archive photos and the database consistently.

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

PhotoPrism application, database and persistent original photos and previews. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted photo library indexing, search and album management.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.photoprism.app/getting-started/cloud/digitalocean/ (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://docs.photoprism.app/getting-started/cloud/hostinger/ (checked 2026-11-19). 


### Cloud deployment evidence

- PhotoPrism DO Guide (digitalocean): https://docs.photoprism.app/getting-started/cloud/digitalocean/
  PhotoPrism application, database and persistent original photos and previews. Community AGPL-3.0 and paid editions have different features. External maps or configured services may receive requests; archive photos and the database consistently.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- PhotoPrism Hostinger Guide (hostinger): https://docs.photoprism.app/getting-started/cloud/hostinger/
  PhotoPrism application, database and persistent original photos and previews. Community AGPL-3.0 and paid editions have different features. External maps or configured services may receive requests; archive photos and the database consistently.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes lastzero, graciousgrey, weblate, 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/photoprism/photoprism/graphs/contributors

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

### Sources

- PhotoPrism DO Guide: https://docs.photoprism.app/getting-started/cloud/digitalocean/

- PhotoPrism Hostinger Guide: https://docs.photoprism.app/getting-started/cloud/hostinger/

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

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

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

### Licensing sources

- https://raw.githubusercontent.com/photoprism/photoprism/develop/LICENSE

### Infrastructure sources

- https://docs.photoprism.app/getting-started/cloud/digitalocean/

- https://docs.photoprism.app/getting-started/cloud/hostinger/


### 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. PhotoPrism documents OIDC user sign-in; its edition comparison lists OpenID Connect for Community, Essentials and Plus. Role capabilities and provisioning differ: Personal editions default new OIDC users to Guest, while Pro supports additional default-role policy. SSO does not imply every paid role-management feature. Scope: Self-hosted PhotoPrism OIDC; edition-specific roles and provider configuration apply. Source: https://docs.photoprism.app/getting-started/advanced/openid-connect/ (reviewed 2026-11-20). Supporting source: Personal edition SSO and role comparison — https://www.photoprism.app/editions.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide publishes a Compose file with application/database configuration and persistent originals/storage directories. Replace example credentials, select matching images, configure HTTPS and retain backups; RAW indexing and model features affect resource needs. Scope: Self-hosted PhotoPrism Compose stack; optional external AI services and replicas are separate. Source: https://docs.photoprism.app/getting-started/docker-compose/ (reviewed 2026-11-20). Deployment artifact: https://dl.photoprism.app/docker/compose.yaml. Artifact reference: Published compose.yaml (unversioned URL); pin the reviewed file and image versions.

- Minimum footprint / sizing: Documented. The official setup guide requires at least two CPU cores, 3 GB physical RAM and a 64-bit OS, with at least 4 GB swap recommended. RAW/panorama processing may need more memory; SSDs help database/cache work. This is a single-server baseline, not validated 1 TB indexing or HA capacity. Scope: Self-hosted PhotoPrism baseline; physical RAM and swap are distinct, and library/model/concurrency needs add resources. Source: https://docs.photoprism.app/getting-started/ (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: PhotoPrism; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/photoprism/photoprism/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## PiGallery2

Self-hosted directory-based photo and video gallery.

- Listing: https://launchinyourcloud.com/directory/pigallery2/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, azure
- 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: VM image; Docker / Compose
- Architecture: PiGallery2 application, directory storage and configured database/index.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.hostinger.com/applications/pigallery2
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The core serves an existing media directory; it is not a full document-ingestion, rights-management or upload approval workflow.

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

PiGallery2 application, directory storage and configured database/index. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted directory-based photo and video gallery.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.pigallery2-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/pigallery2
  PiGallery2 application, directory storage and configured database/index. The core serves an existing media directory; it is not a full document-ingestion, rights-management or upload approval workflow.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.pigallery2-ubuntu-24-04
  PiGallery2 application, directory storage and configured database/index. The core serves an existing media directory; it is not a full document-ingestion, rights-management or upload approval workflow.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes bpatrik, claude, grasdk, 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/bpatrik/pigallery2/graphs/contributors

- Upstream project: https://github.com/bpatrik/pigallery2

### Sources

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

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.pigallery2-ubuntu-24-04

- MIT LICENSE: https://raw.githubusercontent.com/bpatrik/pigallery2/master/LICENSE

- GitHub Releases: https://github.com/bpatrik/pigallery2/releases

### Licensing sources

- https://raw.githubusercontent.com/bpatrik/pigallery2/master/LICENSE

### Infrastructure sources

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

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.pigallery2-ubuntu-24-04


### 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: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: PiGallery2 selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.pigallery2-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.pigallery2-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.pigallery2-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.pigallery2-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.pigallery2-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Documented. PiGallery2 3.8.0 includes an Authentik/OIDC setup guide and application configuration. Enable OIDC with the issuer, client and callback details. The guide distinguishes default name-based matching from Strict security account linking; verify this policy and eligible roles for the chosen provider. Scope: PiGallery2 3.8.0 upstream OIDC user sign-in; provider images have separate packaged versions. Source: https://github.com/bpatrik/pigallery2/blob/3.8.0/docs/setup/advanced/authentik.md (reviewed 2026-11-20). Supporting source: Versioned application OIDC configuration — https://github.com/bpatrik/pigallery2/blob/3.8.0/src/common/config/private/PrivateConfig.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project publishes a Docker Compose example with image, database/configuration and gallery-volume options. Match the 3.8.0 source configuration to its image and configure credentials, durable data, HTTPS and any OIDC provider; the single-host example is not an HA deployment. Scope: PiGallery2 upstream Docker deployment; Hostinger and Azure image packages have their own versions/defaults. Source: https://github.com/bpatrik/pigallery2/blob/3.8.0/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/bpatrik/pigallery2/blob/3.8.0/docker/docker-compose/default/docker-compose.yml. Artifact reference: 3.8.0 source recipe; select a compatible image instead of following latest automatically.

- Minimum footprint / sizing: Sources checked — unresolved. The published benchmark file includes older-commit tests on a 4 GB Raspberry Pi 4 with about 2,000 photos/22 GB of media. This is a scoped historical performance example, not a current whole-stack minimum or evidence for 1 TB and 100-user HA capacity; a workload-specific resource profile remains unconfirmed. Scope: PiGallery2 benchmark evidence bundled with 3.8.0; benchmark commits/data size differ from a new production deployment. Source: https://github.com/bpatrik/pigallery2/blob/3.8.0/benchmark/README.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







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







## Relaticle

Self-hosted CRM with configurable customer records, sales pipelines and workflow tools.

- Listing: https://launchinyourcloud.com/directory/relaticle/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Laravel application, database, persistent storage and queues.
- 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://relaticle.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

MCP and external AI integrations can disclose or modify CRM data according to the agent credentials; own-account application hosting does not make those integrations private.

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

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


### Category fit

- erp-crm: Self-hosted CRM with configurable customer records, sales pipelines and workflow tools.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/relaticle
  Laravel application, database, persistent storage and queues. MCP and external AI integrations can disclose or modify CRM data according to the agent credentials; own-account application hosting does not make those integrations private.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ManukMinasyan, AsmitNepali, Ilyapashayan20, 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/Relaticle/Relaticle/graphs/contributors

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

### Sources

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

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/Relaticle/Relaticle/main/LICENSE

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

### Licensing sources

- https://raw.githubusercontent.com/Relaticle/Relaticle/main/LICENSE

### Infrastructure sources

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


### 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 README documents MCP/API authentication through OAuth 2.1 or personal tokens, but does not establish external SAML/OIDC user sign-in to the CRM. An OAuth authorization server for client integrations is a different login surface from enterprise IdP federation. Scope: Self-hosted Relaticle CRM user login; MCP integration tokens are excluded from the SSO claim. Source: https://github.com/Relaticle/Relaticle/blob/main/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official self-hosting guide provides a Docker Compose deployment with application, queue, scheduler, WebSocket, PostgreSQL and Redis services. Configure secrets, persistent storage, HTTPS, backups and image versions before production. Scope: Self-hosted complete Relaticle stack; multi-container single-host recipe, not HA infrastructure automation. Source: https://relaticle.com/docs/self-hosting (reviewed 2026-11-20). Deployment artifact: https://github.com/Relaticle/relaticle/blob/main/compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The self-hosting guide lists a minimum of 2 GB RAM, one CPU core and 10 GB disk, recommending 4 GB, two cores and 20 GB or more. These are a single-host baseline for the Compose stack, not validated 100-user, 1 TB or HA sizing. Scope: Reviewed self-hosted Relaticle Compose deployment; storage and replicas must be sized separately. Source: https://relaticle.com/docs/self-hosting (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: Relaticle; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/Relaticle/Relaticle/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## SilverBullet

Self-hosted Markdown note and personal knowledge workspace.

- Listing: https://launchinyourcloud.com/directory/silverbullet/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: SilverBullet server with persistent Markdown documents and local metadata.
- 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://silverbullet.md
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

A browser offline/PWA mode does not establish a disconnected production deployment. Review any installed plugs and external AI integrations.

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

SilverBullet server with persistent Markdown documents and local metadata. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted Markdown note and personal knowledge workspace.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/silverbullet
  SilverBullet server with persistent Markdown documents and local metadata. A browser offline/PWA mode does not establish a disconnected production deployment. Review any installed plugs and external AI integrations.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes zefhemel, mjf, MrMugame, 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/silverbulletmd/silverbullet/graphs/contributors

- Upstream project: https://github.com/silverbulletmd/silverbullet

### Sources

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

- MIT LICENSE.md: https://raw.githubusercontent.com/silverbulletmd/silverbullet/main/LICENSE.md

- GitHub Releases: https://github.com/silverbulletmd/silverbullet/releases

### Licensing sources

- https://raw.githubusercontent.com/silverbulletmd/silverbullet/main/LICENSE.md

### Infrastructure sources

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


### 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 published 2.12.1 documentation supports OIDC in account-managed multi-server mode. Administrators provision accounts and assign spaces; the IdP must supply a stable subject and verified email. Legacy single-space credentials and an authentication proxy are separate modes, not equivalent per-user SSO configurations. Scope: SilverBullet 2.12.1 account-managed server; provider configuration and local administrator recovery access required. Source: https://github.com/silverbulletmd/silverbullet/blob/2.12.1/docs/Single%20Sign-On.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide supplies a Compose deployment with a persistent data directory and versioned GHCR/Docker Hub images. Select a stable release rather than the moving edge/v2 channel, and configure the chosen account/authentication mode, HTTPS and backups. Scope: Self-hosted SilverBullet container and persistent server data; not a cloud/HA template. Source: https://silverbullet.md/Install/Docker (reviewed 2026-11-20). Deployment artifact: https://github.com/silverbulletmd/silverbullet/pkgs/container/silverbullet. Artifact reference: 2.12.1 published source reviewed; select its corresponding versioned image instead of latest/edge.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed Docker/configuration guides establish persistent server data and authentication modes but do not specify a quantitative whole-host CPU/RAM/storage floor. Library size, indexing, attached files, browser/runtime features and concurrent spaces must be sized for the selected release. Scope: SilverBullet server and data workload; a small binary/container is not a production or HA sizing guarantee. Source: https://silverbullet.md/Install/Docker (reviewed 2026-11-20). Supporting source: Server modes and configuration — https://silverbullet.md/Install/Configuration.

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

- Operating cost estimate: Not researched.

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







## SiYuan

Self-hosted personal knowledge base and block-based note application.

- Listing: https://launchinyourcloud.com/directory/siyuan/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: SiYuan server and persistent workspace files.
- 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://b3log.org/siyuan
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Release candidates must be separated from stable versions. Optional AI, synchronization and paid services change the external data flow; browser offline use is not air-gapped server support.

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

SiYuan server and persistent workspace files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted personal knowledge base and block-based note application.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/siyuan
  SiYuan server and persistent workspace files. Release candidates must be separated from stable versions. Optional AI, synchronization and paid services change the external data flow; browser offline use is not air-gapped server support.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes 88250, Vanessa219, TCOTC, 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/siyuan-note/siyuan/graphs/contributors

- Upstream project: https://github.com/siyuan-note/siyuan

### Sources

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

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/siyuan-note/siyuan/master/LICENSE

- GitHub Releases: https://github.com/siyuan-note/siyuan/releases

### Licensing sources

- https://raw.githubusercontent.com/siyuan-note/siyuan/master/LICENSE

### Infrastructure sources

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


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SiYuan v3.8.11 documents Docker access through OpenID Connect, with Google, Microsoft and custom OIDC providers plus a separate GitHub OAuth adapter. Accepted identities receive SiYuan administrator access to the workspace; configure claim rules rather than assuming separate per-user roles or private workspaces. Scope: SiYuan v3.8.11 server workspace access; not a general multi-tenant collaboration or SCIM claim. Source: https://github.com/siyuan-note/siyuan/blob/v3.8.11/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 published v3.8.11 README documents Docker and Kubernetes deployment with a persistent workspace and explicit access authentication. The example uses b3log/siyuan; select a compatible image version, correct host ownership, credentials and a public HTTPS/OIDC callback configuration. Scope: Self-hosted SiYuan application/workspace; container deployment is not an HA infrastructure design. Source: https://github.com/siyuan-note/siyuan/blob/v3.8.11/README.md (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/b3log/siyuan. Artifact reference: v3.8.11 source instructions; example image tag is not pinned.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed server-deployment instructions describe workspace persistence and authentication but do not establish a quantitative whole-host CPU/RAM/storage minimum for the chosen library and workload. Desktop package size or container start-up alone would not establish team/HA capacity. Scope: SiYuan server/workspace and its data, search/indexing and backups; quantitative production sizing remains unconfirmed. Source: https://github.com/siyuan-note/siyuan/blob/v3.8.11/README.md (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: SiYuan; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/siyuan-note/siyuan/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SolidInvoice

Customer-operated invoicing, quotations and client billing application.

- Listing: https://launchinyourcloud.com/directory/solidinvoice/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: PHP application, database, uploads and scheduled jobs.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.hostinger.com/applications/solidinvoice
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Scope is invoicing and billing rather than a full enterprise resource planning suite.

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

PHP application, database, uploads and scheduled jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated invoicing, quotations and client billing application.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/solidinvoice
  PHP application, database, uploads and scheduled jobs. Scope is invoicing and billing rather than a full enterprise resource planning suite.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes pierredup, actions-user, claude, 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/SolidInvoice/SolidInvoice/graphs/contributors

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

### Sources

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

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/SolidInvoice/SolidInvoice/2.3.x/LICENSE

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

### Licensing sources

- https://raw.githubusercontent.com/SolidInvoice/SolidInvoice/2.3.x/LICENSE

### Infrastructure sources

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


### 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 SolidInvoice 3.1.3 source documents Google OAuth user login in the shared self-hosted codebase. This establishes Google sign-in, not arbitrary enterprise SAML/OIDC federation. Its separate MCP OAuth server is not evidence of additional user-login providers. Scope: SolidInvoice 3.1.3 self-hosted edition; provider credentials and callback configuration required. Source: https://github.com/SolidInvoice/SolidInvoice/blob/3.1.3/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide provides Docker, distribution-package, native-package and Helm options followed by a first-run wizard. The reviewed 3.1.3 source includes a Docker recipe. Choose matching versions and configure durable data, secrets, HTTPS and backups before production. Scope: SolidInvoice 3.x installation paths; application packaging does not establish a complete HA cloud deployment. Source: https://solidinvoice.co/docs/installation-guide/ (reviewed 2026-11-20). Deployment artifact: https://github.com/SolidInvoice/SolidInvoice/blob/3.1.3/docker-compose.yml. Artifact reference: 3.1.3. Supporting source: Docker installation — https://solidinvoice.co/docs/installation-guide/docker/.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed 3.1.3 README and installation guide specify the PHP/database toolchain and packaging options, but do not establish a quantitative whole-host resource floor for this workload. A PHP memory limit or a small demo container would not establish production HA capacity. Scope: Self-hosted SolidInvoice 3.1.3 application and database; deployment-specific sizing remains to be confirmed. Source: https://github.com/SolidInvoice/SolidInvoice/blob/3.1.3/README.md (reviewed 2026-11-20). Supporting source: System installation — https://solidinvoice.co/docs/installation-guide/system-installation/.

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

- Operating cost estimate: Not researched.

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







## Solidtime

Self-hosted project time tracking and billing records.

- Listing: https://launchinyourcloud.com/directory/solidtime/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Solidtime application, database, workers and persistent files.
- 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.solidtime.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Time tracking and billing are its core scope; it is not a full project planning or payroll system. Update and recreate the Solidtime image/runtime with the corrections supplied in v0.22.1 or a later compatible build.

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

Solidtime application, database, workers and persistent files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted project time tracking and billing records.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/solidtime
  Solidtime application, database, workers and persistent files. Time tracking and billing are its core scope; it is not a full project planning or payroll system.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes Onatcer, korridor, TheSpyder, 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/solidtime-io/solidtime/graphs/contributors

- Upstream project: https://github.com/solidtime-io/solidtime

### Sources

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

- AGPL-3.0 LICENSE.md: https://raw.githubusercontent.com/solidtime-io/solidtime/main/LICENSE.md

- GitHub Releases: https://github.com/solidtime-io/solidtime/releases

- Solidtime PHP runtime security release: https://github.com/solidtime-io/solidtime/releases/tag/v0.22.1

### Licensing sources

- https://raw.githubusercontent.com/solidtime-io/solidtime/main/LICENSE.md

### Infrastructure sources

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


### 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. The self-hosting guide supports company OIDC identity providers and explicitly requires On-Premise Business. Configure the public URL, proxy/HTTPS settings, IdP callback and access rules, with a working super-admin account for recovery. Scope: Current commercial self-hosted SSO feature; not established for the AGPL core v0.22.1 package alone. Source: https://docs.solidtime.io/self-hosting/single-sign-on (reviewed 2026-11-21).

- 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 repository supplies separate application, scheduler and queue-worker services plus PostgreSQL, persistent storage and health checks. Generate keys and configure environment, email, URL/proxy and backup settings; choose matching application images instead of relying on latest. Scope: Upstream self-hosted Compose topology; Business SSO entitlement is separate. Source: https://docs.solidtime.io/self-hosting/guides/docker (reviewed 2026-11-21). Deployment artifact: https://github.com/solidtime-io/self-hosting-examples/blob/main/1-docker-with-database/docker-compose.yml. Artifact reference: main (moving branch); SOLIDTIME_IMAGE_TAG defaults to latest.

- Minimum footprint / sizing: Sources checked — unresolved. The official Compose example identifies application, scheduler, queue worker and database roles with persistent storage, but no production CPU/RAM or concurrency baseline was established. Their combined capacity, retention, database size and HA arrangement need workload-specific sizing. Scope: Service topology confirmed; quantitative production hardware sizing remains unconfirmed. Source: https://github.com/solidtime-io/self-hosting-examples/blob/main/1-docker-with-database/docker-compose.yml (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Solidtime PHP runtime security release (security-advisory): Solidtime 0.22.1 updates PHP to 8.3.36 for two critical runtime issues. Scope: CVE-2026-109618 and CVE-2026-109619 in the PHP runtime; the release updates FrankenPHP as well. Conditions: Custom installations must inspect their own PHP/runtime build; no application-wide vulnerable range is invented. Action: Update and recreate the Solidtime image/runtime with the corrections supplied in v0.22.1 or a later compatible build. Source: https://github.com/solidtime-io/solidtime/releases/tag/v0.22.1; reviewed 2026-11-19.




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







## Teedy (Sismics Docs)

Self-hosted document repository with OCR, search and access controls.

- Listing: https://launchinyourcloud.com/directory/teedy/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: Teedy application, database and durable document storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://teedy.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 published 1.11 release date and recent source activity are separate facts; do not present a source commit as a new stable release or support commitment. Verify that the installed Teedy image contains the reviewed source fixes, or obtain a fixed build; do not assume the old stable tag includes later commits.

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

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


### Category fit

- document-management: Self-hosted document repository with OCR, search and access controls.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/teedy
  Teedy application, database and durable document storage. The published 1.11 release date and recent source activity are separate facts; do not present a source commit as a new stable release or support commitment.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jendib, naku, vmario89, 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/sismics/docs/graphs/contributors

- Upstream project: https://github.com/sismics/docs

### Sources

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

- GPL-2.0 COPYING: https://raw.githubusercontent.com/sismics/docs/master/COPYING

- GitHub Commits: https://github.com/sismics/docs/commits/master

- Teedy source-branch authorization and input fixes: https://github.com/sismics/docs/commit/c188971e72d2595b5d0cc1fcab980bca0b42ea89

### Licensing sources

- https://raw.githubusercontent.com/sismics/docs/master/COPYING

### Infrastructure sources

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


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 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 upstream feature list documents LDAP and two-factor authentication, but the reviewed installation/configuration reference does not establish a supported SAML or OIDC sign-on workflow. LDAP login alone is not evidence of federated SSO. Scope: Self-hosted upstream edition; federation protocol and support scope unresolved. Source: https://raw.githubusercontent.com/sismics/docs/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 includes a Docker Compose application/PostgreSQL stack and persistent volumes. It pins the example application to v1.11; reconcile it with the chosen maintained release and replace example credentials before production. Embedded H2 is evaluation-only. Scope: Upstream Compose example, not a hardened or HA template. Source: https://raw.githubusercontent.com/sismics/docs/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/sismics/docs/blob/master/README.md#examples. Artifact reference: master (moving branch; example image v1.11).

- Minimum footprint / sizing: Sources checked — unresolved. The upstream recipe identifies the application, OCR/conversion tools, PostgreSQL and persistent storage, but does not specify a CPU/RAM minimum or validated workload sizing. Obtain a workload-specific recommendation before choosing production capacity. Scope: Upstream production components; numeric sizing unresolved. Source: https://raw.githubusercontent.com/sismics/docs/master/README.md (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: Teedy (Sismics Docs); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/sismics/docs/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Teedy source-branch authorization and input fixes (security-advisory): Recent upstream source commits correct LDAP filter escaping, active-content rendering and file write-permission checks. Scope: Reviewed main-branch fixes in October–November 2026; the older v1.11 GitHub release does not establish a release containing them. Conditions: LDAP configuration, uploaded active content and file operations have separate conditions; check the installed image’s actual commits. Action: Verify that the installed Teedy image contains the reviewed source fixes, or obtain a fixed build; do not assume the old stable tag includes later commits. Source: https://github.com/sismics/docs/commit/c188971e72d2595b5d0cc1fcab980bca0b42ea89; reviewed 2026-11-19. Supporting source: LDAP escaping correction — https://github.com/sismics/docs/commit/b928f5d376479db5c7b3750fb84c25ba0b69f09d. Supporting source: Active-content rendering correction — https://github.com/sismics/docs/commit/2337d43d8d34b596cff3b0deb0c4bbd0caea2584.




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







## Tududi

Self-hosted task, project and personal productivity application.

- Listing: https://launchinyourcloud.com/directory/tududi/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, 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: Application platform deployment; Docker / Compose
- Architecture: Tududi application and persistent database and files.
- 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://tududi.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.

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

Tududi application and persistent database and files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted task, project and personal productivity application.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/tududi
  Tududi application and persistent database and files. CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/tududi
  Tududi application and persistent database and files. CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes chrisvel, antanst, rome-xi, 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/chrisvel/tududi/graphs/contributors

- Upstream project: https://github.com/chrisvel/tududi

### Sources

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

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

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/chrisvel/tududi/main/LICENSE

- GitHub Releases (v2.1.1): https://github.com/chrisvel/tududi/releases

### Licensing sources

- https://raw.githubusercontent.com/chrisvel/tududi/main/LICENSE

### Infrastructure sources

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

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


### 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 v2.1.1 OIDC guide documents one or multiple identity providers, installation callbacks, account linking and optional just-in-time provisioning. Automatic provisioning and admin-domain rules require deliberate IdP access restrictions; personal API tokens and CalDAV Basic authentication are separate paths. Scope: Versioned self-hosted application-user OIDC login. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docs/10-oidc-sso.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 v2.1.1 Compose example runs Tududi with PostgreSQL 16, database health checks and persistent database/uploads/backups storage. Supply environment secrets and replace the moving latest application image with the intended released version; optional local dumps still need off-host backup. Scope: Versioned Compose example; PostgreSQL-backed v2.x is different from older SQLite installations. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml (reviewed 2026-11-20). Deployment artifact: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml. Artifact reference: v2.1.1 (file snapshot; example application image still uses latest).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed v2.1.1 README and Compose stack establish a PostgreSQL-backed application with persistent uploads and backups, but no production CPU/RAM or concurrency baseline was confirmed. The sample has no resource requests/limits that could substantiate a host minimum. Scope: Deployment topology confirmed; production/HA sizing for the reference workload remains unconfirmed. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml (reviewed 2026-11-20). Supporting source: Versioned installation prerequisites — https://github.com/chrisvel/tududi/blob/v2.1.1/README.md.

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

- Operating cost estimate: Not researched.

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







## useSend

Self-hosted email campaign and transactional messaging application.

- Listing: https://launchinyourcloud.com/directory/usesend/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: useSend application, PostgreSQL, queues and AWS SES/SNS integration.
- 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://useSend.com
- 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 runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.

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

useSend application, PostgreSQL, queues and AWS SES/SNS integration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted email campaign and transactional messaging application.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/usesend
  useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/usesend
  useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes KMKoushik, harshsbhat, magicspon, 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/usesend/useSend/graphs/contributors

- Upstream project: https://github.com/usesend/useSend

### Sources

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

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

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/usesend/useSend/main/LICENSE

- GitHub Releases: https://github.com/usesend/useSend/releases

### Licensing sources

- https://raw.githubusercontent.com/usesend/useSend/main/LICENSE

### Infrastructure sources

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

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


### 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 self-hosting guide documents GitHub login; published v1.10.4 code also registers Google when configured. The code permits an initial bootstrap account, then requires an existing account or team invitation. Configure provider credentials, trusted email/account linking and callbacks. Email codes, SES credentials and API/SMTP tokens are separate; generic SAML/OIDC federation is not established. Scope: Named external login providers for the self-hosted application, with published account-admission behavior. Source: https://docs.usesend.com/self-hosting/overview.md (reviewed 2026-11-20). Supporting source: Published v1.10.4 provider and account-admission code — https://github.com/usesend/useSend/blob/v1.10.4/apps/web/src/server/auth.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official production Docker guide links a Compose stack; the v1.10.4 recipe includes the app, PostgreSQL, Redis and RustFS image storage. Pin the application image instead of latest and configure provider login, secrets, persistent data and TLS. AWS SES/SNS delivery and optional public image URLs require separate configuration; the SMTP proxy is a different service. Scope: Published application stack, distinct from the separate SMTP-server Compose example. Source: https://docs.usesend.com/get-started/set-up-docker.md (reviewed 2026-11-20). Deployment artifact: https://github.com/usesend/useSend/blob/v1.10.4/docker/prod/compose.yml. Artifact reference: v1.10.4 (application image tag is latest; pin a compatible deployment version). Supporting source: Official self-hosting dependencies and settings — https://docs.usesend.com/self-hosting/overview.md.

- Minimum footprint / sizing: Sources checked — unresolved. The official guide establishes an app, PostgreSQL, Redis, SES/SNS and optional image-storage topology but no complete production CPU/RAM/storage minimum. Size campaign volume, queue concurrency, email-content retention and storage before selecting instances; 100 internal users and 1 TB alone do not specify delivery throughput or HA capacity. Scope: Current self-hosted topology; whole-system production sizing remains unconfirmed. Source: https://docs.usesend.com/self-hosting/overview.md (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: useSend; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/usesend/useSend/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Winter CMS

Self-hosted content management framework for websites and applications.

- Listing: https://launchinyourcloud.com/directory/wintercms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: Winter CMS application, database, files and scheduled jobs.
- 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://wintercms.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Winter is a separate MIT project; do not transfer the commercial licensing or release cadence of October CMS.

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

Winter CMS application, database, files and scheduled jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted content management framework for websites and applications.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/wintercms
  Winter CMS application, database, files and scheduled jobs. Winter is a separate MIT project; do not transfer the commercial licensing or release cadence of October CMS.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes daftspunk, LukeTowers, bennothommo, 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/wintercms/winter/graphs/contributors

- Upstream project: https://github.com/wintercms/winter

### Sources

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

- Winter CMS Install Docs: https://wintercms.com/docs/v1.2/docs/setup/installation

- MIT LICENSE: https://raw.githubusercontent.com/wintercms/winter/1.2/LICENSE

- GitHub Releases (v1.2.15): https://github.com/wintercms/winter/releases

### Licensing sources

- https://raw.githubusercontent.com/wintercms/winter/1.2/LICENSE

### Infrastructure sources

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


### 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 Winter.SSO plugin adds backend OAuth through Laravel Socialite. It supports named providers and separately installed provider plugins, with optional SSO-only login. Validate the plugin/core versions and provider settings; this is not a claim of native SAML support. Scope: Upstream Winter CMS backend plugin and provider integrations. Source: https://raw.githubusercontent.com/wintercms/wn-sso-plugin/main/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 versioned installation guide documents Composer, a web installer and a Docker-image option. These install the CMS application; database/web-server configuration and production hardening remain customer work. Match the installer to the chosen Winter release. Scope: Winter 1.2 installation methods; not a provider-specific infrastructure template. Source: https://wintercms.com/docs/v1.2/docs/setup/installation (reviewed 2026-11-20). Deployment artifact: https://wintercms.com/docs/v1.2/docs/setup/installation. Artifact reference: Versioned 1.2 guide; choose compatible package and plugins.

- Minimum footprint / sizing: Sources checked — unresolved. The 1.2 guide lists software prerequisites and warns the installer may temporarily need up to 1.5 GB memory. That installation allowance does not establish a production CPU/RAM/storage floor or capacity for the running CMS. Scope: Installer memory and dependencies only; whole-system production sizing remains open. Source: https://wintercms.com/docs/v1.2/docs/setup/installation (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## XWiki

Self-hosted enterprise wiki and structured knowledge application platform.

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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


### Cloud deployment evidence

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

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


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The OpenID Connect Authenticator extension provides OIDC sign-in and synchronization. It is installed through Extension Manager, is LGPL-2.1 licensed, and requires XWiki 14.10.2 or later; commercial support is separate. Scope: XWiki with separately installed OIDC Authenticator extension. Source: https://extensions.xwiki.org/xwiki/bin/view/Extension/OpenID%20Connect/OpenID%20Connect%20Authenticator/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Official installation options include a production-capable Docker image, Debian packages or a WAR distribution. Production requires a supported database, persistent application data and compatible Java/container versions; the standalone HSQLDB demo is not the production baseline. Scope: Official XWiki distribution options. Source: https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/ (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/_/xwiki. Artifact reference: Select an explicit compatible image tag; no artifact is installed by this review.

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

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

- Operating cost estimate: Not researched.

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






