
# Software on DigitalOcean

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

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



## Related questions

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


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


## Provider guidance

- Account boundary: DigitalOcean team/account and project
- Provider group: cloud-infrastructure
- Provider classification: Droplets and managed Kubernetes use the customer infrastructure account. App Platform is a separate platform-workspace path and is identified per listing. Source: https://docs.digitalocean.com/products/droplets/how-to/create/ (checked 2026-11-20).
- Network: VPC and Cloud Firewalls; review public endpoints
- Identity and access: Team roles, scoped API tokens and SSH keys
- Installation guidance: Provision Droplets or Kubernetes in your account; review the application image, storage, updates and firewall rules.
- Guidance source: https://docs.digitalocean.com/products/droplets/how-to/create/
- Guidance reviewed: 2026-11-12


### Private networking

DigitalOcean VPCs isolate resource traffic from the public internet; VPC peering can connect VPCs. Confirm the selected service can join the intended VPC and configure application access controls.
Source: https://docs.digitalocean.com/products/networking/vpc/ (reviewed 2026-11-14).

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

69 listings.


## 3CX Self-Hosted

Commercial business communications and PBX platform installed into the customer's public-cloud account.

- Listing: https://launchinyourcloud.com/directory/3cx-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary annual 3CX system license; edition and simultaneous-call entitlements vary.
- Licensing model: commercial-only
- Installation: 3CX deployment wizard or provider Marketplace path for AWS, Azure, Google Cloud or DigitalOcean
- Architecture: Customer-operated PBX/application VM with web client, SIP/RTP media, certificates, firewall rules and external trunk or carrier dependencies.
- Operations: Customer manages the cloud instance, networking and firewall, DNS/FQDN, backups, upgrades, monitoring, trunks, endpoints and licensing.
- Product website: https://www.3cx.com/
- Source review: 2026-11-19; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry excludes the Hosted by 3CX service. External SIP trunks, carriers, calling charges and endpoint hardware remain separate. Review provider sizing and media-network requirements before deployment. The AWS AMI is vendor-published package 20.0.10.1785 on Debian 12, with its 3CX licence billed outside AWS Marketplace. 3CX's November 2026 security-hotfix log updates V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest update through the Admin Console, restart as directed and verify the deployed package set; do not treat the application build number alone as proof that OS hotfixes are current.

3CX is proprietary commercial software licensed by edition and capacity; cloud hosting and telecom services are separate.

3CX runs as a persistent PBX and communications application on a customer-managed cloud VM.


### Category fit

- collaboration: Provides business voice, video, chat, web meetings and PBX collaboration in a customer-operated deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-aws/ (checked 2026-11-18). Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-azure/ (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-google-cloud/ (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/manual/install/ (checked 2026-11-18). 


### Cloud deployment evidence

- 3CX in the customer's AWS account (aws): https://www.3cx.com/docs/hosted-pbx-aws/
  3CX documents provisioning the PBX in a customer AWS account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's Azure account (azure): https://www.3cx.com/docs/hosted-pbx-azure/
  3CX documents provisioning the PBX in a customer Azure account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's Google Cloud account (gcp): https://www.3cx.com/docs/hosted-pbx-google-cloud/
  3CX documents provisioning the PBX in a customer Google Cloud account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's DigitalOcean account (digitalocean): https://www.3cx.com/docs/manual/install/
  The current private-cloud install guide identifies DigitalOcean as a supported customer-account deployment target.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX-published AWS self-hosted AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm
  The vendor publishes the full PBX as a Debian 12 x86 AMI in the customer AWS account. Software licensing is external to AWS Marketplace; telecom and infrastructure charges are separate.
  Source type: marketplace-offer; reviewed: 2026-11-18; vendor support: not-assessed. Versions: 20.0.10.1785.


### Sources

- Install 3CX in a private cloud: https://www.3cx.com/docs/manual/install/

- Deploy 3CX on AWS: https://www.3cx.com/docs/hosted-pbx-aws/

- Deploy 3CX on Azure: https://www.3cx.com/docs/hosted-pbx-azure/

- Deploy 3CX on Google Cloud: https://www.3cx.com/docs/hosted-pbx-google-cloud/

- 3CX pricing: https://www.3cx.com/ordering/pricing/

- Exact vendor AWS AMI and external licence billing: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm

- 3CX PBX security updates change log: https://www.3cx.com/blog/change-log/pbx-security-updates/

### Licensing sources

- https://www.3cx.com/ordering/pricing/

### Infrastructure sources

- https://www.3cx.com/docs/manual/install/


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 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: Documented. 3CX publishes prodview-f5qwwdeeq4uvm as an x86 AWS AMI, package 20.0.10.1785 on Debian 12. Its pricing explicitly requires an external 3CX billing/licence relationship; the software licence is purchased outside AWS Marketplace. AWS infrastructure charges remain separate. This is the customer-operated PBX, not Hosted by 3CX. Scope: 3CX AWS self-hosted AMI 20.0.10.1785, externally licensed. Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (reviewed 2026-11-18). Supporting source: Vendor AWS Marketplace installation guide — https://www.3cx.com/docs/pbx-amazon-aws-marketplace/. Offer prodview-f5qwwdeeq4uvm: 3CX; Amazon Machine Image (AMI), x86; package 20.0.10.1785; https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed 3CX AMI offer explicitly requires buying the software licence outside AWS Marketplace. That externally billed licence is not a software charge on the AWS Marketplace invoice for this offer. This answers the licence-billing route only; eligible EC2/EBS spend or a separately negotiated private offer still requires the buyer’s AWS agreement and seller order terms. Scope: Externally billed software licence for the exact reviewed public 3CX AMI offer; not all provider spend or future private offers. Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (reviewed 2026-11-18). Supporting source: AWS BYOL pricing boundary — https://docs.aws.amazon.com/marketplace/latest/userguide/BYOL-pricing.html. Supporting source: Commitment qualification remains product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Edition-dependent. The Microsoft 365 integration documents SSO to the 3CX web client and one-way scheduled user synchronization. It requires a supported Microsoft 365 Exchange plan and configured application permissions. This does not establish SCIM or every client’s login behavior. Deleted/disabled M365 users remain in 3CX until manually removed; SSO is not a substitute for offboarding. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/microsoft-365/ (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The M365 guide documents nightly one-way sync, not a SCIM endpoint. A user deleted or disabled in M365 remains in 3CX and must be removed manually; deleting only in 3CX causes recreation at the next sync while the M365 account remains. This confirms a manual offboarding requirement, but does not establish SCIM operations or active-session/extension revocation through a SCIM integration. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/microsoft-365/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. 3CX describes security reviews with Mandiant, ReversingLabs, Coverity and HackerOne. This establishes a vendor security-testing statement, not a current independent attestation whose scope covers the buyer’s PBX, recordings, carrier/transcription services and operations. Obtain the relevant report, audit period, findings/remediation and deployment boundary. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/pbx/security/ (reviewed 2026-11-18).

- Security controls: Documented. The firewall guide specifies SIP/RTP, tunnel and HTTPS connectivity and requires uninspected outbound HTTPS for activation. Configure the required ports and TLS/FQDN correctly; external SIP trunks, push and meeting services create separate dependencies. M365 sync does not remove users deleted/disabled at the IdP; explicitly remove them in 3CX and review sessions, SIP/extension credentials and retained data. Current review: The November 2026 V20 SP9/SP10 security-hotfix log refreshes Linux packages including nginx, kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest Admin Console update and verify the installed package set. Scope: Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing. Source: https://www.3cx.com/blog/change-log/pbx-security-updates/ (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://www.3cx.com/docs/manual/firewall-router-configuration/. Supporting source: Microsoft 365 SSO configuration — https://www.3cx.com/docs/manual/microsoft-365/.

- Air-gapped operation: Explicitly unsupported. The standard documented self-hosted configuration requires outbound HTTPS to activate.3cx.com for licence activation and other external services for updates and selected functions. It is not a fully disconnected deployment path; a separate offline exception was not established. Scope: 3CX standard documented self-hosted activation and operation. Source: https://www.3cx.com/docs/manual/firewall-router-configuration/ (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The current installation guide provisions a private-cloud PBX in the customer’s chosen AWS, Azure, Google Cloud or DigitalOcean account. This is a vendor deployment workflow, not a reviewed source-controlled Terraform or CloudFormation artifact. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/install/ (reviewed 2026-11-18).

- Minimum footprint / sizing: Documented. The current small PBX table lists 2 vCPU/4 GB RAM and 80 GB SSD, with larger tiers and extra recording/log capacity. Its cloud table places up to 250 extensions in the large tier, with AWS t3.xlarge as an example. These are extension/call-capacity guidelines; HA, simultaneous calls and a 1 TB recording policy still need a design. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/ (reviewed 2026-11-18).

- License pricing: Documented. 3CX publishes annual system licences by edition and simultaneous-call capacity, with extension limits and feature differences. Obtain the selected self-hosted tier; a count of internal users alone does not price licences, trunks or calling charges. The reviewed AWS offer bills its software licence outside AWS Marketplace. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/ordering/pricing/ (reviewed 2026-11-18). Supporting source: External licence billing in the exact AWS offer — https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.

- Operating cost estimate: Sources checked — unresolved. Specify concurrent calls, extensions, edition, SIP trunks/minutes, recording/transcription volume, retention and HA/failover requirements. The t3.xlarge sizing example does not include carrier service, a second server, recording backup or external AI services. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. 3CX announced V20 Update 10 on November 11, 2026; the V20 change log identifies production build 20.0.10.1785. Exclude release candidates and separately versioned mobile clients from this PBX snapshot. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/blog/releases/ai-agents-mcp-local-ai/ (reviewed 2026-11-18). Supporting source: Production PBX build number — https://www.3cx.com/blog/change-log/phone-system-change-log-v20/. Supporting source: AWS AMI package 20.0.10.1785 — https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.




### Security and lifecycle reviews

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

- 3CX V20 November 2026 Linux security hotfix (security-advisory): 3CX refreshed V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync. Scope: Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing. Conditions: The exact installed application and operating-system package set determines exposure. Action: Apply the latest Admin Console update, restart as directed and verify installed package versions. Source: https://www.3cx.com/blog/change-log/pbx-security-updates/; reviewed 2026-11-19.




## Airbyte Self-Managed

Self-managed data movement and ELT platform with customer-operated connectors and job execution.

- Listing: https://launchinyourcloud.com/directory/airbyte/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0 for the Airbyte platform; connector and component licenses vary. Enterprise and Cloud offerings use separate commercial terms.
- Licensing model: source-available
- Installation: Official Helm chart for current Kubernetes deployments; cloud VMs are also documented. DigitalOcean separately lists a legacy 1-Click Droplet image.
- Architecture: Customer-operated platform services, connector jobs, metadata database and object storage
- Operations: Customer manages Kubernetes or VM capacity, the metadata database, object storage, secrets, connector images, network access, backups and upgrades.
- Product website: https://airbyte.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

This entry covers Airbyte Self-Managed, not Airbyte Cloud or the hybrid offering. Connector jobs communicate with configured external sources and destinations. Elastic License 2.0 permits internal self-hosting but restricts offering the software as a managed service and bypassing license-key functionality. DigitalOcean lists a separate legacy v0.30.25 Marketplace image on Ubuntu 20.04. That evidence does not establish current Helm-release compatibility or current vendor support; verify image availability, upgrade paths and support for the selected release.

The Airbyte platform uses Elastic License 2.0, which permits self-hosting and source modification but restricts managed-service use and protected license functionality. Connectors and development tooling can carry different licenses; inspect the selected component and release. Commercial Enterprise and Cloud terms are separate.

The documented deployment uses long-lived Kubernetes platform services and connector job pods, with a metadata database and object storage. Managed cloud databases or object stores do not make the application runtime serverless.


### Category fit

- data-analytics: Moves data between APIs, databases, files, warehouses and lakes using customer-operated connectors and synchronization jobs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

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


### Cloud deployment evidence

- Airbyte self-managed deployment on named cloud providers (aws, azure, gcp): https://docs.airbyte.com/platform/deploying-airbyte
  Airbyte documents its Helm deployment for Kubernetes and explicitly names AWS, Google Cloud and Azure, including EC2/EKS and GCE/GKE examples. This is the self-managed application path; configure provider policies, external storage, secrets and production ingress separately.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Airbyte-published v0.30.25 DigitalOcean Droplet image (digitalocean): https://marketplace.digitalocean.com/apps/airbyte
  DigitalOcean lists an Airbyte-published 1-Click Droplet image, version 0.30.25 on Ubuntu 20.04, and provides creation instructions for the customer account. This is legacy, version-specific application deployment evidence, not verification of the current Helm-based release or current vendor support. Confirm image availability, compatibility, upgrade paths and support before selecting this route.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- Airbyte platform and self-managed plans: https://docs.airbyte.com/platform

- Self-managed Kubernetes and cloud deployment: https://docs.airbyte.com/platform/deploying-airbyte

- Elastic License 2.0 FAQ: https://github.com/airbytehq/airbyte/blob/master/docs/community/licenses/license-faq.md

- Airbyte platform Elastic License 2.0: https://github.com/airbytehq/airbyte/blob/master/LICENSE

- Legacy Airbyte v0.30.25 DigitalOcean Marketplace image: https://marketplace.digitalocean.com/apps/airbyte

### Licensing sources

- https://github.com/airbytehq/airbyte/blob/master/LICENSE

- https://github.com/airbytehq/airbyte/blob/master/docs/community/licenses/license-faq.md

### Infrastructure sources

- https://docs.airbyte.com/platform/deploying-airbyte

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


### Buyer diligence


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

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


- Marketplace delivery: Documented. The DigitalOcean 1-Click page still identifies Airbyte 0.30.25 on Ubuntu 20.04. This is legacy package evidence, not confirmation of a current release, current support or suitability for a new production deployment. Scope: Legacy DigitalOcean image; current upstream deployment requires separate validation. Source: https://marketplace.digitalocean.com/apps/airbyte (reviewed 2026-11-14). Offer airbyte: Airbyte; Droplet 1-Click; package 0.30.25; https://marketplace.digitalocean.com/apps/airbyte.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The vendor documents OIDC login for self-managed instances, but the current plan comparison emphasizes Cloud/Enterprise Flex while Core quickstart uses local credentials. The reviewed pages do not unambiguously establish federation entitlement for the selected Core distribution; obtain edition/version confirmation. Scope: Self-managed OIDC workflow; Core edition entitlement unresolved. Source: https://docs.airbyte.com/platform/access-management/sso (reviewed 2026-11-20). Supporting source: Current self-managed and hybrid plan scope — https://docs.airbyte.com/platform. Supporting source: Core quickstart authentication — https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Airbyte publishes abctl to install a local Kubernetes-based Core instance and a Helm deployment path for customer infrastructure. Local abctl creates its own cluster using Docker; production requires separately configured ingress, storage, secrets and chart/application compatibility. Scope: Official Core installation tooling; local cluster is not an HA architecture. Source: https://docs.airbyte.com/platform/deploying-airbyte/abctl (reviewed 2026-11-20). Deployment artifact: https://github.com/airbytehq/abctl. Artifact reference: Choose an abctl release and compatible chart version.

- Minimum footprint / sizing: Documented. The Core quickstart recommends at least 4 CPUs and 8 GB RAM; low-resource mode can run with 2 CPUs and 8 GB but disables Connector Builder. This is a local deployment profile. Connector concurrency, storage and production/HA components require separate sizing. Scope: Airbyte Core local installation; production HA excluded. Source: https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart (reviewed 2026-11-20).

- License pricing: Documented. The platform is under Elastic License 2.0, including restrictions on offering a substantial hosted/managed service and bypassing licence keys. Connector licences vary. Enterprise features, support and alternative commercial rights require separate terms; this does not price infrastructure. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/airbytehq/airbyte/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Apache Airflow

Workflow orchestration platform for scheduling and monitoring data pipelines and other task workflows authored in Python or supported non-Python formats.

- Listing: https://launchinyourcloud.com/directory/apache-airflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Airflow; dependencies, provider integrations and external services have their own terms.
- Licensing model: open-source
- Installation: Install the Python distribution or official container images; the Apache Airflow Helm chart deploys the platform to a customer-operated Kubernetes cluster.
- Architecture: Scheduler, Dag processor, API server and metadata database, with executor-dependent workers and optional triggerers
- Operations: Customer operates Airflow services, database, worker capacity, Dag code, credentials, authorization, logs, backups and version upgrades.
- Product website: https://airflow.apache.org/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The Helm chart is a deployment mechanism, not a managed control plane. Providers and Dag tasks can call external databases, APIs, compute or model services. Review each integration and executor before treating a complete pipeline as contained in the account. Managed Airflow services are separate offerings. Airflow 3.4’s Dag Importer and language-SDK support is experimental; non-Python Dag authoring requires the applicable language runtime and coordinator on Dag processors and workers.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

Airflow components are Python services that run on servers or Kubernetes pods with persistent metadata storage. Worker layout depends on the selected executor; a serverless task executor does not make the Airflow control plane serverless.


### Category fit

- workflow-orchestration: Directed workflows with task dependencies, scheduling, execution and monitoring. Python remains the traditional authoring language; Airflow 3.4 adds experimental whole-Dag authoring in TypeScript, Java, Go and YAML. Executor and provider configuration determine where work runs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/logging/s3-task-handler.html (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/catalog/airflow/ (checked 2026-11-12). 


### Cloud deployment evidence

- Airflow Helm deployment on EKS with IAM roles (aws): https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/logging/s3-task-handler.html
  The current upstream Amazon provider guide explicitly configures Airflow Helm webserver/worker pods on EKS, including their service account, and links a self-managed Terraform deployment example. S3 logging is optional infrastructure configuration; this is not Amazon Managed Workflows for Apache Airflow. Restrict the example IAM permissions for production.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Apache Airflow full application on DigitalOcean (digitalocean): https://docs.digitalocean.com/products/marketplace/catalog/airflow/
  The provider catalog provisions Airflow on a customer Ubuntu 24.04 Droplet, with the application UI, local PostgreSQL and Redis, or customer-managed database services and Celery workers. This is full application hosting, not a database connector. The catalog does not identify the exact Airflow package release; verify the selected image, compatible dependencies, TLS, access controls, backups and upgrades.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official announcement feed records Airflow 3.4.0 released on November 6, 2026. Stable 1.0.0 TypeScript, Java and Go SDKs followed on November 13, confirming maintained non-Python Dag authoring. The project publishes a named Adyen case study describing production orchestration across more than 20 teams and maintains a broad self-reported organization list; these establish adoption beyond repository popularity.

Reviewed 2026-11-14.

- Current release announcements: https://airflow.apache.org/announcements/

- Adyen production case study: https://airflow.apache.org/use-cases/adyen/

- Project-maintained organization list: https://github.com/apache/airflow/blob/main/INTHEWILD.md

- Airflow 3.4 whole-Dag authoring beyond Python: https://airflow.apache.org/blog/airflow-3.4.0/

- Stable TypeScript SDK 1.0.0: https://github.com/apache/airflow/releases/tag/ts-sdk/1.0.0

- Stable Java SDK 1.0.0: https://github.com/apache/airflow/releases/tag/java-sdk/1.0.0

- Stable Go SDK 1.0.0: https://github.com/apache/airflow/releases/tag/go-sdk/v1.0.0

### Sources

- What Apache Airflow does: https://airflow.apache.org/docs/apache-airflow/stable/

- Component architecture and deployment: https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/overview.html

- Official Apache Airflow Helm chart: https://airflow.apache.org/docs/helm-chart/stable/index.html

- Upstream Apache-2.0 and subcomponent licenses: https://github.com/apache/airflow/blob/main/LICENSE

- DigitalOcean Airflow application deployment: https://docs.digitalocean.com/products/marketplace/catalog/airflow/

- Airflow 3.4 whole-Dag authoring beyond Python: https://airflow.apache.org/blog/airflow-3.4.0/

- Airflow TypeScript SDK 1.0.0: https://github.com/apache/airflow/releases/tag/ts-sdk/1.0.0

- Airflow Java SDK 1.0.0: https://github.com/apache/airflow/releases/tag/java-sdk/1.0.0

- Airflow Go SDK 1.0.0: https://github.com/apache/airflow/releases/tag/go-sdk/v1.0.0

### Licensing sources

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

### Infrastructure sources

- https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/overview.html

- https://airflow.apache.org/docs/helm-chart/stable/index.html


### 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. DigitalOcean provides an Airflow Droplet 1-Click package and separately links a Terraform Blueprint for production. The reviewed image is 3.3.2, not the upstream 3.4 release snapshot; a 4 GB API example is not a production sizing guarantee. Scope: DigitalOcean-listed package; Apache commercial support is not established. Source: https://docs.digitalocean.com/products/marketplace/catalog/airflow/ (reviewed 2026-11-14). Offer airflow: Not identified on the reviewed marketplace page; Droplet 1-Click; package 3.3.2; https://marketplace.digitalocean.com/apps/airflow.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The FAB Auth Manager provider documents OAuth login with named IdPs and custom provider configuration. Enable the compatible FAB auth manager, configure provider credentials/callbacks and user/role mapping; the default authentication manager and API/execution-token paths differ. This is an optional configured integration, not automatic SSO in every Airflow image. Scope: Airflow web-user authentication through the FAB provider; verify Airflow/provider version compatibility. Source: https://airflow.apache.org/docs/apache-airflow-providers-fab/stable/auth-manager/webserver-authentication.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. Apache publishes an Airflow Helm chart with configurable executors and supporting services. Database migrations, chart/application compatibility, secrets and persistent logs require explicit planning. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://airflow.apache.org/docs/helm-chart/stable/index.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The upstream prerequisites recommend at least 4 GB memory but explicitly make capacity deployment-dependent. Scheduler/API, metadata database, triggerer and executor/workers have different resource needs. Task concurrency, DAG parsing, logs, database I/O and replicas must be sized separately; the 4 GB floor is not an HA workload allocation. Scope: Current application installation floor; full service/worker and HA capacity is workload-specific. Source: https://airflow.apache.org/docs/apache-airflow/stable/installation/prerequisites.html (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses Apache License 2.0 with separately identified bundled-component notices. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote. Scope: Apache Airflow 3.4.0 application; not a provider-hosted service; software terms only, excluding infrastructure and operations. Source: https://github.com/apache/airflow/blob/3.4.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







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







## Appsmith Self-Hosted

Build internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.

- Listing: https://launchinyourcloud.com/directory/appsmith/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache-2.0 Community core; commercial edition and plan-dependent features
- Licensing model: open-source
- Installation: Docker Compose or Kubernetes; documented cloud VM/managed-container installation guides
- Architecture: Customer-operated application and supporting databases/cache; vendor licensing/template endpoint
- Operations: Customer manages deployment, persistent databases, backups, networking and upgrades; confirm edition-specific vendor connectivity.
- Product website: https://www.appsmith.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

Community and commercial images differ. Documentation requires outbound HTTPS to cs.appsmith.com for self-hosted license/template services and describes separate air-gapped arrangements. Official setup guides name AWS, Azure and Google Cloud. Fargate and Cloud Run are long-running container hosting options, not evidence that the entire stack is function-based. Appsmith v2.7.0 fixes app and datasource authorization issues, extends restricted-host enforcement to S3-compatible and DynamoDB sources, and updates vulnerable dependencies.

The broad self-hosted listing spans Apache-2.0 Community code and commercially licensed Enterprise functionality requiring an enterprise key. Match the selected image and plan to these terms.

Classified as servers under this directory convention: the application is a long-running container/service. Official Fargate/Cloud Run paths reduce host management but retain application, database and persistence operations. For Helm upgrades, partial probe overrides now inherit new 10-second period and 5-second timeout defaults; invalid probe values fail installation or upgrade. Review custom probe settings before rollout.


Cloud evidence scope: Documented customer-operated deployment guides for AWS, Azure and Google Cloud

### Category fit

- internal-tools: Low-code development of dashboards, admin panels and internal apps connected to databases/APIs; not a turnkey business application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appsmith.com/getting-started/setup/installation-guides (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appsmith.com/getting-started/setup/installation-guides (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appsmith.com/getting-started/setup/installation-guides (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Appsmith provider-specific installation index (aws, azure, gcp): https://docs.appsmith.com/getting-started/setup/installation-guides
  The vendor documents AWS AMI and ECS, Azure Container Instances and Google Cloud Run installation of the application. These are self-hosted installations, with edition-specific licensing and vendor connectivity requirements described separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Appsmith on a customer DigitalOcean Droplet (digitalocean): https://docs.appsmith.com/getting-started/setup/installation-guides/digitalocean
  The vendor walks through choosing the Appsmith Marketplace image, creating a Droplet in the customer account and registering its application administrator. Free and licensed features have separate entitlements; configure domain, TLS, email and recovery for production.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted Docker installation: https://docs.appsmith.com/getting-started/setup/installation-guides/docker

- Deployment architecture and vendor connectivity: https://docs.appsmith.com/getting-started/setup/deployment-architecture

- Provider-specific installation guides: https://docs.appsmith.com/getting-started/setup/installation-guides

- Community project and license: https://github.com/appsmithorg/appsmith

- Licensing and edition terms: https://www.appsmith.com/terms-and-conditions

- Appsmith on a customer DigitalOcean Droplet: https://docs.appsmith.com/getting-started/setup/installation-guides/digitalocean

- Appsmith v2.7.0 security and upgrade notes: https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0

### Licensing sources

- https://www.appsmith.com/terms-and-conditions

- https://github.com/appsmithorg/appsmith

- https://docs.appsmith.com/getting-started/setup/installation-guides/docker

### Infrastructure sources

- https://docs.appsmith.com/getting-started/setup/installation-guides/docker

- https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The self-hosting authentication guides document SAML and OIDC SSO as Enterprise features. SAML can migrate from the bundled Keycloak broker to native server handling starting in v2.7; configure the provider and migration for the selected release. Scope: Self-hosted Enterprise user login; Google/GitHub login and enterprise federation are different options. Source: https://docs.appsmith.com/getting-started/setup/instance-configuration/authentication/security-assertion-markup-language-saml (reviewed 2026-11-20). Supporting source: Enterprise OIDC SSO — https://docs.appsmith.com/getting-started/setup/instance-configuration/authentication/openid-connect-oidc.

- SCIM provisioning: Edition-dependent. Self-hosted Enterprise documents SCIM v2 user and group provisioning. The identity provider must reach the instance SCIM endpoint over HTTPS. Scope: Self-hosted Enterprise; identity-provider and network requirements apply. Source: https://docs.appsmith.com/advanced-concepts/user-provisioning-group-sync (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Edition-dependent. A separate Airgapped Edition is obtained through sales. Offline operation limits templates, SaaS integrations and third-party libraries; disabling telemetry alone is not air-gapped deployment. Scope: Separately arranged Airgapped Edition, not every Appsmith installation. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/air-gapped (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The official Docker guide supplies run and Compose configurations using an Appsmith image and persistent /appsmith-stacks storage. Choose the Community or commercial image deliberately, pin the intended release and configure the host, secrets, HTTPS and backups. Scope: Official all-in-one installation example; choose the edition and a compatible pinned container release. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/docker (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. The all-in-one Docker installation guidance calls for at least 8 GB host RAM because supporting services run inside the container. Externalized services require a different capacity plan. Scope: All-in-one Docker host; not a universal per-application requirement. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/docker (reviewed 2026-11-14).

- License pricing: Documented. The v2.7.0 core is Apache-2.0. The vendor distinguishes free Community from paid Business and Enterprise plans; SAML/OIDC, provisioning and air-gapped add-ons have separate commercial entitlements. Confirm self-hosted feature, user and support terms with the vendor. Scope: Versioned core versus commercially licensed features; displayed Cloud limits and prices are not applied as a self-hosted quote. Source: https://github.com/appsmithorg/appsmith/blob/v2.7.0/LICENSE (reviewed 2026-11-20). Supporting source: Edition and feature pricing — https://www.appsmith.com/pricing.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The Airgapped Edition documentation specifies quarterly packaged updates transferred manually into the isolated environment. This is separate from the normal upstream release stream. Scope: Airgapped Edition update policy; not the cadence of all Appsmith editions. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/air-gapped (reviewed 2026-11-14).




### Security and lifecycle reviews

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

- Appsmith 2.7.0 access and datasource hardening (security-advisory): The release adds missing app-access checks and extends restricted-host rules to S3-compatible and DynamoDB datasources. Scope: Upstream Appsmith 2.7.0 release; Airgapped Edition packaging follows its separate update policy. Conditions: Applicability depends on custom JS-library access, fork permissions and configured datasource endpoints; no complete affected range is asserted. Action: Review the security changes and Helm probe defaults before applying a compatible update. Source: https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0; reviewed 2026-11-17.




## Appwrite Self-Hosted

Self-hosted backend services for authentication, databases, storage, functions and messaging.

- Listing: https://launchinyourcloud.com/directory/appwrite/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause core; enterprise services and feature terms should be confirmed separately
- Licensing model: open-source
- Installation: Docker installer or official Kubernetes Helm chart
- Architecture: Customer-operated container services, database and storage
- Operations: Customer configures the environment and handles software updates, scaling, security and backups.
- Product website: https://appwrite.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosting rather than Appwrite Cloud. Official deployment guides document EC2/EKS, Azure VMs/AKS and Google Compute Engine/GKE. Configure external email, SMS and other integrations deliberately; enterprise support and compliance offerings have separate terms. Appwrite 2.7.3 includes the 2.7.2 security fixes across authentication, abuse limits, storage, realtime, messaging, functions, VCS, proxy handling, and vulnerable base-image packages. It additionally rebuilds appwrite/base and openruntimes/executor to clear remaining image vulnerability findings. Upgrading from 2.7.2 requires no schema changes; use the normal upgrade command and migration step.

This classification covers the public Appwrite self-hosted distribution under BSD-3-Clause. Appwrite separately markets a premium enterprise self-hosted edition; its additional tooling and terms are outside this classification and should not be assumed to inherit the public core license.

Appwrite runs as persistent Docker services or an official Helm deployment on Kubernetes. The function feature does not make the complete backend a serverless deployment.


Cloud evidence scope: Official guides document AWS, Azure and Google Cloud customer-infrastructure deployments.

### Category fit

- backend-platforms: Application backend APIs for authentication, databases, storage, functions, messaging and realtime, deployed on customer infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://appwrite.io/docs/advanced/self-hosting/platforms/aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://appwrite.io/docs/advanced/self-hosting/platforms/azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://appwrite.io/docs/advanced/self-hosting/platforms/google-cloud (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://appwrite.io/docs/advanced/self-hosting/platforms/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Appwrite self-hosting on AWS (aws): https://appwrite.io/docs/advanced/self-hosting/platforms/aws
  The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Appwrite self-hosting on Azure (azure): https://appwrite.io/docs/advanced/self-hosting/platforms/azure
  The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Appwrite self-hosting on google-cloud (gcp): https://appwrite.io/docs/advanced/self-hosting/platforms/google-cloud
  The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Appwrite self-hosting on digitalocean (digitalocean): https://appwrite.io/docs/advanced/self-hosting/platforms/digitalocean
  The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Backend capabilities: https://appwrite.io/docs

- Self-hosting responsibilities: https://appwrite.io/docs/advanced/self-hosting

- Docker installation: https://appwrite.io/docs/advanced/self-hosting/installation

- AWS deployment: https://appwrite.io/docs/advanced/self-hosting/platforms/aws

- Azure deployment: https://appwrite.io/docs/advanced/self-hosting/platforms/azure

- Google Cloud deployment: https://appwrite.io/docs/advanced/self-hosting/platforms/google-cloud

- Core license: https://raw.githubusercontent.com/appwrite/appwrite/main/LICENSE

- Licensing and edition terms: https://appwrite.io/enterprise

- Infrastructure deployment documentation: https://appwrite.io/docs/advanced/self-hosting/platforms/kubernetes

- Appwrite self-hosting on digitalocean: https://appwrite.io/docs/advanced/self-hosting/platforms/digitalocean

- Appwrite 2.7.2 security patch: https://github.com/appwrite/appwrite/releases/tag/2.7.2

- Appwrite 2.7.3 image security update: https://github.com/appwrite/appwrite/releases/tag/2.7.3

### Licensing sources

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

- https://appwrite.io/docs/advanced/self-hosting

- https://appwrite.io/enterprise

### Infrastructure sources

- https://appwrite.io/docs/advanced/self-hosting/installation

- https://appwrite.io/docs/advanced/self-hosting/platforms/kubernetes


### 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. Appwrite documents OAuth2 identity providers for users of applications you build. Separately, the vendor advertises centralized Console SSO in its premium Enterprise platform, available as self-hosted or Cloud. Do not treat core application-user OAuth as administrator SAML: confirm the chosen self-hosted Enterprise package, IdP/protocol and organization policy for Console SSO. Scope: Application-user OAuth versus premium self-hosted Console identity; product/edition boundaries apply. Source: https://appwrite.io/enterprise (reviewed 2026-11-20). Supporting source: Application-user OAuth2 flow and provider setup — https://appwrite.io/docs/products/auth/oauth2.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installer generates a Compose stack and environment/configuration files. Replace encryption/executor secrets, retain all required files and select the worker/database configuration; a Kubernetes Helm option is separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://appwrite.io/docs/advanced/self-hosting/installation (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current installation guide requires at least 2 CPU cores, 4 GB RAM and 2 GB swap on a Docker-capable host. Models, functions, worker topology and workload can raise requirements. Scope: Appwrite installation baseline; not every production workload. Source: https://appwrite.io/docs/advanced/self-hosting/installation (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream application uses BSD 3-Clause licence. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote. Scope: Appwrite 2.7.3 upstream core; not Cloud or Enterprise entitlements; software terms only, excluding infrastructure and operations. Source: https://github.com/appwrite/appwrite/blob/2.7.3/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is 2.7.3, published 2026-11-17. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream appwrite/appwrite release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/appwrite/appwrite/releases/tag/2.7.3 (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Appwrite container security maintenance (security-advisory): Appwrite 2.7.3 refreshes its base and executor images after the 2.7.2 security update. Scope: Self-hosted Appwrite 2.7.3, appwrite/base 2.2.12 and openruntimes/executor 1.3.5; not Appwrite Cloud. Conditions: Container dependency findings depend on the actual deployed images. The release is not proof that every image or integration is vulnerability-free. Action: Back up and use the normal upgrade/migrate procedure; the release says moving from 2.7.2 introduces no schema changes. Source: https://github.com/appwrite/appwrite/releases/tag/2.7.3; reviewed 2026-11-17.




## Baserow Self-Hosted

Self-hosted no-code database for organizing, relating and collaborating on business data.

- Listing: https://launchinyourcloud.com/directory/baserow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, railway, render, heroku
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT-licensed core with paid premium features and subscription terms
- Licensing model: open-source
- Installation: Docker, Docker Compose or official Helm chart
- Architecture: Customer-operated application services with PostgreSQL, Redis and file storage
- Operations: Customer operates the application, database and storage, applies updates and configures backups.
- Product website: https://baserow.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Self-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.

Baserow Open Source Edition is MIT-licensed. The repository separately licenses Premium and Enterprise feature directories, whose production use requires the corresponding paid subscription; publicly visible source does not make those directories open source.

The official guides deploy persistent application containers with PostgreSQL and Redis, either on a server or orchestrated container infrastructure. Fargate is an available hosting path, but the application remains a persistent service.


Cloud evidence scope: Official documentation establishes AWS deployments; other provider compatibility is not inferred.

### Category fit

- no-code-databases: No-code relational tables, views and APIs for collaborative business data; premium capabilities require the applicable license.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-aws (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation/install-with-docker (checked 2026-11-12). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-digital-ocean (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-railway (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-render (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-heroku (checked 2026-11-12). 


### Cloud deployment evidence

- Baserow AWS installation options (aws): https://baserow.io/docs/installation%2Finstall-on-aws
  The vendor documents EC2, ECS/Fargate and EKS application deployment options in the customer AWS account. Select the documented image, persistent database and Redis configuration appropriate to the topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Docker image compatibility with Google Cloud Run (gcp): https://baserow.io/docs/installation/install-with-docker
  The upstream guide explicitly designs the all-in-one application image for simple container services such as Google Cloud Run. Use external PostgreSQL, Redis and durable file storage for a stateless runtime; this is an application-hosting compatibility statement, not evidence based only on a Google storage adapter.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow on DigitalOcean App Platform (digitalocean): https://baserow.io/docs/installation%2Finstall-on-digital-ocean
  The vendor guide deploys the Baserow application container, managed PostgreSQL and Redis, and Spaces storage in the customer DigitalOcean account, with application URL and scaling configuration. The example image tag is version-specific; choose and test the intended supported release.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Railway installation (railway): https://baserow.io/docs/installation%2Finstall-on-railway
  The upstream guide creates a Railway project from the Baserow template and configures the deployed application. The guide requires enough memory and a paid plan rather than assuming the free trial is adequate. Railway operates the underlying infrastructure; the customer controls the application project.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Render application template (render): https://baserow.io/docs/installation%2Finstall-on-render
  The upstream guide provides a full application template using paid Render compute and PostgreSQL plans. Its published plan prices and repository branch examples can age; verify the current template, compatible release, resources and data persistence rather than assuming a free production tier.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Heroku application template (heroku): https://baserow.io/docs/installation%2Finstall-on-heroku
  The upstream guide documents a beta deployment template for the Baserow application and supporting Heroku services, with configuration and scaling instructions. It requires paid resources; review the current template, image, database and file-storage settings before production use.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Product and licensing FAQ: https://baserow.io/faq

- Docker installation: https://baserow.io/docs/installation/install-with-docker

- AWS installation paths: https://baserow.io/docs/installation%2Finstall-on-aws

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/LICENSE

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/premium/LICENSE

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/enterprise/LICENSE

- Baserow on DigitalOcean App Platform: https://baserow.io/docs/installation%2Finstall-on-digital-ocean

- Baserow Railway installation: https://baserow.io/docs/installation%2Finstall-on-railway

- Baserow Render application template: https://baserow.io/docs/installation%2Finstall-on-render

- Baserow Heroku application template: https://baserow.io/docs/installation%2Finstall-on-heroku

### Licensing sources

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

- https://raw.githubusercontent.com/baserow/baserow/develop/premium/LICENSE

- https://raw.githubusercontent.com/baserow/baserow/develop/enterprise/LICENSE

### Infrastructure sources

- https://baserow.io/docs/installation/install-with-docker

- https://baserow.io/docs/installation%2Finstall-on-aws


### 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. Instance administrators can configure SAML and OAuth/OIDC providers on Advanced or Enterprise with an activated license. This is not established for the free self-hosted edition. Scope: Self-hosted Advanced/Enterprise authentication. Source: https://baserow.io/user-docs/enable-single-sign-on-sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The all-in-one Docker guide documents persistence, HTTPS and external database/cache configuration. It recommends an external PostgreSQL service for production and describes database-version upgrade handling. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://baserow.io/docs/installation/install-with-docker (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The official DigitalOcean App Platform guide specifies at least one application container with 1 vCPU and 2 GB RAM, plus separately provisioned managed PostgreSQL, Redis and Spaces storage. Its smaller database example is not the application or complete-host requirement. Scope: Provider-specific stateless application baseline, not a universal all-in-one minimum or HA design. Source: https://baserow.io/docs/installation/install-on-digital-ocean (reviewed 2026-11-20).

- License pricing: Documented. The 2.4.3 Open Source Edition is MIT-licensed, with separate Premium and Enterprise directories. Production use of either paid edition requires the corresponding subscription for the correct number of users and applicable subscription terms; do not apply Cloud prices to a self-hosted contract. Scope: Versioned open-source versus paid-edition software rights; excludes hosting and support. Source: https://github.com/baserow/baserow/blob/2.4.3/LICENSE (reviewed 2026-11-20). Supporting source: Premium edition licence — https://github.com/baserow/baserow/blob/2.4.3/premium/LICENSE. Supporting source: Enterprise edition licence — https://github.com/baserow/baserow/blob/2.4.3/enterprise/LICENSE.

- Operating cost estimate: Not researched.

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







## BigBlueButton

Self-hosted conferencing and virtual classroom platform.

- Listing: https://launchinyourcloud.com/directory/bigbluebutton/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, hetzner, scaleway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Official bbb-install.sh from the maintained 4.0 installer branch on supported Ubuntu
- Architecture: BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure.
- 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://bigbluebutton.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee. The maintained 4.0 installer also explicitly documents Scaleway and Azure behind-NAT deployments.

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

BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted conferencing and virtual classroom platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- scaleway: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 (aws, azure, gcp, digitalocean, hetzner, scaleway): https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md
  BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes antobinary, ritzalam, ramonlsouza, 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/bigbluebutton/bigbluebutton/graphs/contributors

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

### Sources

- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md

- Official Install Docs: https://docs.bigbluebutton.org/administration/install/

- bbb-install README: https://raw.githubusercontent.com/bigbluebutton/bbb-install/master/README.md

- LGPL-3.0 LICENSE: https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE

- Releases v4.0.2: https://github.com/bigbluebutton/bigbluebutton/releases

### Licensing sources

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

### Infrastructure sources

- https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md


### 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 optional Greenlight v3 front end supports external authentication through OpenID Connect and can connect to an external identity server. This is a Greenlight user-login capability, not the conferencing engine shared-secret API or an assurance about every LMS/front-end integration. Scope: BigBlueButton with the separately configured Greenlight v3 front end. Source: https://docs.bigbluebutton.org/greenlight/v3/install/ (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 4.0 installation instructions link the maintained bbb-install.sh branch for Ubuntu 24.04. The older master README describes 2.6 and must not be used as the 4.0 installer reference. Scope: BigBlueButton 4.0 installer; verify the selected release line, dedicated CPU, public address and media firewall rules. Source: https://docs.bigbluebutton.org/administration/install/ (reviewed 2026-11-19). Deployment artifact: https://github.com/bigbluebutton/bbb-install/blob/v4.0.x-release/bbb-install.sh. Artifact reference: v4.0.x-release (moving maintained 4.0 installer branch).

- Minimum footprint / sizing: Documented. The production guide recommends Ubuntu 24.04, 8 CPU cores, 16 GB RAM, symmetric 250 Mbit/s networking and 500 GB free recording space, or 50 GB without recording. Smaller 4-core/8-GB development settings are separate. Concurrent media usage and HA need additional design. Scope: Current upstream production conferencing-node requirements; not meeting capacity for every workload. Source: https://docs.bigbluebutton.org/administration/install/ (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Browsertrix

Open-source browser-based web archiving and collection-management application.

- Listing: https://launchinyourcloud.com/directory/browsertrix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- 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: Kubernetes manifests
- Architecture: Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook.
- 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://webrecorder.net/browsertrix
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.

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

Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- legacy-system-archive-access: Open-source browser-based web archiving and collection-management application.

- archives-collections-management: Open-source browser-based web archiving and collection-management application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.browsertrix.com/deploy/ansible/digitalocean/ (checked 2026-11-19). 


### Cloud deployment evidence

- Browsertrix DigitalOcean Docs (digitalocean): https://docs.browsertrix.com/deploy/ansible/digitalocean/
  Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook. The documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes SuaYoo, ikreymer, tw4l, 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/webrecorder/browsertrix/graphs/contributors

- Upstream project: https://github.com/webrecorder/browsertrix

### Sources

- Browsertrix DigitalOcean Docs: https://docs.browsertrix.com/deploy/ansible/digitalocean/

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE

- GitHub Releases: https://github.com/webrecorder/browsertrix/releases

### Licensing sources

- https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE

### Infrastructure sources

- https://docs.browsertrix.com/deploy/ansible/digitalocean/


### 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. Browsertrix v1.26.6 implements application-issued JWTs and password-based login. The reviewed deployment/authentication material does not establish an external SAML/OIDC login path for platform users. Browser profiles used to authenticate to websites being crawled are a separate feature and do not prove Browsertrix account SSO. Scope: Self-hosted Browsertrix v1.26.6 platform-user identity; captured-site credentials are excluded. Source: https://github.com/webrecorder/browsertrix/blob/v1.26.6/backend/btrixcloud/auth.py (reviewed 2026-11-21). Supporting source: Deployment customization — https://docs.browsertrix.com/deploy/customization/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Browsertrix provides an upstream Helm chart and remote-deployment instructions for Kubernetes, including single-machine MicroK8s/k3s configuration, domains/TLS and optional external MongoDB/S3-compatible storage. Ansible cloud playbooks are described as experimental. Pin the chart/application release and configure secrets, persistent storage, backups and exposure; these recipes do not establish HA. Scope: Self-hosted Browsertrix v1.26.6 Helm artifact; production configuration and experimental Ansible scope. Source: https://docs.browsertrix.com/deploy/remote/ (reviewed 2026-11-21). Deployment artifact: https://github.com/webrecorder/browsertrix/tree/v1.26.6/chart. Artifact reference: v1.26.6. Supporting source: Chart configuration — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/README.md.

- Minimum footprint / sizing: Documented. The v1.26.6 chart defaults request 100 millicores/350 MiB for an API container and 12 millicores/512 MiB with a 2 GiB volume for bundled MongoDB; the deployment templates apply those values. These are per-component scheduling defaults, not a total host minimum or archive capacity. Include Redis, frontend, crawler/browser workers, replicas, captured data and backups when sizing production. Scope: Browsertrix v1.26.6 chart component resource requests; not complete workload/HA sizing. Source: https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/values.yaml (reviewed 2026-11-21). Supporting source: Backend resource template — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/templates/backend.yaml. Supporting source: MongoDB resource template — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/templates/mongo.yaml.

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

- Operating cost estimate: Not researched.

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







## Budibase Self-Hosted

Build operational apps and automations on customer-hosted infrastructure.

- Listing: https://launchinyourcloud.com/directory/budibase/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3 core, MPL client/component packages and BSL paid-feature packages; edition terms apply
- Licensing model: open-source
- Installation: Official all-in-one Docker image or Docker Compose; Kubernetes options
- Architecture: Customer-operated app/worker services with database, cache and object storage dependencies
- Operations: Customer manages containers, persistent storage, credentials, backups and upgrades; account/license connectivity remains relevant.
- Product website: https://budibase.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes Budibase Cloud. Current documentation requires outbound HTTPS for license activation/validation, and some authentication/AI capabilities depend on vendor services. Package licenses differ; paid features are not covered by the core open-source license.

Budibase documents GPLv3 core packages, MPL client/component packages and BSL paid-feature packages. The broad self-hosted listing therefore includes restricted feature code alongside the open-source base.

The reviewed self-hosted Docker option runs a persistent application/worker stack with CouchDB, Redis and object-storage components. Classified servers; workflow triggers do not imply function-based serverless.


### Category fit

- internal-tools: Internal app, form and automation development with connected data; plan and component licensing determine available features.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.budibase.com/docs/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Budibase self-hosting on DigitalOcean (digitalocean): https://docs.budibase.com/docs/digitalocean
  The project documents its one-click Budibase server in a customer DigitalOcean Droplet and requires at least 4 GB RAM. This is separate from Budibase Cloud. Keep the internal database port private and review backups, updates and the selected image before production use.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official Docker installation: https://docs.budibase.com/docs/docker

- Hosting options: https://docs.budibase.com/docs/hosting-methods

- Self-hosted license connectivity: https://docs.budibase.com/docs/self-hosted-licensing

- Network and AI service dependencies: https://docs.budibase.com/docs/whitelisting

- Official package licensing: https://github.com/Budibase/budibase/blob/master/LICENSE

- Product capabilities: https://github.com/Budibase/budibase

### Licensing sources

- https://github.com/Budibase/budibase/blob/master/LICENSE

### Infrastructure sources

- https://docs.budibase.com/docs/docker


### 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 OIDC guide configures an installation-specific callback, issuer configuration, client ID and secret for user sign-in, with automatic user creation on first OIDC login. Requiring all users to use SSO is documented separately as an Enterprise feature. Scope: Self-hosted user OIDC versus paid enforced-SSO policy; restrict IdP app assignments and preserve verified-email linking. Source: https://docs.budibase.com/docs/openid-connect (reviewed 2026-11-20). Supporting source: Enterprise SSO enforcement — https://docs.budibase.com/docs/enforced-sso.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official all-in-one image/Compose example requires generated secrets and a persistent data volume. The documented latest image reference moves; pin a selected release and plan backup and external dependencies. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.budibase.com/docs/docker (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/budibase/budibase. Artifact reference: select a released image tag; latest moves.

- Minimum footprint / sizing: Documented. The all-in-one Docker guide says 2 processing cores and 6 GB RAM should suit most use cases, while explicitly making resource needs usage-dependent. Persistent application/database/object-store data and any external data sources need separate storage and capacity planning. Scope: All-in-one Docker recommendation, not an HA or 1-TB throughput guarantee. Source: https://docs.budibase.com/docs/docker (reviewed 2026-11-20).

- License pricing: Documented. The v4.0.0 repository describes Budibase overall as GPLv3, with MPL-licensed packages for generated apps and paid feature packages under BSL. Self-hosted plan upgrades use an account-portal licence key and validation connectivity; confirm current feature quotas and paid entitlements. Scope: Package-specific terms and self-hosted licensing; generated apps are distinguished from the builder. Source: https://github.com/Budibase/budibase/blob/v4.0.0/LICENSE (reviewed 2026-11-20). Supporting source: Self-hosted licence activation and renewal — https://docs.budibase.com/docs/tenant-management. Supporting source: Licence connectivity — https://docs.budibase.com/docs/self-hosted-licensing.

- Operating cost estimate: Not researched.

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







## Campfire (ONCE)

Self-hosted group chat and team conversation application.

- Listing: https://launchinyourcloud.com/directory/once-campfire/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- 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: ONCE Campfire application and persistent message and upload storage on DigitalOcean.
- 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://once.com/campfire
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The current project is MIT-licensed; historical one-time commercial purchase descriptions are not the current source-code licence.

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

ONCE Campfire application and persistent message and upload storage on DigitalOcean. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted group chat and team conversation application.

### Deployment boundaries


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


### Cloud deployment evidence

- DigitalOcean Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/campfire
  ONCE Campfire application and persistent message and upload storage on DigitalOcean. The current project is MIT-licensed; historical one-time commercial purchase descriptions are not the current source-code licence.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes monorkin, dhh, jeremy, 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/basecamp/once-campfire/graphs/contributors

- Upstream project: https://github.com/basecamp/once-campfire

### Sources

- DigitalOcean Marketplace: https://marketplace.digitalocean.com/apps/campfire

- MIT LICENSE: https://github.com/basecamp/once-campfire/blob/main/MIT-LICENSE

- Releases v1.5.10: https://github.com/basecamp/once-campfire/releases

### Licensing sources

- https://github.com/basecamp/once-campfire/blob/main/MIT-LICENSE

### Infrastructure sources

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


### 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 reviewed application README and self-hosting guide do not establish a supported corporate SAML/OIDC user-login integration. API access and installation through ONCE do not establish SSO. Confirm a maintained integration and supported version rather than infer federation from self-hosting. Scope: Campfire application user identity; current public evidence remains insufficient. Source: https://github.com/basecamp/once-campfire (reviewed 2026-11-20). Supporting source: Official self-hosting configuration — https://raw.githubusercontent.com/basecamp/once-campfire/main/docs/self-hosting.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official self-hosting guide supplies a single-machine image with application, jobs, cache, file serving and TLS. Persist /rails/storage and set instance secrets and domain configuration. ONCE can manage installation/updates/backups; this is not a multi-node HA artifact. Scope: Upstream Campfire Docker deployment and optional ONCE lifecycle tooling. Source: https://raw.githubusercontent.com/basecamp/once-campfire/main/docs/self-hosting.md (reviewed 2026-11-20). Deployment artifact: https://github.com/basecamp/once-campfire. Artifact reference: main (moving repository); use a version-tagged application image.

- Minimum footprint / sizing: Sources checked — unresolved. The official guide establishes a self-contained single-machine deployment with database/uploads in persistent storage, but publishes no quantitative production CPU/RAM/storage floor in the reviewed instructions. Confirm attachment growth, active usage, backup and availability requirements. Scope: Single-machine deployment topology; quantitative production sizing remains open. Source: https://raw.githubusercontent.com/basecamp/once-campfire/main/docs/self-hosting.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Celerp

Source-available customer-operated business, inventory and ERP application.

- Listing: https://launchinyourcloud.com/directory/celerp/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Business Source License 1.1 with an internal-business production grant; commercial hosted resale needs separate permission.
- Licensing model: source-available
- Installation: VM image
- Architecture: Celerp application, database and persistent business records on a DigitalOcean Droplet.
- 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://marketplace.digitalocean.com/apps/celerp
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The BSL-1.1 additional grant permits internal business production use, while hosted resale and white-label offerings need separate commercial permission. Current releases and contributor history establish an actively developed young project; they do not guarantee production capacity or a support SLA.

Business Source License 1.1 with an internal-business production grant; commercial hosted resale needs separate permission.

Celerp application, database and persistent business records on a DigitalOcean Droplet. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Source-available customer-operated business, inventory and ERP application.

### Deployment boundaries


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


### Cloud deployment evidence

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/celerp
  Celerp application, database and persistent business records on a DigitalOcean Droplet. The BSL-1.1 additional grant permits internal business production use, while hosted resale and white-label offerings need separate commercial permission. Current releases and contributor history establish an actively developed young project; they do not guarantee production capacity or a support SLA.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

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

- GitHub LICENSE (BSL-1.1): https://raw.githubusercontent.com/celerp/celerp/main/LICENSE

- GitHub Commits: https://github.com/celerp/celerp/commits/main

### Licensing sources

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

### Infrastructure sources

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


### 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 reviewed self-hosted README describes application setup and login, but does not establish a supported external SAML/OIDC user-login integration. Business-service connectors and application API authentication are not evidence of identity-provider federation. Scope: Reviewed Celerp source distribution; provider, version and login surface still require confirmation. Source: https://github.com/celerp/celerp/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. Celerp documents native packages and a pip installation with celerp init, plus a headless service path using celerp start. Initialization can reuse an existing PostgreSQL server or start a bundled one. This is application installation, not a complete production cloud/HA template. Scope: Reviewed Celerp application and database initialization; service operation, network access and backups require configuration. Source: https://github.com/celerp/celerp/blob/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/celerp/celerp. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The README describes a bundled or external PostgreSQL server and headless operation, but does not establish a quantitative CPU/RAM/storage minimum or an HA profile. The desktop installer being able to serve an office is not a benchmark for the proposed workload. Scope: Reviewed Celerp application plus PostgreSQL; data volume, concurrent users and redundancy require sizing. Source: https://github.com/celerp/celerp/blob/main/README.md (reviewed 2026-11-20).

- License pricing: Edition-dependent. Business Source License 1.1 with an internal-business production grant; commercial hosted resale needs separate permission. Scope: Celerp; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/celerp/celerp/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Chatwoot Self-Hosted

Self-hosted customer-support inbox combining live chat, email and messaging conversations.

- Listing: https://launchinyourcloud.com/directory/chatwoot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp, aws, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition; proprietary enterprise features and paid self-hosted plans
- Licensing model: open-source
- Installation: Production Docker Compose, Linux VM or Kubernetes deployment
- Architecture: Customer-operated application and workers with PostgreSQL, Redis and upload storage
- Operations: Customer maintains the server, database, storage, updates and channel integrations; support differs by plan.
- Product website: https://www.chatwoot.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Community Edition excludes paid features such as SSO/SAML, SLA policies and Captain AI. Captain integrations may send data to external model providers. Official Azure and Google Cloud deployment guides are marked work in progress; validate their instructions against current requirements before production.

The self-hosted offering combines an MIT Community Edition with proprietary Enterprise feature code. Paid feature entitlements are distinct from community source-code rights; premium support alone is not the basis for this classification.

The production Docker guide runs Rails application/worker services alongside PostgreSQL and Redis, or connects to separately managed equivalents. Official cloud guides use VMs and also identify Kubernetes paths.


Cloud evidence scope: Official Azure VM and Google Compute Engine guides exist and are marked work in progress; other cloud badges are not inferred.

### Category fit

- customer-support: Shared support inbox, live chat, email and messaging channels, with automation and reporting; feature entitlements depend on edition.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/gcp (checked 2026-11-12). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/aws (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Chatwoot self-hosted deployment on AWS (aws): https://developers.chatwoot.com/self-hosted/deployment/aws
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on Azure (azure): https://developers.chatwoot.com/self-hosted/deployment/azure
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on Google Cloud (gcp): https://developers.chatwoot.com/self-hosted/deployment/gcp
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on digitalocean (digitalocean): https://developers.chatwoot.com/self-hosted/deployment/digitalocean
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Community support functionality: https://www.chatwoot.com/community

- Production Docker installation: https://developers.chatwoot.com/self-hosted/deployment/docker

- Edition licensing: https://www.chatwoot.com/hc/user-guide/articles/1677776492-enterprise-edition

- Self-hosted plan features: https://www.chatwoot.com/pricing/self-hosted-plans

- Azure deployment: https://developers.chatwoot.com/self-hosted/deployment/azure

- Google Cloud deployment: https://developers.chatwoot.com/self-hosted/deployment/gcp

- Chatwoot self-hosted deployment on aws: https://developers.chatwoot.com/self-hosted/deployment/aws

- Chatwoot self-hosted deployment on digitalocean: https://developers.chatwoot.com/self-hosted/deployment/digitalocean

### Licensing sources

- https://www.chatwoot.com/hc/user-guide/articles/1677776492-enterprise-edition

- https://www.chatwoot.com/pricing/self-hosted-plans

### Infrastructure sources

- https://developers.chatwoot.com/self-hosted/deployment/docker


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML SSO is included in Enterprise, but not Community or Premium Support. Scope: Self-hosted plan comparison. Source: https://www.chatwoot.com/pricing/self-hosted-plans (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The production guide links an upstream Compose stack with Rails, Sidekiq, PostgreSQL and Redis. Its application image uses latest; pin a compatible release, set secrets, and configure TLS, storage and backups. Scope: Production Docker deployment. Source: https://developers.chatwoot.com/self-hosted/deployment/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/chatwoot/chatwoot/blob/develop/docker-compose.production.yaml. Artifact reference: develop (moving branch).

- Minimum footprint / sizing: Documented. The technical requirements page specifies 4 CPU cores and 4 GB RAM for its smallest example workload; the pricing FAQ separately says 2 CPU cores and 4 GB. Resolve this difference for your workload before sizing. Scope: Technical requirements; compare the pricing FAQ. Source: https://developers.chatwoot.com/self-hosted/deployment/requirements (reviewed 2026-11-14). Supporting source: Self-hosted pricing FAQ: production starting point — https://www.chatwoot.com/pricing/self-hosted-plans.

- License pricing: Documented. Community is free to self-host. The current page lists Premium Support at $19 and Enterprise at $99 per agent/month; SAML is Enterprise-only. These are software/support plan units, excluding your infrastructure, taxes and connected AI usage. Confirm currency and billing terms at checkout. Scope: Current self-hosted edition comparison; not a hosted subscription or a total operating-cost estimate. Source: https://www.chatwoot.com/pricing/self-hosted-plans (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.



### Vendor alternative positioning

Positioning is not a finding of feature parity.

- zendesk: The self-hosted plan page positions Chatwoot as an alternative for customer-support workflows. Source: https://www.chatwoot.com/pricing/self-hosted-plans; reviewed 2026-11-16.

- intercom: The self-hosted plan page positions Chatwoot as an alternative for customer-support workflows. Source: https://www.chatwoot.com/pricing/self-hosted-plans; reviewed 2026-11-16.





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







## Consul Democracy

Open-source civic participation and participatory-budgeting platform.

- Listing: https://launchinyourcloud.com/directory/consul-democracy/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: heroku, digitalocean
- 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
- Architecture: Rails application and PostgreSQL on Heroku or the project's DigitalOcean/Ansible deployment.
- 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://consuldemocracy.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Proposal debate, public voting and participatory budgeting are not the same as grant-contract administration. Heroku requires durable external uploads. Match the application and installer releases; database-only suggestions for other clouds do not establish app-hosting paths.

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

Rails application and PostgreSQL on Heroku or the project's DigitalOcean/Ansible deployment. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

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

### Deployment boundaries


- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/docs/en/installation/deploying-on-heroku.md (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/docs/en/installation/digital_ocean.md (checked 2026-11-19). 


### Cloud deployment evidence

- Heroku Guide (heroku): https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/docs/en/installation/deploying-on-heroku.md
  Rails application and PostgreSQL on Heroku or the project's DigitalOcean/Ansible deployment. Proposal debate, public voting and participatory budgeting are not the same as grant-contract administration. Heroku requires durable external uploads. Match the application and installer releases; database-only suggestions for other clouds do not establish app-hosting paths.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- DigitalOcean Guide (digitalocean): https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/docs/en/installation/digital_ocean.md
  Rails application and PostgreSQL on Heroku or the project's DigitalOcean/Ansible deployment. Proposal debate, public voting and participatory budgeting are not the same as grant-contract administration. Heroku requires durable external uploads. Match the application and installer releases; database-only suggestions for other clouds do not establish app-hosting paths.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes javierm, decabeza, voodoorai2000, 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/consuldemocracy/consuldemocracy/graphs/contributors

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

### Sources

- Heroku Guide: https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/docs/en/installation/deploying-on-heroku.md

- DigitalOcean Guide: https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/docs/en/installation/digital_ocean.md

- Installer v2.6.1: https://raw.githubusercontent.com/consuldemocracy/installer/master/README.md

- Consul Democracy: https://consuldemocracy.org/

- AGPL-3.0: https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/LICENSE-AGPLv3.txt

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

- Main Commits: https://github.com/consuldemocracy/consuldemocracy/commits/master

### Licensing sources

- https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/LICENSE-AGPLv3.txt

### Infrastructure sources

- https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/docs/en/installation/deploying-on-heroku.md

- https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/docs/en/installation/digital_ocean.md


### 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 documents external user login through configured OAuth providers, SAML or OIDC, including application registration and callback URLs. Set per-instance/tenant provider configuration and account policy; signing in does not automatically satisfy a participation-verification requirement. Scope: Consul Democracy 2.6.1 application-user external identity. Source: https://github.com/consuldemocracy/consuldemocracy/blob/2.6.1/docs/en/features/oauth.md (reviewed 2026-11-21). Supporting source: Application callbacks — https://github.com/consuldemocracy/consuldemocracy/blob/2.6.1/app/controllers/users/omniauth_callbacks_controller.rb.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for Rails application and PostgreSQL on Heroku or the project's DigitalOcean/Ansible deployment. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Upstream installation scripts; separately verify the application release and configured provider. Source: https://raw.githubusercontent.com/consuldemocracy/installer/master/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/consuldemocracy/installer. Artifact reference: master (moving installer collection).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed installation prerequisites/provider recipes do not establish a quantitative whole-production-host CPU/RAM/storage baseline. Size web/database/search, background work, participatory peaks, uploaded files and replicas; a selected provider VM is not automatically a tested minimum. Scope: Consul Democracy 2.6.1 production sizing remains unconfirmed. Source: https://github.com/consuldemocracy/consuldemocracy/blob/2.6.1/docs/en/installation/prerequisites.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: Consul Democracy; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/consuldemocracy/consuldemocracy/master/LICENSE-AGPLv3.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Discourse

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

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


### Community and maintenance

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

Reviewed 2026-11-14.

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

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

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

### Sources

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

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

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

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

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

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

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

### Licensing sources

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

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. DiscourseConnect is the official SSO protocol for connecting Discourse to an external identity provider through a signed shared-secret exchange. It is distinct from a generic SAML entitlement; configure account/email mapping and callback security for the actual identity service. Scope: Official DiscourseConnect self-hosted forum authentication. Source: https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045 (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official discourse_docker repository supplies launcher scripts and a standalone configuration example with application, PostgreSQL and Redis templates. Configure mail, TLS, secrets, volumes and backups, and pin compatible releases; a standalone container is not a clustered HA topology. Scope: Official self-hosted launcher and standalone container installation. Source: https://raw.githubusercontent.com/discourse/discourse_docker/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml. Artifact reference: main (moving branch). Supporting source: Standalone configuration template — https://raw.githubusercontent.com/discourse/discourse_docker/main/samples/standalone.yml.

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

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## DocuSeal Self-Hosted

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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

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

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

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

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

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

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


### Cloud deployment evidence

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

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

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

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

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

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

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

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

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

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

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

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


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

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

### Sources

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### Licensing sources

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

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

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

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

### Infrastructure sources

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

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

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

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


### Buyer diligence


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

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


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

- Cloud commitment eligibility: Not researched.

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

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

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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



### Vendor alternative positioning

Positioning is not a finding of feature parity.

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

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


### Security and lifecycle reviews

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

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




## DokuWiki

File-based wiki for documentation and shared knowledge.

- Listing: https://launchinyourcloud.com/directory/dokuwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: DokuWiki web application with persistent wiki pages, configuration and attachments.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

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

- Railway (railway): https://railway.com/deploy/dokuwiki
  DokuWiki web application with persistent wiki pages, configuration and attachments. Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes splitbrain, selfthinker, Klap-in, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


- Marketplace delivery: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from TurnKey GNU/Linux. Its package version is 19.0.3; verify the contained application and required entitlements separately. Scope: DokuWiki selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg (reviewed 2026-11-19). Offer prodview-h7wozgfyl3vfg: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The maintainer-provided oauth plugin implements login through OAuth services. It is a separately installed authentication plugin, not a guarantee that the default wiki has corporate SAML/OIDC configured; validate provider-plugin and DokuWiki release compatibility. Scope: CosmoCode DokuWiki OAuth plugin integration. Source: https://raw.githubusercontent.com/cosmocode/dokuwiki-plugin-oauth/master/README (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream DokuWiki container repository documents a non-root image, persistent /storage volume and a Compose example. Configure the initial wiki securely, set writable storage ownership and pin a supported release rather than a moving tag. Scope: Official DokuWiki application container packaging; not cloud-account HA IaC. Source: https://raw.githubusercontent.com/dokuwiki/docker/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/dokuwiki/docker. Artifact reference: master (moving repository); choose a supported version-tagged image.

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

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

- Operating cost estimate: Not researched.

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







## Etherpad

Self-hosted real-time collaborative text editor.

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

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

- Railway (railway): https://railway.com/deploy/etherpad
  Etherpad application, database and persistent plugins and settings. Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

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




## Ever Gauzy

Open-source business operations platform for people, projects, time and financial records.

- Listing: https://launchinyourcloud.com/directory/ever-gauzy/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, fly, railway, render
- 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
- Architecture: Ever Gauzy application/API, database and required workers using provider-specific deployment recipes.
- 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://gauzy.co
- 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 supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.

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

Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Open-source business operations platform for people, projects, time and financial records.

- hr-employee-records-management: Open-source business operations platform for people, projects, time and financial records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/azure-deployment/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/gcp-deployment/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/ (checked 2026-11-19). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/heroku-deployment/ (checked 2026-11-19). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/flyio-deployment/ (checked 2026-11-19). 

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

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/render-deployment/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Guide (aws): https://docs.gauzy.co/deployment/cloud/aws-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.gauzy.co/deployment/cloud/azure-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Guide (gcp): https://docs.gauzy.co/deployment/cloud/gcp-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Guide (digitalocean): https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Heroku Guide (heroku): https://docs.gauzy.co/deployment/cloud/heroku-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Fly.io Guide (fly): https://docs.gauzy.co/deployment/cloud/flyio-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/ever-gauzy
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.

- Render Guide (render): https://docs.gauzy.co/deployment/cloud/render-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes evereq, rahul-rocket, adkif, 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/ever-co/ever-gauzy/graphs/contributors

- Upstream project: https://github.com/ever-co/ever-gauzy

### Sources

- AWS Guide: https://docs.gauzy.co/deployment/cloud/aws-deployment/

- Azure Guide: https://docs.gauzy.co/deployment/cloud/azure-deployment/

- GCP Guide: https://docs.gauzy.co/deployment/cloud/gcp-deployment/

- DO Guide: https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/

- Heroku Guide: https://docs.gauzy.co/deployment/cloud/heroku-deployment/

- Fly.io Guide: https://docs.gauzy.co/deployment/cloud/flyio-deployment/

- Railway: https://railway.com/deploy/ever-gauzy

- Render Guide: https://docs.gauzy.co/deployment/cloud/render-deployment/

- AGPL-3.0 LICENSE: https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE

- Releases v111.250.0: https://github.com/ever-co/ever-gauzy/releases

### Licensing sources

- https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE

### Infrastructure sources

- https://docs.gauzy.co/deployment/cloud/aws-deployment/

- https://docs.gauzy.co/deployment/cloud/azure-deployment/

- https://docs.gauzy.co/deployment/cloud/gcp-deployment/

- https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/

- https://docs.gauzy.co/deployment/cloud/heroku-deployment/

- https://docs.gauzy.co/deployment/cloud/flyio-deployment/

- https://railway.com/deploy/ever-gauzy

- https://docs.gauzy.co/deployment/cloud/render-deployment/


### 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 vendor documents application-user OAuth login with Google, GitHub, Facebook, Twitter, LinkedIn and Microsoft, including registered clients and instance callback settings. Provider login and the application JWT session/API mechanism are distinct configuration layers. Scope: Upstream application-user social OAuth configuration; not proof of arbitrary enterprise SAML or SCIM support. Source: https://docs.gauzy.co/authentication/social-auth/ (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 AWS guide provides service architecture, CLI provisioning and ECS task configuration for the application, PostgreSQL, Redis and S3. Configure images, task resources, secrets, networking and persistence for production; the illustrative commands are not a supplied complete CloudFormation stack. Scope: Vendor-documented customer AWS deployment recipe; complete production configuration and version alignment require review. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The AWS guide illustrates two Fargate tasks at 1 vCPU/2 GB each, a db.t3.medium database with a 50-GB provisioning example and cache.t3.micro Redis. These are example service sizes from the guide, with file storage and load balancing additional; its advertised cost table is not a reference-workload quote. Scope: Published AWS example allocations, not a 100-user/1-TB HA minimum or current operating-cost estimate. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (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: Ever Gauzy; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Flagsmith Self-Hosted

Feature management platform for targeted rollouts and remotely configured application behavior.

- Listing: https://launchinyourcloud.com/directory/flagsmith/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms.
- Licensing model: open-source
- Installation: Deploy the official Docker Compose environment and configure the dashboard/API, PostgreSQL and application SDK endpoints.
- Architecture: Customer-operated dashboard and Django API with PostgreSQL persistence and optional processing services
- Operations: Customer manages flag API availability, SDK endpoints, database, permissions, secrets, backups and upgrades.
- Product website: https://www.flagsmith.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The local Compose guide is an evaluation path requiring production hardening. Point SDKs to the self-hosted endpoint; experimentation can add warehouse and ingestion services with separate operational requirements. Flagsmith v2.291.0 fixes existing authentication tokens remaining valid after a password change or reset, an identities search that could bring down the database, a security update to oauthlib, and trust in compromised eMudhra certificate authorities. Self-hosted operators should upgrade so password changes invalidate existing dashboard tokens and the database-search safeguards are present. Flagsmith v2.292.0 adds SSRF allowlisting, scopes nested writes correctly, exposes organization audit logs, and updates dnspython for security. Review outbound destinations and nested-resource authorization after upgrading.

BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated dashboard and Django API with PostgreSQL persistence and optional processing services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- feature-management: Feature flags, remote configuration, user targeting, segments and multivariate release control; advanced edition features are separate.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (checked 2026-11-12). 


### Cloud deployment evidence

- Flagsmith self-hosted platform architecture (aws, azure, gcp, digitalocean): https://docs.flagsmith.com/flagsmith-concepts/platform-architecture
  The vendor explicitly names AWS, Google Cloud, Azure and DigitalOcean for team-managed Docker or Kubernetes deployments. This is a self-hosted application compatibility statement, distinct from managed Flagsmith SaaS; configure the backing services, security and edition-specific entitlements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The project publishes frequent 2026 releases and a documented public development model. Its named Wistia case study describes production feature-flag adoption; the case study alone does not certify a self-hosted deployment boundary.

Reviewed 2026-11-10.

- Current releases: https://github.com/Flagsmith/flagsmith/releases

- Open-source development and core scope: https://www.flagsmith.com/open-source

- Named production adoption: https://www.flagsmith.com/case-studies/wistia

### Sources

- Official installation and runtime: https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker

- Upstream project and capabilities: https://github.com/Flagsmith/flagsmith

- Current upstream license: https://raw.githubusercontent.com/Flagsmith/flagsmith/main/LICENSE.md

- Flagsmith v2.291.0 security and reliability fixes: https://github.com/Flagsmith/flagsmith/releases/tag/v2.291.0

- Password-change token revocation security issue: https://github.com/Flagsmith/flagsmith/issues/8651

- Flagsmith v2.292.0 release: https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0

### Licensing sources

- https://raw.githubusercontent.com/Flagsmith/flagsmith/main/LICENSE.md

### Infrastructure sources

- https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The platform architecture identifies advanced authentication including Okta, LDAP, SAML and ADFS in Enterprise on-premises deployments. Confirm the licensed integration and protocol configuration for the chosen package. Scope: Enterprise self-hosted/on-premises features. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Flagsmith v2.292.0 adds SSRF allowlisting, corrects nested-write authorization scope, and updates a security dependency. Upgrade to v2.292.0 or later, configure the SSRF allowlist, and retest nested writes. Scope: Upstream v2.292.0 release notes; no consolidated affected-version range is asserted.. Source: https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide downloads an upstream Compose environment for dashboard/API and supporting services. It is a local setup starting point; configure production secrets, network access, database persistence and edition requirements. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/Flagsmith/flagsmith/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The Kubernetes guide leaves resource requests/limits unset by default and recommends limits of 1 vCPU and 2 GB RAM per pod, subject to workload. PostgreSQL, evaluation/SSE traffic, replicas and any experimentation warehouse need separate capacity. These are pod limits, not a whole-host or HA minimum. Scope: Official per-pod allocation guidance; database/warehouse and HA resources are separate. Source: https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/kubernetes-openshift (reviewed 2026-11-20).

- License pricing: Documented. The published v2.292.0 core uses BSD 3-Clause terms. This does not include every Enterprise authentication, support or on-premises entitlement; choose the edition and agreement separately. Application/database hosting, SDK evaluation traffic, experimentation storage and operations have separate costs. Scope: Published OSS core terms; commercial features and infrastructure are separate. Source: https://github.com/Flagsmith/flagsmith/blob/v2.292.0/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Flagsmith v2.292.0 was published November 17, 2026. It adds SSRF allowlisting, corrects nested-write scope, adds organization audit-log UI, and updates dnspython for security. Scope: Upstream Flagsmith self-hosted release. Source: https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Flagsmith 2.292.0 request and authorization hardening (security-advisory): Flagsmith v2.292.0 adds SSRF allowlisting, corrects nested-write authorization scope, and updates a security dependency. Scope: Upstream v2.292.0 release notes; no consolidated affected-version range is asserted. Conditions: Applicability depends on outbound request configuration, nested-resource writes, and the affected dependency. Action: Upgrade to v2.292.0 or later, configure the SSRF allowlist, and retest nested writes. Source: https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0; reviewed 2026-11-18.




## FusionAuth Self-Hosted

Proprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.

- Listing: https://launchinyourcloud.com/directory/fusionauth-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: FusionAuth Customer License Agreement; Community and paid plans are proprietary, with feature and support limits by plan.
- Licensing model: commercial-only
- Installation: Vendor Kubernetes/Helm guides, DigitalOcean Kubernetes 1-Click package, or Render application/PostgreSQL blueprint; versions and production topology differ
- Architecture: FusionAuth application instances with a customer database and optional search, deployed on cloud Kubernetes or as a customer Render web service and PostgreSQL database.
- Operations: Customer configures application releases, plan features, database/search, networking, TLS, secrets, backups and capacity. Kubernetes operations apply to cluster deployments; Render operates its platform while the customer configures the web service and managed database.
- Product website: https://fusionauth.io/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This is self-hosted FusionAuth, not FusionAuth Cloud. The AWS Marketplace guide sells hosted Cloud service; EKS remains a separately documented customer-hosted path. DigitalOcean’s 1-Click package is 1.53.3, distinct from upstream 1.71.0. SCIM and paid air-gap/FIPS options have Enterprise conditions; Render uses a customer-owned application/database blueprint.

FusionAuth is proprietary under its Customer License Agreement, including the no-cost Community plan; paid plan capabilities require corresponding entitlements.

FusionAuth uses provisioned application capacity and persistent database state. Kubernetes and Render have different platform-operation boundaries; the customer selects and configures the application and database deployment.


### Category fit

- identity-access-management: Provides customer-operated authentication, authorization, user management and federation for applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/eks (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/aks (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/gke (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean (checked 2026-11-18). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/marketplaces/render (checked 2026-11-18). 


### Cloud deployment evidence

- FusionAuth on Amazon EKS (aws): https://fusionauth.io/docs/deploy/production/kubernetes/eks
  FusionAuth documents provisioning the cluster, database and full application in customer AWS infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth on Azure AKS (azure): https://fusionauth.io/docs/deploy/production/kubernetes/aks
  FusionAuth documents the full application on a customer AKS cluster and Azure database resources.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth on Google GKE (gcp): https://fusionauth.io/docs/deploy/production/kubernetes/gke
  FusionAuth documents the full application on customer GKE and Google Cloud database resources.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth in customer DigitalOcean Kubernetes (digitalocean): https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean
  The vendor and provider document a full FusionAuth 1-Click Kubernetes application. The provider catalog packages 1.53.3, older than the reviewed upstream release; validate upgrades and production database/HA design.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth and PostgreSQL in customer Render (render): https://fusionauth.io/docs/deploy/production/marketplaces/render
  FusionAuth provides a Render blueprint deploying the full application and PostgreSQL in the customer’s account/project. Production needs paid resource capacity and a deliberate database/backup design.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- FusionAuth on Kubernetes: https://fusionauth.io/docs/deploy/production/kubernetes/

- FusionAuth on Amazon EKS: https://fusionauth.io/docs/deploy/production/kubernetes/eks

- FusionAuth on Azure AKS: https://fusionauth.io/docs/deploy/production/kubernetes/aks

- FusionAuth on Google GKE: https://fusionauth.io/docs/deploy/production/kubernetes/gke

- FusionAuth license: https://fusionauth.io/license

- FusionAuth in customer DigitalOcean Kubernetes: https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean

- FusionAuth and PostgreSQL in customer Render: https://fusionauth.io/docs/deploy/production/marketplaces/render

### Licensing sources

- https://fusionauth.io/license

- https://fusionauth.io/docs/concepts/plans-and-limits/plans-features

### Infrastructure sources

- https://fusionauth.io/docs/deploy/production/kubernetes/


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 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: Edition-dependent. DigitalOcean documents a FusionAuth Kubernetes 1-Click application, currently packaged as 1.53.3. That older package must not be presented as upstream 1.71.0. FusionAuth’s AWS Marketplace guide instead describes FusionAuth Cloud hosting; it is not the self-hosted EKS product. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://docs.digitalocean.com/products/marketplace/catalog/fusionauth/ (reviewed 2026-11-18). Supporting source: AWS offer is hosted FusionAuth Cloud — https://fusionauth.io/docs/deploy/production/marketplaces/aws. Supporting source: Vendor DigitalOcean package guide — https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean. Offer fusionauth: FusionAuth; Kubernetes 1-Click application; package 1.53.3; https://marketplace.digitalocean.com/apps/fusionauth.

- Cloud commitment eligibility: Sources checked — unresolved. The vendor’s AWS Marketplace subscription is FusionAuth Cloud. Its procurement terms do not establish commitment credit for a self-hosted licence. Confirm the selected self-hosted Enterprise order and buyer agreement separately. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/marketplaces/aws (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. Self-hosted FusionAuth provides SSO between applications through its own login/session system and OIDC/SAML integration. Distinguish FusionAuth acting as the application identity provider from connecting an external IdP, and confirm the selected plan’s optional features. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/authentication/sessions/single-sign-on (reviewed 2026-11-18).

- SCIM provisioning: Edition-dependent. SCIM 2.0 is an Enterprise-plan feature available from 1.36.0. FusionAuth acts as an inbound SCIM server for users/groups, with OAuth client credentials and configurable mappings. It is not a SCIM client provisioning other services; application registration remains separate. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/users/provision/scim (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. FusionAuth’s August 2025 announcement identifies AssurancePoint as its ISO 27001:2022 auditor. The current certificate/SOA and SOC 2 report remain request-gated, so their validity and self-hosted system boundary were not independently checked here. Its licence FAQ limits report access and requires Enterprise plus HA hosting for a BAA. Assess the actual report/customer controls; FIPS mode is explicitly not FIPS certification. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://trust.fusionauth.io/?format=html (reviewed 2026-11-18). Supporting source: Licence and assurance FAQ — https://fusionauth.io/license-faq. Supporting source: FIPS mode versus certification — https://fusionauth.io/docs/security/compliance/. Supporting source: Named auditor and original announcement — https://fusionauth.io/blog/fusionauth-iso27001-2025.

- Security controls: Documented. Enterprise self-hosted FIPS mode is available from 1.62.0 only for new installations and requires every node in the cluster to use that mode, with separately compliant database/search components. This is a scoped configuration feature, not FIPS certification. SSO, token and provisioning controls require explicit configuration. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/security/compliance/ (reviewed 2026-11-18). Supporting source: SCIM access control — https://fusionauth.io/docs/users/provision/scim. Supporting source: Application SSO/session behavior — https://fusionauth.io/docs/authentication/sessions/single-sign-on.

- Air-gapped operation: Edition-dependent. Enterprise documents an air-gapped licence, offline key activation and an expiry without a grace period; network-backed features and update feeds need separate handling. The requirements also state Community can block outbound access without a paid licence. Choose the plan and disable or supply reachable dependencies explicitly. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/install/air-gapping (reviewed 2026-11-18). Supporting source: Community versus paid-plan network requirements — https://fusionauth.io/docs/deploy/production/system-requirements.

- Deployment artifact / IaC: Documented. The vendor’s Render blueprint deploys FusionAuth and PostgreSQL into the customer’s Render account. The repository is a moving source, not an immutable image lockfile; fork/review it and select production capacity. EKS/AKS/GKE have separate production guides. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/marketplaces/render (reviewed 2026-11-18). Deployment artifact: https://github.com/FusionAuth/fusionauth-render-blueprint. Artifact reference: Moving repository default branch; reviewed 2026-11-18. Supporting source: EKS deployment — https://fusionauth.io/docs/deploy/production/kubernetes/eks.

- Minimum footprint / sizing: Documented. The application minimum is 512 MB RAM with 10–50 GB disk for application/log needs; database, operating system and optional search are additional. CPU depends on login rate and password hashing. Current releases bundle Java 25 and recommend tested PostgreSQL versions. Multiple app replicas and HA database/search require separate sizing. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/system-requirements (reviewed 2026-11-18).

- License pricing: Documented. FusionAuth uses its proprietary Customer Licence Agreement, including the no-cost Community plan. Paid plan/MAU terms are separate; SCIM and the documented paid air-gap licence require Enterprise. Free Community is not an open-source software licence. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/license (reviewed 2026-11-18). Supporting source: Self-hosting plan comparison — https://fusionauth.io/pricing?hosting=self-hosting&step=plan. Supporting source: SCIM Enterprise entitlement — https://fusionauth.io/docs/users/provision/scim.

- Operating cost estimate: Sources checked — unresolved. Define monthly active users, peak logins/token operations, password-hash settings, identity/audit retention, database/search HA and selected paid features. One hundred internal users need not equal billable MAU, and 1 TB needs a database/log retention split. Include licences, backups, egress and operations. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://fusionauth.io/docs/deploy/production/system-requirements (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. FusionAuth 1.71.0 was released November 17, 2026. It includes security changes and rejects authorized redirect URLs containing fragments; test SAML and redirect configurations during upgrade. The DigitalOcean package remains 1.53.3 in the reviewed catalog. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/release-notes (reviewed 2026-11-18). Supporting source: Separate DigitalOcean package version — https://docs.digitalocean.com/products/marketplace/catalog/fusionauth/.




### Security and lifecycle reviews

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

- FusionAuth 1.71.0 security and redirect configuration review (security-advisory): The release hardens SAML parsing and rejects redirect URLs containing fragments. It also adds an optional Enterprise passwordless-code rate limit. Scope: FusionAuth 1.71.0 release notes; the vendor does not establish a complete affected-version range or CVE for every change. Conditions: Exposure depends on SAML/redirect configuration. The new Enterprise rate limit is disabled by default and applies to the documented FormField strategy. Action: Remove fragments from registered redirects before upgrading, test SAML integrations and explicitly configure the paid rate limit if required. Recheck older provider packages. Source: https://fusionauth.io/docs/release-notes; reviewed 2026-11-18.




## Ghost Self-Hosted

Open-source publishing and membership CMS with documented customer-operated Linode and DigitalOcean deployments.

- Listing: https://launchinyourcloud.com/directory/ghost-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: linode, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT
- Licensing model: open-source
- Installation: Official Ghost-CLI production installation on Linode or Ghost Marketplace Droplet on DigitalOcean
- Architecture: Node.js application with MySQL, reverse proxy, TLS, mail and persistent content storage
- Operations: Customer manages the Linode server or DigitalOcean Droplet, operating system, MySQL, reverse proxy, TLS, mail, storage, backups, monitoring and Ghost upgrades.
- Product website: https://ghost.org/
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers self-hosted Ghost, not Ghost(Pro). The official Linode guide requires a secured Ubuntu server and hands ongoing software maintenance to the customer. Verify the current supported Node.js, MySQL and Ubuntu versions before installation.

The Ghost application is MIT-licensed. Ghost(Pro) hosting and third-party themes, integrations or services have separate terms.

Ghost runs as a long-lived Node.js service with MySQL, proxy, mail and persistent content dependencies on a customer Linode or DigitalOcean Droplet.


### Category fit

- content-management: Provides a self-hosted publishing CMS for websites, memberships, newsletters and structured editorial content.

### Deployment boundaries


- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.ghost.org/install/linode/ (checked 2026-11-15). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.ghost.org/install/digitalocean/ (checked 2026-11-15). 


### Cloud deployment evidence

- Official Ghost production deployment on Linode (linode): https://docs.ghost.org/install/linode/
  Ghost provides an official production guide that starts with a customer-configured and secured Linode Ubuntu server and installs Ghost through Ghost-CLI.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Official Ghost production deployment on DigitalOcean (digitalocean): https://docs.ghost.org/install/digitalocean/
  Ghost documents creating its Marketplace Droplet in the customer DigitalOcean account, connecting by SSH and completing Ghost-CLI, domain, TLS and mail configuration. Confirm the image and upstream runtime versions before production.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Community and maintenance

Ghost release v6.77.0 was published on November 11, 2026, and the public contributor history records sustained upstream participation. This evidence applies to the open-source application, not to Ghost(Pro) hosting or paid support.

Reviewed 2026-11-15.

- Reviewed release v6.77.0: https://github.com/TryGhost/Ghost/releases/tag/v6.77.0

- Upstream contributor history: https://github.com/TryGhost/Ghost/graphs/contributors

### Sources

- Official Ghost installation on Linode: https://docs.ghost.org/install/linode/

- Ghost self-hosting guidance: https://docs.ghost.org/hosting/

- Ghost MIT license: https://github.com/TryGhost/Ghost/blob/main/LICENSE

- Reviewed release v6.77.0: https://github.com/TryGhost/Ghost/releases/tag/v6.77.0

- Upstream contributor history: https://github.com/TryGhost/Ghost/graphs/contributors

- Official Ghost production deployment on DigitalOcean: https://docs.ghost.org/install/digitalocean/

### Licensing sources

- https://github.com/TryGhost/Ghost/blob/main/LICENSE

### Infrastructure sources

- https://docs.ghost.org/install/linode/

- https://docs.ghost.org/hosting/

- https://docs.ghost.org/install/digitalocean/


### 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 native Members documentation describes passwordless email-link/JWT sign-in. This does not establish a supported corporate SAML/OIDC federation path for staff or publication members in the listed self-hosted core. Confirm the exact identity surface and supported integration before treating this as enterprise SSO. Scope: Ghost self-hosted member authentication; staff and external federation are separate questions. Source: https://docs.ghost.org/members/ (reviewed 2026-11-20). Supporting source: Self-hosting configuration and service boundaries — https://docs.ghost.org/hosting/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official ghost-docker repository supplies the Docker Compose deployment for Ghost, MySQL and Caddy, with optional ActivityPub and analytics services. The guide labels this tooling preview; Tinybird-backed analytics and external mail have separate configuration and service boundaries. Scope: Official Ghost 6 Docker tooling preview; not a hardened HA baseline. Source: https://docs.ghost.org/install/docker/ (reviewed 2026-11-20). Deployment artifact: https://github.com/TryGhost/ghost-docker. Artifact reference: Moving repository; use compatible pinned application/service versions.

- Minimum footprint / sizing: Documented. The supported production stack requires at least 1 GB memory, Ubuntu LTS, Node.js LTS, MySQL, NGINX, systemd and a non-root user. This is a minimum prerequisite, not a capacity guarantee; size mail, media, backups and traffic separately. Scope: Ghost supported self-hosting stack checked 2026-11-16. Source: https://docs.ghost.org/hosting (reviewed 2026-11-16).

- License pricing: Documented. Ghost core is distributed under the MIT license. Ghost(Pro) hosting, paid publication services, mail delivery, optional analytics dependencies and third-party deployment packages are separate from the core software terms. Scope: Upstream Ghost software license; not a Ghost(Pro) subscription or infrastructure quote. Source: https://raw.githubusercontent.com/TryGhost/Ghost/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Sources checked — unresolved. Worked infrastructure subtotal: one Regular Basic DigitalOcean Droplet (1 GiB RAM, 1 vCPU, 25 GiB SSD) at the published USD 6 monthly cap, plus Basic weekly backups at 20%, gives USD 7.20/month. This is a rate illustration, not a complete operating-cost estimate or capacity recommendation. It excludes mail, domain, extra storage/transfer, monitoring, support, tax and operator labor. Scope: Illustrative standard-rate month for Ghost self-hosting; select an available region and test capacity. No discounts or free credits assumed; rates checked 2026-11-16.. Source: https://www.digitalocean.com/pricing/droplets (reviewed 2026-11-16). Supporting source: DigitalOcean Basic backup plan percentages — https://docs.digitalocean.com/products/backups/details/pricing/. Supporting source: Ghost supported production stack and minimum memory — https://docs.ghost.org/hosting.

- Release snapshot / cadence: Not researched.







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







## IceHrm (Open Source)

Customer-operated HR records, leave, attendance and people-management application.

- Listing: https://launchinyourcloud.com/directory/icehrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- 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: Package / binary installer
- Architecture: IceHrm application, database and persistent employee 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://icehrm.org/installation-and-setup/installing-icehrm-on-linux/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The listed open-source edition differs from Enterprise and paid modules. The vendor Linux guide names AWS and Linode as possible VPS hosts and provides a worked DigitalOcean path. Apply the IceHrm application corrections and recreate Docker containers from the corrected image when using that deployment mode.

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

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


### Category fit

- hr-employee-records-management: Customer-operated HR records, leave, attendance and people-management application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://icehrm.org/installation-and-setup/installing-icehrm-on-linux/ (checked 2026-11-19). 


### Cloud deployment evidence

- IceHrm Linux VPS Docs (digitalocean): https://icehrm.org/installation-and-setup/installing-icehrm-on-linux/
  IceHrm application, database and persistent employee documents. The listed open-source edition differs from Enterprise and paid modules. The vendor Linux guide names AWS and Linode as possible VPS hosts and provides a worked DigitalOcean path.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes thilinah, ddave001, icehrm, 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/gamonoid/icehrm/graphs/contributors

- Upstream project: https://github.com/gamonoid/icehrm

### Sources

- IceHrm Linux VPS Docs: https://icehrm.org/installation-and-setup/installing-icehrm-on-linux/

- GPL-3.0 LICENSE: https://raw.githubusercontent.com/gamonoid/icehrm/master/LICENSE

- GitHub Releases: https://github.com/gamonoid/icehrm/releases

- IceHrm upload authorization and runtime update: https://github.com/gamonoid/icehrm/releases/tag/v36.0.2

### Licensing sources

- https://raw.githubusercontent.com/gamonoid/icehrm/master/LICENSE

### Infrastructure sources

- https://icehrm.org/installation-and-setup/installing-icehrm-on-linux/


### 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 vendor documents SAML login with Okta for IceHrm Open Source and IceHrmPro, explicitly excluding IceHrm Cloud. The v36.0.2 login code processes enabled SAML responses and redirects to the configured IdP; configure certificates, endpoints and email/name-ID mapping for the selected installation. Scope: Self-hosted IceHrm Open Source v36.0.2 and documented Pro integration; not IceHrm Cloud. Source: https://icehrm.gitbook.io/icehrm/api-and-single-sign-on/sign-in-with-saml-okta (reviewed 2026-11-21). Supporting source: v36.0.2 login implementation — https://github.com/gamonoid/icehrm/blob/v36.0.2/core/login.php. Supporting source: v36.0.2 SAML manager — https://github.com/gamonoid/icehrm/blob/v36.0.2/core/src/Classes/SAMLManager.php.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Upstream publishes a v36.0.2 release and container upgrade instructions; the vendor also provides a manual Linux/PHP/database installation guide. Its older PHP examples are not current release runtime advice: select the release-matched image or installer, configure persistence, secrets and TLS, and validate database/upgrade compatibility. Scope: Self-hosted upstream release/container delivery and manual installation; no turnkey HA IaC established. Source: https://github.com/gamonoid/icehrm/releases/tag/v36.0.2 (reviewed 2026-11-21). Deployment artifact: https://github.com/gamonoid/icehrm/releases/tag/v36.0.2. Artifact reference: v36.0.2. Supporting source: Vendor manual Linux installation — https://icehrm.org/installation-and-setup/installing-icehrm-on-linux/.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed Linux installation and current release notes identify software dependencies and container delivery, but do not establish a numeric production host minimum. Employee concurrency, attachments, scheduled work, database capacity, backups and HA replicas still need a sizing baseline. Scope: Self-hosted IceHrm; older runtime examples do not establish v36.0.2 production capacity. Source: https://icehrm.org/installation-and-setup/installing-icehrm-on-linux/ (reviewed 2026-11-21). Supporting source: Current release — https://github.com/gamonoid/icehrm/releases/tag/v36.0.2.

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- IceHrm upload authorization and runtime update (security-advisory): IceHrm 36.0.2 corrects manager upload permissions and updates Docker PHP dependencies. Scope: IceHrm 36.0.2 release: upload checks, Docker/nginx directory access and PHP 8.3.36 runtime fixes. Conditions: Application updater and Docker runtime updates are separate; updating application files alone does not replace the container’s PHP base. Action: Apply the IceHrm application corrections and recreate Docker containers from the corrected image when using that deployment mode. Source: https://github.com/gamonoid/icehrm/releases/tag/v36.0.2; reviewed 2026-11-19.




## Islandora (ISLE)

Open-source digital repository and collections platform with a community DigitalOcean deployment.

- Listing: https://launchinyourcloud.com/directory/islandora/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- 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: Terraform
- Architecture: ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state.
- 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://sandbox.islandora.ca
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The named-cloud recipe is a community sandbox implementation. Validate persistence, domain configuration, secrets and production recovery separately; its Terraform release is not an Islandora application release.

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

ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- archives-collections-management: Open-source digital repository and collections platform with a community DigitalOcean deployment.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Islandora-Devops/sandbox (checked 2026-11-19). 


### Cloud deployment evidence

- Islandora-Devops/sandbox (digitalocean): https://github.com/Islandora-Devops/sandbox
  ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state. The named-cloud recipe is a community sandbox implementation. Validate persistence, domain configuration, secrets and production recovery separately; its Terraform release is not an Islandora application release.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes rosiel, adam-vessey, aOelschlager, 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/Islandora-Devops/islandora-starter-site/graphs/contributors

- Upstream project: https://github.com/Islandora-Devops/islandora-starter-site

### Sources

- Islandora-Devops/sandbox: https://github.com/Islandora-Devops/sandbox

- main.tf: https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf

- GPL-2.0 LICENSE: https://github.com/Islandora/islandora-starter-site/blob/main/LICENSE

- GitHub Releases: https://github.com/Islandora/islandora-starter-site/releases

### Licensing sources

- https://github.com/Islandora/islandora-starter-site/blob/main/LICENSE

### Infrastructure sources

- https://github.com/Islandora-Devops/sandbox


### 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. Islandora documents JWTs for communication among Drupal and repository microservices. This is service authentication, not a staff browser-login integration. The reviewed starter-site 1.11.0 dependencies do not establish a configured, compatible Drupal 11 SAML/OIDC module and identity mapping; that user-federation path remains unconfirmed. Scope: Islandora starter-site 1.11.0/Drupal 11 user authentication; internal JWTs and generic Drupal module availability are insufficient. Source: https://islandora.github.io/documentation/user-documentation/jwt-authentication/ (reviewed 2026-11-21). Supporting source: Starter-site dependencies — https://github.com/Islandora-Devops/islandora-starter-site/blob/1.11.0/composer.json.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Islandora (ISLE) deployment example; review the full linked installation instructions. Source: https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf (reviewed 2026-11-19). Deployment artifact: https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The ISLE Docker prerequisites call for at least 8 GB RAM, ideally 16 GB, plus Docker/Compose, Make and Git. This is a host setup prerequisite; database, Fedora, search, media processing, files and production replicas require additional workload and storage planning. Scope: ISLE Compose host prerequisite, not a complete production/HA capacity estimate. Source: https://islandora.github.io/documentation/installation/docker/docker-prereq/ (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 1.11.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Islandora starter-site distribution 1.11.0; Drupal, ISLE and other components have separate versions. Source: https://github.com/Islandora-Devops/islandora-starter-site/releases/tag/1.11.0 (reviewed 2026-11-19).







## Joomla!

Customer-operated content management and website publishing platform.

- Listing: https://launchinyourcloud.com/directory/joomla/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci, digitalocean, linode, vultr, northflank
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Joomla web application, database, web server and persistent site assets.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.joomla.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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


### Cloud deployment evidence

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

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

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

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

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


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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

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

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

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. miniOrange publishes a SAML service-provider extension and explicitly states Joomla 3/4/5/6 compatibility. This is a third-party extension with its own plan and support terms, not an included Joomla-core feature; validate the exact site version, provider and purchased plugin capabilities. Scope: Extension vendor documentation for Joomla 6-compatible SAML; not upstream Joomla support. Source: https://plugins.miniorange.com/joomla-single-sign-on-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Akamai documents deploying its Joomla Quick Deploy application through Cloud Manager, API, CLI or Terraform using StackScript 985372. This is a provider-maintained package/recipe; verify the installed Joomla version and upgrade path separately from the upstream release. Scope: Akamai/Linode Joomla application deployment recipe; not a Joomla upstream HA template. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla (reviewed 2026-11-20). Deployment artifact: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla. Artifact reference: Current provider StackScript 985372 examples; package/application versions can differ.

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

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

- Operating cost estimate: Not researched.

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







## Joplin Server

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

- Listing: https://launchinyourcloud.com/directory/joplin-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.
- Licensing model: source-available
- Installation: Cloudron package; Docker / Compose
- Architecture: Joplin Server, database and persistent attachment storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://joplinapp.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Server Personal Use License permits personal non-commercial use and restricts use by business entities and commercial sharing without written permission. This is not a default option for a 100-user business deployment. Desktop/client licences and releases do not establish server rights or Server 3.7.6 publication dates.

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

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


### Sources

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Joplin Server documents SAML user authentication using SP/IdP configuration and server environment settings. Its API and website must use the same base URL for SAML. Commercial organisational use requires the appropriate Server Business rights; this does not establish hosted Cloud plan entitlements. Scope: Self-hosted Joplin Server SAML; supported clients, session policy and business licensing must be checked. Source: https://joplinapp.org/help/apps/server/saml/ (reviewed 2026-11-20). Supporting source: Server Business and self-hosted licensing context — https://joplinapp.org/help/apps/joplin_server_business/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official server README provides versioned Docker images and a production PostgreSQL/Compose setup; the SQLite example is for testing. Configure public URL, database, credentials and reverse proxy before use. Select the appropriate commercial licence for an organisation. Scope: Joplin Server application plus separately provisioned production database and persistent content storage. Source: https://github.com/laurent22/joplin/blob/dev/packages/server/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/laurent22/joplin/blob/dev/docker-compose.server.yml. Artifact reference: dev (moving branch); use a compatible published server image tag.

- Minimum footprint / sizing: Documented. The Server Business guide lists two CPU cores/four threads, at least 4 GB RAM (8 GB recommended) and 50 GB SSD plus content growth. These are moderate-load deployment requirements, not the smaller Cloudron package allocation or a validated 100-user, 1 TB HA topology. Scope: Joplin Server Business self-hosted baseline; provider-package allocations, external content storage and redundancy are separate. Source: https://joplinapp.org/help/apps/joplin_server_business/ (reviewed 2026-11-20). Supporting source: Previously reviewed Cloudron app package allocation — https://www.cloudron.io/store/joplin-server.html.

- License pricing: Edition-dependent. Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization. Scope: Joplin Server; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Kestra Self-Hosted

Self-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.

- Listing: https://launchinyourcloud.com/directory/kestra/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the open-source Kestra platform; commercial Enterprise features and support are separate.
- Licensing model: open-source
- Installation: Docker on AWS EC2 or DigitalOcean Droplets, or Helm on AWS EKS, Google GKE or Azure AKS, with documented database and object storage services.
- Architecture: Customer-operated Kestra server and workers with PostgreSQL queue/repository state and object storage
- Operations: Customer manages server and worker capacity, PostgreSQL, object storage, plugins, credentials, network access, backups and upgrades.
- Product website: https://kestra.io/
- Source review: 2026-11-18; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Vendor guides cover AWS, Azure, Google Cloud and DigitalOcean deployments, including single-VM starting points and distributed Kubernetes installations. Customers operate the application, database and storage configuration; production ingress, authentication, credentials and high availability depend on the selected topology. Enterprise features and support are separately licensed. Kestra v2.0.11 updates dependencies for CVE-2026-45292 and other vulnerable libraries and adds CSRF tokens to Basic-auth browser requests. Recheck browser automation and authenticated API clients after upgrading.

The reviewed Kestra platform is Apache-2.0 licensed. Commercial Enterprise features and support are separately licensed and do not change the upstream open-source classification.

Kestra runs long-lived server and worker processes backed by PostgreSQL and object storage. The documented cloud paths use customer-configured compute or Kubernetes and managed database/storage services.


### Category fit

- workflow-orchestration: Orchestrates scheduled and event-driven data, infrastructure, business and AI workflows with customer-operated execution workers.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kestra.io/docs/installation/aws-ec2 (checked 2026-11-13). Source: https://kestra.io/docs/installation/kubernetes-aws-eks (checked 2026-11-13). 

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

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

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


### Cloud deployment evidence

- Kestra on Amazon EC2 with RDS and S3 (aws): https://kestra.io/docs/installation/aws-ec2
  The vendor documents deploying Kestra on a customer EC2 instance and moving database and internal storage to customer RDS PostgreSQL and S3. Secure the application endpoint and replace example broad credentials with least-privilege IAM.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Kestra on Amazon EKS with RDS and S3 (aws): https://kestra.io/docs/installation/kubernetes-aws-eks
  The vendor documents a distributed Helm deployment on customer EKS with RDS PostgreSQL, S3 storage and an AWS load balancer. Review cluster sizing, ingress, workload identity, backups and high-availability configuration.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Kestra on Google GKE with Cloud SQL and Cloud Storage (gcp): https://kestra.io/docs/installation/kubernetes-gcp-gke
  The vendor documents creating a GKE cluster, installing the Kestra Helm chart, configuring Cloud SQL PostgreSQL and Cloud Storage, and using Workload Identity. The operator manages the application and cluster configuration, access, persistence and availability.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Kestra on Azure AKS with PostgreSQL and Blob Storage (azure): https://kestra.io/docs/installation/kubernetes-azure-aks
  The vendor documents installing Kestra with Helm on a customer AKS cluster and configuring Azure Database for PostgreSQL, Blob Storage and ingress. Configure identities, secrets, network access and production availability for the selected deployment.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Kestra on DigitalOcean Droplets with Managed Database and Spaces (digitalocean): https://kestra.io/docs/installation/digitalocean-droplet
  The vendor documents creating a customer Droplet, installing Docker and Kestra, and connecting DigitalOcean Managed PostgreSQL and Spaces storage. The customer operates the application and configures network access, credentials, persistent storage and backups.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- AWS EC2 deployment with RDS and S3: https://kestra.io/docs/installation/aws-ec2

- AWS EKS deployment with RDS and S3: https://kestra.io/docs/installation/kubernetes-aws-eks

- Apache 2.0 project license: https://github.com/kestra-io/kestra/blob/develop/LICENSE

- Kestra on Google GKE with Cloud SQL and Cloud Storage: https://kestra.io/docs/installation/kubernetes-gcp-gke

- Kestra on Azure AKS with PostgreSQL and Blob Storage: https://kestra.io/docs/installation/kubernetes-azure-aks

- Kestra on DigitalOcean Droplets with Managed Database and Spaces: https://kestra.io/docs/installation/digitalocean-droplet

- Kestra v2.0.11 release: https://github.com/kestra-io/kestra/releases/tag/v2.0.11

### Licensing sources

- https://github.com/kestra-io/kestra/blob/develop/LICENSE

### Infrastructure sources

- https://kestra.io/docs/installation/aws-ec2

- https://kestra.io/docs/installation/kubernetes-aws-eks

- https://kestra.io/docs/installation/kubernetes-gcp-gke

- https://kestra.io/docs/installation/kubernetes-azure-aks

- https://kestra.io/docs/installation/digitalocean-droplet


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The Enterprise authentication guide documents OIDC single sign-on with providers such as Google, Microsoft, Okta and Keycloak. This does not establish SSO in the OSS edition. Scope: Self-managed Kestra Enterprise. Source: https://kestra.io/docs/enterprise/auth/sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Kestra v2.0.11 updates dependencies for CVE-2026-45292 and enforces CSRF tokens for Basic-auth browser requests. Upgrade to v2.0.11 or later and retest browser and API authentication flows. Scope: Upstream v2.0.11 release; consult the dependency advisories for component-specific ranges.. Source: https://github.com/kestra-io/kestra/releases/tag/v2.0.11 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Compose guide provides a standalone server with PostgreSQL and a moving develop-branch recipe. Its root user and Docker socket example is for development; production hardening and licensed images are separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://kestra.io/docs/installation/docker-compose (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/kestra-io/kestra/develop/docker-compose.yml. Artifact reference: develop (moving branch); development example.

- Minimum footprint / sizing: Documented. The official EC2 guide starts Kestra at 2 vCPUs and 4 GiB RAM, suggesting t3.medium for its example. PostgreSQL, object storage, task execution and redundancy are separate capacities. Validate workflow/task concurrency and data movement; the example host is not a complete 1 TB HA production design. Scope: Official AWS application starting point with separately configured database and object storage. Source: https://kestra.io/docs/installation/aws-ec2 (reviewed 2026-11-20).

- License pricing: Documented. The published v2.0.11 core is Apache-2.0 licensed. Enterprise authentication and other commercial features require their own edition agreement and are not granted by the OSS licence. Infrastructure, database/object storage, task execution and support costs are separate from software licensing. Scope: Published Kestra OSS core versus self-hosted Enterprise features. Source: https://github.com/kestra-io/kestra/blob/v2.0.11/LICENSE (reviewed 2026-11-20). Supporting source: Self-managed Enterprise SSO scope — https://kestra.io/docs/enterprise/auth/sso.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Kestra v2.0.11 was published November 17, 2026. It updates dependencies for CVE-2026-45292 and other vulnerable libraries and enforces CSRF tokens on Basic-auth browser requests. Scope: Upstream Kestra 2.0 release. Source: https://github.com/kestra-io/kestra/releases/tag/v2.0.11 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Kestra 2.0.11 dependency and CSRF update (security-advisory): Kestra v2.0.11 updates dependencies for CVE-2026-45292 and enforces CSRF tokens for Basic-auth browser requests. Scope: Upstream v2.0.11 release; consult the dependency advisories for component-specific ranges. Conditions: Browser behavior changes when Basic authentication is used; dependency exposure depends on the deployed components. Action: Upgrade to v2.0.11 or later and retest browser and API authentication flows. Source: https://github.com/kestra-io/kestra/releases/tag/v2.0.11; reviewed 2026-11-18.




## LibreChat Self-Hosted

Self-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.

- Listing: https://launchinyourcloud.com/directory/librechat/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT
- Licensing model: open-source
- Installation: Official Railway one-click template or Docker on a DigitalOcean Ubuntu Droplet
- Architecture: Containerized web and API services with application databases, retrieval services and customer-configured model endpoints
- Operations: Customer manages the Railway project or DigitalOcean Droplet, application secrets, model credentials, data services, backups, scaling and upgrades. Railway operates its platform; Droplet users also maintain the operating system and Docker runtime.
- Product website: https://www.librechat.ai/
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

The Railway path runs in the customer's project on platform-managed infrastructure; the DigitalOcean path uses a customer-operated Droplet. External model, embedding, search and tool providers receive data according to customer configuration. Review generated secrets, public networking, persistent data services and image updates before production use.

LibreChat is MIT-licensed. The licenses and commercial terms of configured model providers, tools and external services are separate.

LibreChat runs persistent application, database and retrieval containers in a Railway project or on a DigitalOcean Droplet.


### Category fit

- ai-applications-rag: Provides self-hosted multi-model chat, agents, file-backed retrieval and tool use over customer-selected model and data services.

- ai-tools: Provides a self-hosted interface and orchestration layer for model endpoints, agents, MCP tools, authentication and administrative controls.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.librechat.ai/docs/remote/railway (checked 2026-11-15). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.librechat.ai/docs/remote/digitalocean (checked 2026-11-15). 


### Cloud deployment evidence

- LibreChat one-click deployment on Railway (railway): https://www.librechat.ai/docs/remote/railway
  LibreChat documents creating a Railway account, reviewing the template's three containers and environment variables, deploying the services and accessing the resulting LibreChat URL in the customer's Railway project.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- LibreChat deployment on DigitalOcean (digitalocean): https://www.librechat.ai/docs/remote/digitalocean
  The upstream guide creates an Ubuntu Droplet in the customer DigitalOcean project, configures a user and firewall, then links to the Docker installation steps. The example is for a small personal deployment, not a production sizing guarantee.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Community and maintenance

LibreChat documents a community of hundreds of contributors and maintains its implementation in a public upstream repository. Contributor history establishes active project participation; it does not establish support for a specific Railway template release.

Reviewed 2026-11-15.

- LibreChat project and community: https://www.librechat.ai/about

- LibreChat contributor history: https://github.com/LibreChat-AI/LibreChat/graphs/contributors

### Sources

- LibreChat Railway deployment: https://www.librechat.ai/docs/remote/railway

- LibreChat project, self-hosting and MIT license: https://www.librechat.ai/about

- LibreChat upstream repository: https://github.com/LibreChat-AI/LibreChat

- LibreChat contributor history: https://github.com/LibreChat-AI/LibreChat/graphs/contributors

- LibreChat deployment on DigitalOcean: https://www.librechat.ai/docs/remote/digitalocean

### Licensing sources

- https://www.librechat.ai/about

### Infrastructure sources

- https://www.librechat.ai/docs/remote/railway

- https://www.librechat.ai/docs/remote/digitalocean


### 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 official self-hosted authentication guide documents OAuth2/OpenID Connect and SAML, with separately configured LDAP and local accounts. Configure the selected provider, registration policy, account linking and administrator recovery; external model credentials are a separate authentication surface. Scope: Self-hosted LibreChat user authentication. Source: https://www.librechat.ai/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 Railway guide describes its repository deploy button, three-container configuration and required environment variables. Review persistence and optional integrations before production; the one-click recipe does not establish a minimum production footprint. Scope: LibreChat Railway deployment guide; moving template and configured features. Source: https://www.librechat.ai/docs/remote/railway (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The Docker guide lists 1 vCPU and 1 GiB RAM minimum for LibreChat containers, recommending at least 2 GB allocated to Docker with the default backing services. MongoDB, search, RAG/pgvector, storage and HA need sizing; locally hosted models require additional compute and often GPUs. Scope: Official Docker starting profile; model inference and production HA excluded. Source: https://www.librechat.ai/docs/local/docker (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is MIT licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/danny-avila/LibreChat/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## LiquidFiles (Self-Hosted Virtual Appliance)

Commercial self-hosted appliance for controlled external file delivery and shared files.

- Listing: https://launchinyourcloud.com/directory/liquidfiles/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: VM image
- Architecture: LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image.
- 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.liquidfiles.com/install/ec2.html
- 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 documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.

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

LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial self-hosted appliance for controlled external file delivery and shared files.

- data-rooms-ma-document-management: Commercial self-hosted appliance for controlled external file delivery and shared files.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/ec2.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/azure.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/digital_ocean.html (checked 2026-11-19). 


### Cloud deployment evidence

- EC2 Guide (aws): https://docs.liquidfiles.com/install/ec2.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.liquidfiles.com/install/azure.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- DigitalOcean Guide (digitalocean): https://docs.liquidfiles.com/install/digital_ocean.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- EC2 Guide: https://docs.liquidfiles.com/install/ec2.html

- Azure Guide: https://docs.liquidfiles.com/install/azure.html

- DigitalOcean Guide: https://docs.liquidfiles.com/install/digital_ocean.html

- License Overview: https://docs.liquidfiles.com/license/overview.html

- v4.3.x Release Notes: https://docs.liquidfiles.com/release_notes/version_4-3-x.html

### Licensing sources

- https://docs.liquidfiles.com/license/overview.html

### Infrastructure sources

- https://docs.liquidfiles.com/install/ec2.html

- https://docs.liquidfiles.com/install/azure.html

- https://docs.liquidfiles.com/install/digital_ocean.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 appliance supports SAML sign-on, metadata exchange, email NameID and group assignment, with optional per-group enforcement. The vendor documents a safeguard local-login path and warns against forcing every external user into the internal IdP. Scope: Self-hosted LiquidFiles SAML authentication. Source: https://docs.liquidfiles.com/authentication/sso_using_saml.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 vendor documents deployment from its EC2 appliance AMI, with cloud-instance, storage and network configuration steps. The appliance contains its own OS; this is a vendor appliance installation path, not an upstream Terraform or CloudFormation template. Select the current regional image and licence. Scope: Official AWS appliance deployment; infrastructure provisioning remains customer work. Source: https://docs.liquidfiles.com/install/ec2.html (reviewed 2026-11-20). Deployment artifact: https://docs.liquidfiles.com/install/ec2.html. Artifact reference: Regional AMI selection described in vendor guide.

- Minimum footprint / sizing: Documented. The vendor recommends 1–2 CPUs, 2 GB RAM and 10 GB disk plus transfer storage. One GB RAM is for testing and can swap. File volume, disk/network throughput, backup and HA must be sized separately; the appliance OS is included. Scope: Vendor appliance baseline; transfer storage and HA excluded. Source: https://docs.liquidfiles.com/install/system_requirements.html (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: LiquidFiles (Self-Hosted Virtual Appliance); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.liquidfiles.com/license/overview.html (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Live Helper Chat

Self-hosted customer live chat and support communications.

- Listing: https://launchinyourcloud.com/directory/livehelperchat/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- 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: VM image; Package / binary installer
- Architecture: PHP application and database on a customer DigitalOcean Droplet.
- 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://doc.livehelperchat.com/docs/development/hosting-on-digitalocean
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Chat integrations, email and video services can add external processors. Upstream Apache-2.0 terms and DigitalOcean image maintenance are distinct.

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

PHP application and database on a customer DigitalOcean Droplet. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted customer live chat and support communications.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean (checked 2026-11-19). 


### Cloud deployment evidence

- LHC DigitalOcean Docs (digitalocean): https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean
  PHP application and database on a customer DigitalOcean Droplet. Chat integrations, email and video services can add external processors. Upstream Apache-2.0 terms and DigitalOcean image maintenance are distinct.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes remdex, doncaz, mysubcult, 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/LiveHelperChat/livehelperchat/graphs/contributors

- Upstream project: https://github.com/LiveHelperChat/livehelperchat

### Sources

- LHC DigitalOcean Docs: https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean

- GitHub LICENSE (Apache-2.0): https://raw.githubusercontent.com/LiveHelperChat/livehelperchat/master/LICENSE

- GitHub Releases: https://github.com/LiveHelperChat/livehelperchat/releases

### Licensing sources

- https://raw.githubusercontent.com/LiveHelperChat/livehelperchat/master/LICENSE

### Infrastructure sources

- https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean


### 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 guide documents custom signed auto-login links for existing operator IDs/usernames using a shared secret and optional expiry. Mailbox OAuth and these links do not by themselves establish a supported SAML/OIDC identity-provider integration, account lifecycle or role mapping. Confirm the intended external authentication design. Scope: Custom auto-login mechanism confirmed; enterprise identity federation remains unconfirmed. Source: https://doc.livehelperchat.com/docs/users/auto-login (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 guide installs an upstream release archive, optionally with dependencies bundled, on a PHP/web-server/database host. Configure database credentials, writable directories, initial admin access and the chat widget; Docker is a separate linked option. Use a version-matched package rather than an unpinned archive. Scope: Upstream PHP installation; distinct from the DigitalOcean packaged image. Source: https://doc.livehelperchat.com/docs/install (reviewed 2026-11-20). Deployment artifact: https://github.com/LiveHelperChat/livehelperchat/releases/tag/5.01v. Artifact reference: 5.01v.

- Minimum footprint / sizing: Sources checked — unresolved. The installation guide specifies PHP, web-server and database dependencies. Its DigitalOcean guide says the smallest droplet can run the package but does not identify a current numeric whole-stack production capacity. Confirm operator/chat concurrency, mail workers, optional co-browsing, retention and HA; do not reuse the guide's small-droplet price as a current cost quote. Scope: Supported software topology; current workload-sized CPU/RAM/storage remains unconfirmed. Source: https://doc.livehelperchat.com/docs/install (reviewed 2026-11-20). Supporting source: DigitalOcean package and optional service overhead — https://doc.livehelperchat.com/docs/development/hosting-on-digitalocean.

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

- Operating cost estimate: Not researched.

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







## MailWizz

Commercial self-hosted email marketing application.

- Listing: https://launchinyourcloud.com/directory/mailwizz/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: PHP application, MySQL or MariaDB, web server and scheduled jobs 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.mailwizz.com/integrations/vps-providers/amazon-aws/
- 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 names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.

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

PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Commercial self-hosted email marketing application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.mailwizz.com/integrations/vps-providers/amazon-aws/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.mailwizz.com/integrations/vps-providers/digitalocean/ (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.mailwizz.com/integrations/vps-providers/linode/ (checked 2026-11-19). 


### Cloud deployment evidence

- MailWizz AWS (aws): https://www.mailwizz.com/integrations/vps-providers/amazon-aws/
  PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. The vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- MailWizz DO (digitalocean): https://www.mailwizz.com/integrations/vps-providers/digitalocean/
  PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. The vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- MailWizz Linode (linode): https://www.mailwizz.com/integrations/vps-providers/linode/
  PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. The vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- MailWizz AWS: https://www.mailwizz.com/integrations/vps-providers/amazon-aws/

- MailWizz DO: https://www.mailwizz.com/integrations/vps-providers/digitalocean/

- MailWizz Linode: https://www.mailwizz.com/integrations/vps-providers/linode/

- MailWizz License: https://www.mailwizz.com/legal/regular-license/

- MailWizz Blog: https://www.mailwizz.com/blog/

### Licensing sources

- https://www.mailwizz.com/legal/regular-license/

### Infrastructure sources

- https://www.mailwizz.com/integrations/vps-providers/amazon-aws/

- https://www.mailwizz.com/integrations/vps-providers/digitalocean/

- https://www.mailwizz.com/integrations/vps-providers/linode/


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 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. A vendor staff reply suggests developing an OpenID Connect integration or using a third-party SSO provider, rather than documenting a shipped integration. The current public material reviewed does not establish a version-matched SAML/OIDC login setup, entitlement or user/role mapping for MailWizz. Keep this as an integration question. Scope: Vendor staff discussion dated 2023-12-12; not proof of current built-in SSO. Source: https://forum.mailwizz.com/threads/single-sign-on-sso-to-mailwizz.8853/ (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 install guide deploys the licensed application archive to a PHP web host and completes its web installer, then removes the install directory. Configure database, secrets, cron jobs and delivery/bounce services. The application archive is a licensed artifact, not a public Terraform/Helm bundle; select a supported release through the vendor channel. Scope: Commercial application-package installation; no public versioned IaC bundle established. Source: https://www.mailwizz.com/kb/install-steps/ (reviewed 2026-11-20). Supporting source: Application and mail-processing setup — https://www.mailwizz.com/kb/getting-started-steps/.

- Minimum footprint / sizing: Sources checked — unresolved. The vendor lists Linux, PHP, a web server, MySQL/MariaDB and OS cron access, recommending a properly configured VPS. It does not specify a numeric whole-stack CPU/RAM/storage minimum. Confirm campaign/send rate, subscribers, delivery services, database growth and redundancy before estimating the requested HA workload. Scope: Current vendor runtime guidance; workload-specific host sizing remains unconfirmed. Source: https://www.mailwizz.com/faq/what-kind-of-hosting-do-i-need/ (reviewed 2026-11-20).

- License pricing: Documented. MailWizz offers proprietary Regular and Extended licences, each for one installation; the vendor requires Extended for a paid SaaS email-marketing service. Additional installations need separate licences. Confirm the applicable agreement, support/update term and HA/staging entitlements; hosting and message-delivery charges are separate, and no current numeric licence quote is recorded here. Scope: Current commercial licence units and use restrictions, refining the earlier generic software-terms fact. Source: https://www.mailwizz.com/kb/what-license-do-i-need/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Mautic Self-Hosted

Self-hosted marketing automation for email campaigns, lead nurturing, forms and landing pages.

- Listing: https://launchinyourcloud.com/directory/mautic/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3-or-later core; separately selected integrations, hosting and support may carry their own terms
- Licensing model: open-source
- Installation: Production package or Composer installation on a PHP web server
- Architecture: Customer-operated PHP application, database and scheduled background jobs
- Operations: Customer manages the web/database servers, scheduled jobs, updates, backups and email-delivery integration.
- Product website: https://mautic.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Install the production package or documented Composer distribution rather than the GitHub development checkout. Email marketing still requires configured delivery infrastructure or an external provider. Self-hosting does not by itself establish privacy compliance, consent or deliverability.

The listed self-hosted Mautic core is GPLv3-or-later. External delivery services, managed hosting, implementation and support can be paid without changing the core software licensing model; separately installed components retain their own terms.

The installation requires a persistent web server, supported database server and configured email transport; scheduled cron processing handles queued activity.


### Category fit

- marketing-automation: Email campaigns, forms, landing pages, lead nurturing and marketing automation; delivery services and consent processes remain the operator's responsibility.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kb.mautic.org/article/how-to-set-up-a-staging-server-to-test-new-mautic-releases.html (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kb.mautic.org/article/how-to-set-up-a-staging-server-to-test-new-mautic-releases.html (checked 2026-11-12). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kb.mautic.org/article/how-to-set-up-a-staging-server-to-test-new-mautic-releases.html (checked 2026-11-12). 


### Cloud deployment evidence

- Mautic production and staging instances on AWS EC2 (aws, digitalocean, linode): https://kb.mautic.org/article/how-to-set-up-a-staging-server-to-test-new-mautic-releases.html
  The official project guide names AWS, DigitalOcean and Linode as hosts of the Mautic production application, then describes cloning that application to staging; the worked snapshot examples use EC2 and a DigitalOcean Droplet. This is a project hosting compatibility statement rather than a storage integration. Follow current Mautic, PHP/database and production security requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production installation: https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html

- Marketing automation capabilities: https://mautic.org/features/

- Core license: https://raw.githubusercontent.com/mautic/mautic/7.x/LICENSE.txt

### Licensing sources

- https://raw.githubusercontent.com/mautic/mautic/7.x/LICENSE.txt

- https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html

### Infrastructure sources

- https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.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: Documented. The versioned Mautic 7 guide documents SAML login and login-time user creation. Configure provider metadata, claim mappings and a restricted default role; this is not evidence of SCIM lifecycle provisioning. Scope: Mautic 7 SAML integration. Source: https://docs.mautic.org/en/7.0/authentication/authentication.html (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Mautic 7 guide documents a production release package or Composer installation. Configure the supported PHP/database stack, writable directories and scheduled tasks; uploading a package alone does not complete operations. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The versioned installation guide checks PHP/database compatibility, disk space and PHP resource limits, but does not establish a complete production CPU/RAM/storage baseline. PHP memory_limit is a process allowance, not whole-server capacity; size contacts, campaign traffic, queues, database growth and HA separately. Scope: Versioned Mautic 7 installation checks; whole-stack sizing remains unconfirmed. Source: https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html (reviewed 2026-11-20).

- License pricing: Documented. Mautic core is available under GPLv3 without a core subscription fee. Hosting, delivery providers, third-party plugins, professional support and any extended-support service have their own charges and terms; the source licence does not include those services. Scope: Published Mautic 7.2.2 core licence; not a hosted-service or operating-cost price. Source: https://github.com/mautic/mautic/blob/7.2.2/LICENSE.txt (reviewed 2026-11-20). Supporting source: Official ways to run Mautic — https://mautic.org/getting-started/.

- Operating cost estimate: Not researched.

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







## Meilisearch Community Edition

Self-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.

- Listing: https://launchinyourcloud.com/directory/meilisearch-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for Community Edition. Enterprise Edition uses a BUSL license, cannot be freely used in production and requires a commercial agreement for production self-hosting.
- Licensing model: open-source
- Installation: Install the official binary on an AWS EC2 instance, Google Compute Engine VM or DigitalOcean Droplet, then configure a dedicated system user, systemd service, persistent data directory, reverse proxy and HTTPS.
- Architecture: Customer-operated search server with persistent index storage and optional external embedding or language-model integrations
- Operations: Customer manages the VM, operating system, network rules, master key, TLS, persistent indexes, backups, monitoring, capacity and version upgrades.
- Product website: https://www.meilisearch.com/
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

The reviewed provider guides deploy a customer-operated server rather than a managed Meilisearch service. Meilisearch Cloud is the vendor-recommended production option, but the Community Edition is explicitly available for independent hosting. Community Edition does not include Enterprise-only sharding, so the documented VM paths do not establish a highly available or horizontally sharded topology. Configured remote embedders or LLM providers can receive indexed or query content; user-provided vectors and customer-selected local endpoints can produce a different data boundary. Meilisearch 1.56.1 and 1.55.1 were security maintenance releases; current 1.57.0 includes those fixes. Affected deployments should move to 1.57.0 or an appropriate later supported patch and review the vendor's branch guidance.

This listing is scoped specifically to the MIT-licensed Community Edition. The separately available Enterprise Edition uses a BUSL license, cannot be used freely in production and reserves sharding as its exclusive feature.

Each reviewed cloud guide runs Meilisearch as a persistent Linux service on a customer-owned VM. The customer provisions and sizes the server and storage; these paths are neither serverless nor vendor-managed.


### Category fit

- databases-vector: Application search engine with typo-tolerant full-text search and semantic or hybrid retrieval over vector embeddings.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp (checked 2026-11-16). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean (checked 2026-11-16). 


### Cloud deployment evidence

- Meilisearch Community Edition on Amazon EC2 (aws): https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws
  The vendor documents a production-oriented installation on a customer AWS EC2 instance, including the official binary installer, dedicated service account, persistent data directory, systemd service and network security. The customer operates the VM and search service; this is separate from Meilisearch Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Meilisearch Community Edition on Google Compute Engine (gcp): https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp
  The vendor documents a production-oriented installation on a customer Google Compute Engine VM with billing enabled, including the official binary installer, dedicated service account, persistent data directory, systemd service and firewall configuration. The customer operates the VM and search service.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Meilisearch Community Edition on a DigitalOcean Droplet (digitalocean): https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean
  The vendor documents installation on a customer DigitalOcean Droplet using its official binary installer, persistent service configuration and production security steps. This is a customer-operated Droplet, not a managed Meilisearch Cloud deployment.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Community and maintenance

The official repository publishes continuing versioned releases and public contribution workflows, while the vendor maintains a broader catalog of open-source integrations and deployment components.

Reviewed 2026-11-16.

- Upstream project and contribution workflow: https://github.com/meilisearch/meilisearch

- Current upstream releases: https://github.com/meilisearch/meilisearch/releases

- Official open-source project catalog: https://www.meilisearch.com/open-source

### Sources

- AWS EC2 deployment: https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws

- Google Compute Engine deployment: https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp

- DigitalOcean Droplet deployment: https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean

- Production self-hosting guidance: https://www.meilisearch.com/docs/resources/self_hosting/deployment/running_production

- Full-text, semantic, hybrid and vector-search capabilities: https://www.meilisearch.com/docs/getting_started/features

- Community and Enterprise edition boundaries: https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition

- Community Edition MIT license: https://github.com/meilisearch/meilisearch/blob/main/LICENSE

- Meilisearch v1.57.0 release: https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0

- Meilisearch v1.56.1 security release: https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1

- Meilisearch v1.55.1 security release: https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1

### Licensing sources

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

- https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition

### Infrastructure sources

- https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws

- https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp

- https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean


### Buyer diligence


Research coverage: 7/12 fields (58%); 6 documented, 1 unresolved. Coverage is not a feature score.

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Explicitly unsupported. The vendor comparison explicitly excludes SAML/OIDC SSO from self-hosted open source and places it in Enterprise. The Community engine’s API keys and tenant tokens are not an organization SSO integration. Scope: Self-hosted open-source/Community tier in the vendor comparison. Source: https://www.meilisearch.com/oss-to-cloud (reviewed 2026-11-16).

- SCIM provisioning: Not researched.

- Compliance attestations: Documented. The vendor comparison explicitly excludes the vendor’s SOC 2 Type II offering from self-hosted open source. Hosted-service assurance does not transfer to a customer-operated Community installation; assess the operator’s environment separately. Scope: Vendor SOC 2 offering versus customer-operated Community engine; not a claim that an operator cannot obtain its own attestation. Source: https://www.meilisearch.com/oss-to-cloud (reviewed 2026-11-16).

- Security controls: Documented. Self-hosted Meilisearch uses a master key of at least 16 bytes and scoped API keys for requests. Keep master/admin keys off public frontends and use a search-scoped key where appropriate. This API authorization does not establish SSO or SCIM. Current advisory review: Meilisearch 1.56.1 and 1.55.1 identify important security fixes and urge affected users to upgrade; 1.57.0 includes those fixes. Upgrade to 1.57.0 or a later supported release, or the applicable fixed patch for a maintained branch. Scope: Self-hosted search engine API authorization; not Meilisearch Cloud account SSO Upstream 1.55 and 1.56 maintenance lines; the release notes do not provide one consolidated affected-version range.. Source: https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://www.meilisearch.com/docs/resources/self_hosting/security/basic_security. Supporting source: v1.55.1 security release — https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1. Supporting source: v1.57.0 — https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The VM guides install an upstream binary, dedicated system user and systemd service, with persistent data and HTTPS/reverse-proxy configuration. Release assets are versioned separately from any cloud image; choose a platform-compatible Community Edition asset. Scope: Community Edition VM installation; not Meilisearch Cloud or Enterprise. Source: https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws (reviewed 2026-11-16). Supporting source: Versioned upstream release assets — https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0.

- Minimum footprint / sizing: Sources checked — unresolved. The indexing guide ties memory and disk use to document fields, payload sizes and batch size. It warns that large payloads can exhaust RAM. The reviewed guide provides tuning guidance, not a universal production CPU/RAM minimum. Scope: Self-hosted indexing workload guidance; capacity requires representative data and benchmarks. Source: https://www.meilisearch.com/blog/indexing-optimization-guide (reviewed 2026-11-16).

- License pricing: Documented. This listing is scoped specifically to the MIT-licensed Community Edition. The separately available Enterprise Edition uses a BUSL license, cannot be used freely in production and reserves sharding as its exclusive feature. Scope: Meilisearch Community Edition: software license terms; infrastructure and operating costs are separate. Source: https://github.com/meilisearch/meilisearch/blob/main/LICENSE (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Meilisearch v1.57.0 was published November 16, 2026, and includes the fixes from the 1.56.1 and 1.55.1 security maintenance releases. Scope: Upstream Meilisearch Community release. Source: https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0 (reviewed 2026-11-18). Supporting source: v1.56.1 security release — https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1. Supporting source: v1.55.1 security release — https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1.




### Security and lifecycle reviews

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

- Meilisearch November 2026 security maintenance (security-advisory): Meilisearch 1.56.1 and 1.55.1 identify important security fixes and urge affected users to upgrade; 1.57.0 includes those fixes. Scope: Upstream 1.55 and 1.56 maintenance lines; the release notes do not provide one consolidated affected-version range. Conditions: Applicability depends on the installed branch and the fixes listed in its release notes. Action: Upgrade to 1.57.0 or a later supported release, or the applicable fixed patch for a maintained branch. Source: https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1; reviewed 2026-11-18. Supporting source: v1.55.1 security release — https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1. Supporting source: v1.57.0 — https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0.




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







## Metabase Self-Hosted

Business intelligence and dashboards on your infrastructure.

- Listing: https://launchinyourcloud.com/directory/metabase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source and commercial options
- Licensing model: open-source
- Installation: Docker image or Java JAR
- Architecture: Customer-operated application and database
- Operations: Your team manages hosting, upgrades and the application database.
- Product website: https://www.metabase.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Metabase documents self-hosting on AWS, Google Cloud, Azure and DigitalOcean. This entry covers self-hosting rather than Metabase Cloud. Infrastructure sizing, the application database and feature entitlements depend on the selected edition. Metabase's critical security advisory affects 0.64.0 through 0.64.3.3 and corresponding Enterprise versions. Self-hosted operators should use Open Source 0.64.3.4 or later, or Enterprise 1.64.3.4 or later. The hardening release strengthens API validation and permission checks, limits metadata exposure, improves deactivated-user session handling, removes database secrets from serialization exports, and adds optional session-signing and encryption keys.

The self-hosted platform offers an AGPL Open Source Edition alongside commercial capabilities and licensing. The classification covers the platform family described in this entry.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- data-analytics: Business intelligence and dashboards on your infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 


### Cloud deployment evidence

- Metabase production hosting compatibility (aws, azure, gcp, digitalocean): https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale
  The vendor names AWS Elastic Beanstalk and Docker, and explicitly identifies Google Cloud, Azure and DigitalOcean as alternative hosts for the Metabase application. Pair this compatibility statement with the current installation guide and a production application database; this is self-hosting, separate from Metabase Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installing Metabase: https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase

- Production hosting options: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale

- Licensing and edition terms: https://www.metabase.com/license

- Metabase 64 critical security update: https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw

### Licensing sources

- https://www.metabase.com/license

### Infrastructure sources

- https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase

- https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale


### 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. SAML authentication is available on Pro and Enterprise for self-hosted deployments. This does not establish SAML for the free/open-source edition. Scope: Self-hosted Pro and Enterprise. Source: https://www.metabase.com/docs/latest/people-and-groups/authenticating-with-saml (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Pro and Enterprise support SCIM. The documentation names Okta and Microsoft Entra ID; Okta supports user/group provisioning while Entra supports user provisioning only. Scope: Self-hosted Pro and Enterprise; identity-provider behavior differs. Source: https://www.metabase.com/docs/latest/people-and-groups/user-provisioning (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies separate Open Source and Enterprise images and publishes Compose examples. Production needs an external supported application database; embedded H2 is evaluation-only. Pin the selected image, configure persistence, TLS and backup, and do not assume an officially supported Helm chart. Scope: Official self-hosted Docker/Compose distributions. Source: https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker (reviewed 2026-11-20). Deployment artifact: https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker#example-docker-compose-yaml-file. Artifact reference: v65 documentation; select a compatible image tag.

- Minimum footprint / sizing: Documented. The vendor gives an application baseline of 1 core/1 GB, plus 1 core/2 GB per 20 concurrent users. The application database starts at 1 core/2 GB and needs additional capacity. Query databases, HA replicas, storage and background jobs are extra; total registered users alone is insufficient for sizing. Scope: Post-v52 production sizing guidance by concurrent users, not registered accounts. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production (reviewed 2026-11-20).

- License pricing: Documented. The repository separates AGPL core code from the commercial enterprise directory and enterprise binaries. Self-hosted Pro/Enterprise features require commercial terms; the core licence does not establish paid-edition prices, support or hosting cost. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/metabase/metabase/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Metabase 64 critical security update (security-advisory): The advisory records API, permission, metadata, session and serialization hardening in the 64 release line. Scope: Open Source 0.64.0 to before 0.64.3.4 and corresponding Pro/Enterprise 1.64 versions. Conditions: Self-hosted edition, configured integrations and exposed endpoints determine which fixes apply; optional key settings need explicit configuration. Action: Upgrade Open Source to at least 0.64.3.4 or Pro/Enterprise to at least 1.64.3.4 and follow the vendor security checklist. Source: https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw; reviewed 2026-11-17.




## n8n Self-Hosted

Automate integrations and business processes with a customer-hosted workflow editor and runtime.

- Listing: https://launchinyourcloud.com/directory/n8n/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
- Licensing model: source-available
- Installation: Docker Compose with persistent data; database and worker topology selected for workload
- Architecture: Customer-operated workflow runtime, credentials store and persistent execution data
- Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
- Product website: https://n8n.io/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.

The core is under the Sustainable Use License with use restrictions, not an OSI open-source license. Enterprise-marked code requires a separate commercial Enterprise license. A free self-hosted option does not change the core license model.

Reviewed topology runs long-lived containers and persistent workflow/credential storage. Event triggers do not make the self-hosted control/runtime stack function-based serverless.


### Category fit

- workflow-automation: Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.

- ai-tools: Orchestrates AI providers, agents, tools and memory as workflows. Model inference and external service dependencies are configured separately.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner (checked 2026-11-12). 


### Cloud deployment evidence

- n8n deployment on AWS (aws): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws
  Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Azure (azure): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure
  Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Google Cloud Run (gcp): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run
  The project documents Cloud Run deployment. Its easy mode is not the production configuration; follow the durable-mode guidance for production and review execution and persistence constraints.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on DigitalOcean (digitalocean): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Heroku (heroku): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Hetzner (hetzner): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner
  The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Current self-hosted Docker Compose guide: https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose

- Official license boundaries: https://github.com/n8n-io/n8n/blob/master/LICENSE.md

- Workflow automation project: https://github.com/n8n-io/n8n

- AI workflow components and integrations: https://docs.n8n.io/build/integrate-ai.md

- n8n self-hosted deployment on DigitalOcean: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean

- n8n self-hosted deployment on Heroku: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku

- n8n self-hosted deployment on Hetzner: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner

- n8n@2.48.6 release: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6

- n8n@1.123.99 release: https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99

- Patched V8 runtime integration: https://github.com/n8n-io/n8n/pull/43703

### Licensing sources

- https://github.com/n8n-io/n8n/blob/master/LICENSE.md

### Infrastructure sources

- https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose


### 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. SAML or OIDC SSO is documented for self-hosted Business and Enterprise. Instance-owner or administrator privileges are required to configure it. Scope: Self-hosted Business and Enterprise; not the unlicensed Community edition. Source: https://docs.n8n.io/deploy/host-n8n/configure-n8n/security/configure-sso.md (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor documents Linux Compose installation and links n8n-hosting configurations for different architectures. Configure persistent data, database, encryption key, domain and TLS; choose the production topology rather than treating the minimal single-server recipe as HA. Scope: Official self-hosted Compose deployment. Source: https://docs.n8n.io/hosting/installation/server-setups/docker-compose/ (reviewed 2026-11-20). Deployment artifact: https://github.com/n8n-io/n8n-hosting. Artifact reference: Select and pin a compatible versioned application image.

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted memory guide ties RAM usage to execution concurrency, JSON/binary payload size and workflow behavior. It does not establish one safe server minimum. Size main processes, workers/task runners, PostgreSQL, queue-mode Redis, binary storage and HA after measuring representative workflows. Scope: Self-hosted workflow-dependent sizing; complete production footprint unresolved. Source: https://docs.n8n.io/hosting/scaling/memory-errors/ (reviewed 2026-11-20). Supporting source: Production topology and dependencies — https://docs.n8n.io/deploy/host-n8n/install-options/production-requirements.md.

- License pricing: Documented. The Sustainable Use License permits internal business or non-commercial/personal use under its conditions. Enterprise files are separately licensed, and other branches have specific restrictions. Commercial redistribution or embedded use must be checked against vendor terms; self-hosting does not grant every Enterprise feature. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/n8n-io/n8n/master/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. n8n n8n@2.48.6 was published November 19, 2026. Official 2.x images use a patched Node 26.13.0 runtime carrying a V8 process-abort fix. Maintained 1.x users should use n8n@1.123.99 or later, which moves to Node 24.22.3. Scope: Upstream n8n 2.x release; the 1.x maintenance line has a separate fixed build. Source: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/n8n-io/n8n/releases/tag/n8n%402.47.7. Supporting source: Maintained 1.x runtime fix — https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99. Supporting source: Patched V8 runtime integration — https://github.com/n8n-io/n8n/pull/43703.







## NetBird Self-Hosted Community Edition

Open-source zero-trust networking control plane self-hosted on a customer cloud VM.

- Listing: https://launchinyourcloud.com/directory/netbird-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, hetzner, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.
- Licensing model: open-source
- Installation: Official self-hosting script and Docker Compose on a Linux VM; advanced deployment supports a custom identity provider
- Architecture: Customer-operated management, signal, relay or STUN, dashboard, identity and state services; peers form direct WireGuard tunnels where possible
- Operations: Customer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.
- Product website: https://netbird.io/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This entry covers the Community self-hosted edition, not NetBird Cloud or the Enterprise Commercial License. The quickstart is single-node; high availability and commercial SCIM or traffic-flow features are outside this edition. The cited advanced guide also establishes DigitalOcean, Hetzner and OCI paths. Its multi-container configuration differs from the combined-server quickstart; preserve version and migration boundaries. The pinned quickstart script still uses latest for several images, which must be locked separately.

Community code is open source but mixed-licensed: most repository code is BSD-3-Clause, while server control-plane directories are AGPL-3.0. Enterprise-licensed features are excluded.

The quickstart deploys the full control plane as persistent containers on a customer-operated Linux VM.


### Category fit

- identity-access-management: Provides self-hosted identity-aware zero-trust network access with users, policies, device peers, routes and private-resource controls.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 


### Cloud deployment evidence

- NetBird self-hosted control plane on a cloud VM (aws, azure, gcp, digitalocean, hetzner, oci): https://docs.netbird.io/selfhosted/selfhosted-guide
  The advanced self-hosting guide explicitly names AWS, DigitalOcean, Hetzner, Google Cloud and Azure VMs, uses Hetzner for its worked installation and documents OCI guest-firewall requirements for UDP 3478. It describes the older multi-container layout; the current quickstart uses the combined netbird-server layout. Select compatible files and configure provider and guest firewalls for the chosen architecture.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Community Edition.


### Community and maintenance

The reviewed upstream contributor history includes mlsmaycon, pascal-fischer, lixmal, with sustained contributions alongside the dated application release and public installation history. This establishes maintained community participation, not a commercial support, compliance or capacity guarantee.

Reviewed 2026-11-19.

- Upstream contributor history: https://github.com/netbirdio/netbird/graphs/contributors

- Reviewed upstream application release: https://github.com/netbirdio/netbird/releases/tag/v0.83.1

### Sources

- NetBird self-hosting quickstart: https://docs.netbird.io/selfhosted/selfhosted-quickstart

- NetBird advanced self-hosting guide: https://docs.netbird.io/selfhosted/selfhosted-guide

- NetBird repository license: https://github.com/netbirdio/netbird/blob/main/LICENSE

- NetBird Enterprise edition boundary: https://docs.netbird.io/selfhosted/enterprise

- Reviewed deployment artifact reference: https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh

- Upstream release and published installer digest: https://github.com/netbirdio/netbird/releases/tag/v0.83.1

- Upstream contributor history: https://github.com/netbirdio/netbird/graphs/contributors

### Licensing sources

- https://github.com/netbirdio/netbird/blob/main/LICENSE

- https://docs.netbird.io/selfhosted/enterprise

### Infrastructure sources

- https://docs.netbird.io/selfhosted/selfhosted-quickstart

- https://docs.netbird.io/selfhosted/selfhosted-guide


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 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: Sources checked — unresolved. The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Single sign-on: Documented. The advanced Community self-hosting guide supports a custom OpenID Connect identity provider and names self-hosted and managed IdP options. Enterprise-only identity lifecycle features are separate. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- SCIM provisioning: Explicitly unsupported. NetBird's edition comparison places SCIM user and group provisioning in the Enterprise Commercial License, not Community Edition. Treat SCIM as unavailable for this selected Community listing. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/enterprise (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19).

- Security controls: Edition-dependent. The self-hosted control plane supports OIDC identity, policy-controlled peer access and customer-managed TLS, firewall and state. Community Edition excludes Enterprise SCIM, traffic-flow logging and active-active HA; secure relay, backup and upgrade operations remain customer responsibilities. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19). Supporting source: Community and Enterprise capability boundary — https://docs.netbird.io/selfhosted/enterprise.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The v0.83.1 release publishes getting-started.sh with a verified SHA-256 digest. The script defaults several NetBird containers to latest, so pinning the script does not pin the complete deployment. Review and lock the generated Compose images and persistent state before production use. Scope: Community combined-server quickstart script; advanced multi-container configuration is separate. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19). Deployment artifact: https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh. Artifact reference: v0.83.1/getting-started.sh; sha256:25ee5000a7421cb51a7c4c0f9090788951f531aba171d1fbff676f66d3265bfe. Supporting source: Upstream release and published installer digest — https://github.com/netbirdio/netbird/releases/tag/v0.83.1.

- Minimum footprint / sizing: Documented. The quickstart specifies one publicly reachable Linux VM with at least 1 CPU and 2 GB RAM plus Docker Compose, a domain and required TCP/UDP ports. This is a small single-node baseline, not an HA or large-fleet sizing recommendation. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19).

- License pricing: Documented. The selected Community Edition is open source under mixed BSD-3-Clause and AGPL-3.0 terms and does not require the Enterprise license. Enterprise HA, SCIM and related capabilities are separately commercial. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://github.com/netbirdio/netbird/blob/main/LICENSE (reviewed 2026-11-19). Supporting source: Enterprise license boundary — https://docs.netbird.io/selfhosted/enterprise.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The reviewed upstream v0.83.1 release was published 2026-11-13. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence. Scope: NetBird Self-Hosted Community Edition upstream application, independently versioned from provider packages. Source: https://github.com/netbirdio/netbird/releases/tag/v0.83.1 (reviewed 2026-11-19).







## NirvaShare

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

- Listing: https://launchinyourcloud.com/directory/nirvashare/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: CloudFormation; VM image
- Architecture: NirvaShare application services on a customer VM with configured object-storage and identity-provider access.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.

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

NirvaShare application services on a customer VM with configured object-storage and identity-provider access. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

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

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

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- AWS Marketplace CFT (aws): https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/nirvashare
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Cloud Platforms (vultr): https://nirvashare.com/docs/deployment/cloud-platforms/
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

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

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

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

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

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

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

### Licensing sources

- https://nirvashare.com/pricing/

### Infrastructure sources

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

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

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


### Buyer diligence


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

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


- Marketplace delivery: Documented. The reviewed AWS offer delivers CloudFormation Template (CFT) from Nirvato Software Pvt Ltd. Its package version is 6.4.1; verify the contained application and required entitlements separately. Scope: NirvaShare selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs (reviewed 2026-11-19). Offer prodview-k6zpjoiopyrzs: Nirvato Software Pvt Ltd; CloudFormation Template (CFT); package 6.4.1; https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SAML 2.0 identity providers can protect shares using external-SSO login profiles. The vendor documents metadata exchange with Entra ID and separate admin-console SSO configuration; review entitlement, claim mapping and enforcement for each surface. Scope: Self-hosted share access; admin console configured separately. Source: https://nirvashare.com/docs/tutorials/share-files-from-smb-storage-with-entra-id-active-directory-users-using-sso/ (reviewed 2026-11-20). Supporting source: Admin-console SSO configuration properties — https://nirvashare.com/docs/deployment/nirvashare-config-properties/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes inline CloudFormation YAML that creates EC2, security rules and an installation bootstrap. Its 2025 example uses a fixed AMI, t2.medium and 40-GB disk, below the current 100-GB requirement, and exposes SSH/application ports publicly. Update region/image, storage, ingress and bootstrap pinning before use; it is not a hardened production template. Scope: Legacy vendor CloudFormation example; conflicts with current sizing and requires review. Source: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/ (reviewed 2026-11-20). Deployment artifact: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/. Artifact reference: Documentation updated 2025-01-10; not executed. Supporting source: Current minimum disk requirement — https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/.

- Minimum footprint / sizing: Documented. The vendor specifies at least 2 CPU cores, 4 GB RAM and 100 GB disk, recommending 8 GB RAM or more on a supported Linux distribution. Object/file storage, optional services and HA are additional; this is a baseline, not validated 100-user capacity. Scope: Vendor Linux server baseline; workload and HA sizing excluded. Source: https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/ (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## NocoDB Self-Hosted

Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.

- Listing: https://launchinyourcloud.com/directory/nocodb/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license.
- Licensing model: source-available
- Installation: Run the official Docker image with persistent storage or use its documented Compose-based server installer.
- Architecture: Customer-operated application with persistent metadata/database services and optional connected databases
- Operations: Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
- Product website: https://nocodb.com/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.

Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Official Docker images run the NocoDB application on a customer-controlled host with persistent storage and a configured SQLite or PostgreSQL metadata backend; the server installer adds supporting services.


### Category fit

- no-code-databases: Spreadsheet-style database interface with linked records, views, forms and programmatic access.

- internal-tools: Interfaces build focused internal pages, dashboards and approval views on base data. The reviewed release limits Interfaces to licensed self-hosted Business plans and above.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 


### Cloud deployment evidence

- NocoDB community cloud installation methods (aws, gcp, digitalocean, railway): https://nocodb.com/docs/self-hosting/installation/community-methods
  The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

NocoDB's published adopter list names Accenture, Bosch and American Express. Its official GitHub discussion records actual exchanges between named users and maintainer o1lab about the 2026 license change, including critical feedback, while the release history shows continuing maintenance. These are adoption and participation signals; they do not establish which edition or hosting model any named organization uses.

Reviewed 2026-11-10.

- Vendor-published named organization adoption claims: https://nocodb.com/

- Observed user/maintainer discussion of the license change: https://github.com/nocodb/nocodb/discussions/12891

- Current maintenance releases: https://github.com/nocodb/nocodb/releases

### Sources

- Upstream project and capabilities: https://github.com/nocodb/nocodb

- Current upstream license: https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md

- Internal Interfaces and self-hosted plan availability: https://nocodb.com/docs/changelog/2026.08.0

- Product functionality: https://nocodb.com/docs/product

- NocoDB 2026.10.2 release: https://github.com/nocodb/nocodb/releases/tag/2026.10.2

### Licensing sources

- https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md

### Infrastructure sources

- https://github.com/nocodb/nocodb


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The authentication guide documents SAML and OIDC providers and explicitly describes on-premises SSO configuration without Cloud DNS-domain verification. SSO is associated with paid self-hosted plans; optional password login alongside SSO has a separate on-premises setting. Scope: Paid self-hosted user federation; verify the selected Business/Scale/Enterprise entitlement rather than assuming Community includes SSO. Source: https://nocodb.com/docs/product-docs/account-settings/authentication (reviewed 2026-11-20). Supporting source: Self-hosted plans and licensing — https://nocodb.com/docs/self-hosting.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. NocoDB 2026.10.2 prevents shared views and dashboards from returning hidden fields, prevents forms from writing unrelated fields, hides workflow secrets from Editors and limits webhook request bodies. Upgrade and retest shares, forms, workflows and SSO. Scope: NocoDB self-hosted access controls documented in the 2026.10.2 release; no broader affected-version range was published. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2 (reviewed 2026-11-19).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream repository publishes an installer that generates a PostgreSQL/Redis/Traefik Compose stack. Re-running can upgrade the application; inspect the script, preserve secrets/data and control version changes. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/nocodb/nocodb (reviewed 2026-11-14). Deployment artifact: https://github.com/nocodb/nocodb/blob/develop/docker-compose/1_Auto_Upstall/noco.sh. Artifact reference: develop installer (moving).

- Minimum footprint / sizing: Documented. The self-hosting guide lists a minimum of 2 vCPU, 2 GB RAM and 10 GB disk, and a production recommendation of 4 vCPU, 8 GB RAM and 50 GB or more disk. Database, attachments, workload and replication require additional sizing. Scope: Single-server starting guidance; not a complete HA design or 1-TB storage allowance. Source: https://nocodb.com/docs/self-hosting (reviewed 2026-11-20).

- License pricing: Documented. The 2026.10.2 licence identifies the Sustainable Use License for the master/develop code: use and modification are limited to internal business, personal or non-commercial purposes, with restricted distribution. Commercial/self-hosted paid features require separate entitlements; this is not an unrestricted OSI open-source licence. Scope: Reviewed source-available terms; confirm commercial use and paid features for the intended deployment. Source: https://github.com/nocodb/nocodb/blob/2026.10.2/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. NocoDB 2026.10.2 was published November 19, 2026. It fixes shared-view, dashboard, form and workflow authorization boundaries, restores NC_SSO=oidc, changes SAML IdP-initiated RelayState handling and repairs air-gapped license refresh. Scope: Upstream NocoDB self-hosted release; paid-feature and license behavior remains edition-dependent. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/nocodb/nocodb/releases/tag/2026.10.1.




### Security and lifecycle reviews

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

- NocoDB 2026.10.2 access-control hardening (security-advisory): NocoDB 2026.10.2 prevents hidden-field disclosure in shares, unrelated form writes and workflow-secret disclosure to Editors, and caps webhook request bodies. Scope: NocoDB self-hosted behavior documented in the 2026.10.2 release; no universal affected-version range was published. Conditions: Public shares or dashboards, forms, Editor access to workflows, configured-key webhooks, OIDC or SAML determine exposure and upgrade impact. Action: Upgrade to 2026.10.2 or later and retest shares, forms, workflows, OIDC and SAML IdP-initiated login. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2; 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).







## Onyx Self-Hosted

Self-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.

- Listing: https://launchinyourcloud.com/directory/onyx/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition; Business and Enterprise features use separate commercial terms.
- Licensing model: open-source
- Installation: Docker Compose on a VM or official Kubernetes and Terraform deployment
- Architecture: Customer-operated web/API services, background workers, PostgreSQL, Redis, search and object storage
- Operations: Customer manages application services, databases, search, object storage, connectors, model credentials, backups, scaling and upgrades.
- Product website: https://www.onyx.app/
- Source review: 2026-11-14; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers self-hosted Onyx, not a vendor-hosted environment. External LLM, embedding and connector services receive data according to the customer's configuration. Business and Enterprise features and support require separate commercial entitlements.

Onyx Community Edition is MIT-licensed. Business and Enterprise features, images and support have separate commercial terms.

Onyx runs web services, workers and persistent database, cache, search and object-storage dependencies on VMs or Kubernetes.


### Category fit

- ai-applications-rag: Provides enterprise search, connectors and retrieval-augmented AI assistants over customer-selected knowledge sources.

- ai-tools: Provides self-hosted indexing, retrieval, model integration and agent services for building internal AI experiences.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/aws/ec2 (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/azure (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/gcp (checked 2026-11-14). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/digital_ocean (checked 2026-11-14). 


### Cloud deployment evidence

- Onyx on AWS (aws): https://docs.onyx.app/deployment/cloud/aws/ec2
  Onyx documents self-hosting on a customer EC2 instance and links a production EKS architecture using AWS managed dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on Azure (azure): https://docs.onyx.app/deployment/cloud/azure
  Onyx documents self-hosting on an Azure VM and an AKS Terraform path using customer Azure managed services.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on Google Cloud (gcp): https://docs.onyx.app/deployment/cloud/gcp
  Onyx documents Compute Engine and production GKE deployment paths in the customer's Google Cloud project.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on DigitalOcean (digitalocean): https://docs.onyx.app/deployment/cloud/digital_ocean
  Onyx documents installing its self-hosted stack on a customer DigitalOcean Droplet.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

Onyx has sustained, substantive code participation from multiple contributors. Release 5.1.2 on November 12, 2026 records continuing maintenance, including permission-handling and retrieval fixes. Contributor and release histories establish maintained project participation; they do not establish that paid Business or Enterprise features are included in the MIT Community Edition.

Reviewed 2026-11-14.

- Reviewed maintenance release v5.1.2: https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2

- Upstream contributor history: https://github.com/onyx-dot-app/onyx/graphs/contributors

### Sources

- AWS EC2 deployment: https://docs.onyx.app/deployment/cloud/aws/ec2

- Azure deployment: https://docs.onyx.app/deployment/cloud/azure

- Google Cloud deployment: https://docs.onyx.app/deployment/cloud/gcp

- DigitalOcean deployment: https://docs.onyx.app/deployment/cloud/digital_ocean

- Community license: https://github.com/onyx-dot-app/onyx/blob/main/LICENSE

- Reviewed maintenance release v5.1.2: https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2

- Upstream contributor history: https://github.com/onyx-dot-app/onyx/graphs/contributors

- Current Business and Enterprise edition boundaries: https://docs.onyx.app/deployment/enterprise_edition.md

### Licensing sources

- https://github.com/onyx-dot-app/onyx/blob/main/LICENSE

- https://docs.onyx.app/deployment/enterprise_edition.md

### Infrastructure sources

- https://docs.onyx.app/deployment/cloud/aws/ec2

- https://docs.onyx.app/deployment/cloud/gcp


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The upstream Enterprise section advertises Google OAuth, OIDC and SAML sign-in. The README does not establish every Community-versus-Enterprise protocol entitlement; confirm the selected self-hosted edition and identity configuration. Scope: Enterprise feature statement; exact protocol entitlement not fully established. Source: https://github.com/onyx-dot-app/onyx (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. The upstream Enterprise section describes group synchronization and SCIM user provisioning. Confirm the licensed self-hosted implementation and supported lifecycle operations rather than assuming Community includes them. Scope: Onyx Enterprise feature statement. Source: https://github.com/onyx-dot-app/onyx (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide uses the upstream deployment/docker_compose directory and an environment template. The default image tag moves; replace example storage credentials and configure the selected inference/storage services. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.onyx.app/deployment/local/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/onyx-dot-app/onyx/tree/main/deployment/docker_compose. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor gives Lite minimum 2 vCPUs/2 GB RAM/10 GB disk and Standard minimum 4 vCPUs/10 GB RAM/32 GB plus roughly 2.5 times indexed data. Its Standard per-container example totals about 12 CPUs/24 GB. These describe different profiles; connector/index volume, model services and HA require additional sizing. Scope: Vendor Lite/Standard profiles; per-container and single-instance recommendations differ. Source: https://docs.onyx.app/deployment/getting_started/resourcing.md (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed; ee directories are under the Onyx Enterprise License. Enterprise features need their own entitlement and quote. The MIT core licence does not establish all-edition feature access, support or model/hosting prices. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/onyx-dot-app/onyx/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## openIMIS

Self-hosted health-financing software supporting health-insurance claim submission, review and reimbursement.

- Listing: https://launchinyourcloud.com/directory/openimis/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source; official distribution licensed under AGPL v3
- Licensing model: open-source
- Installation: Official Docker distribution and installation guide
- Architecture: Customer-operated application services and database
- Operations: Scheme operator and implementation partner host, configure and maintain the installation.
- Product website: https://openimis.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

A sector-specific claims product for health-financing and social-protection programs. Workflows include automated checks, medical review and reimbursement calculations. General property-and-casualty claims functionality was not established. Follow the official production and security guidance when implementing the Docker distribution.

The official openIMIS distribution is licensed under AGPL v3 and is available for operators to deploy and maintain. Implementation, hosting and operational services may have separate costs and agreements.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- claims-management: Health-insurance claim submission, automated checks, medical review and reimbursement are documented; this is not a general property-and-casualty claims platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openimis.atlassian.net/wiki/spaces/OP/pages/4228349954/Production%2BServer%2BopenIMIS%2BWith%2BGunicorn%2BAnd%2BNginx%2BOn%2BA%2BLinux%2BServer. (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openimis.atlassian.net/wiki/spaces/OP/pages/4228349954/Production%2BServer%2BopenIMIS%2BWith%2BGunicorn%2BAnd%2BNginx%2BOn%2BA%2BLinux%2BServer. (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openimis.atlassian.net/wiki/spaces/OP/pages/4228349954/Production%2BServer%2BopenIMIS%2BWith%2BGunicorn%2BAnd%2BNginx%2BOn%2BA%2BLinux%2BServer. (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openimis.atlassian.net/wiki/spaces/OP/pages/4228349954/Production%2BServer%2BopenIMIS%2BWith%2BGunicorn%2BAnd%2BNginx%2BOn%2BA%2BLinux%2BServer. (checked 2026-11-12). 


### Cloud deployment evidence

- openIMIS production server deployment on named VPS providers (aws, azure, gcp, digitalocean): https://openimis.atlassian.net/wiki/spaces/OP/pages/4228349954/Production%2BServer%2BopenIMIS%2BWith%2BGunicorn%2BAnd%2BNginx%2BOn%2BA%2BLinux%2BServer.
  The project wiki explicitly names AWS, Azure, Google Cloud and DigitalOcean for a VPS deployment of the Django/Gunicorn backend and Nginx frontend. Review the current distribution and modules, database and TLS configuration. Harden example settings such as debug mode, service users and credentials before handling production or health data.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting and implementation responsibilities: https://openimis.org/faq

- Claims workflows: https://openimis.org/workflows-and-functionalities

- Health-insurance solution: https://openimis.org/health-insurance

- Official Docker distribution: https://github.com/openimis/openimis-dist_dkr

- Docker installation guide: https://openimis.atlassian.net/wiki/spaces/OP/pages/963182705/MO1.1+Install+the+modular+openIMIS+using+Docker

- Licensing and edition terms: https://raw.githubusercontent.com/openimis/openimis-dist_dkr/develop/LICENSE.md

### Licensing sources

- https://raw.githubusercontent.com/openimis/openimis-dist_dkr/develop/LICENSE.md

- https://openimis.org/faq

### Infrastructure sources

- https://openimis.org/faq

- https://github.com/openimis/openimis-dist_dkr


### 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 project wiki documents a tested 2025 Keycloak OIDC integration, but its deployment guide requires contributor forks and feature/keycloak-integration branches. This establishes a prototype path, not inclusion in the current supported distribution. Confirm a merged/released integration and release-specific configuration before relying on production SSO. Scope: openIMIS student-project integration versus the supported distribution; release inclusion unconfirmed. Source: https://openimis.atlassian.net/wiki/spaces/OP/pages/4661641223/Keycloak+-+Deployment+Guide (reviewed 2026-11-21). Supporting source: User login and role mapping — https://openimis.atlassian.net/wiki/spaces/OP/pages/4661739527/Keycloak+-+User+Guide.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project production guide links its Docker distribution and requires release-pinned database, backend and frontend image tags, strong secrets and disabled demo data. Development images and example administrator credentials are not the production configuration. Scope: Modular openIMIS production Docker workflow; reconcile component and distribution releases. Source: https://openimis.atlassian.net/wiki/spaces/OP/pages/5314347015/Installation+Guide+Development+Production+Deployment (reviewed 2026-11-14). Deployment artifact: https://github.com/openimis/openimis-dist_dkr. Artifact reference: repository default branch (moving); pin matching component release tags.

- Minimum footprint / sizing: Documented. The official server requirements list a production minimum of two CPU cores, 8 GB RAM and 100 GB disk, with Linux as reference OS. This is a starting baseline, not a validated 100-user/1-TB HA deployment; separately size claims processing, attachments, database, replicas and backups. Scope: Official modular openIMIS production minimum; workload and HA additions excluded. Source: https://openimis.atlassian.net/wiki/spaces/OP/pages/3771727873/MO1.+Server+Requirements (reviewed 2026-11-21).

- License pricing: Documented. The reviewed Docker distribution grants GNU AGPLv3 rights and disclaims warranty. Individual services/modules and implementation or hosting agreements require separate licence and support review; no commercial-service entitlement follows from the distribution licence. Scope: Moving upstream Docker distribution licence reviewed on this date. Source: https://github.com/openimis/openimis-dist_dkr/blob/develop/LICENSE.md (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## OpenLIT

OpenTelemetry-based AI tracing and evaluation platform for model and agent operations.

- Listing: https://launchinyourcloud.com/directory/openlit/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream OpenLIT. Models and external integrations have separate terms.
- Licensing model: open-source
- Installation: Run the official Docker Compose platform or documented Kubernetes deployment with its persistent telemetry services.
- Architecture: Customer-operated UI, telemetry receiver and analytical storage with application-side instrumentation
- Operations: Customer manages telemetry collection, analytical storage, capture policies, access controls, retention and upgrades.
- Product website: https://openlit.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Configure instrumentation to send telemetry to the self-hosted receiver. Optional LLM-based evaluations and integrations can call external services; hosting the observability platform does not host every model being observed.

Apache License 2.0 for upstream OpenLIT. Models and external integrations have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated UI, telemetry receiver and analytical storage with application-side instrumentation. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-observability: OpenTelemetry-native tracing, evaluations and cost/GPU monitoring for AI applications and agents.

- ai-tools: AI instrumentation, evaluation and operational feedback tooling with a self-hosted platform.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/catalog/openlit/ (checked 2026-11-12). 


### Cloud deployment evidence

- OpenLIT deployment on DigitalOcean Kubernetes (digitalocean): https://docs.digitalocean.com/products/marketplace/catalog/openlit/
  DigitalOcean documents the OpenLIT Kubernetes add-on, Helm installation verification and access to the application in the customer cluster. Review the included application and ClickHouse versions, persistent storage and access controls; this is the observability platform, not just its instrumentation SDK.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream release history recognizes multiple named contributors and first-time contributions across releases, providing evidence of sustained participation beyond repository stars.

Reviewed 2026-11-10.

- Maintenance and named release contributors: https://github.com/openlit/openlit/releases

- Public platform and contribution process: https://github.com/openlit/openlit

### Sources

- Official installation and runtime: https://raw.githubusercontent.com/openlit/openlit/main/README.md

- Upstream project and capabilities: https://github.com/openlit/openlit

- Current upstream license: https://raw.githubusercontent.com/openlit/openlit/main/LICENSE

### Licensing sources

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

### Infrastructure sources

- https://raw.githubusercontent.com/openlit/openlit/main/README.md


### 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. The DigitalOcean Kubernetes 1-Click catalog packages OpenLIT 1.15.0. Its example cluster command is not a minimum footprint or evidence that the package matches the current upstream release. Scope: OpenLIT-published Kubernetes package; 1.15.0 package scope. Source: https://docs.digitalocean.com/products/marketplace/catalog/openlit/ (reviewed 2026-11-14). Offer openlit: OpenLIT; Kubernetes 1-Click; package 1.15.0; https://marketplace.digitalocean.com/apps/openlit.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official OAuth guide documents Google, GitHub, Microsoft and Okta sign-in, including an Okta OIDC application and provider callbacks. Configure credentials and verified-email account linking. Enterprise UI configuration helpers are separate from the environment-based provider setup; verify the chosen release/edition. Scope: Self-hosted OpenLIT OAuth/OIDC provider setup. Source: https://docs.openlit.io/latest/openlit/oauth.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 OpenLIT repository provides platform deployment instructions separate from its instrumentation SDK. Configure the platform telemetry services, persistent data and network exposure for the selected deployment. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/openlit/openlit (reviewed 2026-11-14). Deployment artifact: https://github.com/openlit/openlit. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The current self-hosting guide identifies the OpenLIT dashboard/API/OTLP receiver, ClickHouse storage and NATS JetStream for threshold alerts. It does not establish a workload-independent CPU/RAM floor. Size ingestion rate, trace retention, indexing and HA for these components together. Scope: Current OpenLIT multi-component topology; numeric production sizing unresolved. Source: https://docs.openlit.io/latest/openlit/installation.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Parse Server

Node.js application backend for data APIs, users, permissions and server-side application logic.

- Listing: https://launchinyourcloud.com/directory/parse-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Parse Server.
- Licensing model: open-source
- Installation: Install the upstream Node.js package and configure a supported MongoDB or PostgreSQL backend; run standalone or in an Express application.
- Architecture: Customer-operated Node.js backend with database and selected file/push integrations
- Operations: Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.
- Product website: https://parseplatform.org/
- Source review: 2026-11-15; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Cloud Code is code executed in the server environment, not evidence of a vendor-operated cloud dependency. External storage, push-notification providers and third-party adapters have their own boundaries and licenses. GHSA-43rg-r2xr-q686 affects Parse Server versions before 9.12.0-alpha.3: creating a user with an existing user's auth data can return protected fields and hidden auth-adapter data, including MFA secrets and recovery codes. The advisory concerns the logging-in user's own object and requires that user's auth data or an applicable session token; it is not an arbitrary-user disclosure. Requests using the master or maintenance key are unaffected. There is no known workaround; Parse Server 8 is not patched, and the first published patched version is the 9.12.0-alpha.3 prerelease.

Apache License 2.0 for upstream Parse Server. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Node.js backend with database and selected file/push integrations. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- backend-platforms: Application backend with data APIs, user authentication, access rules and server-side Cloud Code; database and file adapters are separately configured.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 


### Cloud deployment evidence

- Parse Server cloud hosting options (aws, azure, gcp, digitalocean): https://docs.parseplatform.org/parse-server/guide/
  The upstream guide explicitly lists AWS, Google Cloud, Azure and DigitalOcean as hosts for the Parse Server application and provides installation guidance. This compatibility statement is separate from the DigitalOcean Spaces file adapter; select current Node.js/database versions and secure the deployed server.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Parse Server deployment on Heroku (heroku): https://docs.parseplatform.org/parse-server/guide/
  The upstream guide documents the Parse Server application on Heroku with MongoDB Atlas, including project configuration and validation. The application and database are in separate customer-controlled services; verify database network access, current runtime versions, secrets and production security.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Parse Community maintains an established public project, contributor review process and community forum. The current release stream includes November 2026 stable and LTS maintenance.

Reviewed 2026-11-10.

- Current stable and LTS releases: https://github.com/parse-community/parse-server/releases

- Community contribution process: https://github.com/parse-community/parse-server/blob/alpha/CONTRIBUTING.md

- Long-running community governance discussion: https://community.parseplatform.org/t/official-discord-server/1506

### Sources

- Official installation and runtime: https://docs.parseplatform.org/parse-server/guide/

- Upstream project and capabilities: https://github.com/parse-community/parse-server

- Current upstream license: https://raw.githubusercontent.com/parse-community/parse-server/alpha/LICENSE

- Security advisory GHSA-43rg-r2xr-q686: https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686

### Licensing sources

- https://raw.githubusercontent.com/parse-community/parse-server/alpha/LICENSE

### Infrastructure sources

- https://docs.parseplatform.org/parse-server/guide/


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Parse Server supports external application-user authentication adapters; published 8.6.123 includes a Keycloak adapter that verifies provider tokens and returned user attributes. Configure the adapter/provider and map application users and permissions. This is an app-user backend capability, not proof of administrator SSO in Parse Dashboard, and does not establish SCIM. Scope: Published application-user federation adapter, distinct from separately deployed management dashboards. Source: https://github.com/parse-community/parse-server/blob/8.6.123/src/Adapters/Auth/keycloak.js (reviewed 2026-11-20). Supporting source: Official third-party authentication guide — https://github.com/parse-community/docs/blob/gh-pages/_includes/parse-server/third-party-auth.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. GHSA-43rg-r2xr-q686 can expose protected fields or hidden auth-adapter data in the logging-in user object, including MFA secrets and recovery codes. The advisory affects versions before 9.12.0-alpha.3 and identifies that prerelease as patched; Parse Server 8 is unpatched and no workaround is known. It requires the user auth data or applicable session-token conditions; master/maintenance-key requests are unaffected. Scope: Auth-data login response advisory reviewed November 15; not an arbitrary-user disclosure or a recommendation to adopt a prerelease without compatibility review. Source: https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686 (reviewed 2026-11-15).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official server repository documents a Node.js application/package with a separately configured database. The server, dashboard and optional adapters have separate configuration and lifecycle; they are not one cloud appliance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/parse-community/parse-server (reviewed 2026-11-14). Deployment artifact: https://github.com/parse-community/parse-server. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The published server identifies Node.js plus a supported database and configurable storage/live-query services, but not a workload-specific whole-system CPU/RAM/storage minimum. Size request/query rates, files, live subscriptions, database indexes and replication separately. A managed Parse hosting plan or tutorial allocation is not a self-hosted HA capacity guarantee. Scope: Published upstream runtime/dependency scope; complete production sizing remains unconfirmed. Source: https://github.com/parse-community/parse-server/blob/8.6.123/README.md (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote. Scope: Parse Server 8.6.123 upstream application; not a managed Parse hosting plan; software terms only, excluding infrastructure and operations. Source: https://github.com/parse-community/parse-server/blob/8.6.123/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 8.6.123, published 2026-11-09. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The November 14 advisory GHSA-43rg-r2xr-q686 says Parse Server 8 is unpatched; this historical stable-release snapshot is not a secure-version recommendation. Scope: Upstream parse-community/parse-server release record; commercial editions and deployment packages may differ. Source: https://github.com/parse-community/parse-server/releases/tag/8.6.123 (reviewed 2026-11-15). Supporting source: Parse Server auth-data disclosure advisory — https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686.







## PaygOps Community Edition

Open-source PAYGO loan, asset-finance, customer and payment operations platform.

- Listing: https://launchinyourcloud.com/directory/paygops/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- 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: PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec.
- 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.paygops.com/community-edition
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The publisher identifies MasungaTech/PaygOps-Community as the October 2026 Community release and describes GEAPP backing and EnAccess community support. This is a new edition of an established product, not evidence of years of independent Community deployments. Mobile/API, device keys, payments and messaging integrations have their own data and credential boundaries.

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

PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- financial-application-management: Open-source PAYGO loan, asset-finance, customer and payment operations platform.

- erp-crm: Open-source PAYGO loan, asset-finance, customer and payment operations platform.

### Deployment boundaries


- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml (checked 2026-11-19). 


### Cloud deployment evidence

- DigitalOcean App Spec (digitalocean): https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml
  PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. The publisher identifies MasungaTech/PaygOps-Community as the October 2026 Community release and describes GEAPP backing and EnAccess community support. This is a new edition of an established product, not evidence of years of independent Community deployments. Mobile/API, device keys, payments and messaging integrations have their own data and credential boundaries.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The institutional source identifies actual use, public governance or a named community-support program. The linked application source separately establishes installation and licensing.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://www.paygops.com/post/masunga-releases-paygops-community-edition-as-open-source-with-support-from-global-energy-alliance

- Upstream project: https://github.com/MasungaTech/PaygOps-Community

### Sources

- DigitalOcean App Spec: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml

- Deploy README: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/README.md

- AGPL-3.0: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md

- Commits: https://github.com/MasungaTech/PaygOps-Community/commits/main

### Licensing sources

- https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md

### Infrastructure sources

- https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml


### 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 Community documentation describes application authentication and API tokens, but does not establish an external SAML/OIDC identity-provider login path for customer-hosted Community users. Token-based API access alone is not enterprise user SSO. Scope: PaygOps Community user sign-in; commercial or hosted product capabilities are not transferred. Source: https://github.com/MasungaTech/PaygOps-Community/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 reviewed source supplies deployment configuration for PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: PaygOps Community Edition deployment example; review the full linked installation instructions. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml (reviewed 2026-11-19). Deployment artifact: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The DigitalOcean template allocates two 1-vCPU/2-GB web instances, two API instances of the same size, two 1-vCPU/2-GB workers, and 1-vCPU/1-GB OpenPAYGO and Redis instances. Its three PostgreSQL entries are marked production:false. This is a documented recipe, not an HA or production minimum. Scope: Reviewed Community App Platform template; database capacity, persistent storage and production hardening remain separate. Source: https://github.com/MasungaTech/PaygOps-Community/blob/main/.do/deploy.template.yaml (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: PaygOps Community Edition; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## Perforce P4 Server (Helix Core)

Commercial centralized version-control server deployed from Perforce's cloud quickstarts into customer infrastructure.

- Listing: https://launchinyourcloud.com/directory/perforce-p4-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary P4 license; free within the published small-team limits, with commercial licensing and support above them.
- Licensing model: commercial-only
- Installation: Perforce quickstart images for AWS, Azure, Google Cloud or DigitalOcean; AWS also uses CloudFormation
- Architecture: P4 Server on a customer VM with persistent metadata and depot storage; replication and edge services are optional separate topology choices.
- Operations: Customer manages VM and OS security, depot and metadata storage, accounts, firewall, backups, logs, upgrades, capacity and any replication or edge topology.
- Product website: https://www.perforce.com/products/helix-core
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

Helix Core is being renamed P4 in current documentation. The quickstarts establish single-server deployment, not an HA or disaster-recovery design. Confirm current user/workspace entitlements before production use.

P4 is proprietary software. Perforce publishes a free-use threshold, but larger deployments and support require commercial licensing.

The quickstarts launch a persistent P4 Server VM and attached depot/metadata storage in the customer's cloud.


### Category fit

- devops: Provides centralized version control and a high-volume repository for source code, binaries and digital assets used by development teams.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-azure.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-gcp.html (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-digitalocean.html (checked 2026-11-18). 


### Cloud deployment evidence

- P4 Server on AWS (aws): https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html
  Perforce documents a customer AWS deployment using EC2 and a CloudFormation quickstart.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- P4 Server on Azure (azure): https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-azure.html
  Perforce documents launching P4 Server in the customer's own Azure cloud instance through Marketplace.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- P4 Server on Google Cloud (gcp): https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-gcp.html
  Perforce documents deployment into the customer's selected Google Cloud project.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- P4 Server on DigitalOcean (digitalocean): https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-digitalocean.html
  Perforce documents a P4 Server Droplet in the customer's DigitalOcean account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Plan a P4 Server cloud deployment: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html

- Deploy P4 Server on AWS: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html

- Deploy P4 Server on Azure: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-azure.html

- Deploy P4 Server on Google Cloud: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-gcp.html

- Deploy P4 Server on DigitalOcean: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-digitalocean.html

### Licensing sources

- https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html

### Infrastructure sources

- https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 10 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. Perforce publishes P4 (Self-Managed) on AWS Marketplace as a CloudFormation delivery, package 2026.1.0, on Rocky Linux. The offer is a deployment package; the P4 server patch level and purchased licence must be checked separately. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4 (reviewed 2026-11-18). Offer prodview-nw7wxff425so4: Perforce; CloudFormation Template (CFT); package 2026.1.0; https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Perforce P4 CFT offer explicitly requires buying the software licence outside AWS Marketplace. That externally billed licence is not a software charge on the AWS Marketplace invoice for this offer. This answers the licence-billing route only; eligible EC2/EBS spend or a separately negotiated private offer still requires the buyer’s AWS agreement and seller order terms. Scope: Externally billed software licence for the exact reviewed public Perforce P4 CFT offer; not all provider spend or future private offers. Source: https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4 (reviewed 2026-11-18). Supporting source: AWS BYOL pricing boundary — https://docs.aws.amazon.com/marketplace/latest/userguide/BYOL-pricing.html. Supporting source: Commitment qualification remains product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. P4 Authentication Service integrates SAML and OIDC identity providers with P4 through the authentication extension and supported clients. Deploy and secure the service and extension separately. Logging out of P4 does not necessarily terminate the IdP session. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/overview-of-has.html (reviewed 2026-11-18).

- SCIM provisioning: Documented. P4 Authentication Service exposes SCIM v2 at /scim/v2 for user/group provisioning, protected by a bearer token and a P4 super-user ticket. The documented implementation explicitly does not support deprovisioning; user renames are rejected by default. Do not rely on it for automated offboarding. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/provisioning.html (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. Perforce’s Trust Center separates assurance resources by product, including Delphix, BlazeMeter, Puppet and QAC/Klocwork. Those gated reports and corporate badges do not identify a current P4 Server/Authentication Service assurance boundary. Request the applicable report/certificate, entity, period and customer-control scope; do not transfer another Perforce product’s report to P4. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://trust.perforce.com/resources (reviewed 2026-11-18).

- Security controls: Documented. P4 2026.1 changes security defaults, including raising a lower security level to 4 during p4d -xu. Other configurables keep explicitly set values on upgrade; new defaults are not proof that an existing deployment is hardened. Review protections, TLS, authentication extension privileges and the upgrade procedure. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://www.perforce.com/perforce/doc.current/user/relnotes.txt (reviewed 2026-11-18). Supporting source: SCIM endpoint and privileged ticket requirements — https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/provisioning.html.

- Air-gapped operation: Documented. Perforce’s SDP upgrade tool explicitly covers air-gapped servers: stage the binaries from the locations reported by get_helix_binaries.sh -n. P4 installs a local licence file; request it outside the isolated network and transfer it securely. Commit/central servers and any replica intended for failover need appropriate licences bound to their host identity. Stage client/SDP updates and use reachable internal identity, DNS, backup and support procedures. Scope: Self-managed P4 with staged SDP/server/client artifacts and valid local licence files; external SSO services are not made offline automatically. Source: https://workshop.perforce.com/files/guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/upgrade.sh?v=25 (reviewed 2026-11-18). Supporting source: Install and reload the local licence file — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.tips.release.html. Supporting source: Replica and cloud-host licence requirements — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html.

- Deployment artifact / IaC: Documented. The AWS quickstart launches the Perforce Marketplace CloudFormation package and configures EC2, SSH/P4 security groups and separate encrypted EBS data volumes. It defaults to small-team capacity. Review IAM and source-IP restrictions, then record the resolved template and server build in the deployment inventory. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html (reviewed 2026-11-18). Supporting source: Exact CFT offer and package version — https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4.

- Minimum footprint / sizing: Documented. The server administration guide gives memory planning factors of 64 MB per licensed user and 1.5 KB per depot file for a single server, with additional memory useful for filesystem cache. Depot file count, revisions, concurrency and replication matter. The quickstart’s t3.small default is not an HA design for 100 users. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.memory.html (reviewed 2026-11-18). Supporting source: Small-team AWS quickstart — https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html.

- License pricing: Documented. P4 is proprietary. The published free threshold is up to five users and fewer than twenty workspaces. Larger self-managed installations require a commercial quote; hosted P4 Cloud per-user pricing is a different product. The reviewed AWS offer bills its software licence outside AWS Marketplace. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html (reviewed 2026-11-18). Supporting source: External licence billing in the exact AWS offer — https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4. Supporting source: Separate failover-server licensing requirements — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html.

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 741.44/month. Two 8-vCPU/32-GiB VMs model a primary and licensed failover standby. Each has 1,000 GB archive, 100 GB metadata/journals and 30 GB boot gp3 capacity (2,260 GB total). P4 licences, file/revision-driven sizing, backup and replication transfer are unpriced. This is not a complete operating-cost estimate or validated capacity/SLA claim. Scope: Editorial P4 compute/storage layer on two AZs; configure journal/archive replication, licensing, failover and recovery tests. Metadata allowance and VM size are assumptions to validate against depot file count and throughput, not a vendor sizing guarantee.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-18). Supporting source: Product topology/sizing basis — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/failover.html. Supporting source: Current AWS us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: Single-server memory planning factors — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.memory.html. Supporting source: Primary and failover licence requirements — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html.

- Release snapshot / cadence: Documented. The server release notes identify P4 2026.1 Patch 4 as 2026.1/3141402, dated November 12, 2026. Check p4d -V against the bugfix change level. This is distinct from the Marketplace package 2026.1.0 and Authentication Service’s own release line. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://www.perforce.com/perforce/doc.current/user/relnotes.txt (reviewed 2026-11-18).







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







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







## Plone

Self-hosted enterprise content management and publishing platform.

- Listing: https://launchinyourcloud.com/directory/plone/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, linode, digitalocean, hetzner
- 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: CloudFormation; Docker / Compose; Application platform deployment
- Architecture: Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box.
- 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://plone.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 community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.

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

Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted enterprise content management and publishing platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 


### Cloud deployment evidence

- plone-in-a-box (aws, linode, digitalocean, hetzner): https://github.com/collective/plone-in-a-box
  Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. The community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes mauritsvanrees, jensens, vangheem, 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/plone/Products.CMFPlone/graphs/contributors

- Upstream project: https://github.com/plone/Products.CMFPlone

### Sources

- plone-in-a-box: https://github.com/collective/plone-in-a-box

- GPL-2.0 LICENSE.md: https://github.com/plone/Products.CMFPlone/blob/master/LICENSE

- Releases v6.2.3: https://github.com/plone/Products.CMFPlone/releases

### Licensing sources

- https://github.com/plone/Products.CMFPlone/blob/master/LICENSE

### Infrastructure sources

- https://github.com/collective/plone-in-a-box


### 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 community pas.plugins.oidc add-on documents OpenID Connect authentication for Plone. This is an add-on integration rather than a universal core entitlement; validate its Plone/backend/front-end compatibility and provider mapping for the selected deployment. Scope: Maintainer documentation for a Plone PAS OIDC add-on. Source: https://github.com/collective/pas.plugins.oidc (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. Cookieplone is the upstream-recommended project generator and creates the selected Plone backend/frontend project. It supplies an application project/deployment workflow, not an automatically hardened cloud-account infrastructure stack. Scope: Plone 6 Cookieplone project generation; Classic and Volto variants have different requirements. Source: https://6.docs.plone.org/install/create-project-cookieplone.html (reviewed 2026-11-20). Deployment artifact: https://github.com/plone/cookieplone. Artifact reference: Moving generator repository; select compatible pinned template/dependency versions.

- Minimum footprint / sizing: Documented. The Plone 6 guide recommends 2 GB or more RAM per site and 40 GB or more disk. Volto frontend installation needs at least 2 GB RAM; lower backend process minima and swap figures are not whole-stack sizing. Addons, caches, builds and HA require additional resources. Scope: Rough upstream Classic/Volto requirements, not a 100-user/1-TB HA benchmark. Source: https://6.docs.plone.org/install/create-project-cookieplone.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Rocket.Chat Self-Managed

Self-managed team messaging and collaboration platform deployed on customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/rocket-chat-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition core; Enterprise Edition code and non-community plans use separate proprietary licensing.
- Licensing model: open-source
- Installation: Docker or Docker Compose, Kubernetes with the official Helm chart, or the Launchpad CLI
- Architecture: Customer-operated Rocket.Chat application and MongoDB deployment on virtual machines or Kubernetes.
- Operations: Customer operates MongoDB, application instances, storage, TLS, monitoring, backups, scaling and upgrades; plan entitlements govern enterprise capabilities.
- Product website: https://www.rocket.chat/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-18; infrastructure review: 2026-11-17

### Scope and qualifications

New self-managed deployments receive the Starter plan, intended for evaluation or small non-critical teams and limited to 50 users. Commercial, Government, Defense and air-gapped capabilities require the applicable plan. Push notifications normally require Rocket.Chat Cloud registration and outbound access unless an alternative gateway is configured. Launchpad excludes Omnichannel and federation workloads and includes a closed-source operator. The documented DigitalOcean Marketplace one-click path is unsupported. Rocket.Chat 9.0.0 moves LDAP, SAML, and Custom OAuth to premium editions and removes several login integrations. It also fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure; verify at least one administrator login path before upgrading.

Community Edition code outside designated Enterprise Edition paths is MIT-licensed. Enterprise Edition code and paid self-managed plans have separate proprietary terms and feature entitlements. Since 9.0.0, LDAP, SAML, and Custom OAuth are premium features; several legacy login integrations were removed. Confirm the purchased plan and an administrator recovery path before upgrade.

Production paths run persistent application and MongoDB workloads on customer virtual machines or Kubernetes.


### Category fit

- collaboration: Team channels, messaging, file sharing and collaborative workflows; governance, scale and isolated-network capabilities depend on plan.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.rocket.chat/partners/aws (checked 2026-11-17). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://rocket.chat/install (checked 2026-11-17). 


### Cloud deployment evidence

- Rocket.Chat in the customer's AWS environment (aws): https://www.rocket.chat/partners/aws
  Rocket.Chat states that the self-managed deployment runs in the customer's own AWS environment and can be launched from AWS Marketplace. The EKS Launchpad guide is a separate current implementation path.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Rocket.Chat self-managed deployment on DigitalOcean (digitalocean): https://rocket.chat/install
  The current publisher installation page explicitly names DigitalOcean for self-managed deployment. The older Marketplace one-click guide is unsupported and is not presented as a supported one-click method.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Self-managed installation options and named clouds: https://rocket.chat/install

- AWS customer-account deployment: https://www.rocket.chat/partners/aws

- Launchpad deployment on Amazon EKS: https://docs.rocket.chat/docs/deploy-with-launchpad

- Kubernetes and Helm deployment: https://docs.rocket.chat/docs/deploy-with-kubernetes

- Deployment guide: https://docs.rocket.chat/docs/deployment-guide

- Community Edition license: https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE

- Enterprise Edition license: https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/ee/LICENSE

- Current self-managed plans: https://docs.rocket.chat/our-plans

- Release support lifecycle: https://docs.rocket.chat/docs/releaselifecycle

- Unsupported DigitalOcean one-click path: https://docs.rocket.chat/docs/deploy-with-digital-ocean

- Rocket.Chat 9.0.0 release notes: https://docs.rocket.chat/docs/rocketchat-release-notes/

### Licensing sources

- https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE

- https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/ee/LICENSE

- https://docs.rocket.chat/our-plans

- https://docs.rocket.chat/docs/rocketchat-release-notes/

### Infrastructure sources

- https://docs.rocket.chat/docs/deployment-guide

- https://docs.rocket.chat/docs/deploy-with-kubernetes


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 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: Sources checked — unresolved. The installation page names customer AWS/DigitalOcean deployment, but not a current cloud Marketplace procurement offer. The Rocket.Chat app Marketplace is a different catalogue. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://rocket.chat/install (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Named-cloud installation and paid workspace plans do not establish a qualifying Marketplace purchase or cloud-commitment eligibility. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://rocket.chat/install (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. From Rocket.Chat 9.0, LDAP and SAML are included in Starter and premium plans, and excluded from Community. The reviewed identity FAQ explicitly separates these plans; older Community entitlement assumptions no longer apply. Scope: Self-managed Rocket.Chat 9.0+ identity plan boundary. Source: https://docs.rocket.chat/docs/identity-management-faq (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Current self-managed identity guidance documents LDAP/SAML and plan boundaries. A SCIM endpoint, lifecycle operations and entitlement were not established. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://docs.rocket.chat/docs/identity-management-faq (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Rocket.Chat Self-Managed material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.rocket.chat/docs/security-overview (reviewed 2026-11-17).

- Security controls: Documented. The security overview distinguishes plan-specific audit, custom-role and encryption capabilities. FIPS configuration requires a Government/Defense add-on; customers operate TLS, firewall rules and the compatible MongoDB deployment. Current advisory review: Rocket.Chat 9.0.0 fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure while changing authentication feature availability. Upgrade to 9.0.0 or later, verify an administrator login path, and confirm premium authentication entitlements. Scope: Self-managed controls; plan qualifications retained Rocket.Chat self-managed 9.0.0 release; exact component and feature applicability follows the release notes.. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/ (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.rocket.chat/docs/security-overview.

- Air-gapped operation: Edition-dependent. The documented air-gapped model requires a paid plan and alternative handling for cloud-dependent services. Stage licensing/registration and apps through the supported workflow; ordinary mobile push and app Marketplace access require separate arrangements. Scope: Paid isolated workspace configuration. Source: https://docs.rocket.chat/v1/docs/choose-your-deployment-model (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Rocket.Chat documents Helm deployment into customer Kubernetes, with MongoDB and application configuration managed separately. Launchpad is a distinct deployment path with its own feature and operator constraints. Scope: Self-managed Kubernetes installation. Source: https://docs.rocket.chat/docs/deploy-with-kubernetes (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. For HA premium workspaces, the sizing guide lists Rocket.Chat at 4 vCPU/8–12 GiB and MongoDB at 2 vCPU/8–16 GiB per replica, recommending three MongoDB members. It is a workload-specific baseline, not proof that every 100-user workload fits. Scope: Premium HA sizing table; application replica count and data size require design. Source: https://docs.rocket.chat/docs/system-requirements (reviewed 2026-11-17).

- License pricing: Documented. Community Edition code outside designated Enterprise Edition paths is MIT-licensed. Enterprise Edition code and paid self-managed plans have separate proprietary terms and feature entitlements. Scope: Rocket.Chat Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm a premium HA workspace design, application replicas, MongoDB replica sizing, attachment storage and clock-speed requirements. The Starter 50-user plan does not cover the requested 100-user scenario. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://docs.rocket.chat/docs/system-requirements (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Rocket.Chat 9.0.0 was released November 10, 2026. It changes authentication feature entitlements, removes login integrations, and includes access-scoping, SSRF, and Brotli fixes. Scope: Rocket.Chat self-managed 9.0 release. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/ (reviewed 2026-11-18). Supporting source: Release lifecycle — https://docs.rocket.chat/docs/releaselifecycle.




### Security and lifecycle reviews

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

- Rocket.Chat 9.0.0 security and authentication update (security-advisory): Rocket.Chat 9.0.0 fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure while changing authentication feature availability. Scope: Rocket.Chat self-managed 9.0.0 release; exact component and feature applicability follows the release notes. Conditions: Exposure depends on messaging, transcript, outbound request, and affected dependency use. Authentication migration depends on edition. Action: Upgrade to 9.0.0 or later, verify an administrator login path, and confirm premium authentication entitlements. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/; reviewed 2026-11-18.




## Sandfly Security

Commercial self-hosted Linux threat-hunting and investigation platform.

- Listing: https://launchinyourcloud.com/directory/sandfly-security/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: VM image
- Architecture: Sandfly application services and database on a customer DigitalOcean Droplet.
- 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://marketplace.digitalocean.com/apps/sandflysecurity
- 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 provider package and current upstream major are different versions. Follow the vendor's database-schema upgrade instructions rather than replacing an image blindly. A database search finding no CVEs is not a security-assurance claim.

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

Sandfly application services and database on a customer DigitalOcean Droplet. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Commercial self-hosted Linux threat-hunting and investigation platform.

### Deployment boundaries


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


### Cloud deployment evidence

- DigitalOcean 1-Click (digitalocean): https://marketplace.digitalocean.com/apps/sandflysecurity
  Sandfly application services and database on a customer DigitalOcean Droplet. The reviewed provider package and current upstream major are different versions. Follow the vendor's database-schema upgrade instructions rather than replacing an image blindly. A database search finding no CVEs is not a security-assurance claim.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- DigitalOcean 1-Click: https://marketplace.digitalocean.com/apps/sandflysecurity

- License & EULA: https://docs.sandflysecurity.com/docs/license-eula

- Docs & v6.0.1: https://docs.sandflysecurity.com/

- Upgrade Notes: https://docs.sandflysecurity.com/docs/upgrade-notes

### Licensing sources

- https://docs.sandflysecurity.com/docs/license-eula

### Infrastructure sources

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


### 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. The vendor documents SAMLv2 using Redirect requests/Post responses, configured NameID/IdP metadata and optional request signing. SSO requires an upgraded plan. Confirm the purchased entitlement, provider attributes and account/role policy; host scanning credentials are separate. Scope: Current Sandfly application-user SAML; upgraded-plan entitlement. Source: https://docs.sandflysecurity.com/docs/sso-configuration (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. Sandfly supplies setup tooling that generates Compose configurations for PostgreSQL, server and scanning nodes. Use the supported Compose v2 path and matching setup/image versions; the vendor distinguishes it from the separate Docker/Podman installation method. Configure TLS, secrets, persistence and backups. Scope: Vendor Sandfly Compose-generated application deployment; supported runtime/tool versions required. Source: https://docs.sandflysecurity.com/docs/sandfly-install-docker-compose (reviewed 2026-11-21). Deployment artifact: https://docs.sandflysecurity.com/docs/sandfly-install-docker-compose. Artifact reference: Current guide updated 2026-11-17.

- Minimum footprint / sizing: Documented. The current guide recommends a dedicated server with at least 8 GB RAM and two CPU cores, plus separate scanning-node capacity (4 GB RAM per node host recommended). Scanned-host count, scan concurrency, database retention and redundancy change requirements; protected endpoints have separate prerequisites. Scope: Sandfly server and scanning-node recommendations; whole estate/HA sizing separate. Source: https://docs.sandflysecurity.com/docs/installation-requirements (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Statamic

Self-hosted content management system with flat-file and database options.

- Listing: https://launchinyourcloud.com/directory/statamic/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean, linode
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Statamic per-site source-available licence; Pro features have separate commercial terms.
- Licensing model: source-available
- Installation: Source / language package
- Architecture: Statamic Laravel application, persistent content and configured media 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://statamic.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 per-site source-available licence and commercial Pro features require review; possession of public source does not permit unrestricted reuse on other sites.

Statamic per-site source-available licence; Pro features have separate commercial terms.

Statamic Laravel application, persistent content and configured media storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted content management system with flat-file and database options.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://statamic.dev/getting-started/installing/digital-ocean (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://statamic.dev/getting-started/installing/linode (checked 2026-11-19). 


### Cloud deployment evidence

- DigitalOcean Guide (digitalocean): https://statamic.dev/getting-started/installing/digital-ocean
  Statamic Laravel application, persistent content and configured media storage. The per-site source-available licence and commercial Pro features require review; possession of public source does not permit unrestricted reuse on other sites.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Linode Guide (linode): https://statamic.dev/getting-started/installing/linode
  Statamic Laravel application, persistent content and configured media storage. The per-site source-available licence and commercial Pro features require review; possession of public source does not permit unrestricted reuse on other sites.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- DigitalOcean Guide: https://statamic.dev/getting-started/installing/digital-ocean

- Linode Guide: https://statamic.dev/getting-started/installing/linode

- Statamic LICENSE.md: https://github.com/statamic/cms/blob/6.x/LICENSE.md

- Releases v6.42.0: https://github.com/statamic/cms/releases

### Licensing sources

- https://github.com/statamic/cms/blob/6.x/LICENSE.md

### Infrastructure sources

- https://statamic.dev/getting-started/installing/digital-ocean

- https://statamic.dev/getting-started/installing/linode


### 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 current OAuth guide marks this a Pro feature. Install Laravel Socialite and configure provider credentials; built-in examples include Google, GitHub and other providers. Additional Socialite providers require their own compatibility review. Scope: Statamic 6 Pro control-panel OAuth; not a Core entitlement or generic SAML guarantee. Source: https://statamic.dev/advanced-topics/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 current Ubuntu guide installs Statamic through its CLI or Composer project template, then configures the web server and PHP environment. This is an application installation workflow, not an upstream cloud-account infrastructure or HA template. Scope: Statamic 6 Ubuntu application installation. Source: https://statamic.dev/getting-started/installing/ubuntu (reviewed 2026-11-20). Deployment artifact: https://statamic.dev/getting-started/installing/ubuntu. Artifact reference: Current versioned documentation; pin Composer dependencies and project release.

- Minimum footprint / sizing: Sources checked — unresolved. The current requirements specify PHP 8.3+, Composer and required extensions, including image processing. They do not establish a quantitative CPU/RAM/storage production floor for the application and its selected addons. Scope: Statamic 6 software prerequisites; quantitative deployment sizing remains open. Source: https://statamic.dev/getting-started/requirements (reviewed 2026-11-20).

- License pricing: Documented. Statamic per-site source-available licence; Pro features have separate commercial terms. Scope: Statamic; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/statamic/cms/blob/6.x/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## ToolJet Self-Hosted

Build internal tools and business applications with a customer-hosted app builder.

- Listing: https://launchinyourcloud.com/directory/tooljet/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 open-source foundation; commercial self-hosted editions/plans
- Licensing model: open-source
- Installation: Docker Compose or Kubernetes; optional Terraform provisioning for AWS/Azure/GCP VMs
- Architecture: Customer-operated app services, PostgreSQL and optional cache
- Operations: Customer operates application, database, credentials, backups and upgrades; vendor license activation applies to paid features.
- Product website: https://www.tooljet.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted Basic tier and paid editions have different limits and governance features. Official Docker documentation includes customer VM provisioning paths for AWS, Azure and Google Cloud. AI features require additional outbound vendor endpoints; self-hosting does not imply air-gapped operation. ToolJet v3.21.96-lts lets administrators revoke any workspace personal access token, applies configured rate limits to workflow webhooks, and updates vulnerable dependencies. Self-hosted operators should use v3.21.96-lts or later.

The self-hosted product combines an AGPL-3.0 open-source foundation with commercially licensed/gated self-hosted Enterprise capabilities; Basic/free plan access does not include all premium features.

Reviewed topology uses long-lived application containers on a VM or Kubernetes cluster with PostgreSQL. Classified servers rather than function-based serverless.


Cloud evidence scope: Documented customer-operated deployment guides for AWS, Azure and Google Cloud

### Category fit

- internal-tools: Visual internal app development with database/API connections, dashboards and workflows; access and governance depend on edition.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tooljet.com/docs/setup/docker/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tooljet.com/docs/setup/docker/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tooljet.com/docs/setup/docker/ (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tooljet.com/docs/setup/digitalocean/ (checked 2026-11-12). 


### Cloud deployment evidence

- ToolJet application deployment on cloud VMs (aws, azure, gcp): https://docs.tooljet.com/docs/setup/docker/
  The current vendor Docker guide links optional Terraform VM provisioning on AWS, Azure and Google Cloud, followed by ToolJet server deployment. Configure the application databases, image edition and production settings separately; AI features can use vendor endpoints.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- ToolJet on a customer DigitalOcean Droplet (digitalocean): https://docs.tooljet.com/docs/setup/digitalocean/
  The vendor guide creates an Ubuntu Droplet, configures its firewall and installs Docker and Compose, then follows the ToolJet Docker deployment. The current instructions include LTS and enterprise image guidance; license and AI endpoint requirements remain edition-dependent.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Server Docker Compose deployment and cloud VM provisioning: https://docs.tooljet.com/docs/setup/docker/

- Self-hosted license types and limits: https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/

- System requirements: https://docs.tooljet.com/docs/setup/system-requirements/

- Project functionality and license: https://github.com/ToolJet/ToolJet

- ToolJet on a customer DigitalOcean Droplet: https://docs.tooljet.com/docs/setup/digitalocean/

- ToolJet v3.21.96 LTS security hardening: https://github.com/ToolJet/ToolJet/releases/tag/v3.21.96-lts

### Licensing sources

- https://github.com/ToolJet/ToolJet

- https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/

### Infrastructure sources

- https://docs.tooljet.com/docs/setup/docker/


### 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. Self-hosted workspace login documents Google, GitHub, OIDC, LDAP and SAML. The licensing guide explicitly says OpenID SSO is lost when a paid/trial key expires and the instance reverts to Basic; confirm the selected plan for other identity providers. Scope: Self-hosted login; OpenID entitlement is paid and protocol availability must not imply every provider is included in Basic. Source: https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/ (reviewed 2026-11-20). Supporting source: Self-hosted workspace login — https://docs.tooljet.com/docs/user-management/authentication/self-hosted/workspace-login/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The server guide documents Compose with PostgreSQL and links optional VM Terraform examples. Multi-instance workers need external Redis; ToolJet AI also requires separately documented outbound endpoints. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.tooljet.com/docs/setup/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The self-hosted requirements specify an x86 VM with 1 vCPU, 4 GB RAM and at least 8 GiB disk. PostgreSQL is separately sized at 2 vCPU, 8 GB RAM and 20 GB disk, and Redis at 1 vCPU, 512 MB RAM and 1 GB disk (1 GB RAM recommended for production). Scope: Application, database and Redis requirements are separate; ARM64 is not supported by the reviewed guide and these are not HA capacity guarantees. Source: https://docs.tooljet.com/docs/setup/system-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. The self-hosted licensing guide distinguishes free Basic, 14-day Trial and paid plans. Since v3.5.20-ee-lts, Basic is limited to 2 builders including the super admin, 50 end users, 2 apps, 2 workflows and 1 workspace. Paid features require a vendor-issued key; confirm a quote for larger deployments. Scope: Current self-hosted Basic/paid licensing; not an unlimited 100-user entitlement or hosted-plan quote. Source: https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is v3.21.96-lts, published 2026-11-13. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream ToolJet/ToolJet release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/ToolJet/ToolJet/releases/tag/v3.21.96-lts (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- ToolJet LTS security maintenance review (security-advisory): The release fixes dependency findings, extends webhook rate limits and adds administrator token revocation. Scope: ToolJet v3.21.96-lts release review; this is security maintenance, not a named product-wide vulnerability or a cross-branch support claim. Conditions: Configured workflow webhooks, personal access tokens and bundled dependencies determine applicability. Action: Review the selected LTS line and apply its supported patch; validate webhook limits and token administration. Source: https://github.com/ToolJet/ToolJet/releases/tag/v3.21.96-lts; reviewed 2026-11-17.




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







## Umami

Self-hosted website and event analytics application with dashboards and PostgreSQL storage.

- Listing: https://launchinyourcloud.com/directory/umami/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean, fly, heroku, northflank, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for upstream Umami.
- Licensing model: open-source
- Installation: Build from source, run the official prebuilt container or use its Docker Compose application/PostgreSQL setup.
- Architecture: Customer-operated web analytics service and PostgreSQL database
- Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
- Product website: https://umami.is/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Change the documented initial administrator password and configure production secrets. Third-party integrations, tracking destinations and external databases require separate configuration; Umami Cloud is a distinct offering.

MIT License for upstream Umami. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated web analytics service and PostgreSQL database. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- web-analytics: Website and event analytics through a deployed tracking endpoint and analytics application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-digitalocean (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-fly-io (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-heroku (checked 2026-11-12). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-northflank (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-railway (checked 2026-11-12). 


### Cloud deployment evidence

- Umami self-hosting on a DigitalOcean Droplet (digitalocean): https://docs.umami.is/docs/guides/running-on-digitalocean
  The project documents running the Umami application and PostgreSQL on a customer Droplet with PM2 and Nginx. The guide links older Ubuntu setup examples; use currently supported OS and Node.js versions, configure HTTPS and maintain backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Fly.io (fly): https://docs.umami.is/docs/guides/running-on-fly-io
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Heroku (heroku): https://docs.umami.is/docs/guides/running-on-heroku
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Northflank (northflank): https://docs.umami.is/docs/guides/running-on-northflank
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Railway (railway): https://docs.umami.is/docs/guides/running-on-railway
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Upstream release notes document current runtime/security work and credit multiple named contributors across successive releases.

Reviewed 2026-11-10.

- Maintenance and named release contributors: https://github.com/umami-software/umami/releases

- Public upstream project: https://github.com/umami-software/umami

### Sources

- Official installation and runtime: https://docs.umami.is/docs/install

- Upstream project and capabilities: https://github.com/umami-software/umami

- Current upstream license: https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

- Umami self-hosted deployment on Fly.io: https://docs.umami.is/docs/guides/running-on-fly-io

- Umami self-hosted deployment on Heroku: https://docs.umami.is/docs/guides/running-on-heroku

- Umami self-hosted deployment on Northflank: https://docs.umami.is/docs/guides/running-on-northflank

- Umami self-hosted deployment on Railway: https://docs.umami.is/docs/guides/running-on-railway

### Licensing sources

- https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

### Infrastructure sources

- https://docs.umami.is/docs/install


### 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 API documents an SSO token endpoint requiring existing authentication and Redis. This does not establish a generic SAML/OIDC enterprise identity-provider integration or its edition entitlement. Scope: Authenticated token exchange checked; enterprise federation remains unresolved. Source: https://docs.umami.is/docs/api-reference/sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official guide documents source builds, application containers and Compose. It explicitly identifies the HelmForge Kubernetes chart as third-party; change the default administrator password and configure the database and secrets. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.umami.is/docs/install (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide requires the application runtime and a PostgreSQL database, but does not give a numeric whole-stack production CPU/RAM/storage minimum. Event volume, retention, query concurrency and HA determine capacity; provider demo allocations are not a 100-user, 1 TB HA sizing guarantee. Scope: Current upstream self-hosted topology; whole-system sizing remains unconfirmed. Source: https://docs.umami.is/docs/install (reviewed 2026-11-20).

- License pricing: Documented. The reviewed v3.5.0 application is MIT-licensed and can be self-hosted without a core software subscription. Retain the required copyright/licence notices; hosting, database, operations and Umami Cloud services are separate costs. Scope: Published self-hosted application terms; not a Cloud plan quote. Source: https://github.com/umami-software/umami/blob/v3.5.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







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







## Wiki.js

Open-source self-hosted wiki and knowledge-management content platform.

- Listing: https://launchinyourcloud.com/directory/wiki-js/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0
- Licensing model: open-source
- Installation: Wiki.js-maintained DigitalOcean cloud image, Docker or Helm
- Architecture: Persistent Wiki.js application service with PostgreSQL and optional search and storage integrations
- Operations: Customer manages the DigitalOcean project, Droplet or Kubernetes runtime, PostgreSQL, storage, TLS, identity, backups and upgrades.
- Product website: https://js.wiki/
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

The current installation documentation covers Wiki.js 3.x and warns against the unversioned latest container tag. Pin a supported release, replace default administrator credentials, use a production PostgreSQL deployment and confirm the DigitalOcean image version and upgrade path.

The reviewed Wiki.js upstream license is GNU AGPL version 3.

Wiki.js uses long-lived application and PostgreSQL workloads on a Droplet or Kubernetes cluster.


### Category fit

- content-management: Provides a self-hosted wiki and collaborative knowledge-management CMS with structured pages, permissions and search.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.js.wiki/setup/installation (checked 2026-11-15). 


### Cloud deployment evidence

- Wiki.js-maintained DigitalOcean cloud image (digitalocean): https://docs.js.wiki/setup/installation
  Wiki.js lists DigitalOcean under its maintained cloud-image installation paths. DigitalOcean separately documents the Marketplace image and deployment into a customer DigitalOcean project.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Community and maintenance

Wiki.js release 3.4.0 was published on November 15, 2026, and the upstream contributor history records continuing project participation. The release evidence does not establish the version currently packaged in DigitalOcean Marketplace.

Reviewed 2026-11-15.

- Reviewed release 3.4.0: https://github.com/requarks/wiki/releases/tag/3.4.0

- Upstream contributor history: https://github.com/requarks/wiki/graphs/contributors

### Sources

- Wiki.js installation and cloud images: https://docs.js.wiki/setup/installation

- Wiki.js DigitalOcean Marketplace image: https://docs.digitalocean.com/products/marketplace/catalog/wiki-js/

- Wiki.js AGPL-3.0 license: https://github.com/requarks/wiki/blob/scarlett/LICENSE

- Reviewed release 3.4.0: https://github.com/requarks/wiki/releases/tag/3.4.0

- Upstream contributor history: https://github.com/requarks/wiki/graphs/contributors

### Licensing sources

- https://github.com/requarks/wiki/blob/scarlett/LICENSE

### Infrastructure sources

- https://docs.js.wiki/setup/installation

- https://docs.digitalocean.com/products/marketplace/catalog/wiki-js/


### Buyer diligence


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

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


- Marketplace delivery: Documented. The DigitalOcean 1-Click Droplet catalog packages Wiki.js 3.3.0 and PostgreSQL 18. This package version differs from the directory upstream release snapshot. Review the image and upgrade path before provisioning; marketplace presence does not imply vendor support or commitment credit. Scope: DigitalOcean Wiki.js Droplet package generated 2026-11-11. Source: https://docs.digitalocean.com/products/marketplace/catalog/wiki-js/ (reviewed 2026-11-16).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The current authentication guide documents SAML 2.0, OIDC, OAuth2 and Microsoft Entra ID strategies. Enable a strategy and activate it for each site; reverse proxies must forward the correct host and scheme for callbacks. Scope: Current Wiki.js 3.x administration; older 2.x strategy names differ. Source: https://docs.js.wiki/admin/auth (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 3.x guide supplies Docker Compose and an OCI Helm chart. Its bundled PostgreSQL StatefulSet is a convenience deployment; production database HA is separate. Replace example secrets and pin compatible versions; the latest image tag is not assigned in 3.x. Scope: Upstream 3.x Compose example and Helm deployment; not a validated HA package. Source: https://docs.js.wiki/setup/installation (reviewed 2026-11-20). Deployment artifact: https://docs.js.wiki/setup/installation. Artifact reference: Current 3.x installation examples and oci://ghcr.io/requarks/charts/wiki.

- Minimum footprint / sizing: Documented. The requirements page says one CPU core can run Wiki.js, recommends two or more for workers, and specifies at least 1 GB RAM on Linux plus 1 GB application storage. Database, image and uploaded-content storage are additional; this is not HA sizing for 1 TB of data. Scope: Upstream application starting requirements; not a load or availability guarantee. Source: https://docs.js.wiki/setup/requirements (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream Wiki.js core is licensed under AGPL version 3. This identifies the software terms, not a bundled hosting, support or marketplace-image price; those services and components require separate review. Scope: Upstream scarlett branch license; separately distributed packages may have other charges. Source: https://raw.githubusercontent.com/requarks/wiki/scarlett/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Windmill Self-Hosted

Run scripts and workflows with customer-operated execution workers and an app builder.

- Listing: https://launchinyourcloud.com/directory/windmill/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, render, hetzner, fly, ubicloud
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits
- Licensing model: open-source
- Installation: Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas
- Architecture: Customer-operated server, worker processes and PostgreSQL job/state storage
- Operations: Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
- Product website: https://www.windmill.dev/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes hosted Windmill Cloud. Review current community limits and Enterprise features rather than assuming all features are included. Workflow code can reach external services; worker sandboxing and credentials need explicit configuration. Official self-hosting documentation gives AWS/Azure/GCP guidance. Windmill v1.877.0 prevents workspace members from bypassing the configured AI-model allowlist through direct proxy or completion API calls. Direct configured-key POSTs must now contain JSON with a string model, and existing GitHub App repository resources remain admin-only until an administrator saves them once. Retest API callers and repository-resource access. v1.878.0 is the reviewed current follow-up release.

Official repository licensing combines AGPLv3/Apache-2.0 components with proprietary Enterprise feature code. The broad listing includes both community and commercial editions; current plan limits must be checked separately.

Classified servers for the documented long-lived server/worker containers and PostgreSQL queue/state. Fargate compatibility is managed-container hosting, not a function-only software stack.


Cloud evidence scope: Documented customer-operated deployment guides for AWS, Azure and Google Cloud

### Category fit

- workflow-automation: Code-first scripts, flows, schedules and internal apps with worker execution; enterprise controls and quotas vary.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- ubicloud: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). Source: https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial (checked 2026-11-12). 


### Cloud deployment evidence

- Windmill upstream self-hosting provider compatibility (aws, azure, gcp, digitalocean, render, hetzner, fly, ubicloud): https://github.com/windmill-labs/windmill
  The upstream self-hosting section explicitly names AWS EKS/ECS, Google Cloud, Azure, Ubicloud, Fly.io, Render, Hetzner and DigitalOcean, paired with Docker Compose and Helm installation commands. This is an upstream application-hosting compatibility statement; image licensing and enterprise features are separate. Operate the application in a customer cloud account or managed-platform project as appropriate to the selected provider.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Windmill production deployment on Ubicloud Kubernetes (ubicloud): https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial
  Ubicloud documents customer account setup, PostgreSQL and Kubernetes provisioning, Windmill Helm deployment, application access and TLS configuration. This is a full customer application deployment, not a PostgreSQL connector or GitHub Actions runner integration.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-host architecture, Docker and provider guidance: https://www.windmill.dev/docs/advanced/self_host

- Project capabilities and license files: https://github.com/windmill-labs/windmill

- Self-hosted edition limits: https://www.windmill.dev/pricing

- Licensing and edition terms: https://github.com/windmill-labs/windmill/blob/main/LICENSE

- Windmill production deployment on Ubicloud Kubernetes: https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial

- Windmill v1.878.0 release: https://github.com/windmill-labs/windmill/releases/tag/v1.878.0

- Windmill v1.877.0 policy hardening: https://github.com/windmill-labs/windmill/releases/tag/v1.877.0

- Configured AI-key model enforcement: https://github.com/windmill-labs/windmill/pull/12527

- GitHub App repository approval persistence: https://github.com/windmill-labs/windmill/pull/12524

### Licensing sources

- https://github.com/windmill-labs/windmill/blob/main/LICENSE

- https://www.windmill.dev/pricing

### Infrastructure sources

- https://www.windmill.dev/docs/advanced/self_host


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The self-hosted OAuth/SSO guide documents user login through Google, Microsoft, GitHub and other configured providers, separately from OAuth resource connections. SAML and SCIM are explicitly Enterprise features; identity-group synchronization and custom claim settings also have edition limits. Scope: Instance user login; built-in SSO and Enterprise SAML have different entitlements. Source: https://www.windmill.dev/docs/advanced/setup_oauth (reviewed 2026-11-20). Supporting source: Enterprise SAML and SCIM — https://www.windmill.dev/docs/advanced/saml_and_scim.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. v1.877.0 blocks workspace members from spending configured workspace or instance AI keys on models outside the admin-enabled list. Direct configured-key calls now require JSON with a string model; retest clients. Existing GitHub App repository resources require one administrator save before non-admin access. Scope: Windmill configured AI-key proxy and GitHub App repository-resource authorization. Source: https://github.com/windmill-labs/windmill/pull/12527 (reviewed 2026-11-19). Supporting source: v1.877.0 release — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: Repository approval behavior — https://github.com/windmill-labs/windmill/pull/12524.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose stack includes PostgreSQL and application/worker services. Follow its database-major-version migration notes and choose matching application and dependency releases. Scope: Upstream self-hosted stack; database upgrades require explicit migration planning. Source: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The self-hosting guide suggests roughly one worker per vCPU with 1–2 GB RAM per worker. PostgreSQL, server, proxy and optional editor services require additional capacity; worker concurrency and job isolation change sizing. Scope: Worker rule of thumb, not a complete host minimum or a 100-user/1-TB HA design. Source: https://www.windmill.dev/docs/advanced/self_host (reviewed 2026-11-20).

- License pricing: Documented. At v1.878.0, compilable non-enterprise source is AGPLv3, with Apache-licensed clients/specifications. Published Community binaries also contain proprietary features with free internal-use rights and restrictions on redistribution, resale and embedding. Enterprise rights require a commercial licence. Scope: Versioned source and distributed-binary terms differ; cloud infrastructure and support are separate. Source: https://github.com/windmill-labs/windmill/blob/v1.878.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Windmill v1.878.0 was published November 19, 2026. The preceding v1.877.0 release tightened configured AI-key model authorization and changed direct API validation, while also requiring administrators to resave existing GitHub App repository resources before non-admin use. Scope: Upstream Windmill self-hosted release. Source: https://github.com/windmill-labs/windmill/releases/tag/v1.878.0 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/windmill-labs/windmill/releases/tag/v1.875.0. Supporting source: v1.877.0 policy changes — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: AI model allowlist enforcement — https://github.com/windmill-labs/windmill/pull/12527. Supporting source: GitHub App repository approvals — https://github.com/windmill-labs/windmill/pull/12524.




### Security and lifecycle reviews

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

- Windmill v1.877.0 configured-AI-key policy hardening (security-advisory): Windmill now rejects direct configured-key calls to provider models outside the administrator-enabled list. Scope: Workspace or instance AI keys and GitHub App repository resources in self-hosted Windmill. Conditions: Workspace members with direct API access could previously spend the configured key on other provider models; direct callers now need JSON with a string model. Action: Upgrade to v1.877.0 or later, retest API clients and have an administrator resave existing GitHub App repository resources. Source: https://github.com/windmill-labs/windmill/pull/12527; reviewed 2026-11-19. Supporting source: v1.877.0 release — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: Repository approval persistence — https://github.com/windmill-labs/windmill/pull/12524.




## WordPress Self-Hosted

Open-source content management system with documented customer-account deployments across major clouds and application-provider images.

- Listing: https://launchinyourcloud.com/directory/wordpress-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, oci, linode, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv2 or later; themes, plugins and provider packaging may have separate terms.
- Licensing model: open-source
- Installation: Provider application images/blueprints, Azure App Service quickstart, OCI Resource Manager template, or Akamai StackScript; package and topology vary by provider
- Architecture: PHP application with a customer-controlled MySQL or MariaDB database and persistent media storage.
- Operations: Customer manages WordPress core, themes and plugins, application security, identities, content, database, media, backups, scaling and upgrades.
- Product website: https://wordpress.org/
- Source review: 2026-11-19; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers WordPress.org self-hosting, not WordPress.com SaaS. Provider blueprints accelerate installation but do not replace application hardening, backup, patching and plugin review. Provider packages can lag upstream. The current recommended PHP/database versions and application/plugin stack need a separate patch and HA review. WordPress 7.1.5 is a security release fixing multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Security fixes were backported to eligible older branches. Update immediately, and verify provider images that still advertise 7.1.4 or earlier rather than assuming the platform package is current.

WordPress core is released under GPLv2 or later. Themes, plugins and provider images can add separate licenses or charges.

WordPress runs on provisioned application and database capacity with durable media and database state, even when a provider manages parts of the substrate.


### Category fit

- content-management: Publishes websites, blogs and extensible structured content with themes, plugins and a browser-based editorial interface.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://cloud.google.com/wordpress (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/ (checked 2026-11-18). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm (checked 2026-11-18). 

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

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/one-click-wordpress (checked 2026-11-18). 


### Cloud deployment evidence

- WordPress in the customer's Amazon Lightsail account (aws): https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html
  AWS documents selecting a region, launching the WordPress blueprint and operating the instance in the customer's Lightsail account.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Azure App Service (azure): https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress
  Microsoft's quickstart deploys the WordPress Marketplace item and backing Azure resources into the customer's selected subscription and resource group.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Google Cloud (gcp): https://cloud.google.com/wordpress
  Google documents customer deployments of WordPress on Google Cloud, including a Compute Engine path. Provider packaging and support scope must be reviewed.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress DigitalOcean 1-Click application (digitalocean): https://docs.digitalocean.com/products/marketplace/catalog/wordpress/
  DigitalOcean installs the full WordPress application and database on a customer Droplet. Confirm the resolved image version and production/HA design.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- OCI Resource Manager WordPress template (oci): https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm
  Oracle lists a Resource Manager quickstart that deploys a WordPress instance into OCI. It is a provider application template, not a WordPress support contract or HA guarantee.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Akamai Cloud (Linode) (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress
  Akamai documents full application/database deployment on a customer Compute Instance using StackScript 401697, with Cloud Manager and API/CLI inputs.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- Vultr One-Click WordPress (vultr): https://docs.vultr.com/one-click-wordpress
  Vultr documents launching the full WordPress application on the customer’s selected server size/location and configuring its administrator, domain and TLS.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

The project maintains a dated core release history and documents NASA’s WordPress-based web properties. This establishes maintained software and named adoption, not the cloud account or suitability of a particular plugin stack.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://wordpress.org/documentation/article/wordpress-versions/

- Official maintenance and adoption evidence: https://wordpress.org/showcase/nasa/

### Sources

- Launch and configure WordPress on Amazon Lightsail: https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html

- Create a WordPress site on Azure App Service: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress

- WordPress on Google Cloud: https://cloud.google.com/wordpress

- WordPress GPL license: https://wordpress.org/about/license/

- WordPress DigitalOcean 1-Click application: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/

- OCI Resource Manager WordPress template: https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm

- WordPress on Akamai Cloud (Linode): https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress

- Vultr One-Click WordPress: https://docs.vultr.com/one-click-wordpress

- WordPress 7.1.5 security release: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/

- WordPress 7.1.5 documentation: https://wordpress.org/documentation/wordpress-version/version-7-1-5/

### Licensing sources

- https://wordpress.org/about/license/

### Infrastructure sources

- https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html

- https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress


### Buyer diligence


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

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


- Marketplace delivery: Documented. DigitalOcean offers a WordPress 1-Click Droplet, currently including WordPress 7.1.4, PHP 8.3.36 and MySQL 8.0.46. That database version is below WordPress’s current MySQL 8.4 recommendation. Microsoft also documents an App Service Marketplace item. Packaging and infrastructure charges are separate from WordPress.com. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/ (reviewed 2026-11-18). Supporting source: Microsoft WordPress deployment — https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress. Supporting source: Lightsail WordPress blueprint — https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html. Supporting source: Upstream runtime/database recommendations — https://wordpress.org/about/requirements/. Offer wordpress: DigitalOcean; Droplet 1-Click application; package WordPress 7.1.4; package label latest; https://marketplace.digitalocean.com/apps/wordpress.

- Cloud commitment eligibility: Sources checked — unresolved. The Azure quickstart creates App Service and database resources, but does not establish software-offer commitment credit. Check the selected provider charges and the buyer’s agreement; WordPress core’s free license is not a transactable commitment claim. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. OpenID Connect Generic Client 3.11.4 provides authorization-code SSO and optional account creation/linking for WordPress logins. It is a separately installed community plugin, not bundled core or a provider-image entitlement. It requires PHP 8.0+; configure the IdP, redirect URI and linking policy. Version 3.11.4 changes state/nonce validation and requires review of PKCE and existing-user linking settings. Scope: Optional OpenID Connect Generic Client 3.11.4; WordPress user login, not every theme/plugin or external application. Source: https://wordpress.org/plugins/daggerhart-openid-connect-generic/ (reviewed 2026-11-18). Deployment artifact: https://downloads.wordpress.org/plugin/daggerhart-openid-connect-generic.3.11.4.zip. Artifact reference: OpenID Connect Generic Client 3.11.4.

- SCIM provisioning: Edition-dependent. miniOrange supplies an optional inbound SCIM endpoint: the IdP sends users to WordPress using a base URL and bearer token. Free creation is documented; profile updates, deletion/deactivation and reactivation require Premium. Enhanced group push/import are listed as future work. Soft deactivation retains the account and blocks login, but the guides do not establish revocation of existing sessions. Public package 1.2.0 is separate from the licensed Premium delivery. Scope: Third-party miniOrange WordPress provisioning plugin; inbound users, with Premium lifecycle operations; not native core SCIM. Source: https://wordpress.org/plugins/scim-user-provisioning/ (reviewed 2026-11-18). Supporting source: Provisioning operations, Premium boundary and group limitations — https://plugins.miniorange.com/wordpress-scim-user-provisioning.

- Compliance attestations: Sources checked — unresolved. The WordPress security paper describes project practices, not an independent attestation covering the buyer’s site, plugins, hosting and operations. Obtain the deployment-specific control and audit scope. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/security/ (reviewed 2026-11-18).

- Security controls: Documented. The hardening guide covers restricted database privileges, file permissions, protecting wp-config.php, disabling dashboard file editing, backups and logging. Core, theme and plugin updates remain customer responsibilities; a provider image does not complete this work. Current review: WordPress 7.1.5 fixes multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Update immediately or use the corresponding supported backport, and verify the exact provider image version. Scope: WordPress core 7.1 and eligible backported branches; third-party themes and plugins are outside this advisory. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/ (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://developer.wordpress.org/advanced-administration/security/hardening/. Supporting source: Optional OIDC plugin 3.11.4 security settings and upgrade behavior — https://wordpress.org/plugins/daggerhart-openid-connect-generic/.

- Air-gapped operation: Sources checked — unresolved. WordPress documents manual updates and WP_HTTP_BLOCK_EXTERNAL for requests made through its HTTP API. The latter allows local/site requests and does not govern arbitrary PHP networking by plugins. These controls do not validate a disconnected lifecycle for a selected theme/plugin stack. Confirm offline packages, licences, mail, IdP, media/CDN and update dependencies for that stack. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://developer.wordpress.org/reference/classes/wp_http/block_request/ (reviewed 2026-11-18). Supporting source: Manual core update procedure — https://wordpress.org/documentation/article/updating-wordpress/.

- Deployment artifact / IaC: Documented. Akamai documents WordPress StackScript 401697 and maps its database, administrator and web-server inputs to Cloud Manager and API/CLI deployment. AWS supplies a Lightsail blueprint and OCI lists a Resource Manager WordPress template. These are provider-managed moving packages, not a pinned upstream application release. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress (reviewed 2026-11-18). Supporting source: Lightsail blueprint — https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html. Supporting source: OCI Resource Manager application templates — https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm.

- Minimum footprint / sizing: Documented. The project recommends PHP 8.3+, MariaDB 10.11+ or MySQL 8.4+, and HTTPS; Apache or Nginx is recommended. It does not give a universal CPU/RAM minimum. PHP 7.4/MySQL 5.5.5 compatibility is a legacy fallback, not a recommendation to use those EOL runtimes. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/requirements/ (reviewed 2026-11-18).

- License pricing: Documented. WordPress core is GPLv2 or later, without a core software subscription. Themes, plugins, commercial support and provider packaging may introduce separate terms and charges. Hosting and operations are additional. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/license/ (reviewed 2026-11-18).

- Operating cost estimate: Sources checked — unresolved. 100 internal users and 1 TB do not determine page requests, PHP workers, database I/O or media delivery. Specify traffic/concurrency, plugin stack, cache/CDN, media versus database storage, HA database and application design, backups, egress and paid extensions before estimating AWS us-east-1 operations. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://wordpress.org/about/requirements/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. WordPress 7.1.5 was released November 18, 2026. It is a security release fixing multisite privilege escalation, stored and reflected XSS paths and media-type hardening. Eligible older branches received backports; provider packages may lag. Scope: WordPress.org self-hosted core; themes, plugins and provider images require separate version review. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/ (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://wordpress.org/documentation/article/wordpress-versions/. Supporting source: Version-specific documentation — https://wordpress.org/documentation/wordpress-version/version-7-1-5/.




### Security and lifecycle reviews

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

- Optional WordPress OIDC plugin security settings need review (security-advisory): OpenID Connect Generic Client 3.11.4 changes login state, nonce and verified-email linking checks. PKCE defaults on for new installs but stays off on existing sites until enabled. Scope: Only WordPress sites using the optional OpenID Connect Generic Client plugin; this is not a WordPress core or every-provider-image advisory. Conditions: Existing sites that link users have Link Users Without Verified Email enabled during upgrade and receive an admin notice. The changelog provides no universal affected-version range or CVE. Action: Use the current reviewed plugin, enable PKCE after IdP testing and review linking without verified email. Check callback, account linking and recovery behavior rather than assuming upgrade changes all existing settings. Source: https://wordpress.org/plugins/daggerhart-openid-connect-generic/; reviewed 2026-11-18.

- WordPress 7.1.5 security release (security-advisory): WordPress 7.1.5 fixes multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Scope: WordPress core 7.1 and eligible supported backport branches; themes and plugins remain separate. Conditions: Multisite administration, block-editor/media workflows and the installed core branch determine applicability. Action: Update immediately to 7.1.5 or the corresponding supported backport and verify the exact provider-image version. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/; reviewed 2026-11-19.




## Zabbix Server

Open-source monitoring platform deployed from official Zabbix cloud images into customer accounts.

- Listing: https://launchinyourcloud.com/directory/zabbix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 for Zabbix 7.0+; older releases such as the reviewed DigitalOcean 6.x packages use GPLv2. Provider images/support can be separately charged.
- Licensing model: open-source
- Installation: Official Zabbix VM images from AWS, Azure, Google Cloud or DigitalOcean marketplaces
- Architecture: Customer-operated Zabbix server, web frontend and database on a cloud virtual machine.
- Operations: Customer manages VM, database, storage, agents, networking, TLS, retention, backups, upgrades and monitoring capacity.
- Product website: https://www.zabbix.com/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

Provider packages differ: the reviewed AWS AMI is v7.4.16, the Azure guide uses a 7.4 example, and DigitalOcean lists older 6.x images. Upstream 8.0.0 does not make those images current. Recheck supported branches/OS and patch before use; single appliances do not establish HA or retention sizing.

Zabbix 7.0 and later are AGPLv3; professional support is optional and separate.

Zabbix runs persistent monitoring and database services on customer virtual-machine capacity.


### Category fit

- observability: Monitors infrastructure, networks, applications, logs and service availability through a customer-operated server and agents.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.zabbix.com/documentation/current/en/manual/installation/install/aws_deployment_guide (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.zabbix.com/documentation/current/en/manual/installation/install/cloud_google (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/ (checked 2026-11-18). 


### Cloud deployment evidence

- Zabbix Server on AWS (aws): https://www.zabbix.com/documentation/current/en/manual/installation/install/aws_deployment_guide
  Zabbix documents launching the official server image into the customer's selected AWS VPC and subnet.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Zabbix Server on Azure (azure): https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide
  The current Azure deployment guide launches the server appliance in the customer subscription. Its 7.4 example does not include infrastructure redundancy and is distinct from current upstream 8.0.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Zabbix Server on Google Cloud (gcp): https://www.zabbix.com/documentation/current/en/manual/installation/install/cloud_google
  Zabbix documents deployment from Google Cloud Marketplace into the customer's project.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Official Zabbix DigitalOcean image (digitalocean): https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/
  DigitalOcean lists full Zabbix Server Droplet packages, including 6.0.17 (image 131398452, slug zabbix-zabbixserver60). These older images require supported-branch/patch/OS review; they are not current upstream 8.0 packages.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

Zabbix maintains a named user/case-study catalog and dated current/LTS release histories, providing adoption and maintenance evidence beyond downloads. Provider images retain their own versions, licences and support terms.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://www.zabbix.com/users

- Official maintenance and adoption evidence: https://www.zabbix.com/release_notes

### Sources

- Zabbix cloud images: https://www.zabbix.com/cloud_images

- AWS deployment guide: https://www.zabbix.com/documentation/current/en/manual/installation/install/aws_deployment_guide

- Azure deployment guide: https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide

- Google Cloud deployment guide: https://www.zabbix.com/documentation/current/en/manual/installation/install/cloud_google

- Zabbix license: https://www.zabbix.com/license

- DigitalOcean Droplet package catalog: https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/

### Licensing sources

- https://www.zabbix.com/license

### Infrastructure sources

- https://www.zabbix.com/cloud_images


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 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: Documented. Zabbix publishes an AWS Server AMI, currently package v7.4.16 on Rocky Linux 10.2, with usage pricing after its trial. DigitalOcean’s catalog separately lists older 6.0/6.2/6.4 images. Neither package should be represented as the current upstream 8.0.0 release. Scope: Zabbix Server: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4 (reviewed 2026-11-18). Supporting source: DigitalOcean image IDs and versions — https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/. Offer prodview-jf4elxhe5llj4: Zabbix; Amazon Machine Image (AMI); package v7.4.16; https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4.

- Cloud commitment eligibility: Sources checked — unresolved. The paid AWS image does not establish the buyer’s software commitment eligibility. Direct source/package installation, support contracts and provider images have different charging paths; verify the chosen order and agreement. Scope: Zabbix Server: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4 (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. Zabbix documents SAML 2.0 frontend authentication with IdP mapping and optional just-in-time provisioning. Configure group/role mappings and login permissions. This is distinct from agent/proxy authentication. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml (reviewed 2026-11-18).

- SCIM provisioning: Documented. SCIM 2.0 is documented with SAML just-in-time provisioning enabled, a Super admin API token and api_scim.php. Only users provisioned through the SAML/JIT path are continuously updated; existing local users are not automatically imported. Review deprovisioned-group mapping and the privileged token. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. Zabbix’s year-in-review reports three-year ISO 27001/27017 recertification in 2025. Its public BM PDF MSC-27-849 still expires December 27, 2025. These sources distinguish a renewal claim from the older certificate; neither supplies the renewed issuer record and current assessed scope here. Obtain that document/status before relying on current supplier assurance, and assess the customer monitoring environment separately. The old PDF is not proof that certification lapsed. Scope: Vendor-reported renewal plus an older issuer certificate; current certificate/issuer validity and assessed scope remain unconfirmed. Source: https://blog.zabbix.com/zabbix-in-2025-a-year-of-growth-community-and-innovation/32470/ (reviewed 2026-11-18). Supporting source: Current vendor security-policy statement — https://www.zabbix.com/zabbix_security_policy. Supporting source: Older published issuer certificate — https://assets.zabbix.com/img/about/Zabbix_ISO_27001_ISO_27017_Certificate_EN_2024.pdf. Supporting source: Issuer directs management-system checks to IAF CertSearch — https://bmcertification.com/about-us/certificate-check/.

- Security controls: Documented. The frontend provides SAML role/group mappings and privileged-token controls for SCIM. Zabbix separately documents certificate/PSK encryption for component connections. Configure each transport and access boundary; SSO does not secure agent/proxy traffic by itself. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml (reviewed 2026-11-18). Supporting source: Component encryption guide — https://www.zabbix.com/documentation/current/en/manual/encryption.

- Air-gapped operation: Documented. Zabbix explicitly describes fully on-premises, air-gapped monitoring without external cloud services. The current server setting AllowSoftwareUpdateCheck=0 disables software-update checks. Stage OS/application packages, database, agents, templates and updates for the isolated network; external notification channels and cloud integrations need reachable internal replacements or must be omitted. Scope: Self-hosted Zabbix with prepared packages and local monitoring/database dependencies; not every optional external integration. Source: https://blog.zabbix.com/showcasing-our-potential-at-europol-industry-and-research-days/32733/ (reviewed 2026-11-18). Supporting source: Current update-check setting and server configuration — https://www.zabbix.com/documentation/current/en/manual/concepts/server/server_params.

- Deployment artifact / IaC: Documented. The Azure guide deploys a Zabbix appliance VM into the customer subscription but uses a 7.4 example without infrastructure redundancy. AWS and DigitalOcean provide separately versioned images. Pin the actual image ID/version and supply database/HA automation rather than treating an appliance as a complete HA artifact. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide (reviewed 2026-11-18). Supporting source: AWS image/package — https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4. Supporting source: DigitalOcean image IDs — https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/.

- Minimum footprint / sizing: Documented. The requirements table gives an illustrative small installation at 1,000 metrics with 2 CPUs/8 GiB RAM and medium at 10,000 metrics with 4 CPUs/16 GiB. History/trend retention, polling frequency and database design dominate storage. These are metric-count examples, not user-count or fully redundant database sizing. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/installation/requirements (reviewed 2026-11-18).

- License pricing: Documented. Zabbix 7.0+ is AGPLv3; older releases including the DigitalOcean 6.x images use GPLv2. Direct open-source software, paid support and provider-image usage charges are separate. The reviewed AWS AMI is usage-priced despite open-source upstream licensing. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/license (reviewed 2026-11-18). Supporting source: AWS image usage terms — https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4. Supporting source: Older DigitalOcean release packages — https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/.

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 144.96/month. Only two 2-vCPU/8-GiB application VMs and 30 GB boot gp3 each are priced. Native server HA is active/standby and shares a database. The HA database, all 1 TB monitoring/history data, frontend and proxies are unpriced; this is not the paid appliance AMI price. This is not a complete operating-cost estimate or validated capacity/SLA claim. Scope: Editorial Zabbix native-server HA application layer across two AZs, with a separately designed reachable HA database. Two CPUs/8 GiB mirrors the small 1,000-metric illustration, not a 100-user or throughput benchmark. No data volume or database service is included.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-18). Supporting source: Product topology/sizing basis — https://www.zabbix.com/documentation/current/en/manual/concepts/server/ha. Supporting source: Current AWS us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: Metric-count sizing illustrations — https://www.zabbix.com/documentation/current/en/manual/installation/requirements.

- Release snapshot / cadence: Documented. Zabbix 8.0.0 was released November 5, 2026. The reviewed AWS AMI remains v7.4.16 and DigitalOcean offers older 6.x images. A current upstream release does not mean every provider package has been refreshed. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/release_notes (reviewed 2026-11-18). Supporting source: AWS packaged version — https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4. Supporting source: DigitalOcean packaged versions — https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/.







## Zulip

Topic-organized team chat with a documented self-hosted server.

- Listing: https://launchinyourcloud.com/directory/zulip/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0; hosted services and commercial support plans are separate.
- Licensing model: open-source
- Installation: Install the production server on supported Ubuntu/Debian or use the documented Docker image.
- Architecture: Persistent application and database services on your chosen server infrastructure.
- Operations: Operate server security, email delivery, backups, upgrades and any optional external notification services.
- Product website: https://zulip.com/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This listing covers the self-hosted server; review mobile notification and support service terms for your deployment. Zulip 13.2, released November 13, 2026, fixes new installations failing when PostgreSQL cannot start because postgresql-common 294 leaves the PostgreSQL log directory owned by root; upgrades are unaffected.

The Zulip application is Apache 2.0. Paid hosting, support or notification service arrangements are separate from the server source license.

The production instructions provision an Ubuntu/Debian server or Docker services; classified as servers.


### Category fit

- collaboration: Dedicated team chat organized into channels and topics for real-time and asynchronous collaboration.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://zulip.readthedocs.io/en/stable/production/install.html (checked 2026-11-12). 


### Cloud deployment evidence

- Zulip server installation options (digitalocean): https://zulip.readthedocs.io/en/stable/production/install.html
  The current server installation documentation explicitly offers a preconfigured DigitalOcean Droplet as a self-hosting option, separately from Zulip Cloud. Operate the server, backups and upgrades yourself; mobile push notifications use a separately configured external service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Zulip Server 13.0 and 13.1 were released November 12, 2026, and 13.2 followed on November 13. Version 13.2 fixes a PostgreSQL startup failure affecting new installations. The independent Zulip Foundation stewards the project and owns its operating company Kandra Labs.

Reviewed 2026-11-14.

- Zulip 13.0 major release: https://blog.zulip.com/2026/11/12/zulip-13-0-released/

- Zulip 13.2 maintenance release: https://github.com/zulip/zulip/releases/tag/13.2

- Current production version: https://zulip.readthedocs.io/en/latest/production/install.html

- Foundation governance: https://zulip.com/team/

### Sources

- Production server installation: https://zulip.readthedocs.io/en/latest/production/install.html

- Project capabilities and Apache license: https://github.com/zulip/zulip

- Zulip 13.0 major release announcement: https://blog.zulip.com/2026/11/12/zulip-13-0-released/

- Zulip 13.2 maintenance release: https://github.com/zulip/zulip/releases/tag/13.2

- Zulip Foundation governance: https://zulip.com/team/

- Infrastructure or licensing evidence: https://github.com/zulip/zulip/blob/main/docs/contributing/licensing.md

### Licensing sources

- https://github.com/zulip/zulip

- https://github.com/zulip/zulip/blob/main/docs/contributing/licensing.md

### Infrastructure sources

- https://zulip.readthedocs.io/en/latest/production/install.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 stable server manual documents SAML, OIDC, LDAP and other authentication backends. Configure the selected backend and provider values; Docker installations use corresponding environment settings. Scope: Zulip 13.2 stable documentation as reviewed; not development branch. Source: https://zulip.readthedocs.io/en/stable/production/authentication-methods.html (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The production installation guide documents its server installer and links a Docker alternative. Select a supported release/OS and configure DNS, TLS, email and backups; development documentation may describe a newer branch. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://zulip.readthedocs.io/en/latest/production/install.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The stable guide specifies 1 CPU, 2 GB RAM and 2 GB swap for a smaller deployment, rising to 2 CPUs and 4 GB for 100+ users. Allow at least 10 GB dedicated free disk plus the operating system. Scope: Zulip 13.2 stable baseline; dedicated supported server/VM. Source: https://zulip.readthedocs.io/en/stable/production/requirements.html (reviewed 2026-11-14).

- License pricing: Documented. All Zulip self-hosted features are available in the free open-source edition. Paid self-hosted plans add services such as mobile notifications and support, with eligibility/usage limits on the free notification service. Those service plans differ from Zulip Cloud hosting and customer infrastructure costs. Scope: Published self-hosted plans and optional service entitlements; not Cloud subscription pricing. Source: https://zulip.com/plans/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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






