
# Software on Azure

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

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



## Related questions

- [What self-hosted software runs on Microsoft Azure?](https://launchinyourcloud.com/questions/software-on-azure/)


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: Subscription and resource group
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal (checked 2026-11-20).
- Network: Virtual Network (VNet)
- Identity and access: Microsoft Entra identities and Azure RBAC
- Installation guidance: Bicep/ARM templates or Terraform; review deployment scope and role assignments.
- Guidance source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview
- Guidance reviewed: 2026-11-10


### Private offers

Microsoft Marketplace private offers negotiate product pricing and terms. Confirm the exact offer, billing scope and benefit eligibility rather than assuming all purchases count toward a commitment.
Source: https://learn.microsoft.com/en-us/marketplace/private-offers-overview (reviewed 2026-11-14).

### Private connectivity

Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability.
Source: https://learn.microsoft.com/en-us/azure/private-link/private-link-overview (reviewed 2026-11-14).

### Cross-tenant operations

Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor.
Source: https://learn.microsoft.com/en-us/azure/lighthouse/overview (reviewed 2026-11-14).

### Government environments

Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government.
Source: https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-welcome (reviewed 2026-11-14).

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

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




## ActivityInfo (Self-Managed Server)

Commercial self-managed data collection, relational records and program-reporting platform.

- Listing: https://launchinyourcloud.com/directory/activityinfo-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: Kubernetes manifests
- Architecture: ActivityInfo container with its SQLite data on Azure App Service/Azure Files or a single AKS pod and managed disk.
- 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.activityinfo.org/support/docs/self-managed/azure-web-app-deployment.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 Azure guides describe a single application writer. Extra nodes can improve rescheduling but do not make the SQLite application active-active. Program data models and donor/grant reporting require configuration; this is not a packaged grant-award workflow.

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

ActivityInfo container with its SQLite data on Azure App Service/Azure Files or a single AKS pod and managed disk. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- no-code-databases: Commercial self-managed data collection, relational records and program-reporting platform.

- data-analytics: Commercial self-managed data collection, relational records and program-reporting platform.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.activityinfo.org/support/docs/self-managed/azure-web-app-deployment.html (checked 2026-11-19). 


### Cloud deployment evidence

- Azure Web App (azure): https://www.activityinfo.org/support/docs/self-managed/azure-web-app-deployment.html
  ActivityInfo container with its SQLite data on Azure App Service/Azure Files or a single AKS pod and managed disk. The Azure guides describe a single application writer. Extra nodes can improve rescheduling but do not make the SQLite application active-active. Program data models and donor/grant reporting require configuration; this is not a packaged grant-award workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure Web App: https://www.activityinfo.org/support/docs/self-managed/azure-web-app-deployment.html

- Azure AKS: https://www.activityinfo.org/support/docs/self-managed/azure-kubernetes-deployment.html

- License Key Docs: https://www.activityinfo.org/support/docs/self-managed/update-your-license-key.html

- Grant Mgmt: https://www.activityinfo.org/about/grant-management-system.html

- Self-Managed 5.2: https://www.activityinfo.org/about/releases/self-managed/5.2/index.html

### Licensing sources

- https://www.activityinfo.org/support/docs/self-managed/update-your-license-key.html

- https://www.activityinfo.org/about/grant-management-system.html

### Infrastructure sources

- https://www.activityinfo.org/support/docs/self-managed/azure-web-app-deployment.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 Self-managed Server supports OIDC SSO with ADFS, Microsoft Entra ID and Google Workspace. Its Entra guide registers a customer-server callback and configures the provider in Server Settings, distinguishing the customer installation from ActivityInfo Cloud. Scope: Self-managed application-user federation; customer IdP app registration and server configuration required. Source: https://www.activityinfo.org/support/docs/self-managed/server-requirements.html (reviewed 2026-11-20). Supporting source: Self-managed Entra ID setup — https://www.activityinfo.org/support/docs/self-managed/microsoft-entra-id-configuration.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official AKS guide supplies storage-class, single-replica StatefulSet and Service manifests, with a versioned ActivityInfo image and persistent data volume. Public access, HTTPS and off-cluster backups are separate steps. A second node helps rescheduling; it does not make the application active-active. Scope: Documented single-pod AKS example; not a multi-replica HA architecture. Source: https://www.activityinfo.org/support/docs/self-managed/azure-kubernetes-deployment.html (reviewed 2026-11-20). Deployment artifact: https://www.activityinfo.org/support/docs/self-managed/azure-kubernetes-deployment.html. Artifact reference: guide example: activityinfo/activityinfo:5.2.0; verify a current compatible release.

- Minimum footprint / sizing: Documented. The vendor gives indicative small, medium and large scenarios. Small is 2 virtual cores, 4 GB RAM and 80 GB disk for 10–20 concurrent users and 10 GB attachments; large is 4 cores, 32 GB RAM and 500 GB disk for 50+ concurrent users and 100 GB attachments. Audit history also grows storage. Scope: Scenario-based self-managed sizing, not a 100-user/1-TB or HA capacity guarantee. Source: https://www.activityinfo.org/support/docs/self-managed/server-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: ActivityInfo (Self-Managed Server); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.activityinfo.org/support/docs/self-managed/update-your-license-key.html (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Acumatica Private Cloud ERP

Customer-operated ERP with contract billing, renewals and business records.

- Listing: https://launchinyourcloud.com/directory/acumatica/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: Windows application servers and a supported SQL Server database on customer-controlled cloud 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://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor explicitly identifies AWS and Azure private deployments separately from Acumatica SaaS. Azure Configuration Packages were retired; use supported Windows VMs and current installation requirements. Contract management here concerns billing and renewals, rather than a complete legal negotiation or signature platform. The licence permits usage reporting, which must be reviewed before assuming disconnected operation.

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

Windows application servers and a supported SQL Server database on customer-controlled cloud infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated ERP with contract billing, renewals and business records.

- contract-management: Customer-operated ERP with contract billing, renewals and business records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.acumatica.com/blog/cloud-erp-implementation-choosing-deployment/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319 (checked 2026-11-19). 


### Cloud deployment evidence

- Private Cloud Azure/AWS (aws): https://www.acumatica.com/blog/cloud-erp-implementation-choosing-deployment/
  Windows application servers and a supported SQL Server database on customer-controlled cloud infrastructure. The vendor explicitly identifies AWS and Azure private deployments separately from Acumatica SaaS. Azure Configuration Packages were retired; use supported Windows VMs and current installation requirements. Contract management here concerns billing and renewals, rather than a complete legal negotiation or signature platform. The licence permits usage reporting, which must be reviewed before assuming disconnected operation.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Private Cloud Guide (8319) (azure): https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319
  Windows application servers and a supported SQL Server database on customer-controlled cloud infrastructure. The vendor explicitly identifies AWS and Azure private deployments separately from Acumatica SaaS. Azure Configuration Packages were retired; use supported Windows VMs and current installation requirements. Contract management here concerns billing and renewals, rather than a complete legal negotiation or signature platform. The licence permits usage reporting, which must be reviewed before assuming disconnected operation.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Private Cloud Azure/AWS: https://www.acumatica.com/blog/cloud-erp-implementation-choosing-deployment/

- Azure Private Cloud Guide (8319): https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319

- 2026 R2 PCS SQL Server Requirements: https://community.acumatica.com/acumatica-news-updates-2/important-update-deprecation-of-sql-server-2019-and-added-support-for-sql-server-2025-33402

- Contract Management: https://www.acumatica.com/cloud-erp-software/financial-management/contract-management/

- Contract Management Datasheet PDF: https://www.acumatica.com/media/2026/02/Contract_Management-DS-GBE.pdf

- Acumatica Agreements: https://www.acumatica.com/agreements/

- Acumatica EULA PDF: https://www.acumatica.com/media/2026/02/Acumatica-End-User-License-Agreement-January-2026.pdf

- 2026 R2 Release (Oct 2026): https://www.acumatica.com/corporate-newsroom/press-releases/acumatica-2026-r2-release-with-embedded-ai/

- 2026R2 Build Notes: https://community.acumatica.com/acumatica-news-updates-2/introducing-acumatica-cloud-erp-2026r2-37191

### Licensing sources

- https://www.acumatica.com/agreements/

- https://www.acumatica.com/media/2026/02/Acumatica-End-User-License-Agreement-January-2026.pdf

### Infrastructure sources

- https://www.acumatica.com/blog/cloud-erp-implementation-choosing-deployment/

- https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319


### 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. Acumatica ERP 2026 R2 documents Microsoft Entra ID SSO and group-to-role mapping. The Active Directory and Other External SSO feature must be enabled. This is a configured external identity integration, not an entitlement included in every licence. Scope: Acumatica ERP 2026 R2; external SSO feature, provider registration and tenant access configuration required. Source: https://beacon.acumatica.com/r/Integration-Guide/Integrating-Acumatica-ERP-with-Microsoft-Entra-ID/Integration-with-Microsoft-Entra-ID (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The 2026 R2 guide documents the AcumaticaERPInstall.msi installer and Configuration Wizard. Downloads require partner access and a selected build. This is a licensed Windows application installer, not a public IaC template; retired Azure Configuration Packages should not be reused. Scope: Acumatica ERP 2026 R2 application deployment on a separately provisioned supported server. Source: https://beacon.acumatica.com/r/Installation-Guide/Installing-Acumatica-ERP-On-Premises/Acumatica-ERP-Installation-On-Premises-To-Install-the-Acumatica-ERP-Configuration-Wizard (reviewed 2026-11-20). Deployment artifact: https://community.acumatica.com/. Artifact reference: Acumatica ERP 2026 R2; select the entitled installer build. Supporting source: Retired Azure configuration packages — https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319.

- Minimum footprint / sizing: Documented. The 2026 R2 guide lists 16 GB RAM and two 3.5 GHz cores for the application server, plus a database requirement of 8 GB RAM and two 2 GHz cores. Its small disk baselines exclude workload growth; production uses a supported server OS. Scope: Version-specific application/database requirements; not a complete 1 TB HA deployment or performance guarantee. Source: https://beacon.acumatica.com/r/Installation-Guide/System-Requirements-for-the-Acumatica-ERP-Installation?contentId=a0hF3ukKGMcMMAAO9NbHXA (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Adobe Experience Manager 6.5 Forms (Correspondence Management)

Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.

- Listing: https://launchinyourcloud.com/directory/adobe-aem-forms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AEM 6.5 Forms is separate from AEM as a Cloud Service and Adobe Managed Services. Production Forms capabilities require their own licence. Adobe's VM support remains subject to its technical requirements and reproducibility rules; supported S3 or Blob datastores do not make every cloud-native service supported.

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

Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- correspondence-management: Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.

- document-management: Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements (checked 2026-11-19). 


### Cloud deployment evidence

- AEM 6.5 Tech Reqs (aws, azure): https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements
  Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components. AEM 6.5 Forms is separate from AEM as a Cloud Service and Adobe Managed Services. Production Forms capabilities require their own licence. Adobe's VM support remains subject to its technical requirements and reproducibility rules; supported S3 or Blob datastores do not make every cloud-native service supported.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AEM 6.5 Tech Reqs: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements

- Correspondence Management: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/letters-correspondences/cm-overview

- AEM 6.5 Licensing & Deploy: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy

- AEM 6.5.26.0 Release Notes: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes

### Licensing sources

- https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy

### Infrastructure sources

- https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. AEM 6.5 provides a SAML 2.0 Web SSO handler with signed/encrypted assertions, user creation and group synchronization. It is disabled until configured with provider/entity information and trust material. This establishes the AEM/OSGi web-login path, not automatic SSO for every Forms JEE or desktop component. Scope: AEM 6.5 platform web authentication used by the Forms deployment; choose the applicable runtime and repository paths. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/security/saml-2-0-authenticationhandler (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. Adobe documents installing AEM 6.5 Quickstart and a compatible Forms add-on package through its package-management workflow. Downloads require entitled Adobe access. Select the matching Forms runtime/service pack and deployment topology; this is licensed application installation, not a public Terraform or complete cloud template. Scope: AEM 6.5 Forms on OSGi installation path; Forms JEE and Correspondence Management components require their applicable guides. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/install-aem-forms/osgi-installation/installing-configuring-aem-forms-osgi (reviewed 2026-11-20). Deployment artifact: https://experience.adobe.com/downloads. Artifact reference: AEM 6.5 Quickstart plus compatible Forms add-on/service pack; entitled download selection required. Supporting source: Base AEM installation — https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy.

- Minimum footprint / sizing: Sources checked — unresolved. Adobe lists base AEM installation requirements and separate Forms temporary-space/topology requirements, but these do not establish a complete Correspondence Management production sizing profile. Author/publish roles, document services, storage and redundant instances must be sized for the selected Forms runtime and workload. Scope: AEM 6.5 Forms/Correspondence Management; generic AEM minima and installer temporary space are not a validated whole-system HA floor. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/install-aem-forms/osgi-installation/installing-configuring-aem-forms-osgi (reviewed 2026-11-20). Supporting source: General AEM technical requirements — https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements.

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Adobe Experience Manager 6.5 Forms (Correspondence Management); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Aiven for Apache Kafka BYOC

Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.

- Listing: https://launchinyourcloud.com/directory/aiven-kafka-byoc/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately.
- Licensing model: commercial-only
- Installation: Enable BYOC with Aiven, apply the provider-specific Terraform template, then provision Classic Kafka through the Aiven Console or CLI.
- Architecture: Persistent Kafka workload nodes run in the customer's custom cloud. In the documented private topology, the Aiven management plane connects through a bastion.
- Operations: Aiven manages provisioning and maintenance. The customer provides the cloud account, network configuration, IAM, quotas, and backup storage access.
- Product website: https://aiven.io/kafka
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-21; infrastructure review: 2026-11-21

### Scope and qualifications

Classic Kafka uses fixed service plans. Diskless topics require enablement and an eligible custom cloud and plan. Aiven documents limited OCI access for its wider BYOC program. Confirm product and region eligibility. Metrics and logs reach Aiven, and controlled support access is documented. Agree how to migrate topics and remove delegated access before exit.

Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately.

Persistent Kafka workload nodes run in the customer's custom cloud. In the documented private topology, the Aiven management plane connects through a bastion.


### Category fit

- streaming: Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud (checked 2026-11-21). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud (checked 2026-11-21). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud (checked 2026-11-21). 

Operating responsibility: Aiven operates and maintains Kafka in the customer's custom cloud. Its separate management plane provisions and monitors the service through delegated access; the customer supplies cloud-account, network and policy prerequisites. Source: https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc (checked 2026-11-21). Supporting source: BYOC networking and control plane — https://aiven.io/docs/platform/howto/byoc/networking-security.


### Cloud deployment evidence

- Aiven custom cloud on AWS (aws): https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud
  The customer applies a Terraform template in its AWS account and grants Aiven permissions through an IAM role.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Aiven custom cloud on Azure (azure): https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud
  The customer sets up an Azure custom cloud in its subscription before provisioning Kafka.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Aiven custom cloud on Google Cloud (gcp): https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud
  The customer sets up a Google Cloud custom cloud in its project before provisioning Kafka.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Kafka BYOC provisioning: https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc

- Private networking and vendor access: https://aiven.io/docs/platform/howto/byoc/networking-security

- BYOC eligibility and billing: https://aiven.io/docs/platform/concepts/byoc

- Shared responsibility matrix: https://aiven.io/responsibility-matrix

- Aiven custom cloud on AWS: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud

- Aiven custom cloud on Azure: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud

- Aiven custom cloud on Google Cloud: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud

### Licensing sources

- https://aiven.io/docs/platform/concepts/byoc

### Infrastructure sources

- https://aiven.io/docs/platform/howto/byoc/networking-security


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Organization administrators can configure a SAML identity provider and verified domains for Aiven Console users. BYOC Kafka is provisioned through that same Aiven organization and Console. This authenticates the vendor-hosted management plane; Kafka client authentication is a separate configuration. Scope: Aiven organization / Console identity for the managed BYOC service, not Kafka protocol clients.. Source: https://aiven.io/docs/platform/howto/saml/add-identity-providers (reviewed 2026-11-21). Supporting source: Kafka BYOC Console prerequisites — https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. After BYOC approval, Aiven generates a customer-specific Terraform template in Console or CLI. The customer downloads and applies it to prepare the cloud account and delegated access, then provisions Kafka in the custom cloud. This is account-specific managed-service onboarding, not a public standalone self-managed Kafka installer. Scope: AWS custom-cloud Terraform onboarding; obtain and review the generated template and permissions.. Source: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud (reviewed 2026-11-21). Supporting source: Google Cloud generated Terraform onboarding — https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud. Supporting source: Azure custom-cloud onboarding — https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud.

- Minimum footprint / sizing: Sources checked — unresolved. The Kafka BYOC guide requires a fixed Classic Kafka plan and gives business-4 as a CLI example, but does not establish a quantitative minimum topology for the customer's provider, region and workload. Diskless topics have separate eligible plans and can add a PostgreSQL service. Obtain broker counts, instance resources, storage and availability-zone design from Aiven; the example plan name is not a sizing guarantee. Scope: Managed Kafka BYOC sizing unresolved; do not substitute Aiven-hosted Free/Developer plans.. Source: https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc (reviewed 2026-11-21).

- License pricing: Documented. BYOC is a bespoke commercial managed service requiring an Aiven commitment and Advanced or Premium support. Pricing depends on the agreement. Aiven bills managed-service fees separately from the customer's cloud infrastructure and network traffic; standard all-inclusive Aiven Cloud rates do not establish BYOC charges. Scope: Commercial Kafka BYOC eligibility and separate billing; request the supported plan and a quote.. Source: https://aiven.io/docs/platform/concepts/byoc (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Apache Doris Self-Hosted

Apache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.

- Listing: https://launchinyourcloud.com/directory/apache-doris/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, alibaba, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the core project; optional third-party components can carry separate or incompatible licenses.
- Licensing model: open-source
- Installation: Doris Operator on AWS EKS or Alibaba ACK/ACS, or cloudimg’s Azure VM image; pin application/operator/image versions separately
- Architecture: Customer-operated FE/BE services with persistent storage, through Kubernetes or a separately packaged single-node Azure VM.
- Operations: Customer manages the selected Kubernetes platform or Azure VM/OS, provider permissions, networking, persistent storage, database identities, backups, monitoring, scaling and upgrades. Upstream EKS/ACK/ACS instructions and the seller VM have different host and service boundaries.
- Product website: https://doris.apache.org/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers Apache Doris, not a vendor-hosted derivative. Upstream guides document EKS and Alibaba ACK/ACS; ACS needs privileged BE initialization and has service/network constraints. The separate cloudimg Azure image packages Doris 4.0.6 with one FE/BE and is not HA. Its moving image and older application version require review; seller packaging does not establish Apache support. Review quorum, replication, storage and optional dependency licences for the chosen topology.

Apache Doris core is Apache-2.0 licensed. Optional third-party dependencies must be reviewed separately.

Doris runs persistent FE/BE database services on provisioned Kubernetes capacity or a separately packaged Azure VM/data disk. AWS EKS, Alibaba ACK/ACS and the single-node cloudimg VM have different initialization, redundancy and service constraints.


### Category fit

- data-analytics: Provides a massively parallel analytical database for real-time reporting and large-scale SQL analytics.

- databases-vector: Runs a persistent distributed analytical database on customer-controlled compute and storage.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/ (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/ (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/ (checked 2026-11-18). 


### Cloud deployment evidence

- Apache Doris on Amazon EKS (aws): https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/
  The stable 4.x guide covers AWS EKS node/IAM preparation and links to Doris Operator for the application cluster. Review the full operator manifests and replica/storage design; the separate CloudFormation trial template is not HA.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Apache Doris on Alibaba Cloud ACK/ACS (alibaba): https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/
  The stable 4.x guide deploys a DorisCluster through Doris Operator on customer ACK or ACS, including private image registry, FE/BE resources and service/load-balancer configuration. ACS requires privileged mode for BE initialization; use ACK if that capability is unavailable.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- cloudimg Apache Doris VM in a customer Azure subscription (azure): https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/
  The seller documents subscription/resource group/VNet selection and the image URN cloudimg1647283583153:apache-doris-ubuntu-24-04:default:latest. It installs full FE/BE services with a dedicated disk, local administrator credentials and SQL/HTTP access. The guide packages 4.0.6 as a single-node deployment, not HA or an upstream support contract; resolve the moving image before use.
  Source type: third-party-package; reviewed: 2026-11-18; vendor support: not-assessed. Versions: Guide application 4.0.6; Azure image latest must be resolved.


### Community and maintenance

Apache Doris publishes its PMC/committer team and a named user catalog, including production analytics users, alongside current application releases. Governance/adoption does not establish a managed service’s customer-account boundary.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://doris.apache.org/community/team/

- Official maintenance and adoption evidence: https://doris.apache.org/users/

- Official maintenance and adoption evidence: https://github.com/apache/doris/releases/tag/4.1.5-release

### Sources

- Apache Doris 4.x AWS EKS preparation: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/

- Stable Doris Operator overview: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/doris-operator-overview/

- Apache Doris license: https://github.com/apache/doris/blob/master/LICENSE.txt

- Apache Doris on Alibaba Cloud ACK/ACS: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/

- cloudimg full Azure deployment guide: https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/

- Provider exact Azure offer metadata: https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en

### Licensing sources

- https://github.com/apache/doris/blob/master/LICENSE.txt

### Infrastructure sources

- https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/

- https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/

- https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/


### 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: Documented. cloudimg publishes Azure VM offer cloudimg1647283583153.apache-doris-ubuntu-24-04, default plan. The seller guide and current public catalog identify Apache Doris 4.0.6, one FE and one BE, OpenJDK 17 and a dedicated data disk. This is a charged third-party package of Apache-licensed Doris, not VeloDB Cloud or an upstream support commitment. Resolve the exact image behind the moving latest URN and review upgrades; a single-node image is not an HA cluster. Scope: Third-party Azure VM package; US public-catalog availability and seller guide checked; not every region, version or production topology. Source: https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/ (reviewed 2026-11-18). Supporting source: Current seller product and Marketplace link — https://www.cloudimg.co.uk/products/apache-doris-on-ubuntu-24-04-lts-azure/. Supporting source: Provider public offer, plan and availability metadata — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en. Offer cloudimg1647283583153.apache-doris-ubuntu-24-04: cloudimg; Azure virtual-machine image; default plan; package Guide application 4.0.6; moving latest image; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.apache-doris-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. Microsoft’s public catalog marks the reviewed cloudimg Apache Doris Azure VM offer as ineligible for MACC. Its software packaging/support charge therefore does not supply MACC-eligible software spend through this public offer. Recheck the current offer at procurement. Azure infrastructure, other providers, commercial add-ons and separately negotiated offers need their own eligibility and agreement review. Scope: MACC eligibility of public cloudimg offer cloudimg1647283583153.apache-doris-ubuntu-24-04, default plan, US catalog checked; other procurement paths are outside this finding. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-18). Supporting source: Microsoft definition of the catalog eligibility field — https://raw.githubusercontent.com/Azure/azure-rest-api-specs/00f083f4efcbfe54730b7af700a50327232c199a/specification/marketplacecatalog/data-plane/Marketplace/stable/2021-10-01/marketplacecatalog.json. Supporting source: Microsoft MACC purchasing and infrastructure boundaries — https://learn.microsoft.com/en-us/marketplace/azure-consumption-commitment-benefit.

- Single sign-on: Sources checked — unresolved. Version-4.x documentation describes custom pluggable authenticators for OIDC/JWT and BI-tool sign-on, while its authentication overview lists built-in passwords and LDAP. No reviewed ready-to-use, supported OIDC plugin/version is established here. Confirm the plugin, protocol and client handshake rather than treating the SPI as bundled SSO. Scope: 4.x custom authentication extension path; packaged federation unresolved. Source: https://doris.apache.org/docs/4.x/key-features/pluggable-auth/ (reviewed 2026-11-20). Supporting source: Built-in authentication scope — https://doris.apache.org/docs/4.x/admin-manual/auth/authentication-and-authorization/.

- SCIM provisioning: Sources checked — unresolved. Doris 4.x pluggable authentication, LDAP group mapping and Ranger authorisation do not establish an inbound SCIM endpoint. Confirm a current provisioning integration/artifact, user/group create/update/deactivate/delete behavior, SQL role mapping and active-session handling; authentication extension points alone do not settle lifecycle management. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/key-features/pluggable-auth/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. Apache’s stable 4.x documentation establishes authentication and authorisation configuration, not an independent attestation for the customer’s Doris cluster. No current report/certificate with a relevant assessed boundary was established. Assess the actual FE/BE/operator, identity and data-source components and request the supplier/operating assurance the buyer requires. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/key-features/pluggable-auth/ (reviewed 2026-11-18).

- Security controls: Documented. Doris documents RBAC roles/grants, LDAP authentication, IP restrictions and configurable password policy. The password-policy default is not a hardened deployment guarantee; configure the selected controls and protect FE/BE endpoints. The Azure seller generates a per-VM root password and defaults the NSG to SSH only. Its overview says loopback binding while the plan says all interfaces: inspect listeners and NSG rules before enabling SQL/HTTP access. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/admin-manual/auth/authentication-and-authorization/ (reviewed 2026-11-18). Supporting source: Azure first-boot credentials and network defaults — https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/. Supporting source: Provider description/plan binding disagreement — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.

- Air-gapped operation: Sources checked — unresolved. The 4.x guide explicitly warns that external LDAP/KDC/Ranger integrations are unsuitable when unreachable in an air-gapped cluster and recommends local accounts/RBAC. That is an identity-design constraint, not a complete offline lifecycle. Confirm all FE/BE/operator/OS artifacts, image mirroring, upgrades, backups and internal data-source dependencies for the selected stable release. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/key-features/pluggable-auth/ (reviewed 2026-11-18). Supporting source: Current operator/private-registry installation evidence — https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/doris-operator-overview/.

- Deployment artifact / IaC: Documented. Apache maintains Doris Operator for custom-resource deployment and lifecycle management, with AWS and Alibaba-specific preparation guides. Pin operator and FE/BE image versions separately. The AWS CloudFormation quickstart is explicitly a test/experience path with a single FE, not the HA reference. The separate Azure image uses the moving URN cloudimg1647283583153:apache-doris-ubuntu-24-04:default:latest; resolve and pin its image version. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/doris-operator-overview/ (reviewed 2026-11-18). Supporting source: Version 4.x AWS preparation — https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/. Supporting source: Version 4.x Alibaba ACK/ACS preparation — https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/. Supporting source: Testing-only CloudFormation limitations — https://doris.apache.org/docs/dev/install/deploy-on-cloud/doris-on-aws/. Supporting source: Upstream operator artifact repository — https://github.com/apache/doris-operator. Supporting source: Azure image URN and CLI deployment — https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/.

- Minimum footprint / sizing: Documented. The stable 4.x hardware guide gives FE memory minimum 16 GB and recommended 64 GB+, and BE memory of CPU cores × 4 GB minimum and × 8 GB recommended. It recommends SSDs, ext4/xfs and 10 Gb networking. Set FE quorum, BE replication, compression and compaction reserve explicitly; a single-FE trial is not HA. cloudimg instead suggests Standard_B4ms (4 vCPU/16 GiB) for its single-node appliance; this is not the upstream production/HA sizing baseline. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/install/preparation/env-checking/ (reviewed 2026-11-18). Supporting source: Separate Azure appliance sizing — https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/.

- License pricing: Documented. Apache Doris is Apache 2.0 licensed. Review optional dependencies and distribution components under their own notices. Vendor-hosted derivatives, commercial support and marketplace repackaging have separate terms. The reviewed Azure default plan charges USD 0.04/vCPU-hour for cloudimg packaging/support (USD 0.16/hour at four vCPUs), plus Azure infrastructure; the upstream Apache licence stays free. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://github.com/apache/doris/blob/master/LICENSE.txt (reviewed 2026-11-18). Supporting source: Exact Azure plan and per-core meters — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.

- Operating cost estimate: Sources checked — unresolved. Specify ingestion rate, query concurrency, indexes, compression, replica count, FE quorum, BE count, compaction reserve and storage-compute mode. One TB raw data and 100 users do not determine usable replicated storage, IOPS or an HA compute bill. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://doris.apache.org/docs/4.x/install/preparation/env-checking/ (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. Apache Doris 4.1.5-release was published October 15, 2026. This application release is separate from the date/version of Doris Operator. Use stable documentation and verify operator/application compatibility; dev documentation describes unreleased behavior. cloudimg’s Azure guide/plan packages 4.0.6; it is separate from this 4.1.5-release snapshot and the resolved image version. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://github.com/apache/doris/releases/tag/4.1.5-release (reviewed 2026-11-18). Supporting source: Older Azure packaged application — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.







## Apache Druid

Column-oriented analytics database for interactive queries over streaming and historical event data.

- Listing: https://launchinyourcloud.com/directory/apache-druid/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Apache Druid.
- Licensing model: open-source
- Installation: Run the official server distribution with bin/start-druid; distributed production deployments require the documented cluster services and storage configuration.
- Architecture: Customer-operated JVM analytics services, metadata store and deep storage
- Operations: Customer manages cluster sizing, ingestion, metadata and deep storage, access controls, backups and upgrades.
- Product website: https://druid.apache.org/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The smallest bundled configurations are evaluation examples. Data ingestion connectors and storage destinations can involve external services; configure their account and network boundaries separately. Apache Druid 39.0.0 requires Java 25 and drops Java 21 support. Its upgrade notes also change SQL INSERT/REPLACE authorization, replace SysMonitor with OshiSysMonitor, add taskStatus to task/run/time metrics, change Netty direct-memory behavior, and move the bundled MariaDB driver to 3.5.10 with jdbc:mariadb: preferred. Test permissions, dashboards, memory limits and metadata-store URLs before rollout.

Apache License 2.0 for upstream Apache Druid. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated JVM analytics services, metadata store and deep storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- data-analytics: Real-time OLAP database for SQL analysis of ingested streaming and batch data; this is an analytics engine rather than a dashboard authoring application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 


### Cloud deployment evidence

- Apache Druid cloud deployment FAQ (aws, azure, gcp): https://druid.apache.org/faq/
  The Apache project explicitly identifies AWS, Google Cloud and Azure as deployment environments for Druid. This is a project compatibility statement paired with the installation documentation, not a managed service or certification; configure metadata, deep storage and cluster operations separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Apache project with a maintained upstream release history and a project-curated production adopter directory including Adikteev, AdsWizz and Airbnb.

Reviewed 2026-11-10.

- Current Druid releases: https://github.com/apache/druid/releases

- Named production adopters: https://druid.apache.org/druid-powered/

### Sources

- Official installation and runtime: https://druid.apache.org/docs/latest/operations/single-server/

- Upstream project and capabilities: https://github.com/apache/druid

- Current upstream license: https://github.com/apache/druid/blob/master/LICENSE

- Analytics functionality: https://druid.apache.org/

- Apache Druid 39.0.0 release: https://github.com/apache/druid/releases/tag/druid-39.0.0

- Apache Druid 39.0.0 upgrade notes: https://druid.apache.org/docs/39.0.0/release-info/upgrade-notes

### Licensing sources

- https://github.com/apache/druid/blob/master/LICENSE

### Infrastructure sources

- https://druid.apache.org/docs/latest/operations/single-server/


### 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 druid-kerberos extension provides SPNEGO/GSSAPI authentication for Druid HTTP endpoints, with service principals, keytabs, cookies and authorizer mapping. Configure compatible browser/API clients and protect every endpoint; this is Kerberos federation, not native SAML/OIDC. Scope: Upstream HTTP Kerberos/SPNEGO authentication extension. Source: https://druid.apache.org/docs/latest/development/extensions-core/druid-kerberos/ (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 server distribution includes bin/start-druid, which derives memory settings from host resources. Older single-server reference scripts are deprecated; production cluster storage/services need a separate architecture plan. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://druid.apache.org/docs/latest/operations/single-server/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current 39.0.0 local quickstart requires at least 6 GiB RAM and Java 25. It is an introductory single-machine ingestion/query setup, not a production or HA footprint. Data volume, ingestion tasks, service roles and availability requirements need separate sizing. Scope: Druid 39 local tutorial baseline; production capacity excluded. Source: https://druid.apache.org/docs/latest/tutorials/index.html (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/apache/druid/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Apache Druid druid-39.0.0 was published November 19, 2026. It requires Java 25, changes SQL write authorization and monitoring labels, replaces SysMonitor, changes Netty direct-memory behavior and updates MariaDB Connector/J. Review the complete incompatible-change and upgrade notes. Scope: Upstream Apache Druid release; deployment packages and commercial distributions may differ. Source: https://github.com/apache/druid/releases/tag/druid-39.0.0 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/apache/druid/releases/tag/druid-38.0.0. Supporting source: Version-specific upgrade notes — https://druid.apache.org/docs/39.0.0/release-info/upgrade-notes.







## Apache Unomi

Apache customer-data platform for event profiles, segmentation and personalization.

- Listing: https://launchinyourcloud.com/directory/apache-unomi/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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
- Architecture: Unomi Java services and search datastore in a cloudimg Azure VM.
- 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/apache/unomi
- 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 concerns customer profiles and segmentation; it is not itself a complete campaign delivery or email service.

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

Unomi Java services and search datastore in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Apache customer-data platform for event profiles, segmentation and personalization.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.apache-unomi-ubuntu-24-04
  Unomi Java services and search datastore in a cloudimg Azure VM. This entry concerns customer profiles and segmentation; it is not itself a complete campaign delivery or email service.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes sergehuber, jkevan, jsinovassin, 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/unomi/graphs/contributors

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

### Sources

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

- GitHub LICENSE (Apache-2.0): https://raw.githubusercontent.com/apache/unomi/master/LICENSE

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

- GitHub Commits: https://github.com/apache/unomi/commits/master

- Official upstream releases: https://unomi.apache.org/download.html

### Licensing sources

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

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The versioned server guide documents HTTP Basic authentication, Karaf accounts and protected API access. Sending a customer-profile login/identify event from another SSO system does not authenticate an operator to Unomi. A supported external SAML/OIDC operator-login integration and role mapping remain unconfirmed. Scope: Unomi 3.1 headless server/operator authentication, distinct from tracked visitor identity. Source: https://unomi.apache.org/manual/3_1_x/index.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Apache publishes the Unomi 3.1.0 binary distribution with signatures/checksums. The versioned manual documents Java/Karaf startup and a compatible Elasticsearch service. Use the selected release distribution and verify dependencies; some Docker quickstart snippets still show older image versions and must not be copied as a version-matched production stack. Scope: Current official 3.1.0 server binary; upstream application and third-party Azure image are separate releases. Source: https://unomi.apache.org/download.html (reviewed 2026-11-20). Deployment artifact: https://www.apache.org/dyn/closer.lua/unomi/3.1.0/unomi-3.1.0-bin.tar.gz. Artifact reference: 3.1.0 official binary distribution; verify Apache signature and SHA512. Supporting source: Versioned 3.1 installation and operations manual — https://unomi.apache.org/manual/3_1_x/index.html.

- Minimum footprint / sizing: Sources checked — unresolved. The 3.1 manual establishes Java/Karaf and Elasticsearch dependencies, clustering and heap tuning but no whole-stack CPU/RAM/storage minimum for this workload. A JVM heap example is not physical server capacity; size profile/event throughput, retention, search storage and redundancy separately. Scope: Unomi 3.1 application/search topology; workload-specific production sizing remains unconfirmed. Source: https://unomi.apache.org/manual/3_1_x/index.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The official Apache download page identifies Unomi 3.1.0, released 2026-11-19. This updates the earlier 3.0.1 snapshot. The server and JavaScript tracker have separate releases; confirm the third-party Azure image version independently. This does not establish support duration or a future cadence. Scope: Official upstream server release, distinct from tracker and provider-image versions. Source: https://unomi.apache.org/download.html (reviewed 2026-11-20).







## Appian Connected Contract Lifecycle Management (CLM)

Commercial contract lifecycle application installed into a licensed, self-managed Appian platform.

- Listing: https://launchinyourcloud.com/directory/appian-clm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Appian Operator and Helm on EKS, AKS or GKE, an Appian system database and a separate supported business database.
- 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.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

CLM 1.2.0 requires the documented Appian 25.3 Advanced or Premium tier and a separate CLM purchase. Platform/operator versions and CLM packages are separate. Newly issued Kubernetes licences require Operator 0.205.0 or later from November 2026; exclude Fargate, GKE Autopilot and Azure ACI from this persistent-cluster path.

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

Appian Operator and Helm on EKS, AKS or GKE, an Appian system database and a separate supported business database. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- contract-management: Commercial contract lifecycle application installed into a licensed, self-managed Appian platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html (checked 2026-11-19). 


### Cloud deployment evidence

- Appian on K8s (aws, azure, gcp): https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html
  Appian Operator and Helm on EKS, AKS or GKE, an Appian system database and a separate supported business database. CLM 1.2.0 requires the documented Appian 25.3 Advanced or Premium tier and a separate CLM purchase. Platform/operator versions and CLM packages are separate. Newly issued Kubernetes licences require Operator 0.205.0 or later from November 2026; exclude Fargate, GKE Autopilot and Azure ACI from this persistent-cluster path.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Appian on K8s: https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html

- CLM Self-Managed Install: https://docs.appian.com/suite/help/26.10/clm-25.3.1.2/clm-install-guide.html

- K8s License Request: https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html#request-licenses

- Appian Terms (Website ToU): https://appian.com/legal/terms-of-use

- Release Notes: https://docs.appian.com/suite/help/26.10/Appian_Release_Notes.html

### Licensing sources

- https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html#request-licenses

- https://appian.com/legal/terms-of-use

### Infrastructure sources

- https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.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. Appian 26.10 documents SAML browser SSO configured in its Admin Console with IdP metadata, certificates and account mapping. CLM runs on that Appian identity platform; confirm users, groups and any external integration identities separately rather than treating every connected service as federated. Scope: Self-managed Appian platform authentication underlying CLM. Source: https://docs.appian.com/suite/help/26.10/SAML_for_Single_Sign-On.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Appian-on-Kubernetes guide deploys the licensed platform/operator; the separate CLM guide installs plugins, database SQL and an imported application package/customisation file. Obtain entitled images/packages and compatible versions. Platform provisioning alone does not install or configure the CLM solution. Scope: Appian 26.10 platform and separately imported CLM solution; package access and configuration required. Source: https://docs.appian.com/suite/help/26.10/clm-25.3.1.2/clm-install-guide.html (reviewed 2026-11-21). Deployment artifact: https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html. Artifact reference: Appian 26.10 / Kubernetes guide k8s-0.205.0. Supporting source: Platform Kubernetes installation — https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html.

- Minimum footprint / sizing: Documented. The self-managed Kubernetes guide gives Extra Small sites a non-HA reference of 8 CPU/64 GB RAM plus 115 GB RWO and 100 GB log storage; HA increases CPU/RAM threefold and changes persistent storage. These are Appian platform starting points, not a CLM-only or validated 100-user/1-TB capacity estimate. Scope: Appian 26.10 platform-level Kubernetes sizing classes; CLM workload and dependencies need validation. Source: https://docs.appian.com/suite/help/26.10/resource-requests-and-limits.html (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Appian Connected Contract Lifecycle Management (CLM); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html#request-licenses (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## Apryse Fluent

Customer-hosted document-template management and rendering software for automated business output.

- Listing: https://launchinyourcloud.com/directory/apryse-fluent/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- 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; Docker / Compose
- Architecture: Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App Service.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.

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

Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App Service. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Customer-hosted document-template management and rendering software for automated business output.

- workflow-automation: Customer-hosted document-template management and rendering software for automated business output.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2 (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerContainerAppDeployment (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EC2 Guide (aws): https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2
  Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App Service. This is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Container Apps (azure): https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerContainerAppDeployment
  Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App Service. This is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS EC2 Guide: https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2

- Azure Container Apps: https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerContainerAppDeployment

- Azure App Service Engine: https://fluent.apryse.com/documentation/engine-guide/Fluent%20RESTful%20Engines/DeployingJavaRESTfulEngineAzureAppService

- License Types: https://fluent.apryse.com/documentation/store-guide/Licensing/types

- Apryse Legal: https://apryse.com/legal

- Release Schedule: https://fluent.apryse.com/documentation/support-guide/ReleaseSchedule

### Licensing sources

- https://fluent.apryse.com/documentation/store-guide/Licensing/types

- https://apryse.com/legal

### Infrastructure sources

- https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2

- https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerContainerAppDeployment


### 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. Fluent Manager supports SAML 2.0 as a service provider; the vendor identifies Microsoft Entra ID and Keycloak as tested providers. A Global Administrator configures the integration. This is Manager user login, not an SSO claim for the headless Fluent rendering engine. Scope: Fluent Manager component; check the selected Manager version and IdP configuration. Source: https://fluent.apryse.com/documentation/manager-guide/sso/ManagerSSO (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 provides a version-matched Kotlin helper script that generates a Docker Compose deployment for Manager frontend, backend and database. Match the script version to Manager and configure durable data, secrets and HTTPS; the script is not a complete cloud/HA template. Scope: Fluent Manager deployment; headless engine and Designer are separate components. Source: https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerDockerDeployment (reviewed 2026-11-20). Deployment artifact: https://fluent.apryse.com/documentation/downloads. Artifact reference: Select helper script x.y.z matching Fluent Manager x.y.z from the linked vendor download.

- Minimum footprint / sizing: Documented. The Manager Docker guide lists a minimum of two CPU cores, 4 GB RAM and 12 GB disk, including 7 GB for its database and 5 GB for containers/images. Storage grows with templates. This baseline does not size rendering-engine workloads, replicas or a 100-user, 1 TB HA deployment. Scope: Fluent Manager frontend/backend/database baseline; not the complete Fluent product family or a throughput guarantee. Source: https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerDockerDeployment (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Archer Third-Party Governance

Commercial customer-hosted third-party risk and governance application on the Archer platform.

- Listing: https://launchinyourcloud.com/directory/archer-tprm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: Supported Archer application and database VMs on customer AWS or Azure 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://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Use the current On-Premises release and sizing matrix with the selected Third-Party Governance entitlement. The dated cloud guide's example instance types do not establish a current HA workload or price estimate. Archer SaaS is separate.

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

Supported Archer application and database VMs on customer AWS or Azure infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- vendor-supplier-document-management: Commercial customer-hosted third-party risk and governance application on the Archer platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm (checked 2026-11-19). 


### Cloud deployment evidence

- AWS & Azure Cloud Hosting (aws, azure): https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm
  Supported Archer application and database VMs on customer AWS or Azure infrastructure. Use the current On-Premises release and sizing matrix with the selected Third-Party Governance entitlement. The dated cloud guide's example instance types do not establish a current HA workload or price estimate. Archer SaaS is separate.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS & Azure Cloud Hosting: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm

- Third-Party Governance: https://www.archerirm.com/third-party-governance

- Archer On-Premise Agreement PDF: https://www.archerirm.com/wp-content/uploads/2026/07/4d99d5_37b1c77af24d434d8e85335dcdeca740.pdf

- Legal Center: https://www.archerirm.com/company/legal-center

- On-Prem Release Notes (2025.12.05): https://help.archerirm.cloud/archerreleasenotes/content/rnhome/archer_releases_onprem.htm

- On-Prem Maintenance PDF: https://www.archerirm.com/wp-content/uploads/2026/07/4d99d5_45d0859400a24fbf8969ac1e40fc3d4d.pdf

### Licensing sources

- https://www.archerirm.com/wp-content/uploads/2026/07/4d99d5_37b1c77af24d434d8e85335dcdeca740.pdf

- https://www.archerirm.com/company/legal-center

### Infrastructure sources

- https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Archer documents instance-level SSO configuration including Windows-integrated and SAML modes, identity-provider connections and user/attribute provisioning. Configure the selected supported release and directory/trust settings. Third-Party Governance uses the Archer platform; this is not evidence for the separate SaaS identity surface. Scope: Archer platform 2024.09 user SSO configuration underlying TPRM; release compatibility required. Source: https://help.archerirm.cloud/platform_2024_09/en-us/content/archercontrolpanel/acp_inst_sso_configuring.htm (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Public cloud-hosting guidance describes supported deployment context, but the requested installation page requires login and the reviewed material does not expose a current customer-delivery artifact. Obtain the entitled installer and supported database/platform version; do not infer a complete installation template from hosting guidance. Scope: Archer self-managed installation artifact remains unconfirmed. Source: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The 2024.11 small-environment guide specifies a database server with four dedicated cores/16 GB RAM and separate combined web/services server with four cores/16 GB; disk and HA/load-balancer/SQL cluster requirements are additional. This historical platform sizing example requires revalidation for the selected current release and TPRM workload. Scope: Archer 2024.11 small-environment component minimums; current-release and solution sizing separate. Source: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_small_environment.htm (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Archer Third-Party Governance; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.archerirm.com/wp-content/uploads/2026/07/4d99d5_37b1c77af24d434d8e85335dcdeca740.pdf (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Arize Phoenix Self-Hosted

AI observability and evaluation server for traces, datasets and application experiments.

- Listing: https://launchinyourcloud.com/directory/phoenix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.
- Licensing model: source-available
- Installation: Use the official self-hosted Docker/Compose or Kubernetes deployment instructions and configure persistent storage and instrumentation endpoints.
- Architecture: Customer-operated trace/evaluation application with persistent trace and dataset storage
- Operations: Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.
- Product website: https://arize.com/phoenix/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted product is distinct from commercial Arize offerings. Traces may contain prompts and outputs; evaluation jobs can call separately configured external model services even when trace storage is local.

Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated trace/evaluation application with persistent trace and dataset storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-observability: AI trace collection, evaluation, datasets, experiments and prompt analysis for instrumented model applications.

- ai-tools: AI development and operations tooling for tracing and evaluation rather than a model-serving runtime.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 


### Cloud deployment evidence

- Phoenix self-hosting deployment options (aws, azure, gcp, railway): https://arize.com/docs/phoenix/self-hosting
  The current Phoenix self-hosting index includes a Railway one-click template as well as AWS CloudFormation, Azure ARM and Google Cloud Run. These deploy the Phoenix application, not the separately licensed Arize AX product. A Railway project is customer-controlled while Railway manages its infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Phoenix self-hosted Render Blueprint (render): https://arize.com/docs/phoenix/self-hosting
  The vendor self-hosting index offers a Render one-click Blueprint for Phoenix alongside its Railway, AWS, Azure and Google Cloud options. This is the self-hosted Phoenix application, separate from Arize AX; customer workspace control does not imply ownership of the platform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Arize's June 2026 maintainer account describes actual participation outside the core team: it attributes OIDC authentication to users needing Keycloak/Cognito and credits contributors with expanding framework integrations and OpenInference. The upstream release history shows continuing maintenance. This concerns concrete community involvement rather than repository star counts; it does not certify any named customer's deployment model.

Reviewed 2026-11-10.

- Maintainer account of user-contributed authentication and integrations: https://arize.com/blog/phoenix-10k/

- Current Phoenix maintenance releases: https://github.com/Arize-ai/phoenix/releases

### Sources

- Official installation and runtime: https://arize.com/docs/phoenix/self-hosting

- Upstream project and capabilities: https://github.com/Arize-ai/phoenix

- Current upstream license: https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE

### Licensing sources

- https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE

### Infrastructure sources

- https://arize.com/docs/phoenix/self-hosting


### 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. Phoenix documents OAuth2 authorization-code login with OIDC provider discovery, configured alongside application authentication and secret settings. Configure the trusted provider, callback and account policy; client API keys remain a separate surface. Scope: Self-hosted Phoenix UI OAuth2/OIDC. Source: https://arize.com/docs/phoenix/deployment/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 upstream Phoenix repository provides self-hosting/container documentation for the observability server. Match persistence and authentication settings to the chosen release; instrumented applications and model services remain separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/arize-ai/phoenix (reviewed 2026-11-14). Deployment artifact: https://github.com/arize-ai/phoenix. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosting guide documents deployment, storage/database configuration and trace retention, but does not establish a complete CPU/RAM minimum for a specified workload. Size span ingestion, retention, database, evaluation/model dependencies and redundant service instances. Hosted Arize AX sizing is a separate offering. Scope: Phoenix self-hosted application and data services; numeric workload sizing unresolved. Source: https://arize.com/docs/phoenix/self-hosting/deploying-phoenix.md (reviewed 2026-11-20).

- License pricing: Documented. Phoenix uses Elastic License 2.0, including limits on offering substantial hosted/managed functionality and bypassing licence controls. This is not an unrestricted Apache/MIT licence or a hosted-service price; review commercial service/support terms separately. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was arize-phoenix-v21.1.0, 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 Arize-ai/phoenix release record; commercial editions and deployment packages may differ. Source: https://github.com/Arize-ai/phoenix/releases/tag/arize-phoenix-v21.1.0 (reviewed 2026-11-14).







## Atomic CRM

Customer-operated CRM for contacts, companies, deals and communication history.

- Listing: https://launchinyourcloud.com/directory/atomic-crm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Atomic CRM frontend and a complete self-hosted Supabase backend on an Azure VM.
- 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.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The cloudimg package includes local backend services; using hosted Supabase would create a different data boundary. Do not transfer hosted-service attestations.

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

Atomic CRM frontend and a complete self-hosted Supabase backend on an Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated CRM for contacts, companies, deals and communication history.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm
  Atomic CRM frontend and a complete self-hosted Supabase backend on an Azure VM. The cloudimg package includes local backend services; using hosted Supabase would create a different data boundary. Do not transfer hosted-service attestations.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes fzaninotto, slax57, nawan-b, 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/marmelab/atomic-crm/graphs/contributors

- Upstream project: https://github.com/marmelab/atomic-crm

### Sources

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm

- GitHub LICENSE.md (MIT): https://raw.githubusercontent.com/marmelab/atomic-crm/main/LICENSE.md

- GitHub Commits: https://github.com/marmelab/atomic-crm/commits/main

### Licensing sources

- https://raw.githubusercontent.com/marmelab/atomic-crm/main/LICENSE.md

### Infrastructure sources

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm


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

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

- Single sign-on: Documented. Atomic CRM documents SAML 2.0 sign-in through Supabase Auth. Supabase also publishes a self-hosted SAML setup requiring signing keys, Auth settings and registered IdP metadata. Configure the CRM login path and matching backend version; the hosted Supabase console instructions alone do not configure a local backend. Scope: Atomic CRM with a configured self-hosted Supabase Auth backend; provider-image defaults are not assumed. Source: https://marmelab.com/atomic-crm/doc/developers/sso/ (reviewed 2026-11-20). Supporting source: Self-hosted Supabase SAML configuration — https://supabase.com/docs/guides/self-hosting/self-hosted-saml-sso.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The production guide deploys Supabase schema/functions separately from the built static frontend. For customer-owned infrastructure, deploy the complete self-hosted Supabase backend and apply CRM migrations/functions; hosting only the frontend while using hosted Supabase changes the data boundary. Scope: Atomic CRM upstream deployment; Azure publisher packaging has a separate version and operations model. Source: https://marmelab.com/atomic-crm/doc/developers/deploy/ (reviewed 2026-11-20). Deployment artifact: https://github.com/marmelab/atomic-crm. Artifact reference: main (moving branch); match the selected CRM release to its migrations and backend configuration. Supporting source: Complete self-hosted backend deployment — https://supabase.com/docs/guides/self-hosting/docker.

- Minimum footprint / sizing: Documented. The underlying self-hosted Supabase Docker guide lists a minimum of 4 GB RAM, two CPU cores and 40 GB SSD, recommending 8 GB, four cores and 80 GB or more. This is a backend baseline only; CRM functions, attachments, frontend hosting, backups and HA need additional workload sizing. Scope: Supabase platform floor supporting Atomic CRM; not a validated CRM or Azure image minimum for 100 users and 1 TB. Source: https://supabase.com/docs/guides/self-hosting/docker (reviewed 2026-11-20). Supporting source: CRM backend/frontend deployment boundary — https://marmelab.com/atomic-crm/doc/developers/deploy/.

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

- Operating cost estimate: Not researched.

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







## AureusERP

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

- Listing: https://launchinyourcloud.com/directory/aureuserp/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Docker / Compose
- Architecture: Laravel application, PostgreSQL, file storage and workers.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://aureuserp.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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


### Cloud deployment evidence

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

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


### Community and maintenance

The reviewed upstream contributor history includes jitendra-webkul, suraj-webkul, sandeep-webkul, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The reviewed AureusERP README documents local administration and role/permission setup, but does not establish an external SAML/OIDC user-login provider for the self-hosted core. Laravel, Filament and role-management dependencies alone do not establish SSO support. Scope: AureusERP self-hosted core; optional plugins require their own supported-version and entitlement evidence. Source: https://github.com/aureuserp/aureuserp/blob/master/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream README provides a Composer/source installation and php artisan erp:install to create the environment, schema, roles and admin account. Its quick start and Sail Compose file are development-oriented; they do not establish a hardened production or HA deployment. Scope: Reviewed AureusERP application bootstrap; provision production web/database services separately. Source: https://github.com/aureuserp/aureuserp/blob/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/aureuserp/aureuserp. Artifact reference: master (moving branch). Supporting source: Sail development Compose configuration — https://github.com/aureuserp/aureuserp/blob/master/docker-compose.yml.

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

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

- Operating cost estimate: Not researched.

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







## Azure DevOps Server

Source control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.

- Listing: https://launchinyourcloud.com/directory/azure-devops-server/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary; Express is free for up to five active users, while paid Server use requires server and user entitlements plus Windows licensing.
- Licensing model: commercial-only
- Installation: Windows installer on an Azure VM with SQL Server, Azure SQL Database or Azure SQL Managed Instance
- Architecture: Customer-operated Windows application tier and SQL data tier.
- Operations: Customer operates the Azure VMs, Windows, SQL data tier, backups, patches, upgrades and Azure DevOps Server configuration.
- Product website: https://azure.microsoft.com/en-us/products/devops/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Azure DevOps Server, not Microsoft-hosted Azure DevOps Services. Microsoft's Azure configuration installs the server on an Azure VM and can use Azure SQL Database or Azure SQL Managed Instance. Advanced configuration is unavailable on Azure VMs; use Basic or Azure configuration. SQL Server on Linux is unsupported. Only Azure receives a badge because current first-party documentation does not establish equivalent AWS or Google Cloud server deployments. Azure DevOps Server 2022.2 Patch 9, published October 13, 2026, includes security fixes and is recommended by Microsoft. Confirm the exact server generation and prerequisite patch sequence before applying it.

Azure DevOps Server is proprietary Microsoft software. Express is a no-cost license limited to five active users, not an open-source edition; broader use requires paid server/CAL or eligible Visual Studio and Azure DevOps entitlements.

Azure DevOps Server runs on customer-operated Windows application-tier VMs and requires a supported SQL Server or Azure SQL data tier.


### Category fit

- devops: Self-hosted repositories, pipelines, test plans and artifact management.

- project-management: Azure Boards provides work-item tracking, backlogs and planning within the same server.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server (checked 2026-11-17). 


### Cloud deployment evidence

- Azure DevOps Server on an Azure VM with Azure SQL (azure): https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server
  Microsoft requires Azure DevOps Server on an Azure VM for the documented Azure SQL topology and supplies Azure VM identity, networking, firewall and database steps. Application and data tiers remain in the customer's Azure environment.
  Source type: provider-guide; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Install and configure Azure DevOps Server: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- Use Azure SQL with Azure DevOps Server: https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server

- Azure DevOps Server requirements: https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server

- Azure DevOps Server pricing and licensing: https://azure.microsoft.com/en-us/pricing/details/devops/server/

- Azure DevOps Server release notes: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server

### Licensing sources

- https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- https://azure.microsoft.com/en-us/pricing/details/devops/server/

### Infrastructure sources

- https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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. Server installation media and server/CAL licensing are documented. A current first-party Marketplace offer delivering this self-hosted Server edition was not established. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Azure DevOps Services billing and Azure VM charges do not establish Marketplace commitment treatment for Server licences/CALs. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Single sign-on: Documented. Microsoft distinguishes Server Windows authentication from Services Microsoft Entra authentication. Use Windows integrated authentication for the self-hosted server; Services service-principal and managed-identity patterns do not establish Server support. Scope: Azure DevOps Server identity boundary. Source: https://learn.microsoft.com/en-us/azure/devops/organizations/security/authentication-guidance?view=azure-devops (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The Server authentication guidance establishes Windows authentication and supported PAT/client-library paths, not a SCIM lifecycle endpoint. Microsoft Entra provisioning for Azure DevOps Services cannot be transferred to Server. Scope: Azure DevOps Server; SCIM unconfirmed. Source: https://learn.microsoft.com/en-us/azure/devops/organizations/security/authentication-guidance?view=azure-devops (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Azure DevOps Server 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://learn.microsoft.com/en-us/azure/devops/server/architecture/key-concepts?view=azure-devops (reviewed 2026-11-17).

- Security controls: Documented. Use the documented Windows/domain identity and permission boundaries and restrict service accounts and database access. Server security requirements are distinct from the Microsoft-hosted Services security posture. Current advisory review: Microsoft's Patch 9 for Azure DevOps Server 2022.2 includes security fixes and is recommended for affected installations. Apply Patch 9 or a later applicable supported update after checking prerequisites. Scope: Self-managed Server identity and authorization Azure DevOps Server 2022.2; other server generations require their own patch guidance.. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://learn.microsoft.com/en-us/azure/devops/server/architecture/key-concepts?view=azure-devops.

- Air-gapped operation: Sources checked — unresolved. The self-hosted installer and Windows/SQL dependencies are documented, but a complete disconnected activation, extension/feed and security-update workflow was not established. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Microsoft documents installing Server on a supported Windows host and configuring the application/database tiers. The Azure SQL topology requires Azure VMs; this is an installer/configuration workflow, not a pinned IaC artifact. Scope: Self-managed Windows Server installation. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Microsoft recommends an eight-core machine, 16 GB RAM and SSD for a single-server deployment. HA application tiers and SQL availability add servers; repository size, builds and usage can require more. Scope: Server hardware recommendation; not an HA minimum. Source: https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server (reviewed 2026-11-17).

- License pricing: Documented. Azure DevOps Server is proprietary Microsoft software. Express is a no-cost license limited to five active users, not an open-source edition; broader use requires paid server/CAL or eligible Visual Studio and Azure DevOps entitlements. Scope: Azure DevOps Server: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Only Azure deployment is confirmed here. An AWS estimate would assume an unevidenced cloud path; obtain an Azure topology and Server/CAL/Windows/SQL licensing quote. 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://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Azure DevOps Server 2022.2 Patch 9 was published October 13, 2026 and includes security fixes. Match the patch to the exact installed server generation and prerequisites. Scope: Azure DevOps Server 2022.2. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Azure DevOps Server 2022.2 Patch 9 security update (security-advisory): Microsoft's Patch 9 for Azure DevOps Server 2022.2 includes security fixes and is recommended for affected installations. Scope: Azure DevOps Server 2022.2; other server generations require their own patch guidance. Conditions: Installed server generation and prerequisite patch level determine applicability. Action: Apply Patch 9 or a later applicable supported update after checking prerequisites. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server; reviewed 2026-11-18.




## Azure Trusted Research Environment

Open-source reference platform for isolated research workspaces and controlled data movement.

- Listing: https://launchinyourcloud.com/directory/azure-tre/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform
- Architecture: Customer Azure core services, workspaces, researcher compute, storage and Airlock workflows provisioned through Terraform.
- 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://microsoft.github.io/AzureTRE
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Airlock implements data import/export review gates; it does not supply an institution's IRB or grant-review decision process. This is an engineering reference implementation with workspace templates, not an automatically certified or supported research service.

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

Customer Azure core services, workspaces, researcher compute, storage and Airlock workflows provisioned through Terraform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- internal-tools: Open-source reference platform for isolated research workspaces and controlled data movement.

- data-analytics: Open-source reference platform for isolated research workspaces and controlled data movement.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://microsoft.github.io/AzureTRE/latest/tre-admins/setup-instructions/ (checked 2026-11-19). 


### Cloud deployment evidence

- Setup Instructions (azure): https://microsoft.github.io/AzureTRE/latest/tre-admins/setup-instructions/
  Customer Azure core services, workspaces, researcher compute, storage and Airlock workflows provisioned through Terraform. Airlock implements data import/export review gates; it does not supply an institution's IRB or grant-review decision process. This is an engineering reference implementation with workspace templates, not an automatically certified or supported research service.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes tamirkamara, marrobi, stuartleeks, 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/microsoft/AzureTRE/graphs/contributors

- Upstream project: https://github.com/microsoft/AzureTRE

### Sources

- Setup Instructions: https://microsoft.github.io/AzureTRE/latest/tre-admins/setup-instructions/

- Airlock Governance: https://microsoft.github.io/AzureTRE/latest/azure-tre-overview/airlock/

- MIT: https://github.com/microsoft/AzureTRE/blob/main/LICENSE

- Release v0.29.1: https://github.com/microsoft/AzureTRE/releases/tag/v0.29.1

### Licensing sources

- https://github.com/microsoft/AzureTRE/blob/main/LICENSE

### Infrastructure sources

- https://microsoft.github.io/AzureTRE/latest/tre-admins/setup-instructions/


### 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. Azure TRE uses Microsoft Entra ID for TRE/workspace users and administrators, with separate application registrations and app-role permissions. The setup guide distinguishes tenant administration from Azure subscription administration and notes that group assignment may need premium Entra licensing. Scope: TRE UI/API and workspace identities; not evidence that every application launched inside a workspace inherits the same SSO. Source: https://microsoft.github.io/AzureTRE/latest/tre-admins/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 repository supplies Terraform for core Azure resources and workspace/service templates, orchestrated by the documented deployment workflow. Register resource providers, configure identities and secrets, select a release and deploy the core before optional workspaces/services; replace the initial self-signed certificate. Scope: Azure TRE core and separately deployed workspace templates. Source: https://microsoft.github.io/AzureTRE/latest/tre-admins/setup-instructions/manual-deployment/ (reviewed 2026-11-20). Deployment artifact: https://github.com/microsoft/AzureTRE/tree/v0.29.1/core/terraform. Artifact reference: v0.29.1. Supporting source: Deployment repository setup — https://microsoft.github.io/AzureTRE/latest/tre-admins/setup-instructions/deployment-repo/.

- Minimum footprint / sizing: Documented. The v0.29.1 core Terraform defaults include a P1v3 App Service plan and Standard_B2s resource-processor VM scale-set SKU. The core also provisions network/security and managed-service components; research workspaces and their VMs/services are additional. These defaults do not size a whole research workload or establish its cost. Scope: Versioned Azure core defaults, not an AWS design, total resource count or HA/1-TB capacity minimum. Source: https://github.com/microsoft/AzureTRE/blob/v0.29.1/core/terraform/variables.tf (reviewed 2026-11-20). Supporting source: Core resource composition — https://github.com/microsoft/AzureTRE/blob/v0.29.1/core/terraform/main.tf.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Belenios

Self-hosted verifiable online voting with separated election administration, credential and trustee roles.

- Listing: https://launchinyourcloud.com/directory/belenios/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: cloudimg Azure VM with Belenios 3.3.0, nginx/TLS and persistent election spool.
- 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.belenios.net
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure offer and its complete first-boot guide identify the customer VM and packaged upstream release. Cryptographic verifiability does not certify an election process or replace independent trustees, secure credentials, backups and a threat-model review.

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

cloudimg Azure VM with Belenios 3.3.0, nginx/TLS and persistent election spool. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- board-committee-governance: Self-hosted verifiable online voting with separated election administration, credential and trustee roles.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/belenios-on-ubuntu-24-04-azure/ (checked 2026-11-19). 


### Cloud deployment evidence

- cloudimg Azure Guide (azure): https://www.cloudimg.co.uk/guides/belenios-on-ubuntu-24-04-azure/
  cloudimg Azure VM with Belenios 3.3.0, nginx/TLS and persistent election spool. The Azure offer and its complete first-boot guide identify the customer VM and packaged upstream release. Cryptographic verifiability does not certify an election process or replace independent trustees, secure credentials, backups and a threat-model review.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes glondu, swergas, mateusz-holysz, 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/glondu/belenios/graphs/contributors

- Upstream project: https://github.com/glondu/belenios

### Sources

- cloudimg Azure Guide: https://www.cloudimg.co.uk/guides/belenios-on-ubuntu-24-04-azure/

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

- AGPL-3.0 COPYING: https://raw.githubusercontent.com/glondu/belenios/master/COPYING

- GitHub Tags: https://github.com/glondu/belenios/tags

### Licensing sources

- https://raw.githubusercontent.com/glondu/belenios/master/COPYING

### Infrastructure sources

- https://www.cloudimg.co.uk/guides/belenios-on-ubuntu-24-04-azure/


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

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

- Single sign-on: Documented. The upstream FAQ confirms OpenID Connect authentication and Google as a supported provider, and discusses CAS in the voter-authentication context. Configure the selected instance and election authentication deliberately; this does not prove every Azure image ships configured enterprise federation or that voter and administrator login are identical. Scope: Upstream Belenios instance/election identity options; packaged-image and role scope. Source: https://www.belenios.org/faq.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Upstream documents building/installing with OPAM bootstrap and configuring a server with dependencies and persistent election data. This is distinct from the third-party Azure VM image. Match versions, deploy behind HTTPS and plan secure updates and retained spool data. Scope: Moving upstream manual/source installation; marketplace packaging separate. Source: https://github.com/glondu/belenios/blob/master/INSTALL.md (reviewed 2026-11-21). Deployment artifact: https://github.com/glondu/belenios/blob/master/INSTALL.md. Artifact reference: Current upstream installation guide reviewed on this date.

- Minimum footprint / sizing: Documented. The upstream FAQ describes its own Debian VM with two CPUs, 4 GB RAM and 16 GB disk, and recommends an HTTPS reverse proxy for production. This is an operator reference, not a minimum or guarantee for a 100-user/1-TB HA election service; storage, cryptographic/tallying peaks and replicas need validation. Scope: Upstream Belenios reference server, not a third-party-image or HA sizing guarantee. Source: https://www.belenios.org/faq.html (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## BillionMail

Customer-operated mail server and marketing application.

- Listing: https://launchinyourcloud.com/directory/billionmail/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: BillionMail container services and persistent mail data in a cloudimg Azure VM.
- 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.microsoft.com/en-gb/product/cloudimg1647283583153.billionmail-ubuntu-24-04
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Operating a mail server also requires DNS, reverse DNS, deliverability and provider port approval; a VM image does not guarantee inbox placement.

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

BillionMail container services and persistent mail data in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Customer-operated mail server and marketing application.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.billionmail-ubuntu-24-04
  BillionMail container services and persistent mail data in a cloudimg Azure VM. Operating a mail server also requires DNS, reverse DNS, deliverability and provider port approval; a VM image does not guarantee inbox placement.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes lotkmm, aaPanel, dreambladeflag, 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/Billionmail/BillionMail/graphs/contributors

- Upstream project: https://github.com/Billionmail/BillionMail

### Sources

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

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

- GitHub Commits: https://github.com/aaPanel/BillionMail/commits/main

### Licensing sources

- https://raw.githubusercontent.com/aaPanel/BillionMail/main/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The reviewed v4.9 dashboard authentication code documents application login and tokens, without establishing an external SAML/OIDC identity-provider integration. Dovecot mail-authentication backends and SMTP/IMAP accounts are separate from administrator SSO. Confirm a supported dashboard integration and account/role mapping. Scope: Published management-dashboard authentication; mail protocol identities are separate. Source: https://github.com/Billionmail/BillionMail/blob/v4.9/core/api/rbac/v1/auth.go (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 project supplies an installation script and Docker Compose recipe; the v4.9 README explains script/Compose setup, domain verification and DNS. Review and pin the selected source/images, secrets and persistent data. Configure mail ports, delivery/relay policy, reverse DNS and TLS; this is a mail-server deployment as well as an application. Scope: Published upstream deployment recipe; distinct from the third-party Azure image. Source: https://github.com/Billionmail/BillionMail/blob/v4.9/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/Billionmail/BillionMail/blob/v4.9/docker-compose.yml. Artifact reference: v4.9. Supporting source: Official preparation and mail-port guidance — https://www.billionmail.com/start/preparation.html.

- Minimum footprint / sizing: Documented. The official quickstart lists a minimum of 1 CPU core, 1 GB RAM and 20 GB disk on a compatible Linux host. That startup baseline does not size 1 TB of retained data, concurrent campaigns or HA; include database, mail queues, mailbox/attachment growth, backups and replica capacity separately. Scope: Vendor-published installation minimum; not a throughput benchmark or HA sizing guarantee. Source: https://www.billionmail.com/start/preparation.html (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: BillionMail; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/aaPanel/BillionMail/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Bitbucket Data Center

Commercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.

- Listing: https://launchinyourcloud.com/directory/bitbucket-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Bitbucket Data Center term license; eligible existing customers must transition to the Bitbucket Hybrid License to continue self-managed use beyond March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation
- Architecture: Single-node or clustered Bitbucket application nodes with Git storage or Mesh, an external database, load balancer, shared home and search services
- Operations: Customer manages Kubernetes or hosts, Git and shared storage, Mesh where used, database, search, networking, TLS, identity, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/bitbucket/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-managed Bitbucket Data Center. Atlassian documents EKS, AKS and GKE with its supported Helm chart; the older AWS Quick Start and Azure Resource Manager templates are no longer maintained. Bitbucket and Bamboo are exempt from the retirement of the other affected Data Center products. Continued self-managed use after March 28, 2029 requires the Bitbucket Hybrid License; without transitioning, existing subscription instances become read-only. Atlassian plans availability in early 2027 for eligible existing Bitbucket or Bamboo Data Center/Server customers. The license also includes cloud services, but Atlassian states that the self-managed environment can remain in place without a data transfer. Atlassian rates CVE-2026-21589 critical (9.3). All Bitbucket Data Center versions before the fixed 9.4.26, 10.2.8, or 10.5.1 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Bitbucket URL-rewrite mitigation to every application and mirror node. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

Bitbucket is exempt from the end-of-life retirement of Jira and Confluence Data Center. Atlassian says eligible existing Bitbucket or Bamboo Data Center/Server customers can move to the Bitbucket Hybrid License, planned for early 2027, to retain self-managed Bitbucket beyond March 28, 2029. The existing standalone license route ends in 2029; without the Hybrid License transition, instances become read-only. Confirm eligibility, availability and renewal terms.

Bitbucket Data Center runs persistent application and Git-storage services with durable database, shared-home and repository storage.


### Category fit

- devops: Provides self-managed Git repository hosting, pull requests, code review, permissions and software-delivery integrations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html (checked 2026-11-16). 


### Cloud deployment evidence

- Bitbucket Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html
  Atlassian documents Bitbucket Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Product-specific AWS and Azure pages also direct customers to the Helm path because the older templates are no longer maintained.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Run Bitbucket Data Center on Kubernetes: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html

- Bitbucket Data Center supported platforms: https://confluence.atlassian.com/display/BitbucketServer/Supported%2Bplatforms

- Bitbucket Data Center deployment on AWS: https://confluence.atlassian.com/security/deploy-bitbucket-data-center-in-aws-1402669978.html

- Bitbucket Data Center deployment on Azure: https://confluence.atlassian.com/security/deploy-bitbucket-data-center-in-azure-1402669984.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian Data Center end-of-life exceptions: https://www.atlassian.com/licensing/data-center-end-of-life

- Bitbucket Hybrid License eligibility and transition: https://www.atlassian.com/migration/bitbucket-hybrid-license

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

- https://www.atlassian.com/migration/bitbucket-hybrid-license

### Infrastructure sources

- https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html

- https://confluence.atlassian.com/display/BitbucketServer/Supported%2Bplatforms


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 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. Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Bitbucket 7.12+; authentication does not assign application access or permissions. Scope: Bitbucket 7.12+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16). Supporting source: OIDC product/version scope — https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html.

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Bitbucket Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The Bitbucket 10.4 platform guide specifies x86-64, at least 2 CPU cores and 3 GB available RAM, including memory for Git operations. Repository activity, concurrency, database, shared storage and Mesh nodes require separate sizing. Scope: Bitbucket 10.4 application-host baseline; not a production cluster total. Source: https://confluence.atlassian.com/bitbucketserver104/supported-platforms-1822592149.html (reviewed 2026-11-16).

- License pricing: Documented. Bitbucket is exempt from the end-of-life retirement of Jira and Confluence Data Center. Atlassian says eligible existing Bitbucket or Bamboo Data Center/Server customers can move to the Bitbucket Hybrid License, planned for early 2027, to retain self-managed Bitbucket beyond March 28, 2029. The existing standalone license route ends in 2029; without the Hybrid License transition, instances become read-only. Confirm eligibility, availability and renewal terms. Scope: Bitbucket Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life. Supporting source: Edition and license conditions — https://www.atlassian.com/migration/bitbucket-hybrid-license.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 10.2.9, released 2026-11-03. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/stash.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/BitbucketServer/Bitbucket+Data+Center+10.2+release+notes.




### Security and lifecycle reviews

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

- Bitbucket Hybrid License transition (lifecycle): Bitbucket remains self-managed beyond 2029 through the Hybrid License. Atlassian plans availability in early 2027 for eligible existing Bitbucket/Bamboo customers. Scope: Bitbucket Data Center licensing; separate from the retirement of Jira and Confluence Data Center. Conditions: Eligibility and exact launch date must be confirmed; existing license availability changes on March 28, 2029. Action: Review the required license transition with Atlassian; do not infer unrestricted new-customer availability. Source: https://www.atlassian.com/migration/bitbucket-hybrid-license; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




## BoardPAC On-Premise

Customer-hosted board meeting and governance platform with role-based meeting access.

- Listing: https://launchinyourcloud.com/directory/boardpac-on-premises/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription software; obtain on-premises order terms
- Licensing model: commercial-only
- Installation: Vendor-assisted on-premises/self-hosted implementation
- Architecture: Persistent customer-hosted board platform with browser and mobile clients; detailed backend requirements must be scoped with BoardPAC.
- Operations: Customer and BoardPAC agree infrastructure ownership, backups, updates and support for the selected on-premises installation.
- Product website: https://boardpac.co/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The official features page explicitly offers on-premises or self-hosted deployment. Confirm the customer-operated topology and the feature set in the on-premises order, especially optional AI and video-conferencing integrations.

BoardPAC uses commercial end-user subscription terms with usage and redistribution restrictions. Confirm the specific on-premises order and support agreement rather than applying SaaS availability terms to customer operations.

Persistent customer-hosted board platform with browser and mobile clients; detailed backend requirements must be scoped with BoardPAC.


### Category fit

- board-committee-governance: Board-meeting collaboration and document access controls through a vendor-supported on-premises board platform.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://boardpac.co/news/boardpac-a-microsoft-azure-partner-joins-azure-marketplace/ (checked 2026-11-12). 


### Cloud deployment evidence

- BoardPAC deployment within an existing Azure environment (azure): https://boardpac.co/news/boardpac-a-microsoft-azure-partner-joins-azure-marketplace/
  The vendor explicitly states that organizations can deploy BoardPAC within their existing Azure environment. This is a vendor deployment statement rather than a public installation guide; agree the customer subscription, backend requirements, operational ownership and commercial terms before deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Board features and self-hosted option: https://boardpac.co/features/

- Commercial subscription and usage terms: https://boardpac.co/terms-of-use/

### Licensing sources

- https://boardpac.co/terms-of-use/

### Infrastructure sources

- https://boardpac.co/features/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The feature page advertises SSO and on-premises deployment, but does not identify the protocol or licensed on-premises configuration. Confirm both before treating a particular identity provider as supported. Scope: On-premises SSO protocol/entitlement unresolved. Source: https://boardpac.co/features/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. BoardPAC advertises on-premises/self-hosted deployment, but the reviewed public features and terms do not supply a backend installer or automation artifact. Mobile-app connection instructions do not establish server installation; obtain the contracted backend package and vendor implementation procedure. Scope: BoardPAC customer-managed backend artifact remains unconfirmed. Source: https://boardpac.co/features/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Sources checked — unresolved. The public self-hosting statement does not specify backend CPU/RAM/storage or HA requirements. Agree the server/database topology, concurrent board users, document processing, offline-device synchronisation and backup/recovery capacity with the vendor. Scope: BoardPAC on-premises backend sizing remains unconfirmed. Source: https://boardpac.co/features/ (reviewed 2026-11-21).

- License pricing: Documented. BoardPAC terms grant time-limited internal use of a subscription subject to the order and restrict redistribution and sublicensing. Confirm the on-premises order, user/device limits, backend entitlement, updates and support separately; general service terms do not establish the final self-hosted price. Scope: BoardPAC public subscription framework; specific on-premises order terms require review. Source: https://boardpac.co/terms-of-use/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Camunda 8 Self-Managed

Commercial self-managed process orchestration and workflow automation platform.

- Listing: https://launchinyourcloud.com/directory/camunda-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Enterprise license required for production; unlicensed use is limited to non-production conditions.
- Licensing model: commercial-only
- Installation: Official Helm charts on EKS, AKS or GKE
- Architecture: Customer-operated orchestration cluster, connectors, identity services and persistent secondary storage
- Operations: Customer manages Kubernetes, supported databases or search services, storage, ingress, identity, backups, scaling and upgrades.
- Product website: https://camunda.com/platform/
- Source review: 2026-11-19; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers Camunda 8 Self-Managed, not Camunda SaaS. Match Helm and component versions, size persistent storage for the workload and review external database/search dependencies. A valid Enterprise license is required for production use. Camunda Notice 80 covers critical eMudhra trust-store issues, including CVE-2026-114820, across multiple 8.6–8.10 components; fixed versions differ by component, and Keycloak requires a sufficiently recent rebuilt image. Notices 81 and 82 also patch Web Modeler HTTP parser and custom HTTP/2 denial-of-service paths. Follow the component matrix instead of treating one Helm version as a universal fix. Camunda Optimize 8.6.30 and 8.7.32 mitigate CVE-2026-114938 by disabling the affected AVX-512 Base64 intrinsic. Apply the branch-specific Optimize update, or move to a fixed JDK when supplied, and do not treat a single Helm version as a universal Camunda fix.

Camunda documents unlicensed Self-Managed components as non-production and requires a Camunda Self-Managed Enterprise Edition license for production use.

The documented production topology uses persistent Kubernetes workloads plus databases or search services. Managed provider dependencies do not make the Camunda runtime serverless.


### Category fit

- workflow-automation: Executes modeled business processes, user tasks, connectors and decision-driven automation in customer-operated infrastructure.

- workflow-orchestration: Coordinates durable process instances, service tasks and distributed workers using the Camunda orchestration cluster.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/ (checked 2026-11-14). 


### Cloud deployment evidence

- Camunda 8 Self-Managed on Amazon EKS (aws): https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/
  Camunda provides current EKS infrastructure and Helm installation guidance for a customer AWS account, including managed persistence dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Camunda 8 Self-Managed on Microsoft AKS (azure): https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/
  Camunda provides current AKS and Helm guidance for a customer Azure subscription, with provider-specific reference infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Camunda 8 Self-Managed on Google GKE (gcp): https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/
  Camunda documents its Self-Managed Helm deployment and Google Cloud-specific GKE configuration.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- Supported self-managed environments: https://docs.camunda.io/docs/reference/supported-environments/

- Amazon EKS deployment: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/

- Microsoft AKS deployment: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/

- Google GKE deployment: https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/

- Self-managed licensing: https://docs.camunda.io/docs/self-managed/components/orchestration-cluster/core-settings/configuration/licensing/

- Camunda security notices: https://docs.camunda.io/docs/reference/notices/

- Camunda Optimize 8.6.30: https://github.com/camunda/camunda/releases/tag/8.6.30-optimize

- Camunda Optimize 8.7.32: https://github.com/camunda/camunda/releases/tag/8.7.32-optimize

- OpenJDK November 2026 advisory: https://openjdk.org/groups/vulnerability/advisories/2026-11-17

### Licensing sources

- https://docs.camunda.io/docs/self-managed/components/orchestration-cluster/core-settings/configuration/licensing/

### Infrastructure sources

- https://docs.camunda.io/docs/self-managed/reference-architecture/kubernetes/

- https://docs.camunda.io/docs/reference/supported-environments/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The current Orchestration Cluster guide documents OIDC for Web UI users and OAuth2 API access through an external IdP, with identity mapping and role/authorization configuration. Basic authentication is a different default. Management Identity/Hub and older component releases have separate configurations; configure the selected self-managed version and licensed components. Scope: Current Camunda 8 Orchestration Cluster authentication; not automatic uniform SSO for every component/version. Source: https://docs.camunda.io/docs/self-managed/concepts/authentication/authentication-to-orchestration-cluster/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Camunda Notices 80–82 cover critical eMudhra trust-store exposure plus Web Modeler HTTP parser and custom HTTP/2 denial-of-service issues. Use the notice's component-specific fixed versions, ensure Keycloak uses a rebuilt image, or remove the named trust roots where Camunda documents that workaround. Apply the Web Modeler fixes separately. Current review: Optimize 8.6.30 and 8.7.32 mitigate CVE-2026-114938, an AVX-512 Base64 intrinsic memory-corruption issue, by forcing -XX:-UseBASE64Intrinsics. Camunda says Optimize decodes untrusted Base64 while then-current base and customer JDKs lacked the upstream fix. Use the branch-specific Optimize release or a fixed JDK 21.0.13.1 or 25.0.5.1 and restart affected processes. Scope: Camunda Optimize 8.6 and 8.7 on affected x86-64 AVX-512 JDKs; other Camunda components require separate assessment. Source: https://github.com/camunda/camunda/releases/tag/8.7.32-optimize (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://docs.camunda.io/docs/reference/notices/. Supporting source: Optimize 8.6.30 mitigation — https://github.com/camunda/camunda/releases/tag/8.6.30-optimize. Supporting source: OpenJDK fixed versions — https://openjdk.org/groups/vulnerability/advisories/2026-11-17.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Camunda publishes Self-Managed Helm charts. Select a chart/application version combination supported by the deployment guide and account for external services, storage and licensed components. Scope: Camunda 8 Self-Managed chart family; not a SaaS subscription. Source: https://github.com/camunda/camunda-platform-helm (reviewed 2026-11-14). Deployment artifact: https://github.com/camunda/camunda-platform-helm. Artifact reference: repository default branch (moving; select a supported chart release).

- Minimum footprint / sizing: Documented. The manual-deployment reference suggests at least 2 CPU cores, 4 GB RAM and 32 GB SSD per host, then requires workload benchmarking. The 8.10 resource-planning guide separately sizes brokers, secondary storage, identity and optional Optimize; retention and replicas materially change storage. Per-host minima are not a complete 1 TB HA platform bill of materials. Scope: Current manual host floor plus versioned application/component planning; not a throughput guarantee. Source: https://docs.camunda.io/docs/self-managed/reference-architecture/manual/ (reviewed 2026-11-20). Supporting source: Self-Managed resource planning and component baselines — https://docs.camunda.io/docs/components/best-practices/architecture/sizing-self-managed/.

- License pricing: Documented. Camunda 8.6+ compiled platform components use proprietary Self-Managed Non-Production or Enterprise terms; production requires the Enterprise licence. Some SDKs/connectors and Desktop Modeler have different source licences. The free development option is not a production grant; obtain the component-specific self-managed quote and support terms separately from Cloud and infrastructure. Scope: Current Camunda 8 component licensing and self-managed production boundary. Source: https://docs.camunda.io/docs/reference/licenses/ (reviewed 2026-11-20). Supporting source: Self-Managed development versus licensed production pricing — https://camunda.com/pricing/.

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

- Camunda November 2026 component security notices (security-advisory): Camunda Notices 80–82 cover critical eMudhra trust-store exposure plus Web Modeler HTTP parser and custom HTTP/2 denial-of-service issues. Scope: Notice 80 affects listed Orchestration Cluster, Connectors, Management Identity, Hub, Web Modeler, Zeebe, Operate, Tasklist, Optimize, Console, and Keycloak builds. Notices 81 and 82 have separate Web Modeler ranges and fixes. Conditions: Component, branch, bundled Java trust store, Keycloak image build date, and HTTP/2 configuration determine applicability. Action: Use the notice's component-specific fixed versions, ensure Keycloak uses a rebuilt image, or remove the named trust roots where Camunda documents that workaround. Apply the Web Modeler fixes separately. Source: https://docs.camunda.io/docs/reference/notices/; reviewed 2026-11-18.

- Camunda Optimize CVE-2026-114938 mitigation (security-advisory): Optimize 8.6.30 and 8.7.32 disable the affected AVX-512 Base64 intrinsic for CVE-2026-114938. Scope: Camunda Optimize 8.6 and 8.7 on affected x86-64 AVX-512 JDKs; other components require separate assessment. Conditions: Camunda states Optimize decodes untrusted Base64 while then-current base and customer JDKs lacked the upstream fix. Action: Apply the branch-specific Optimize release or a fixed JDK, restart affected processes and verify the mitigation. Source: https://github.com/camunda/camunda/releases/tag/8.7.32-optimize; reviewed 2026-11-19. Supporting source: Optimize 8.6.30 — https://github.com/camunda/camunda/releases/tag/8.6.30-optimize. Supporting source: OpenJDK fixed versions — https://openjdk.org/groups/vulnerability/advisories/2026-11-17.




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





## ClickHouse BYOC

Managed analytical database with its data plane in your cloud account.

- Listing: https://launchinyourcloud.com/directory/clickhouse/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial
- Licensing model: commercial-only
- Installation: Vendor-assisted BYOC onboarding
- Architecture: Vendor control plane; customer data plane
- Operations: ClickHouse operates the BYOC service; the customer owns the cloud environment.
- Product website: https://clickhouse.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 vendor lists AWS, Google Cloud and Azure BYOC options. Confirm region availability and commercial requirements during onboarding. This entry does not describe ordinary ClickHouse Cloud hosting. CVE-2026-116366 is a critical unauthenticated network code-execution issue. ClickHouse states that Cloud and BYOC were patched; self-managed fixes are available in 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7.

This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.

The documented BYOC data plane uses a customer-cloud Kubernetes cluster and ClickHouse servers. Vendor management of the control plane is separate from this runtime classification.


### Category fit

- databases-vector: Managed analytical database with its data plane in your cloud account.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://clickhouse.com/cloud/bring-your-own-cloud (checked 2026-11-12). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://clickhouse.com/cloud/bring-your-own-cloud (checked 2026-11-12). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://clickhouse.com/cloud/bring-your-own-cloud (checked 2026-11-12). 

Operating responsibility: The vendor describes a fully managed ClickHouse service in the customer's AWS, Google Cloud or Azure account. Commercial availability and access are agreed during onboarding. Source: https://clickhouse.com/cloud/bring-your-own-cloud (checked 2026-11-20). Supporting source: Control-plane and data-plane architecture — https://clickhouse.com/docs/cloud/reference/byoc/overview.


### Cloud deployment evidence

- ClickHouse BYOC customer account support (aws, azure, gcp): https://clickhouse.com/cloud/bring-your-own-cloud
  The vendor explicitly offers its managed BYOC service in the customer AWS, Google Cloud or Azure account. This establishes provider compatibility for the commercial BYOC offering rather than a generic open-source Docker deployment; agree availability, access, region and operational boundaries with the vendor.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Bring Your Own Cloud: https://clickhouse.com/cloud/bring-your-own-cloud

- Google Cloud BYOC architecture: https://clickhouse.com/blog/byoc-gcp-ga

- ClickHouse security changelog: https://clickhouse.com/docs/resources/changelogs/security-changelog

### Licensing sources

- https://clickhouse.com/cloud/bring-your-own-cloud

### Infrastructure sources

- https://clickhouse.com/blog/byoc-gcp-ga


### Buyer diligence


Research coverage: 8/12 fields (67%); 5 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. Microsoft Marketplace lists ClickHouse Cloud BYOC as a fully managed service deployed into the customer's own Azure account. This is the Azure BYOC offer, separate from vendor-account ClickHouse Cloud. Scope: ClickHouse Cloud BYOC procurement for Azure; confirm private-offer, region and agreement terms.. Source: https://marketplace.microsoft.com/en-us/product/clickhouse.byoc_clickhouse_cloud?tab=Overview (reviewed 2026-11-21).

- Cloud commitment eligibility: Edition-dependent. ClickHouse states that its Microsoft Marketplace BYOC offer can count toward Microsoft Azure Consumption Commitments (MACC). Confirm the selected offer and purchase agreement are eligible before procurement; this does not establish AWS or Google Cloud software-commitment eligibility. Scope: Azure BYOC Marketplace purchase only; agreement and offer qualifications apply.. Source: https://clickhouse.com/blog/clickhouse-expands-collaboration-with-microsoft (reviewed 2026-11-21). Supporting source: Azure BYOC Marketplace offer — https://marketplace.microsoft.com/en-us/product/clickhouse.byoc_clickhouse_cloud?tab=Overview.

- Single sign-on: Documented. The vendor explicitly includes BYOC organizations in its SAML/SCIM availability statement. Configure the organization SAML connection and verified domains; this concerns vendor-hosted organization/control-plane identity, not autonomous authentication for every database client. Scope: Commercial ClickHouse BYOC organization SAML. Source: https://clickhouse.com/blog/introducing-scim-provisioning-in-clickhouse-cloud (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The BYOC page states SOC 2 and ISO 27001 alignment but does not provide the assessed service boundary, report or certificate scope for this customer-account deployment. Obtain the applicable evidence before treating it as an attestation. Scope: BYOC marketing statement checked; applicable attestation scope unresolved. Source: https://clickhouse.com/cloud/bring-your-own-cloud (reviewed 2026-11-14).

- Security controls: Documented. Current advisory review: CVE-2026-116366 is a critical unauthenticated network code-execution issue in affected ClickHouse releases. Upgrade self-managed deployments to the fixed release for the selected branch or later, and confirm managed-service patch status. Scope: Vendor fixes are 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7. ClickHouse states that its Cloud and BYOC services were patched.. Source: https://clickhouse.com/docs/resources/changelogs/security-changelog (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The public BYOC page establishes personalized vendor onboarding and a customer-cloud data plane, but does not expose a reviewed reusable provisioning artifact. Obtain the region-specific onboarding template, role policy and version from ClickHouse; an open-source ClickHouse Helm chart is a different deployment. Scope: Managed BYOC onboarding; public artifact unresolved. Source: https://clickhouse.com/cloud/bring-your-own-cloud (reviewed 2026-11-20).

- Minimum footprint / sizing: Sources checked — unresolved. The public BYOC offer targets large-scale deployments with vendor onboarding but does not publish a validated minimum CPU/RAM/storage topology. Obtain supported instance types, availability-zone design and workload sizing for the contracted provider and region. Do not substitute open-source single-node minima. Scope: Commercial managed BYOC footprint unresolved. Source: https://clickhouse.com/cloud/bring-your-own-cloud (reviewed 2026-11-20).

- License pricing: Documented. ClickHouse provides BYOC rates through its Trust Center after approving an access request. Azure customers can procure the managed BYOC service through Microsoft Marketplace. ClickHouse says purchases can count toward Microsoft Azure Consumption Commitments. Scope: Commercial BYOC pricing access and Azure procurement. Confirm offer terms, region availability, and the applicable commitment with ClickHouse.. Source: https://clickhouse.com/cloud/bring-your-own-cloud (reviewed 2026-11-21). Supporting source: ClickHouse Cloud BYOC offer in Microsoft Marketplace — https://marketplace.microsoft.com/en-us/product/clickhouse.byoc_clickhouse_cloud?tab=Overview. Supporting source: ClickHouse announcement of Microsoft Marketplace availability — https://clickhouse.com/blog/clickhouse-expands-collaboration-with-microsoft.

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

- ClickHouse unauthenticated network code execution (security-advisory): CVE-2026-116366 is a critical unauthenticated network code-execution issue in affected ClickHouse releases. Scope: Vendor fixes are 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7. ClickHouse states that its Cloud and BYOC services were patched. Conditions: Network reachability to an affected service is required; validate the exact installed release and exposure. Action: Upgrade self-managed deployments to the fixed release for the selected branch or later, and confirm managed-service patch status. Source: https://clickhouse.com/docs/resources/changelogs/security-changelog; reviewed 2026-11-18.




## CloudBees CI on Modern Cloud Platforms

Enterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.

- Listing: https://launchinyourcloud.com/directory/cloudbees-ci-modern-cloud-platforms/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial CloudBees CI license required.
- Licensing model: commercial-only
- Installation: CloudBees Helm chart on EKS, AKS or GKE
- Architecture: CloudBees operations center and managed controllers in the customer Kubernetes cluster.
- Operations: Customer provisions and operates Kubernetes, storage, networking, ingress, DNS, certificates and upgrades; CloudBees supports the licensed application within documented boundaries.
- Product website: https://www.cloudbees.com/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers CloudBees CI on modern cloud platforms, not plain Jenkins or a CloudBees-hosted service. CloudBees publishes separate EKS, AKS and GKE paths and a strict platform/version support matrix. Each standalone controller requires a valid license. CloudBees CI 2.580.2.38435 is the October 29 security release. Java 17 has been unsupported since 2.555.1.36485, so migrate controllers and agents to Java 21; Blue Ocean and Team controllers reached end of life in July 2026.

CloudBees CI is proprietary licensed software; operations center and standalone controllers require valid CloudBees licensing. Upstream Jenkins is a separate product.

The application runs as persistent Kubernetes workloads, including an operations center and managed controllers, in the customer's cluster.


### Category fit

- devops: Centrally managed enterprise continuous integration and delivery environment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro (checked 2026-11-17). 


### Cloud deployment evidence

- CloudBees CI installation on EKS, AKS and GKE (aws, azure, gcp): https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro
  CloudBees provides product installation guides for Amazon EKS, Azure AKS and Google GKE, and its supported-platform matrix lists all three. The customer operates the Kubernetes cluster.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- CloudBees CI installation index: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro

- Modern cloud platform onboarding: https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-onboarding

- Supported Kubernetes platforms and versions: https://docs.cloudbees.com/docs/cloudbees-common/latest/supported-platforms/cloudbees-ci-cloud

- CloudBees CI administration and licensing: https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/

- CloudBees CI release notes: https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/

### Licensing sources

- https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/

### Infrastructure sources

- https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro

- https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-onboarding


### 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: Documented. CloudBees identifies CI availability through AWS Marketplace, including a separate GovCloud marketplace route. Confirm the CI offer, subscription and delivery terms rather than substituting CodeShip or Unify listings. Scope: Vendor CI procurement statement; offer details must be selected. Source: https://www.cloudbees.com/partners/platform/aws (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The AWS partnership page establishes CI procurement availability, but not qualifying charges or committed-spend treatment under a buyer agreement. Scope: Reviewed public evidence for CloudBees CI on Modern Cloud Platforms; unresolved within this edition/deployment. Source: https://www.cloudbees.com/partners/platform/aws (reviewed 2026-11-17).

- Single sign-on: Documented. CloudBees CI documents SAML authentication with the supported SAML plugin and IdP metadata. Group attributes can inform RBAC, but the plugin does not synchronize external groups or roles. Scope: CloudBees CI SAML security realm. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The SAML guide explicitly separates authentication and group assertions from external group/role synchronization. A supported CI SCIM lifecycle endpoint was not established; CloudBees Unify or generic Jenkins plugins are insufficient evidence. Scope: CloudBees CI, not Unify or community plugins. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed CloudBees CI on Modern Cloud Platforms 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.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup (reviewed 2026-11-17).

- Security controls: Documented. Configure the SAML security realm and CloudBees RBAC separately; signing/encryption and IdP attributes must match the configured trust. Use supported plugins and current security fixes. Current advisory review: CloudBees CI 2.580.2.38435 contains security updates and is on the Java 21-supported line. Upgrade to 2.580.2.38435 or later, migrate to Java 21, and retire end-of-life controller types. Scope: CI authentication and authorization configuration CloudBees CI modern cloud platforms release 2.580.2.38435; component applicability follows the vendor release notes.. Source: https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/ (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup.

- Air-gapped operation: Sources checked — unresolved. CloudBees documents an update-center mirror for plugin management in air-gapped environments. That establishes a plugin-transfer mechanism, but not every licensing, image, agent and upgrade dependency for a fully isolated deployment. Scope: CI plugin mirror; complete offline deployment remains to be established. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/casc-plugin-management/alternate-plugin-download-site (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The modern-platform installation index provides Helm deployment paths for EKS, AKS and GKE. The AWS partnership page also links a CI EKS Blueprints add-on; configure storage, ingress and controllers for the selected supported platform. Scope: CloudBees CI modern cloud platforms. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The AWS reference architecture sizes operations center, managed controllers and build agents separately. Its examples are recommendations rather than universal requirements; build concurrency and agent workloads drive capacity. Scope: AWS Kubernetes reference architecture; not an HA capacity guarantee. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-reference-architecture/ra-for-aws/ (reviewed 2026-11-17).

- License pricing: Documented. CloudBees CI is proprietary licensed software; operations center and standalone controllers require valid CloudBees licensing. Upstream Jenkins is a separate product. Scope: CloudBees CI on Modern Cloud Platforms: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/ (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm controllers, operations center, build agents, concurrency and licence/support scope. Worker VM hours and artifact storage cannot be inferred from a 100-user headcount. 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.cloudbees.com/docs/cloudbees-ci/latest/cloud-reference-architecture/ra-for-aws/ (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. CloudBees CI 2.580.2.38435 was released October 29, 2026 with security updates. Java 21 is required for supported current releases; Blue Ocean and Team controllers are end of life. Scope: CloudBees CI modern cloud platforms. Source: https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/ (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- CloudBees CI October 2026 security update (security-advisory): CloudBees CI 2.580.2.38435 contains security updates and is on the Java 21-supported line. Scope: CloudBees CI modern cloud platforms release 2.580.2.38435; component applicability follows the vendor release notes. Conditions: Installed plugins, controller type, and Java runtime determine applicability and upgrade sequencing. Action: Upgrade to 2.580.2.38435 or later, migrate to Java 21, and retire end-of-life controller types. Source: https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/; reviewed 2026-11-18.




## CloudBolt Cloud Management Platform

Self-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.

- Listing: https://launchinyourcloud.com/directory/cloudbolt-cmp/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial license with a full-featured free tier limited to 100 managed resources for up to one year
- Licensing model: commercial-only
- Installation: Official AWS Marketplace AMI, or vendor installer on supported RHEL or Oracle Linux virtual machines
- Architecture: Customer-operated CMP appliance or HA VM nodes with PostgreSQL and shared storage
- Operations: Customer secures and maintains deployment infrastructure, database, storage, certificates, backups, upgrades, integrations and availability; CloudBolt maintains the appliance software.
- Product website: https://www.cloudbolt.io/cloud-management-platform/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The free tier is a capped and time-limited commercial entitlement, not an open-source edition. Clouds connected as managed resource handlers are distinct from the cloud account hosting the CMP application.

CMP requires a CloudBolt product license. A new appliance receives a full-featured but capped and time-limited free-tier license; paid keys raise its limits and term.

CMP is installed as one or more persistent VM or appliance nodes; HA adds an external database, shared storage and load balancer.


### Category fit

- internal-tools: Provides a self-service cloud-management portal for governed infrastructure provisioning and operations.

- workflow-automation: Blueprints and automation coordinate infrastructure requests, approvals, provisioning and lifecycle actions.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-in-aws/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/high-availability/azure/ (checked 2026-11-19). 


### Cloud deployment evidence

- CloudBolt CMP AWS Marketplace AMI (aws): https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-in-aws/
  The official guide launches the complete CMP AMI from the customer's AWS account and has the customer select region, VPC, subnet, security group, EC2 size, storage and KMS encryption.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- CloudBolt CMP Azure VM and HA deployment (azure): https://docs.cloudbolt.io/docs/cmp/get-started/install/high-availability/azure/
  The official guide installs CMP on customer Azure VMs and builds the full HA topology with Azure Load Balancer, Azure Database for PostgreSQL Flexible Server, Azure Files and customer virtual networks.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- CloudBolt CMP installation and shared responsibility: https://docs.cloudbolt.io/docs/cmp/get-started/install/

- Deploy CloudBolt CMP in AWS: https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-in-aws/

- Deploy CloudBolt CMP with the installer: https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-with-installer/

- CloudBolt CMP high availability in Azure: https://docs.cloudbolt.io/docs/cmp/get-started/install/high-availability/azure/

- CloudBolt CMP product license: https://docs.cloudbolt.io/docs/cmp/configure/administration/product-license/

- Exact reviewed AWS offer and package version: https://aws.amazon.com/marketplace/pp/prodview-tuvzf2rewwcy4

### Licensing sources

- https://docs.cloudbolt.io/docs/cmp/configure/administration/product-license/

### Infrastructure sources

- https://docs.cloudbolt.io/docs/cmp/get-started/install/

- https://docs.cloudbolt.io/docs/cmp/get-started/install/high-availability/azure/


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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. CloudBolt documents the complete CMP appliance as an AWS Marketplace AMI launched into the customer's AWS account. Azure uses the installer path rather than an established marketplace offer in this review. Scope: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-in-aws/ (reviewed 2026-11-19). Supporting source: Exact reviewed AWS offer and package version — https://aws.amazon.com/marketplace/pp/prodview-tuvzf2rewwcy4. Offer prodview-tuvzf2rewwcy4: CloudBolt; BYOL x86 AMI; external CloudBolt entitlement; package 2026.3.78 (AMI package); https://aws.amazon.com/marketplace/pp/prodview-tuvzf2rewwcy4.

- 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: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-in-aws/ (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/ (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: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/ (reviewed 2026-11-19).

- Security controls: Sources checked — unresolved. The deployment documentation establishes customer control of infrastructure but does not by itself establish a complete hardened baseline. Review identity, encryption, secrets, network exposure, audit logging, backups, patching and incident response for the selected topology. Scope: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-in-aws/ (reviewed 2026-11-19).

- Air-gapped operation: Documented. CloudBolt states that its OVA, installer and upgrader contain the required packages and run in air-gapped mode by default. A valid CMP license remains required; confirm offline license renewal, integrations and managed-cloud API dependencies for the intended workflow. Scope: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/ (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The CloudBolt-published AWS offer prodview-tuvzf2rewwcy4 delivers the x86 CMP AMI, currently packaged as 2026.3.78. The marketplace image requires a CloudBolt entitlement purchased outside AWS Marketplace, subject to the vendor’s free-tier terms where applicable. Azure installer and HA resources are a separate path. Scope: Specific CloudBolt CMP AWS BYOL AMI; not a public versioned Azure installer download. Source: https://aws.amazon.com/marketplace/pp/prodview-tuvzf2rewwcy4 (reviewed 2026-11-19). Deployment artifact: https://aws.amazon.com/marketplace/pp/prodview-tuvzf2rewwcy4. Artifact reference: prodview-tuvzf2rewwcy4; x86 AMI package 2026.3.78; external CloudBolt licence.

- Minimum footprint / sizing: Edition-dependent. The AWS appliance guide requires at least 4 vCPUs and 16 GB RAM, with 50 GB storage for a minimal install and 100 GB for production. HA database, shared storage, backups and managed workloads add capacity beyond this single-node baseline. Scope: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-in-aws/ (reviewed 2026-11-19).

- License pricing: Edition-dependent. CloudBolt documents a full-featured free-tier license for up to 100 managed resources and up to one year, plus paid licenses with higher resource and term limits. Obtain the paid quote and renewal terms; infrastructure is separate. Scope: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/configure/administration/product-license/ (reviewed 2026-11-19).

- 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: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://docs.cloudbolt.io/docs/cmp/get-started/install/deploy-in-aws/ (reviewed 2026-11-19).

- Release snapshot / cadence: Sources checked — unresolved. AWS offer prodview-tuvzf2rewwcy4 identifies AMI package 2026.3.78. That package version does not establish one dated current application/installer bundle across AWS and Azure or its support window. Confirm the entitled installer and upgrade matrix for the selected deployment. Scope: CloudBolt Cloud Management Platform: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-tuvzf2rewwcy4 (reviewed 2026-11-19).







## Cloudera on Cloud

Cloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.

- Listing: https://launchinyourcloud.com/directory/cloudera-on-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Shared operations · vendor control plane
- Infrastructure IDs: servers
- License: Commercial Cloudera subscription with cloud infrastructure charges paid separately.
- Licensing model: commercial-only
- Installation: Register the customer cloud environment and credentials, then provision Cloudera workload services through the control plane
- Architecture: Vendor-operated control plane with data, compute, networking and workload environments in the customer's cloud account.
- Operations: Cloudera operates the service control plane; the customer owns cloud resources, credentials, data governance, network integration, workload sizing and shared operational responsibilities.
- Product website: https://www.cloudera.com/products/cloudera-cloud.html
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Cloudera's public-cloud BYOC service, not a fully customer-operated software distribution. Workloads and data run in the customer's AWS, Azure or Google Cloud environment while Cloudera operates the control plane. Service availability and implementation details differ by provider, especially on Google Cloud, so confirm each required service before procurement. Cloudera November bulletins cover critical Brotli CVE-2026-111497 and compromised eMudhra certificates. Use the TSB matrices for the exact Runtime or Private Cloud Base component and fixed build rather than applying a generic platform version.

Cloudera on Cloud is a commercial subscription service. Customer cloud-resource charges and Cloudera software/service consumption are separate.

The customer account contains persistent data and compute services while Cloudera operates an external control plane. Runtime topology varies by selected workload service.


### Category fit

- data-analytics: Managed data engineering, warehousing and analytics services operate over data in customer cloud environments.

- streaming: Cloudera provides streaming ingestion and processing services where supported by the selected cloud deployment.

- ai-tools: Machine-learning and AI workload services are available within the Cloudera platform, subject to provider and subscription availability.

### Deployment boundaries


- aws: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

- azure: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

- gcp: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

Operating responsibility: Cloudera operates the control plane while workloads run in the customer's cloud accounts. Customer responsibilities include credentials, account policies, workload configuration and data governance; confirm each selected service's responsibility split. Source: https://www.cloudera.com/products/trust-center/shared-responsibility-model.html (checked 2026-11-20).


### Cloud deployment evidence

- Cloudera workloads in customer AWS, Azure and Google Cloud environments (aws, azure, gcp): https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html
  Cloudera documents registering customer AWS, Azure and Google Cloud environments and credentials so its control plane can provision workload resources. Provider service availability differs and must be checked for the selected workload.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Cloudera public-cloud architecture and ownership: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-public-cloud.html

- Cloud prerequisites and credential setup: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html

- Cloudera workload services: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html

- Cloudera pricing: https://www.cloudera.com/products/pricing.html

- Cloudera TSB-2026-1007: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html

- Cloudera TSB-2026-1009: https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html

### Licensing sources

- https://www.cloudera.com/products/pricing.html

### Infrastructure sources

- https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-public-cloud.html

- https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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 Google partnership page still labels Marketplace deployment coming soon. A current offer for the selected workload service and provider was not established from these sources. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://www.cloudera.com/partners/solutions/google-cloud-platform.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Platform pricing and cloud cost-optimization guidance do not establish which software fees qualify for a buyer’s committed-spend agreement. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://www.cloudera.com/products/pricing.html (reviewed 2026-11-17).

- Single sign-on: Documented. Management Console supports federation using enterprise SAML IdP metadata. Identity-provider creation is privileged; duplicate group names across IdPs can grant unintended memberships. Scope: Cloudera-managed control plane for customer-cloud workloads. Source: https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-setting-up-the-identity-provider-in-cdp.html (reviewed 2026-11-17).

- SCIM provisioning: Documented. Cloudera documents SCIM with Entra ID alongside SAML federation. Only one SCIM IdP per account is supported; userName and group-name changes are unsupported, so choose stable identifiers. Scope: Cloudera account provisioning, not a self-hosted SCIM server. Source: https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-configuring_scim_with_azure_ad.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Cloudera on Cloud 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.cloudera.com/management-console/cloud/user-management/topics/mc-known_issues_and_troubleshooting_related_to_idp_setup_in_cdp.html (reviewed 2026-11-17).

- Security controls: Documented. The user-management guidance warns about mutable identity keys and concurrent SAML/SCIM group synchronization. Align stable NameID/userName values and review privileged account/group mappings. Current advisory review: Cloudera TSBs address critical Brotli CVE-2026-111497 and compromised eMudhra certificates in specified CDP components. Apply the exact fixed component build and review affected certificate trust. Scope: Management Console identity synchronization and permissions Affected and fixed versions vary by Runtime and Private Cloud Base component; consult TSB-2026-1007 and TSB-2026-1009.. Source: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-known_issues_and_troubleshooting_related_to_idp_setup_in_cdp.html. Supporting source: TSB-2026-1009 — https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html.

- Air-gapped operation: Sources checked — unresolved. This listing uses an external vendor control plane. The reviewed public-cloud setup does not establish complete isolated operation; Cloudera Private Cloud documentation is a different offering. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Customer-cloud setup requires cloud account credentials, network prerequisites and an environment registration before Cloudera provisions workloads. The vendor control plane remains external to the customer account. Scope: Cloudera public-cloud environment setup; services differ by provider. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Sources checked — unresolved. The platform offers multiple workload services with different node, storage and database needs. The overview does not establish one minimum HA footprint for 100 users/1 TB; select the actual services and workload configuration. Scope: Cloudera on cloud workload-specific sizing. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).

- License pricing: Documented. Cloudera on Cloud is a commercial subscription service. Customer cloud-resource charges and Cloudera software/service consumption are separate. Scope: Cloudera on Cloud: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.cloudera.com/products/pricing.html (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Select workload services, Data Lake/runtime topology, data scans/compute-hours and provider-specific service availability. Vendor fees and customer-cloud resources are billed separately. 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.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. Management Console and customer-cloud workload services have independent release/runtime lines. A single platform latest-version number or universal upgrade schedule was not established. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Cloudera November 2026 Brotli and certificate bulletins (security-advisory): Cloudera TSBs address critical Brotli CVE-2026-111497 and compromised eMudhra certificates in specified CDP components. Scope: Affected and fixed versions vary by Runtime and Private Cloud Base component; consult TSB-2026-1007 and TSB-2026-1009. Conditions: Bundled Brotli and certificate trust stores determine exposure. Action: Apply the exact fixed component build and review affected certificate trust. Source: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html; reviewed 2026-11-18. Supporting source: TSB-2026-1009 — https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html.




## CockroachDB BYOC

Vendor-managed CockroachDB service deployed into the customer's AWS, Azure or Google Cloud account.

- Listing: https://launchinyourcloud.com/directory/cockroachdb-byoc/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial CockroachDB BYOC service.
- Licensing model: commercial-only
- Installation: Vendor-assisted BYOC onboarding using scoped cross-account cloud identity
- Architecture: Cockroach Labs control plane with database data plane in the customer cloud account
- Operations: Cockroach Labs manages database provisioning, upgrades, backups, monitoring and incidents; the customer owns the cloud account, network and billing boundary.
- Product website: https://www.cockroachlabs.com/
- Source review: 2026-11-17; cloud review: 2026-11-14; licensing review: 2026-11-17; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers CockroachDB BYOC on Cockroach Continuum, not ordinary fully managed CockroachDB Cloud or customer-operated self-hosting. BYOC is a Mission Critical deployment in AWS, Azure, or Google Cloud, priced at $1,000 per vCPU per year, with premium support and 99.99% single-region or 99.999% multi-region SLAs. Cluster Virtualization is a $200 per host-vCPU per year public-preview add-on on AWS and Google Cloud; dedicated and virtual clusters are excluded from the availability SLA during preview. Existing BYOC organizations created before Continuum keep their current pricing and support until an account-team migration path is available. Invoice billing and per-organization enablement are required.

This listing covers the commercial BYOC managed service, not source-code licensing for a separately self-hosted CockroachDB distribution. Cockroach Continuum packages BYOC as a Mission Critical deployment at $1,000 per vCPU per year; the public-preview Cluster Virtualization add-on is $200 per host-vCPU per year. Existing pre-Continuum organizations retain current pricing and support until a migration path is available.

The database data plane runs as persistent compute and storage inside the customer account, while Cockroach Labs operates it through a separate control plane.


### Category fit

- databases-vector: Provides a managed distributed SQL database whose data-plane resources run inside the customer's cloud account.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/ (checked 2026-11-14). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/ (checked 2026-11-14). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/ (checked 2026-11-14). 

Operating responsibility: Cockroach Labs handles provisioning, patching, backups and monitoring in the customer's cloud account. The customer supplies account access, network policy and cloud-resource governance. Source: https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/ (checked 2026-11-20). Supporting source: BYOC service component locations — https://www.cockroachlabs.com/cockroachdb-master-agreement/byoc/.


### Cloud deployment evidence

- CockroachDB BYOC customer-cloud support (aws, azure, gcp): https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/
  Cockroach Labs explicitly offers BYOC in the customer's AWS, Azure or Google Cloud account. The vendor operates database services using scoped cross-account identity while the customer retains the cloud account and data-plane boundary.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- CockroachDB Bring Your Own Cloud: https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/

- BYOC general availability and operating model: https://www.cockroachlabs.com/blog/cockroachdb-byoc-available/

- CockroachDB pricing: https://www.cockroachlabs.com/cockroachdb/pricing/

- CockroachDB BYOC on Continuum packaging and pricing: https://www.cockroachlabs.com/blog/byoc-cockroach-continuum/

### Licensing sources

- https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/

- https://www.cockroachlabs.com/cockroachdb/pricing/

- https://www.cockroachlabs.com/blog/byoc-cockroach-continuum/

### Infrastructure sources

- https://www.cockroachlabs.com/blog/cockroachdb-byoc-available/


### 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: Documented. The BYOC product page says customer-account infrastructure can use applicable committed-use discounts or reserved instances. This does not establish that Cockroach Labs software charges decrement a particular cloud commitment. Scope: Customer cloud infrastructure discounts; software/service billing eligibility is separate. Source: https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/ (reviewed 2026-11-14).

- Single sign-on: Documented. The vendor documents Cloud Organization SSO using SAML or OIDC with a customer IdP, enforcement and domain restrictions. A BYOC cluster belongs to that managed organization. This is vendor-hosted Cloud Console identity; SQL-user federation and DB Console policies are separately configured. Scope: Commercial Cloud organization identity used with BYOC; database-client identity separate. Source: https://www.cockroachlabs.com/cockroachdb-cloud-security/ (reviewed 2026-11-20). Supporting source: BYOC organization and cluster boundary — https://docs.cockroachlabs.com/docs/continuum/byoc-overview.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The AWS onboarding guide publishes customer-account role/trust and lifecycle permission policies, then provisions the managed cluster through Cloud Console or API. Vendor documentation also lists Terraform creation. Use the BYOC-specific role and account preparation; self-hosted CockroachDB manifests are a different deployment. Scope: Vendor-operated Continuum BYOC AWS onboarding artifacts and API path. Source: https://docs.cockroachlabs.com/docs/continuum/byoc-aws-deployment.md (reviewed 2026-11-20). Deployment artifact: https://docs.cockroachlabs.com/docs/continuum/byoc-aws-deployment.md. Artifact reference: Current Continuum onboarding policies; agree account/region and supported service version.

- Minimum footprint / sizing: Sources checked — unresolved. The BYOC overview requires a customer-sized Mission Critical cluster, cloud quotas and continuous lifecycle permissions. It does not establish a single minimum CPU/RAM/storage/zone topology for 100 users and 1 TB. Select workload concurrency, provisioned storage, regional availability and failure headroom with Cockroach Labs before requesting capacity. Scope: Continuum managed BYOC workload sizing; complete numerical footprint unresolved. Source: https://docs.cockroachlabs.com/docs/continuum/byoc-overview.md (reviewed 2026-11-20).

- License pricing: Documented. Continuum Mission Critical BYOC is USD 1,000 per vCPU per year, metered by the minute, with premium support. The public-preview Cluster Virtualization add-on is USD 200 per host-vCPU per year on AWS and Google Cloud. Invoice billing and per-organization enablement are required. Customer cloud infrastructure is billed separately. Pre-Continuum organizations keep their existing pricing/support until migration is available. Scope: CockroachDB BYOC on Continuum commercial service charges, not a total operating estimate or pricing for separately self-hosted CockroachDB. Public-preview host/virtual clusters are excluded from availability SLAs.. Source: https://www.cockroachlabs.com/blog/byoc-cockroach-continuum/ (reviewed 2026-11-17).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Confluence Data Center

Commercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/confluence-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation
- Architecture: Single-node or clustered Confluence and optional Synchrony services with an external database, load balancer, shared home and local indexes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, Synchrony, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/confluence/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Confluence Data Center, not Confluence Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). Upgrade to Confluence 9.2.26, 10.2.19, or a later fixed release to prevent unauthenticated access to specifically named files under the web application root. Separately, CVE-2026-90436 is a critical unauthenticated remote-code-execution issue in Confluence 1.x–9.x when Remote API (XML-RPC and SOAP) is enabled. Upgrade to 9.2.28 or a later fixed release, or disable the remote API and verify that the Axis endpoint returns HTTP 403; Confluence 10.x and later are unaffected by the RCE. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.

Confluence Data Center runs persistent application and collaborative-editing services with durable database, shared-home and local-index storage.


### Category fit

- collaboration: Provides self-managed team workspaces, collaborative authoring and enterprise knowledge sharing.

- content-management: Manages structured spaces, pages, attachments, templates and governed enterprise knowledge content.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 


### Cloud deployment evidence

- Confluence Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html
  Atlassian documents Confluence Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. The linked page applies to Confluence Data Center 11.0; select a Helm chart compatible with the installed product release.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Versions: 11.0; use the current compatibility matrix for other releases.


### Sources

- Install Confluence Data Center 11.0: https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html

- Run Confluence Data Center on Kubernetes: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html

- Confluence Data Center supported platforms: https://confluence.atlassian.com/doc/supported-platforms-207488198.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian product-specific end-of-life and purchase eligibility: https://www.atlassian.com/licensing/data-center-end-of-life

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian CVE-2026-90436 Confluence RCE advisory: https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

### Infrastructure sources

- https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html

- https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 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. Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Confluence 7.12+; authentication does not assign application access or permissions. Scope: Confluence 7.12+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16). Supporting source: OIDC product/version scope — https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html.

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Confluence Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The Data Center technical overview recommends at least 10 GB RAM per Confluence node, including operating-system, JVM, external-process and Synchrony allocations. Database, shared storage, node count and any separate Synchrony cluster require additional planning. Scope: Clustered Confluence Data Center node guideline; not an installation-wide total. Source: https://confluence.atlassian.com/enterprise/confluence-data-center-technical-overview-612959401.html (reviewed 2026-11-16).

- License pricing: Documented. New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies. Scope: Confluence Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 11.0.1, released 2026-11-03. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/confluence.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/DOC/Confluence+11.0+Release+Notes.




### Security and lifecycle reviews

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

- Data Center purchase restrictions and 2029 retirement (lifecycle): Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window. Scope: Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement. Conditions: Existing-customer status and the purchased product determine eligibility. Action: Confirm purchase eligibility, migration timing and any written exception before evaluation. Source: https://www.atlassian.com/licensing/data-center-end-of-life; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Confluence Remote API code-execution advisory (security-advisory): CVE-2026-90436 is an unauthenticated code-execution issue when the affected Remote API is enabled. Scope: Confluence Data Center 1.x–9.x before the applicable fix; 9.2.28 is the listed fixed LTS release. Confluence 10.x and later are unaffected. Conditions: Requires Remote API (XML-RPC and SOAP). Disabling it can break scripts, automation and add-ons. Action: Install a fixed supported release, or disable Remote API and verify HTTP 403 from the documented SOAP Axis endpoint. Source: https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




## Confluent Platform Self-Managed

Self-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.

- Listing: https://launchinyourcloud.com/directory/confluent-platform-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: A commercial Confluent subscription is required for Confluent Platform components deployed with CFK; component licenses otherwise vary.
- Licensing model: commercial-only
- Installation: Install the Confluent for Kubernetes operator with Helm, then deploy Confluent Platform components through Kubernetes custom resources.
- Architecture: CFK operator managing persistent Kafka, KRaft, Schema Registry, Connect, ksqlDB and other selected Confluent Platform services in a customer Kubernetes cluster
- Operations: Customer manages Kubernetes clusters, node pools, persistent storage, load balancers, DNS and routing, identity and RBAC, secrets, backups, scaling and upgrades; CFK reconciles the declared Confluent application resources.
- Product website: https://www.confluent.io/product/confluent-platform/
- Source review: 2026-11-19; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-managed Confluent Platform deployed with Confluent for Kubernetes, not Confluent Cloud. Current CFK guidance explicitly addresses Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. Provider examples do not certify every Kubernetes, Confluent Platform or topology combination; use the current supported-environments matrix and validate cross-cluster networking, storage, security, version compatibility and subscription terms. Confluent's November 2026 security releases address multiple broker, Kafka Connect, ZooKeeper, TLS trust, JWT, file-read, and denial-of-service issues. Upgrade to the latest patched release for the deployed branch: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3, or 8.4.1. Until patched, deployments using a separate Kafka Connect administrative listener should remove admin.listeners; the ZooKeeper fix applies to the affected 7.x lines identified by Confluent. CONFSA-2026-37 covers CVE-2026-114938 in Confluent Platform 7.6.x–8.4.x and Control Center 2.0.x–2.7.x when package/archive installs use affected customer JDKs, plus specified Docker-image ranges. Fixed-runtime releases were still being prepared at review time. Apply -XX:-UseBASE64Intrinsics to every affected Java process, restart and verify the flag until the applicable fixed image or runtime is available.

This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering.

CFK deploys long-running stateful brokers, controllers and supporting services on customer Kubernetes worker nodes with persistent storage. Using a managed Kubernetes control plane does not make the Confluent Platform application runtime serverless.


### Category fit

- streaming: Runs Apache Kafka brokers together with schema, connector and stream-processing services for customer-operated event streaming.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 


### Cloud deployment evidence

- Confluent for Kubernetes guidance for EKS, AKS and GKE (aws, azure, gcp): https://docs.confluent.io/operator/current/co-multi-region.html
  The current CFK multi-region guide explicitly identifies Google Kubernetes Engine, Amazon Elastic Kubernetes Service and Azure Kubernetes Service for provider-specific configuration and validation. The CFK overview defines the product as managing self-managed Confluent Platform in the customer's own Kubernetes environment. This evidence does not include the separately operated Confluent Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Confluent for Kubernetes overview: https://docs.confluent.io/operator/current/overview.html

- Deploy Confluent for Kubernetes: https://docs.confluent.io/operator/current/co-deploy-operator.html

- Supported environments and versions: https://docs.confluent.io/operator/current/co-supported-environments.html

- CFK multi-region deployment guidance: https://docs.confluent.io/operator/current/co-multi-region.html

- Confluent Platform licensing: https://docs.confluent.io/platform/current/installation/license.html

- Confluent November 2026 security advisories and patched releases: https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes

- Confluent compromised CA trust advisory: https://support.confluent.io/hc/en-us/articles/55611336006292-CONFSA-2026-33-CVE-2026-114820-CVE-2026-114406-Confluent-Platform-Compromised-eMudhra-Certificate-Authority-Roots-and-intermediates

- Confluent Kafka Connect administrative-listener advisory: https://support.confluent.io/hc/en-us/articles/55610452168340-CONFSA-2026-27-CVE-2026-115644-Confluent-Platform-Missing-Access-Control-Unauthenticated-Access-to-Kafka-Connect-Logging-API

- CONFSA-2026-37 Java4Shell advisory: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell

### Licensing sources

- https://docs.confluent.io/platform/current/installation/license.html

### Infrastructure sources

- https://docs.confluent.io/operator/current/overview.html

- https://docs.confluent.io/operator/current/co-supported-environments.html

- https://docs.confluent.io/operator/current/co-deploy-operator.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 6 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: Documented. Control Center supports OIDC SSO and automated configuration through CFK. The guide says IdP refresh-token rotation must be disabled for this integration. This is self-managed Control Center authentication, distinct from Confluent Cloud SAML. Scope: Confluent Platform Control Center OIDC; requires the relevant licensed components. Source: https://docs.confluent.io/platform/current/security/authentication/sso-for-c3/overview.html (reviewed 2026-11-16).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The Platform guide says Confluent’s annual SOC 2 report is available on request. It does not supply the current report period or customer-environment scope; its separate FIPS configuration guidance must not be treated as a whole-deployment attestation. Scope: Vendor security-controls report availability and deployment configuration; actual attestation scope unresolved. Source: https://docs.confluent.io/platform/current/security/compliance/overview.html (reviewed 2026-11-16).

- Security controls: Documented. CFK telemetry is disabled by default; enabling Health+ sends service metadata to Confluent. The built-in JMX Prometheus exporter lacks authentication/encryption and cannot be disabled through CFK, so restrict access at the network boundary and configure other security surfaces separately. Current review: CONFSA-2026-37 covers CVE-2026-114938 in package/archive installs using affected customer JDKs and in the advisory's Platform, Control Center, CMF, Flink, operator, Gateway and CFK init-container image ranges. Fixed-runtime releases were still in preparation. Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed. Scope: Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact Docker-image ranges in CONFSA-2026-37. Source: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://docs.confluent.io/operator/current/co-monitor-cp.html.

- Air-gapped operation: Sources checked — unresolved. CFK documents copying the required tagged Platform/operator/init-container images into a private registry and configuring pulls from it. This establishes private image delivery, but the reviewed guide does not establish end-to-end offline licensing, dependencies or updates for the selected stack. Scope: CFK private-registry installation mechanics; full disconnected operation remains unresolved. Source: https://docs.confluent.io/operator/current/co-custom-registry.html (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. The CFK guide installs confluent-for-kubernetes from Confluent’s Helm repository, then manages Platform components through custom resources. The repository index moves; select a CFK/chart release compatible with the Platform components and Kubernetes version. Scope: Confluent for Kubernetes deployment; commercial subscription applies. Source: https://docs.confluent.io/operator/current/co-deploy-operator.html (reviewed 2026-11-16). Deployment artifact: https://packages.confluent.io/helm/index.yaml. Artifact reference: moving Helm repository index; select compatible chart version.

- Minimum footprint / sizing: Documented. The current CFK guide starts with three Kafka brokers and three KRaft controllers. Each broker’s minimum is 4 CPUs, 16 GB RAM and 1 TB disk; the production column is larger. Controllers and other components add resources. Scope: CFK minimum cluster planning; not aggregate production sizing or pre-8.0 ZooKeeper guidance. Source: https://docs.confluent.io/operator/current/co-plan-sizing.html (reviewed 2026-11-16).

- License pricing: Documented. This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering. Scope: Confluent Platform Self-Managed: software license terms; infrastructure and operating costs are separate. Source: https://docs.confluent.io/platform/current/installation/license.html (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed compatibility matrix dates CFK 3.4.x to 2026-10-28, with standard support through 2028-10-28. It supports Platform 7.6.x–8.4.x and lists separate Control Center and Kubernetes ranges. The operator, init container and Platform have distinct versions; do not use a Platform patch number as the chart/operator version. Scope: CFK 3.4 release-line/support and component compatibility; not a claim about the newest Platform patch. Source: https://docs.confluent.io/operator/current/co-supported-environments.html (reviewed 2026-11-16).




### Security and lifecycle reviews

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

- Confluent Platform November security patches (security-advisory): Vendor advisories cover broker/Connect, CA trust, JWT, ZooKeeper and denial-of-service issues; component conditions vary. Scope: Confluent Platform fixes: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3 or 8.4.1, as applicable to each advisory. CFK/operator versions are separate. Conditions: Kafka Connect admin.listeners creates a separate affected administrative surface. ZooKeeper fixes apply only to the vendor-identified 7.x lines; do not transfer these claims to Confluent Cloud. Action: Use each advisory to choose the patched branch and compatible CFK/components. Until patched, remove the separate Connect admin.listeners setting. Source: https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes; reviewed 2026-11-17. Supporting source: Compromised CA trust remediation — https://support.confluent.io/hc/en-us/articles/55611336006292-CONFSA-2026-33-CVE-2026-114820-CVE-2026-114406-Confluent-Platform-Compromised-eMudhra-Certificate-Authority-Roots-and-intermediates. Supporting source: Connect administrative listener mitigation — https://support.confluent.io/hc/en-us/articles/55610452168340-CONFSA-2026-27-CVE-2026-115644-Confluent-Platform-Missing-Access-Control-Unauthenticated-Access-to-Kafka-Connect-Logging-API.

- Confluent CONFSA-2026-37 Java4Shell guidance (security-advisory): CONFSA-2026-37 covers CVE-2026-114938 in customer-JDK installs and multiple Confluent Docker-image ranges. Scope: Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact additional image ranges in the advisory. Conditions: Package/archive installs inherit the customer JDK; Docker applicability depends on the image and tag. Action: Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed. Source: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell; reviewed 2026-11-19.




## Coppermine Photo Gallery

Self-hosted web photo gallery and album application.

- Listing: https://launchinyourcloud.com/directory/coppermine/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: VM image
- Architecture: Coppermine application, database and images on a cloudimg Azure VM.
- 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/coppermine-gallery/cpg1.6.x
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The guide packages 1.6.29 while upstream publishes 1.6.31; check security and upgrade compatibility before exposing the image.

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

Coppermine application, database and images on a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted web photo gallery and album application.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.coppermine-ubuntu-24-04
  Coppermine application, database and images on a cloudimg Azure VM. The guide packages 1.6.29 while upstream publishes 1.6.31; check security and upgrade compatibility before exposing the image.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ron4mac, eenemeenemuu, dpaulat, 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/coppermine-gallery/cpg1.6.x/graphs/contributors

- Upstream project: https://github.com/coppermine-gallery/cpg1.6.x

### Sources

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

- GPL-3.0 LICENSE.txt: https://raw.githubusercontent.com/coppermine-gallery/cpg1.6.x/develop/LICENSE.txt

- GitHub Releases: https://github.com/coppermine-gallery/cpg1.6.x/releases

### Licensing sources

- https://raw.githubusercontent.com/coppermine-gallery/cpg1.6.x/develop/LICENSE.txt

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Documented. Coppermine v1.6.31 includes a Simple Machines Forum 2.1 bridge that shares forum-user identity through the SMF authentication cookie and user/group database, redirecting login to the forum. This confirms a specific shared-login integration, not general SAML/OIDC federation. Configure compatible forum/gallery versions and cookie/database boundaries; marketplace images need separate verification. Scope: Upstream Coppermine v1.6.31 with the bundled SMF 2.1 bridge; narrow shared-session integration. Source: https://github.com/coppermine-gallery/cpg1.6.x/blob/v1.6.31/bridge/smf21.inc.php (reviewed 2026-11-21). Supporting source: Bridge authentication implementation — https://github.com/coppermine-gallery/cpg1.6.x/blob/v1.6.31/bridge/udb_base.inc.php.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream v1.6.31 release includes a PHP browser installer with database, administrator and installation checks. Provision the PHP/web/database/image-processing dependencies and persistent gallery storage separately, then secure and maintain the installed application. This is manual application delivery rather than a cloud provisioning or HA template. Scope: Upstream Coppermine v1.6.31 browser installer; third-party marketplace VM provisioning is separate. Source: https://github.com/coppermine-gallery/cpg1.6.x/blob/v1.6.31/install.php (reviewed 2026-11-21). Deployment artifact: https://github.com/coppermine-gallery/cpg1.6.x/blob/v1.6.31/install.php. Artifact reference: v1.6.31. Supporting source: Release README — https://github.com/coppermine-gallery/cpg1.6.x/blob/v1.6.31/README.txt.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed release installer and README identify application/dependency checks but do not establish numeric production CPU/RAM/storage requirements. Image-processing concurrency, originals and derivatives, database capacity, backups and HA remain workload-specific; a marketplace VM offer alone would not establish an upstream minimum. Scope: Coppermine v1.6.31 production sizing remains unconfirmed. Source: https://github.com/coppermine-gallery/cpg1.6.x/blob/v1.6.31/README.txt (reviewed 2026-11-21).

- License pricing: Documented. GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Coppermine Photo Gallery; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/coppermine-gallery/cpg1.6.x/develop/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Coroot Community Edition

Self-hosted application observability with service maps, logs, metrics, traces and continuous profiling.

- Listing: https://launchinyourcloud.com/directory/coroot-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for Coroot Community Edition. Enterprise Edition has separate subscription terms.
- Licensing model: open-source
- Installation: Install the Coroot Operator and Community Edition Helm chart on the customer's Kubernetes cluster.
- Architecture: Customer-operated Coroot server and agents. ClickHouse stores logs, traces and profiles, and metrics can use ClickHouse or Prometheus.
- Operations: The customer manages the operator, image versions, privileged node-agent permissions, storage capacity, telemetry retention, backup and recovery, and access to the UI.
- Product website: https://coroot.com/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

The node agent requires privileged access for eBPF and host inspection, and upstream describes AWS Fargate support as basic. Anonymous usage statistics are enabled by default and can be disabled. The operator updates unpinned Coroot component images automatically. Native SAML/OIDC SSO is Enterprise-only. The Coroot server v1.29.4, Community chart 0.3.3 and operator chart 0.10.8 are separate version tracks; inspect and pin each required image.

Apache-2.0 applies to the published Community code. The Kubernetes guide identifies the separate licensed Enterprise chart.

Coroot and its agents run as Kubernetes workloads. Cluster node agents use eBPF and require compatible Linux kernels and privileged access.


### Category fit

- observability: Node and cluster agents collect operational telemetry for application monitoring and troubleshooting.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 


### Cloud deployment evidence

- Coroot on Amazon EKS (aws): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names EKS as a supported Kubernetes environment. Use the linked Community Helm instructions to deploy the operator, server and agents. The vendor specifies basic support for Fargate.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Azure AKS (azure): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names AKS among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster, subject to privileges and Linux requirements.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Google GKE (gcp): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names GKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Oracle OKE (oci): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names OKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Community and maintenance

The upstream project has sustained public contributor history (including def, apetruhin, Split174) and a reviewed dated v1.29.4 release. This establishes maintenance/community participation rather than a production suitability, support or capacity guarantee.

Reviewed 2026-11-20.

- Public contributor history: https://github.com/coroot/coroot/graphs/contributors

- Reviewed dated upstream release: https://github.com/coroot/coroot/releases/tag/v1.29.4

### Sources

- Community Helm installation and operating requirements: https://docs.coroot.com/installation/kubernetes/

- Supported orchestrators and Linux requirements: https://docs.coroot.com/installation/requirements/

- Coroot assembly and telemetry flow: https://docs.coroot.com/installation/architecture/

- ClickHouse storage and retention: https://docs.coroot.com/configuration/clickhouse/

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

- Upstream release history: https://github.com/coroot/coroot/releases

- Usage statistics and opt-out: https://docs.coroot.com/misc/anonymous-usage-statistics/

- Operator package: https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz

- Published chart index: https://coroot.github.io/helm-charts/index.yaml

- Buyer evidence: sso: https://docs.coroot.com/configuration/authentication/

- Buyer evidence: footprint: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz

- Buyer evidence: licensePricing: https://github.com/coroot/coroot/blob/v1.29.4/LICENSE

- Buyer evidence: release: https://github.com/coroot/coroot/releases/tag/v1.29.4

- Public contributor history: https://github.com/coroot/coroot/graphs/contributors

### Licensing sources

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

- https://docs.coroot.com/installation/kubernetes/

### Infrastructure sources

- https://docs.coroot.com/installation/kubernetes/

- https://docs.coroot.com/installation/architecture/


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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 edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Single sign-on: Explicitly unsupported. The authentication guide explicitly reserves native SAML/OIDC single sign-on for Coroot Enterprise. Community has local users with Admin, Editor and Viewer roles. An external authentication proxy would be a separate configuration, not native Community SSO. Scope: Native Coroot Community authentication; Enterprise is a separate edition. Source: https://docs.coroot.com/configuration/authentication/ (reviewed 2026-11-20).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Security controls: Documented. Community provides local-user authentication, three predefined roles and API-key service accounts. Set the initial admin password before exposure and review anonymous-mode settings. Node agents need privileged eBPF/host access; review the operator ClusterRole and its optional restriction on global secret access. Scope: Configured Community access controls and privileged collector/operator boundary. Source: https://docs.coroot.com/configuration/authentication/ (reviewed 2026-11-20). Supporting source: Node-agent privilege requirements — https://docs.coroot.com/installation/kubernetes/. Supporting source: Inspected operator permissions/configuration — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected coroot-ce 0.3.3 chart creates a Community custom resource and requires a separately installed operator; the reviewed operator chart is 0.10.8 (operator application 1.10.8). Neither chart version identifies the Coroot server release. Pin server, node-agent and cluster-agent images to prevent the documented automatic upgrades. Scope: Community custom resource plus separately versioned operator and component images. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20). Deployment artifact: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz. Artifact reference: coroot-ce 0.3.3; sha256:e6213b27a4e73924d2fe03c12aa815ebd8ec806436c3a5ab9bd4a8801c18e6f3; operator chart 0.10.8 / operator 1.10.8. Supporting source: Operator package — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz. Supporting source: Published chart index — https://coroot.github.io/helm-charts/index.yaml.

- Minimum footprint / sizing: Documented. The inspected Community chart defaults to 10 GiB Coroot storage, 10 GiB Prometheus storage and 100 GiB per ClickHouse instance. Its default ClickHouse layout is one shard/replica; the installation guide overrides this to two shards and two replicas. Operator requests are 100m CPU/64 MiB. These are component defaults, not total cluster CPU/RAM minima or an HA capacity guarantee. Scope: Chart-specific storage and operator request baseline; server/agent/database sizing remains workload-dependent. Source: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz (reviewed 2026-11-20). Supporting source: Separate operator requests — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz. Supporting source: Installation layout and replica override — https://docs.coroot.com/installation/kubernetes/. Supporting source: Kernel and orchestrator prerequisites — https://docs.coroot.com/installation/requirements/.

- License pricing: Documented. Coroot Community v1.29.4 is licensed under Apache-2.0. This establishes the software licence rather than a per-seat subscription; Enterprise features/support, dependencies and infrastructure have separate costs. Scope: Upstream Community code; excludes Enterprise subscriptions. Source: https://github.com/coroot/coroot/blob/v1.29.4/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed Coroot Community server snapshot is v1.29.4, published November 18, 2026. Operator, server, agents and charts are independently versioned; this snapshot does not guarantee support or pin the complete installation. Scope: Upstream Community server release. Source: https://github.com/coroot/coroot/releases/tag/v1.29.4 (reviewed 2026-11-20).







## Couchbase Server Enterprise Edition

Self-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.

- Listing: https://launchinyourcloud.com/directory/couchbase-server-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription for Couchbase Server Enterprise Edition; Community Edition is separately licensed.
- Licensing model: commercial-only
- Installation: Couchbase Kubernetes Operator by Helm or downloaded package, then CouchbaseCluster resources for Enterprise Edition
- Architecture: Customer-operated Couchbase Server pods, Kubernetes Operator, services and persistent volumes
- Operations: Customer manages Kubernetes, storage, networking, security, backups and upgrade policy; the Operator automates database lifecycle operations.
- Product website: https://www.couchbase.com/products/server/
- 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 Operator supports Couchbase Server Enterprise Edition 7.2 through 8.0 and is certified for Amazon EKS, Microsoft AKS and Google GKE. Couchbase Capella and Community Edition are outside this listing; verify the exact Operator, Server and Kubernetes compatibility matrix.

This entry is limited to Enterprise Edition, which Couchbase documents as a commercial subscription. Community Edition is a separate licensing scope.

Couchbase Server runs as stateful pods with persistent volumes while the in-cluster Operator reconciles Couchbase resources and lifecycle actions.


### Category fit

- databases-vector: Distributed NoSQL database deployed and lifecycle-managed in customer-controlled Kubernetes clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.couchbase.com/operator/current/overview.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.couchbase.com/operator/current/overview.html (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.couchbase.com/operator/current/overview.html (checked 2026-11-19). 


### Cloud deployment evidence

- Couchbase Server Enterprise on EKS, AKS and GKE (aws, azure, gcp): https://docs.couchbase.com/operator/current/overview.html
  Couchbase states that the Operator deploys and manages Server Enterprise Edition and is certified for Amazon EKS, Microsoft AKS and Google GKE. Database pods, services and storage run in the customer's cluster; this is not Couchbase Capella.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Enterprise Edition. Versions: Server 7.2 through 8.0 in the reviewed compatibility matrix.


### Sources

- Couchbase Operator introduction and certified platforms: https://docs.couchbase.com/operator/current/overview.html

- Couchbase Operator prerequisites and supported versions: https://docs.couchbase.com/operator/current/prerequisite-and-setup.html

- Install Couchbase Operator on Kubernetes: https://docs.couchbase.com/operator/current/install-kubernetes.html

- Couchbase Server editions and licensing: https://production.docs.couchbase.com/server/current/introduction/editions.html

- Buyer evidence: sso: https://docs.couchbase.com/server/current/manage/manage-security/configure-saml.html

- Buyer evidence: iac: https://docs.couchbase.com/operator/current/helm-setup-guide.html

- Reviewed deployment artifact reference: https://github.com/couchbase-partners/helm-charts/releases/download/couchbase-operator-2.94.0/couchbase-operator-2.94.0.tgz

- Official chart index and digest: https://couchbase-partners.github.io/helm-charts/index.yaml

### Licensing sources

- https://production.docs.couchbase.com/server/current/introduction/editions.html

### Infrastructure sources

- https://docs.couchbase.com/operator/current/concept-operator.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (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: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Single sign-on: Documented. The current Enterprise Server Web Console supports SAML SSO, with tested Okta and Microsoft Azure AD/Entra ID integrations. Configure metadata, certificate validation, user/group/role mappings and NameID handling. This console authentication does not establish SAML authentication for application SDK or database data-plane clients. Scope: Couchbase Server Enterprise current 8.0-line Web Console; verify older Server and Operator combinations separately. Source: https://docs.couchbase.com/server/current/manage/manage-security/configure-saml.html (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (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: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Security controls: Edition-dependent. The Operator manages the Enterprise database inside the customer's Kubernetes boundary. The deployment still requires buyer configuration of TLS, authentication, network policy, storage encryption, backup and Kubernetes access controls. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/prerequisite-and-setup.html (reviewed 2026-11-19).

- 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: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The official Helm repository publishes couchbase-operator chart 2.94.0 for Operator 2.9.4. The downloaded chart matches its published SHA-256 digest. It can deploy the Operator, admission controller and a CouchbaseCluster; select a compatible licensed Server image and production values separately. Chart and Operator versions are not Couchbase Server release versions. Scope: Public Helm deployment artifact for the Enterprise database; application licence and Server image remain separate. Source: https://docs.couchbase.com/operator/current/helm-setup-guide.html (reviewed 2026-11-19). Deployment artifact: https://github.com/couchbase-partners/helm-charts/releases/download/couchbase-operator-2.94.0/couchbase-operator-2.94.0.tgz. Artifact reference: chart 2.94.0 / Operator 2.9.4; sha256:f08d9f62fa955964ab380129a5206a414a36495c370bcc245309607afcb38c2a. Supporting source: Official chart index and digest — https://couchbase-partners.github.io/helm-charts/index.yaml.

- Minimum footprint / sizing: Documented. The current 8.0 x86 production floor is a 2-GHz two-core AVX2 CPU, 4 GiB physical RAM and 8 GiB block storage per node. The recommendation is four cores, at least 16 GiB RAM and SSDs. Each enabled service adds requirements; replicas, dataset/index size, backups and HA are additional. Scope: Couchbase Server 8.0 x86 per-node baseline; full service topology requires sizing. Source: https://docs.couchbase.com/server/current/install/pre-install.html (reviewed 2026-11-20).

- License pricing: Edition-dependent. Couchbase Server Enterprise Edition requires a commercial subscription. Community Edition is a different product scope; obtain a quote covering the selected nodes, support and Operator use. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://production.docs.couchbase.com/server/current/introduction/editions.html (reviewed 2026-11-19).

- 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: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The current Operator compatibility material covers Couchbase Server Enterprise Edition 7.2 through 8.0. Compatibility is a matrix across Operator, Server and Kubernetes versions; pin the exact supported combination rather than treating the range as one release. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/prerequisite-and-setup.html (reviewed 2026-11-19).







## Creatio Customer-Managed

Customer-managed business application platform with sales, orders and contract records.

- Listing: https://launchinyourcloud.com/directory/creatio/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: Creatio application servers and a supported database, with documented AWS and Azure configurations.
- 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://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The general deployment procedure names additional clouds, while the detailed system matrix specifically identifies AWS and Azure and qualifies other infrastructure. The reviewed badges follow the concrete matrix; named-user, server and product entitlements remain separate. Contract administration is part of the configured sales workflow.

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

Creatio application servers and a supported database, with documented AWS and Azure configurations. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-managed business application platform with sales, orders and contract records.

- contract-management: Customer-managed business application platform with sales, orders and contract records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements (checked 2026-11-19). 


### Cloud deployment evidence

- Customer-Managed Deployment (aws): https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure
  Creatio application servers and a supported database, with documented AWS and Azure configurations. The general deployment procedure names additional clouds, while the detailed system matrix specifically identifies AWS and Azure and qualifies other infrastructure. The reviewed badges follow the concrete matrix; named-user, server and product entitlements remain separate. Contract administration is part of the configured sales workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- System Requirements (azure): https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements
  Creatio application servers and a supported database, with documented AWS and Azure configurations. The general deployment procedure names additional clouds, while the detailed system matrix specifically identifies AWS and Azure and qualifies other infrastructure. The reviewed badges follow the concrete matrix; named-user, server and product entitlements remain separate. Contract administration is part of the configured sales workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Customer-Managed Deployment: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure

- System Requirements: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements

- Contracts Guide: https://academy.creatio.com/guides/creatio-apps/products/sales-tools/orders-and-invoices/create-contract

- Creatio Licensing Overview: https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing

- Licensing FAQ: https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing-faq

- 8.3.4 Twin Release Notes (May 2026): https://academy.creatio.com/guides/resources/release-notes/8-3-4-twin-release-notes

- 10.1 Unlimited Release Notes: https://academy.creatio.com/guides/resources/release-notes/10-1-unlimited-release-notes

- AI Studio Oct 2026: https://academy.creatio.com/guides/ai-studio/release-notes/october-2026/ai-studio-2026-10-22-release-notes

### Licensing sources

- https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing

- https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing-faq

### Infrastructure sources

- https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure

- https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Creatio 10 documents Microsoft Entra ID SAML sign-in with metadata exchange, application endpoint configuration and optional just-in-time provisioning. Configure the external identity provider and Creatio instance; LDAP synchronization is a separate capability. Scope: Creatio 10 customer-managed application; version-specific SAML and mobile SSO settings apply. Source: https://academy.creatio.com/guides/setup-and-administration/administration/user-and-access-management/authentication/set-up-sso-via-azure-ad (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 customer-managed Windows/IIS and Linux/.NET deployments, with separate database, Redis and application-server setup. This establishes an installation procedure, not a complete public Terraform or Helm deployment. Obtain the licensed setup files and follow the selected platform guide. Scope: Creatio 10 customer-managed cloud/on-site installation; infrastructure and optional components are separate. Source: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure (reviewed 2026-11-20). Supporting source: Server requirements — https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements.

- Minimum footprint / sizing: Sources checked — unresolved. The vendor provides a requirements calculator that depends on application, platform, database and active-user choices. The reviewed requirements do not establish a single quantitative whole-stack floor for the proposed workload; mail-listener or network figures are not application-server sizing. Scope: Creatio customer-managed application, database, Redis and selected optional services; workload and HA inputs required. Source: https://academy.creatio.com/resources/system-requirements-calculator (reviewed 2026-11-20). Supporting source: Server-side requirements — https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Damselfly

Self-hosted photo asset catalog, indexing and recognition application.

- Listing: https://launchinyourcloud.com/directory/damselfly/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: VM image
- Architecture: Damselfly application and persistent image catalog on an Azure VM.
- 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/Webreaper/Damselfly
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The cloudimg VM is a third-party package; recognition/model dependencies and upstream application maintenance are distinct.

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

Damselfly application and persistent image catalog on an Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted photo asset catalog, indexing and recognition application.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.damselfly-ubuntu-24-04
  Damselfly application and persistent image catalog on an Azure VM. The cloudimg VM is a third-party package; recognition/model dependencies and upstream application maintenance are distinct.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes Webreaper, jongalloway, vcsjones, 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/Webreaper/Damselfly/graphs/contributors

- Upstream project: https://github.com/Webreaper/Damselfly

### Sources

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

- GPL-3.0 LICENSE: https://raw.githubusercontent.com/Webreaper/Damselfly/master/LICENSE

- GitHub Releases: https://github.com/Webreaper/Damselfly/releases

### Licensing sources

- https://raw.githubusercontent.com/Webreaper/Damselfly/master/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The upstream multi-user guide documents local accounts, authentication enablement and application roles, but does not establish an external SAML/OIDC identity-provider login path. Its WordPress JWT upload integration is a different surface and does not establish user SSO. Scope: Damselfly application sign-in; a separate reverse proxy or integration needs its own supported configuration evidence. Source: https://github.com/Webreaper/Damselfly/blob/master/docs/Multi-user.md (reviewed 2026-11-20). Supporting source: WordPress integration and architecture — https://github.com/Webreaper/Damselfly/blob/master/docs/FAQ.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream installation guide supplies Docker/Compose instructions with separate pictures, configuration/database and thumbnail volumes. Configure user authentication, storage permissions, backups and HTTPS; the example is a single application deployment, not cloud/HA automation. Scope: Self-hosted Damselfly upstream container recipe; the Azure publisher image has a separate packaged version. Source: https://github.com/Webreaper/Damselfly/blob/master/docs/Installation.md (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/webreaper/damselfly. Artifact reference: master guide (moving branch); sample image tag is not pinned.

- Minimum footprint / sizing: Sources checked — unresolved. The installation guide describes pictures, thumbnails, configuration/database volumes and file-watcher limits, but does not establish a quantitative whole-host CPU/RAM/storage floor. Face/object processing, image count, thumbnails and backup needs change the required resources. Scope: Damselfly self-hosted application and media data; container startup and the Azure VM package are not universal HA capacity guarantees. Source: https://github.com/Webreaper/Damselfly/blob/master/docs/Installation.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Darktrace Forensic Acquisition and Investigation

Commercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.

- Listing: https://launchinyourcloud.com/directory/cado-response/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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; Terraform
- Architecture: Provider-specific CloudFormation or Terraform application stacks and evidence storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.

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

Provider-specific CloudFormation or Terraform application stacks and evidence storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Commercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (checked 2026-11-19). 

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

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


### Cloud deployment evidence

- AWS CloudFormation (aws): https://docs.cadosecurity.com/cado/deploy/aws/cloudformation
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Deploy (azure): https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Deploy (gcp): https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS CloudFormation: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation

- Azure Deploy: https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy

- GCP Deploy: https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy

- Licensing Docs: https://docs.cadosecurity.com/cado/deploy/licenses

- Product Page: https://www.darktrace.com/forensic-acquisition-investigation

- Darktrace News: https://www.darktrace.com/news/darktrace-unveils-automated-forensics-capabilities-in-its-activeai-security-platform

### Licensing sources

- https://docs.cadosecurity.com/cado/deploy/licenses

- https://www.darktrace.com/forensic-acquisition-investigation

### Infrastructure sources

- https://docs.cadosecurity.com/cado/deploy/aws/cloudformation

- https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy

- https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy


### 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 customer-deployed guide documents an Okta SAML integration, explicitly marked beta, with application callback/audience and email/group mapping. It excludes SaaS deployments and points those to a different identity guide. Validate the selected release, beta suitability, IdP and administrator-group handling. Scope: Darktrace customer-deployed Forensic Acquisition and Investigation; documented beta Okta SAML path. Source: https://docs.cadosecurity.com/cado/manage/users-authentication/sso/okta_saml (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 vendor supplies CloudFormation templates for public/private, existing-VPC and GovCloud deployment, with IAM/network parameters and sales/trial delivery access. Obtain the entitled template and licence, review permissions/TLS/storage, and choose the appropriate account/region topology. Scope: Vendor Cado/Darktrace customer-deployed AWS CloudFormation delivery. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (reviewed 2026-11-21). Deployment artifact: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation. Artifact reference: Current vendor CloudFormation guide reviewed on this date.

- Minimum footprint / sizing: Documented. The CloudFormation guide recommends m5.4xlarge as the enterprise minimum for the main EC2 server. Acquisition/processing workers, evidence volumes, network transfer and standby/recovery resources are additional. This is a vendor main-server recommendation, not a whole-system cost or HA workload guarantee. Scope: Customer-deployed Darktrace/Cado main-server recommendation; worker and evidence capacity separate. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Databricks classic compute

Data and AI platform with classic compute in your cloud environment.

- Listing: https://launchinyourcloud.com/directory/databricks/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Shared operations · vendor control plane
- Infrastructure IDs: servers
- License: Commercial
- Licensing model: commercial-only
- Installation: Cloud-specific workspace provisioning
- Architecture: Vendor control plane; customer classic compute
- Operations: The vendor manages the control plane. Your team configures classic compute, cloud resources and policies.
- Product website: https://www.databricks.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers classic compute only. Serverless compute runs in a Databricks-managed environment and is outside this entry. Confirm the responsibility split and metadata flows for your cloud. Beginning November 18, 2026, new VARIANT tables created on Databricks Runtime 17.3 or later automatically use variantShredding. Databricks Runtime 15.4 cannot read or write those tables, so upgrade affected classic clusters to 16.4 or later before creating or accessing them.

This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.

Classic compute uses customer-cloud compute resources. Databricks serverless compute is a different vendor-managed deployment and is outside this listing.


### Category fit

- data-analytics: Data and AI platform with classic compute in your cloud environment.

### Deployment boundaries


- aws: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.databricks.com/aws/en/getting-started/high-level-architecture (checked 2026-11-12). 

- azure: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture (checked 2026-11-12). 

- gcp: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.databricks.com/gcp/en/security/network/concepts/architecture (checked 2026-11-12). 

Operating responsibility: Classic compute and workspace storage are in the customer cloud account. Databricks operates the separate management plane; the customer configures compute, networking and policy. Serverless compute is outside this listing. Source: https://docs.databricks.com/aws/en/getting-started/high-level-architecture (checked 2026-11-20).


### Cloud deployment evidence

- Databricks classic compute architecture (aws): https://docs.databricks.com/aws/en/getting-started/high-level-architecture
  The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Databricks classic compute architecture (azure): https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture
  The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Databricks classic compute architecture (gcp): https://docs.databricks.com/gcp/en/security/network/concepts/architecture
  The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- AWS architecture: https://docs.databricks.com/aws/en/getting-started/high-level-architecture

- Azure architecture: https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture

- Google Cloud architecture: https://docs.databricks.com/gcp/en/security/network/concepts/architecture

- Classic versus serverless compute: https://docs.databricks.com/aws/en/compute/use-compute

- Databricks upcoming behavior changes: https://docs.databricks.com/aws/en/release-notes/whats-coming

### Licensing sources

- https://docs.databricks.com/aws/en/getting-started/high-level-architecture

### Infrastructure sources

- https://docs.databricks.com/aws/en/compute/use-compute


### 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 AWS account/workspace login configuration supports SAML 2.0 or OpenID Connect. Unified-login and emergency-access settings must be planned for the account. Scope: Databricks AWS account/workspace identity; separate vendor-operated control plane. Source: https://docs.databricks.com/aws/en/security/auth/single-sign-on/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Account-level SCIM user/group provisioning is documented with Premium or above. Identity federation is required for workspace assignment; workspace-level provisioning is legacy. Scope: Databricks on AWS; Premium or above; not a statement about every cloud edition. Source: https://docs.databricks.com/aws/en/admin/users-groups/scim (reviewed 2026-11-16).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor-supported Terraform provider manages workspaces and administrative resources; AWS infrastructure is provisioned with the AWS provider. Databricks recommends Terraform for cloud/external resources and administrative actions, and Automation Bundles for jobs and pipelines. Select compatible provider versions and least-privilege credentials. Scope: Classic AWS workspace/infrastructure administration; serverless has a different boundary. Source: https://docs.databricks.com/aws/en/dev-tools/terraform/ (reviewed 2026-11-20). Deployment artifact: https://github.com/databricks/terraform-provider-databricks. Artifact reference: Pin Databricks and cloud provider versions.

- Minimum footprint / sizing: Sources checked — unresolved. The classic-compute guide requires selecting runtime, worker types, driver, autoscaling and policies for the workload. It does not establish one platform-wide CPU/RAM floor. Size the customer-account compute separately from Databricks-hosted control-plane and optional serverless services. Scope: Classic AWS compute sizing unresolved without workload and topology. Source: https://docs.databricks.com/aws/en/compute/configure (reviewed 2026-11-20).

- License pricing: Documented. Databricks publishes usage-based product pricing in DBUs with optional committed-use contracts. Rates depend on cloud, region, workload and product. Customer-account classic infrastructure can incur a separate cloud bill; obtain the selected product rate and contract rather than treating a starting DBU price as the whole deployment cost. Scope: Databricks commercial usage model; no workload-specific quote or total cost. Source: https://www.databricks.com/product/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Datadog BYOC Logs

Datadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.

- Listing: https://launchinyourcloud.com/directory/datadog-byoc-logs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated · vendor control plane
- Infrastructure IDs: servers
- License: Commercial Datadog software and service. Confirm BYOC Logs activation and commercial terms with the account team.
- Licensing model: commercial-only
- Installation: Install the BYOC Logs engine and Observability Pipelines Worker with Helm. An operator-managed installation is documented on Amazon EKS.
- Architecture: Customer-operated Kubernetes engine and pipeline workers use object storage for log data and PostgreSQL for index metadata. Datadog hosts the UI and routes queries.
- Operations: The customer provisions and sizes the cluster, manages storage, database, IAM and network connectivity, and applies validated engine and Worker version pairs. Datadog maintains the hosted UI.
- Product website: https://docs.datadoghq.com/byoc-logs/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

Log ingestion, indexing and storage run in the customer's account. Matching query results travel to Datadog for display. The default connection is outbound from searcher pods to Datadog. Confirm service-site availability and account activation. A Docker path is documented for local evaluation. Docker is evaluation-only, and the Operator path is EKS-only. Engine v0.1.36/chart 0.6.0 needs the documented StatefulSet policy migration on existing clusters. Hosted Datadog SSO/SCIM and compliance boundaries remain distinct from the customer engine.

The offering requires a Datadog account and the vendor's terms. Account activation and the customer's applicable pricing and entitlement should be confirmed with Datadog.

Production workload uses Kubernetes, object storage and PostgreSQL. The listing's runtime describes the customer-operated engine and workers.


### Category fit

- observability: The customer-cloud Logs engine ingests, indexes, stores and queries operational logs. Datadog hosts the Log Explorer and pipeline configuration UI.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/aws_eks/ (checked 2026-11-20). 

- azure: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/azure_aks/ (checked 2026-11-20). 

- gcp: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/gcp_gke/ (checked 2026-11-20). 

Operating responsibility: The customer installs and operates log processing, indexing and storage in its infrastructure. The Datadog-hosted UI submits queries and receives results; storing logs locally does not establish a disconnected or wholly customer-operated management plane. Source: https://docs.datadoghq.com/byoc-logs/introduction.md (checked 2026-11-20). Supporting source: Customer deployment and cluster configuration — https://docs.datadoghq.com/byoc-logs/install.md.


### Cloud deployment evidence

- Datadog BYOC Logs on Amazon EKS (aws): https://docs.datadoghq.com/byoc-logs/install/aws_eks/
  Vendor guide installs the engine in the customer's EKS cluster using S3 and PostgreSQL. Helm and the EKS-specific Datadog Operator are documented.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Datadog BYOC Logs on Azure AKS (azure): https://docs.datadoghq.com/byoc-logs/install/azure_aks/
  Vendor guide installs the engine into the customer's AKS cluster with Azure Blob Storage and PostgreSQL Flexible Server.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Datadog BYOC Logs on Google GKE (gcp): https://docs.datadoghq.com/byoc-logs/install/gcp_gke/
  Vendor guide installs the engine in the customer's Google Cloud project with GKE, Cloud Storage, PostgreSQL and Workload Identity.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Sources

- BYOC Logs install options and account activation: https://docs.datadoghq.com/byoc-logs/install/

- Architecture and query-result boundary: https://docs.datadoghq.com/byoc-logs/introduction/architecture/

- Connections and network data flow: https://docs.datadoghq.com/byoc-logs/introduction/network/

- Validated engine and worker updates: https://docs.datadoghq.com/byoc-logs/operate/updates/

- Datadog End-User License Agreement: https://www.datadoghq.com/legal/eula/

- BYOC Logs account configuration and activation: https://docs.datadoghq.com/byoc-logs/configure/

- Datadog BYOC Logs on Amazon EKS: https://docs.datadoghq.com/byoc-logs/install/aws_eks/

- Datadog BYOC Logs on Azure AKS: https://docs.datadoghq.com/byoc-logs/install/azure_aks/

- Datadog BYOC Logs on Google GKE: https://docs.datadoghq.com/byoc-logs/install/gcp_gke/

- Buyer evidence: scim: https://docs.datadoghq.com/account_management/scim/

- Separate Worker artifact; not asserted to be a validated pair: https://github.com/DataDog/helm-charts/releases/download/observability-pipelines-worker-2.26.0/observability-pipelines-worker-2.26.0.tgz

- Engine release and StatefulSet migration: https://docs.datadoghq.com/byoc-logs/release_notes/

- Buyer evidence: sso: https://docs.datadoghq.com/account_management/saml/

- Buyer evidence: footprint: https://docs.datadoghq.com/byoc-logs/operate/sizing/

### Licensing sources

- https://www.datadoghq.com/legal/eula/

- https://docs.datadoghq.com/byoc-logs/configure/

### Infrastructure sources

- https://docs.datadoghq.com/byoc-logs/install/

- https://docs.datadoghq.com/byoc-logs/introduction/architecture/


### 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: Sources checked — unresolved. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Single sign-on: Documented. The hosted Datadog organization used for Log Explorer supports SAML SSO with a configured identity provider. This authenticates users to Datadog’s hosted UI; the customer-side engine connection instead uses Datadog API credentials and the selected network configuration. Scope: Datadog hosted account/control-plane identity; not an independent engine login. Source: https://docs.datadoghq.com/account_management/saml/ (reviewed 2026-11-20). Supporting source: BYOC query and control-plane boundary — https://docs.datadoghq.com/byoc-logs/introduction/architecture/.

- SCIM provisioning: Edition-dependent. Datadog documents SCIM user/team/role provisioning for Infrastructure Pro, Infrastructure Enterprise and Startup plans. Confirm the organization’s plan entitlement; BYOC Logs activation alone does not establish it. The endpoint manages hosted Datadog organization identities, not local engine users. Scope: Plan-dependent hosted Datadog organization provisioning. Source: https://docs.datadoghq.com/account_management/scim/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Security controls: Documented. The default searcher-initiated reverse connection uses outbound HTTPS/WebSocket access to Datadog and carries queries, results and index-management messages without a public query ingress. The optional public ingress uses mTLS. Review API credentials, storage IAM, network restrictions and the resulting query-result egress. Scope: BYOC query/control-plane connectivity and configurable customer-side controls. Source: https://docs.datadoghq.com/byoc-logs/introduction/network/ (reviewed 2026-11-20).

- Air-gapped operation: Explicitly unsupported. The documented BYOC workflow depends on a connection to the hosted Datadog UI/control plane. Searchers maintain outbound connections by default, or Datadog connects through an optional ingress. This connected offering does not provide a documented fully disconnected mode. Scope: Complete documented Datadog BYOC Logs workflow, including hosted UI. Source: https://docs.datadoghq.com/byoc-logs/introduction/network/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected cloudprem chart 0.6.0 packages engine v0.1.36. The separately indexed Worker chart is 2.26.0; observing both artifacts does not establish a validated engine/Worker pair. Select the vendor-approved combination. Chart 0.6.0 changes the indexer StatefulSet pod-management default; existing installations need the documented migration or an OrderedReady override. Scope: BYOC engine artifact plus separate Worker and cloud dependencies. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20). Deployment artifact: https://github.com/DataDog/helm-charts/releases/download/cloudprem-0.6.0/cloudprem-0.6.0.tgz. Artifact reference: cloudprem 0.6.0 / engine v0.1.36; sha256:7cf894e6c9fd3dc4e28f120fd354847151ea414e7885b7724d73fe2f1babae73. Supporting source: Separate Worker artifact; not asserted to be a validated pair — https://github.com/DataDog/helm-charts/releases/download/observability-pipelines-worker-2.26.0/observability-pipelines-worker-2.26.0.tgz. Supporting source: Vendor update/compatibility policy — https://docs.datadoghq.com/byoc-logs/operate/updates/. Supporting source: Engine release and StatefulSet migration — https://docs.datadoghq.com/byoc-logs/release_notes/.

- Minimum footprint / sizing: Documented. The sizing guide starts indexers at 2 vCPUs per TB/day, compactors at 1 vCPU per 2 TB/day and searchers near twice the indexer CPU, with query-driven adjustment. It separately sizes control services, Workers and PostgreSQL and recommends Multi-AZ database availability. Its 1 TB/day example assumes 30-day retention and roughly 6x compression; 1 TB stored is a different input. Scope: Vendor sizing model and assumptions; not a universal minimum or measured workload/cost estimate. Source: https://docs.datadoghq.com/byoc-logs/operate/sizing/ (reviewed 2026-11-20).

- License pricing: Documented. BYOC Logs is commercial Datadog software/service and requires activation through the account team. The reviewed materials do not establish an all-in public BYOC unit price or a customer quote; organization plan entitlements, engine/Worker billing and customer cloud charges must be confirmed separately. Scope: Commercial activation/licensing boundary, not an operating-cost estimate. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20). Supporting source: Datadog EULA — https://www.datadoghq.com/legal/eula/.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed BYOC engine snapshot is v0.1.36, dated November 3, 2026 and bundled in cloudprem chart 0.6.0. Engine, Worker and charts have separate versions; use the vendor-validated combination. Datadog states an engine release cadence of at least monthly, which is a vendor policy rather than a support guarantee from this directory. Scope: BYOC engine snapshot and separately documented update policy. Source: https://docs.datadoghq.com/byoc-logs/release_notes/ (reviewed 2026-11-20). Supporting source: Vendor version-pair and update policy — https://docs.datadoghq.com/byoc-logs/operate/updates/.




### Security and lifecycle reviews

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

- Datadog BYOC chart 0.6.0 indexer policy transition (lifecycle): Chart 0.6.0 defaults indexer podManagementPolicy to Parallel, an immutable StatefulSet field. Existing deployments need an override or the documented migration. Scope: BYOC engine v0.1.36 packaged in cloudprem chart 0.6.0; chart and application versions are separate. Conditions: Clusters running nodes older than engine v0.1.33 also need the documented gossip protocol compatibility setting during the transition. Action: Retain OrderedReady explicitly or follow the indexer StatefulSet migration. Keep gossip protocol 0 while older nodes remain, then apply the vendor-approved engine/Worker versions. Source: https://docs.datadoghq.com/byoc-logs/release_notes/; reviewed 2026-11-20.




## DataHub OSS

Open-source data catalog and metadata platform for discovery, lineage and governance.

- Listing: https://launchinyourcloud.com/directory/datahub/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: Official Helm deployment on EKS, AKS or GKE
- Architecture: Customer-operated application services with database, search, graph and event-stream dependencies
- Operations: Customer manages Kubernetes, stateful dependencies, networking, secrets, backups, scaling, ingestion, and upgrades, including search-backend compatibility and per-version breaking-change actions.
- Product website: https://datahub.com/
- Source review: 2026-11-19; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers DataHub OSS, not DataHub Cloud. Production deployments require careful operation of the metadata database, search index, event streaming and upgrade jobs; managed provider services can replace some in-cluster dependencies. DataHub v1.9.0 removes Elasticsearch 7.x support and requires Elasticsearch 8.x or OpenSearch 2.x/3.x. Metrics are enabled by default; set METRICS_ENABLED=false to disable them. The release requires CLI/Python SDK 1.7.0.19 and Helm chart 1.1.10, and operators should review all documented breaking changes before rollout. DataHub v1.9.1 rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and removes cached Wolfi layers that retained the earlier JDK. It also fixes OpenSearch 2.x semantic search with multiple OR groups. Preserve the v1.9.0 breaking-change, search-backend, CLI and Helm upgrade requirements when applying the patch.

DataHub OSS is Apache-2.0 licensed. DataHub Cloud and associated enterprise services use separate commercial terms.

DataHub uses persistent application services and stateful database, search and event-stream components. Provider-managed dependencies do not remove application operations. DataHub v1.9.0 supports Elasticsearch 8.x or OpenSearch 2.x/3.x; GMS will not start with Elasticsearch 7.x or OpenSearch compatibility mode reporting 7.10.2.


### Category fit

- data-analytics: Provides a metadata catalog, lineage graph, discovery and governance layer for connected data systems.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.datahub.com/docs/deploy/aws (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.datahub.com/docs/deploy/azure (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.datahub.com/docs/deploy/gcp (checked 2026-11-14). 


### Cloud deployment evidence

- DataHub on Amazon EKS (aws): https://docs.datahub.com/docs/deploy/aws
  The official guide deploys DataHub to a customer EKS cluster and describes optional AWS managed services for stateful dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- DataHub on Azure Kubernetes Service (azure): https://docs.datahub.com/docs/deploy/azure
  The official guide deploys DataHub to a customer AKS cluster and documents the required infrastructure and Helm installation.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- DataHub on Google Kubernetes Engine (gcp): https://docs.datahub.com/docs/deploy/gcp
  The official guide deploys DataHub to a customer GKE cluster with Helm and provider-managed dependency options.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

The project community profiles identify Zynga running a customized DataHub fork and Farm Credit Canada hardening a Kubernetes deployment. Public contributor history shows sustained work by multiple participants, and release 1.9.0 on November 16, 2026 documents active maintenance, security updates, and significant upgrade requirements. These profiles establish project use without treating DataHub Cloud customers as proof of OSS deployment.

Reviewed 2026-11-16.

- Reviewed maintenance release v1.9.0: https://github.com/datahub-project/datahub/releases/tag/v1.9.0

- Upstream contributor history: https://github.com/datahub-project/datahub/graphs/contributors

- Community profiles: Zynga fork and Farm Credit Canada deployment: https://datahub.com/community/champions/

### Sources

- Self-hosting on Kubernetes: https://docs.datahub.com/docs/deploy/kubernetes

- AWS deployment: https://docs.datahub.com/docs/deploy/aws

- Azure deployment: https://docs.datahub.com/docs/deploy/azure

- Google Cloud deployment: https://docs.datahub.com/docs/deploy/gcp

- Apache 2.0 license: https://github.com/datahub-project/datahub/blob/master/LICENSE

- DataHub v1.9.0 release and upgrade requirements: https://github.com/datahub-project/datahub/releases/tag/v1.9.0

- Upstream contributor history: https://github.com/datahub-project/datahub/graphs/contributors

- Community profiles: Zynga fork and Farm Credit Canada deployment: https://datahub.com/community/champions/

- DataHub v1.9.0 breaking changes: https://docs.datahub.com/docs/how/breaking-changes#v190

- DataHub v1.9.1 release: https://github.com/datahub-project/datahub/releases/tag/v1.9.1

### Licensing sources

- https://github.com/datahub-project/datahub/blob/master/LICENSE

### Infrastructure sources

- https://docs.datahub.com/docs/deploy/kubernetes

- https://github.com/datahub-project/datahub/releases/tag/v1.9.0

- https://docs.datahub.com/docs/how/breaking-changes#v190


### 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 self-managed React application supports OIDC identity providers such as Okta, Google and Keycloak through its authentication configuration. This is separate from DataHub Cloud login setup. Scope: DataHub self-managed frontend OIDC configuration. Source: https://docs.datahub.com/docs/authentication/guides/sso/configure-oidc-react (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. v1.9.1 rebuilds GMS, frontend, MAE/MCE consumer, upgrade and actions images on OpenJDK 25.0.5.1 to address CVE-2026-114938, and removes cached Wolfi layers that could retain the prior JDK. Upgrade every service image and restart. Scope: DataHub OSS service images from the v1.9.1 release and its v1.9.0 hotfix branch. Source: https://github.com/datahub-project/datahub/releases/tag/v1.9.1 (reviewed 2026-11-19).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Helm repository provides separate DataHub and prerequisite charts, including external database, search and Kafka dependencies. The deployment guide includes example credentials that must be replaced. Pin compatible chart and application versions, and review whether to use managed or separately operated dependencies. Scope: Official Kubernetes Helm deployment. Source: https://docs.datahub.com/docs/deploy/kubernetes (reviewed 2026-11-20). Deployment artifact: https://github.com/acryldata/datahub-helm. Artifact reference: Select compatible chart and application releases.

- Minimum footprint / sizing: Documented. The Kubernetes guide requires more than 7 GB RAM for a local Minikube deployment including dependencies. This is not a production minimum: application services, database, Kafka, search and any graph service require separate resource and availability sizing. Scope: Local all-component deployment floor; production/HA capacity excluded. Source: https://docs.datahub.com/docs/deploy/kubernetes (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/datahub-project/datahub/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. DataHub v1.9.1 was published November 19, 2026. It rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and fixes OpenSearch 2.x semantic search with multiple OR groups. Retain the v1.9.0 Elasticsearch/OpenSearch, CLI, Helm and breaking-change requirements. Scope: Upstream DataHub OSS service images and hotfix branch; commercial editions and provider packages may differ. Source: https://github.com/datahub-project/datahub/releases/tag/v1.9.1 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/datahub-project/datahub/releases/tag/v1.9.0.




### Security and lifecycle reviews

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

- DataHub v1.9.1 OpenJDK security rebuild (security-advisory): DataHub v1.9.1 rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and removes cached Wolfi layers retaining the older JDK. Scope: DataHub OSS GMS, frontend, MAE/MCE consumer, upgrade and actions images; fixes were also cherry-picked to the v1.9.0 hotfix branch. Conditions: Affected image and CPU/JDK behavior determine exposure. Action: Deploy fixed images for every DataHub service and restart them while retaining the v1.9.0 upgrade prerequisites. Source: https://github.com/datahub-project/datahub/releases/tag/v1.9.1; reviewed 2026-11-19.




## Dataiku DSS Cloud Stacks

Commercial Dataiku DSS deployment managed through Fleet Manager inside a customer AWS, Azure or Google Cloud tenant.

- Listing: https://launchinyourcloud.com/directory/dataiku-dss-cloud-stacks/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Dataiku license or license token required for the full Cloud Stacks capabilities.
- Licensing model: commercial-only
- Installation: AWS CloudFormation, Azure ARM template or Google Cloud Infrastructure Manager with Terraform
- Architecture: Customer-hosted Fleet Manager provisioning VM-backed DSS instances and optional elastic Kubernetes compute in the customer's cloud tenant
- Operations: Customer manages cloud accounts, Fleet Manager, IAM identities, networking, VM and Kubernetes capacity, storage, TLS, backups, upgrades and license configuration.
- Product website: https://www.dataiku.com/product/
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Dataiku Cloud Stacks, not vendor-hosted Dataiku Cloud. Dataiku states that Cloud Stacks resources run in the customer's organization or tenant and that Dataiku does not have access to customer data. Fleet Manager requires broad cloud permissions and outbound access for images, license validation and configured identity services. Dataiku DSS Free Edition is separate from the fully featured licensed Cloud Stacks deployment.

The listed fully featured Cloud Stacks deployment requires a Dataiku license or license token. Dataiku documents a separate DSS Free Edition, but that does not determine the licensing of the listed Cloud Stacks offering.

Cloud Stacks deploys a persistent Fleet Manager and VM-backed DSS nodes in the customer tenant, with optional EKS, AKS or GKE elastic-compute clusters.


### Category fit

- data-analytics: Provides customer-operated data preparation, analytics, visual workflows, elastic computation and governed data projects.

- ai-tools: Provides customer-operated data science, machine-learning, generative-AI, model-deployment and AI-governance capabilities.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/guided-setup-new-vpc-elastic-compute.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/guided-setup-new-vnet-elastic-compute.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/guided-setup-new-vpc-elastic-compute.html (checked 2026-11-16). 


### Cloud deployment evidence

- Dataiku DSS Cloud Stacks on AWS (aws): https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/guided-setup-new-vpc-elastic-compute.html
  Dataiku documents using an AWS CloudFormation template to deploy Fleet Manager into the customer's AWS account, then provisioning DSS nodes and optional EKS elastic-compute clusters.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Dataiku DSS Cloud Stacks on Azure (azure): https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/guided-setup-new-vnet-elastic-compute.html
  Dataiku documents deploying Fleet Manager and its supporting resources through an Azure ARM template, then provisioning DSS instances and optional AKS elastic compute in the customer's subscription.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Dataiku DSS Cloud Stacks on Google Cloud (gcp): https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/guided-setup-new-vpc-elastic-compute.html
  Dataiku documents deploying Fleet Manager through Google Cloud Infrastructure Manager using its supplied Terraform configuration, then provisioning DSS instances and optional GKE elastic compute in the customer's projects.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Dataiku DSS installation options: https://doc.dataiku.com/dss/latest/installation/

- Dataiku Cloud Stacks for AWS: https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html

- Dataiku Cloud Stacks for Azure: https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/index.html

- Dataiku Cloud Stacks for Google Cloud: https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/index.html

- Dataiku DSS licensing: https://doc.dataiku.com/dss/latest/operations/license.html

### Licensing sources

- https://doc.dataiku.com/dss/latest/operations/license.html

- https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html

### Infrastructure sources

- https://doc.dataiku.com/dss/latest/installation/

- https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html

- https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/concepts.html

- https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/index.html


### Buyer diligence


Research coverage: 10/12 fields (83%); 7 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: Sources checked — unresolved. The reviewed Dataiku Trial offer delivers an AWS AMI and uses an externally purchased license. That does not establish the current fully featured Cloud Stacks entitlement or a Fleet Manager deployment; confirm the selected contract and installer separately. Scope: Trial AMI versus the listed commercial Cloud Stacks offering. Source: https://aws.amazon.com/marketplace/pp/prodview-hrcm5q34opptc (reviewed 2026-11-16).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. DSS 15 documents SAML and OpenID Connect SSO. Its SAML compatibility list includes Okta, Entra ID, ADFS, Auth0 and Keycloak; encrypted SAML assertions are explicitly unsupported. Configure the DSS instance and identity provider together. Scope: DSS instance authentication within Cloud Stacks; license and enabled features still govern entitlement. Source: https://doc.dataiku.com/dss/latest/security/sso.html (reviewed 2026-11-16). Supporting source: DSS authentication mechanisms — https://doc.dataiku.com/dss/latest/security/authentication/.

- SCIM provisioning: Sources checked — unresolved. DSS documents SSO/LDAP/Azure AD user suppliers, login-time provisioning and administrative synchronization. These mechanisms do not establish a SCIM protocol endpoint; the reviewed authentication manual leaves direct SCIM support unresolved. Scope: DSS 15 user suppliers and synchronization; not a claim that SCIM is unsupported. Source: https://doc.dataiku.com/dss/latest/security/authentication/ (reviewed 2026-11-16).

- Compliance attestations: Documented. Dataiku’s published certificate 1850881-6 covers its organizational ISMS/PIMS supporting the Dataiku platform, including R&D. It was issued 2026-04-30 and expires 2027-12-14, subject to surveillance. The certificate expressly does not authorize labeling products, processes or services as certified; it does not certify the customer’s Cloud Stacks environment. Scope: Dataiku Inc. ISO/IEC 27001:2022 and 27701:2019 organizational management systems; not a customer-deployment certificate. Source: https://downloads.dataiku.com/publicdocs/Dataiku_ISO_27001_Certificate_of_Registration.pdf (reviewed 2026-11-16). Supporting source: Self-managed and SaaS account boundaries — https://www.dataiku.com/legal/trust.

- Security controls: Documented. For AWS Cloud Stacks, Fleet Manager recommends an IAM instance profile for cloud API calls. If it stores secrets, they are encrypted with an AWS KMS customer-managed key. HTTP access is used for image lists, license verification and OIDC. Scope: Fleet Manager AWS access, optional secret storage and outbound requirements. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html (reviewed 2026-11-16).

- Air-gapped operation: Sources checked — unresolved. DSS 15 documents offline document-extraction resources, but Fleet Manager’s standard Cloud Stacks setup uses HTTP for image lists, license updates/verification and OIDC. The reviewed material does not establish an end-to-end disconnected Cloud Stacks procedure. Scope: Cloud Stacks/Fleet Manager boundary; an offline DSS feature does not establish a disconnected management stack. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html (reviewed 2026-11-16). Supporting source: DSS 15 air-gapped extraction upgrade notes — https://doc.dataiku.com/dss/latest/release_notes/15.html.

- Deployment artifact / IaC: Documented. The GCP guide deploys Fleet Manager with Infrastructure Manager and Terraform. It identifies gs://dataiku-cloudstacks/templates/fleet-manager/15.2.1/fleet-manager-instance.tf and a separate terraform.tfvars file. This is the guide’s versioned example, not a universal latest-version claim; AWS uses CloudFormation and Azure uses ARM templates. Scope: Cloud Stacks Fleet Manager; provider-specific templates and permissions. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/guided-setup-new-vpc-elastic-compute.html (reviewed 2026-11-16). Supporting source: AWS Cloud Stacks — https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html. Supporting source: Azure Cloud Stacks — https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/concepts.html.

- Minimum footprint / sizing: Documented. DSS 15’s server requirements specify x86-64 Linux and at least 32 GB RAM, with more for in-memory data and additional users. This sizes the DSS application component only; Fleet Manager, execution infrastructure and cloud services add resources. Scope: DSS 15 application requirements; not a complete Cloud Stacks architecture estimate. Source: https://doc.dataiku.com/dss/latest/installation/custom/requirements.html (reviewed 2026-11-16).

- License pricing: Documented. The listed fully featured Cloud Stacks deployment requires a Dataiku license or license token. Dataiku documents a separate DSS Free Edition, but that does not determine the licensing of the listed Cloud Stacks offering. Scope: Dataiku DSS Cloud Stacks: software license terms; infrastructure and operating costs are separate. Source: https://doc.dataiku.com/dss/latest/operations/license.html (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor release is 15.2.2, published 2026-11-06. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Scope: DSS application release; Fleet Manager templates and deployed instance versions may differ; source supplies a publication day, not a timestamp. Source: https://doc.dataiku.com/dss/latest/release_notes/15.html (reviewed 2026-11-16).







## Decisions Self-Hosted

Commercial rules and workflow platform with provider-specific container deployments.

- Listing: https://launchinyourcloud.com/directory/decisions-platform/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- 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: Docker / Compose; Kubernetes manifests
- Architecture: Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP.
- 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://documentation.decisions.com/docs/deploying-containers-on-aws-1.md
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.

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

Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- workflow-automation: Commercial rules and workflow platform with provider-specific container deployments.

- internal-tools: Commercial rules and workflow platform with provider-specific container deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md (checked 2026-11-19). 


### Cloud deployment evidence

- AWS ECS Deploy (aws): https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Deploy (azure): https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Deploy (gcp): https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS ECS Deploy: https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md

- Azure Deploy: https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md

- GCP Deploy: https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md

- AWS EKS Deploy: https://documentation.decisions.com/docs/deploying-an-aws-kubernetes-cluster.md

- Azure AKS Deploy: https://documentation.decisions.com/docs/deploying-azure-kubernetes-services-aks.md

- Financial Services: https://decisions.com/solutions/industry/financial-services

- Terms of Use: https://decisions.com/terms-of-use

- Container Licensing: https://documentation.decisions.com/docs/licensing-a-container.md

- v10.4.x Release Notes: https://documentation.decisions.com/v99/docs/version-104x-release-notes.md

### Licensing sources

- https://decisions.com/terms-of-use

- https://documentation.decisions.com/docs/licensing-a-container.md

### Infrastructure sources

- https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md

- https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md

- https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md


### 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 SAML login through an installed identity-provider module, certificate and IdP settings, with accounts updated before enforcement and at least one working admin SSO account. It warns that Active Directory Sync cannot run simultaneously with SAML/OpenID SSO modules. Scope: Self-hosted application user SSO; module/release and IdP configuration required. Source: https://documentation.decisions.com/docs/saml (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 installation guide provides the v10.x installer and supported database setup. The ECS guide documents task definitions using the vendor container image, environment variables and persistent file storage; it is a console recipe rather than a supplied Terraform/CloudFormation stack. Pin a compatible released image rather than copying latest. Scope: Licensed self-hosted installer/container workflow; application, database and HA setup are separate. Source: https://documentation.decisions.com/docs/deploying-containers-on-aws-1 (reviewed 2026-11-20). Supporting source: v10 installation guide and release download — https://documentation.decisions.com/version-10/docs/installation-guide.

- Minimum footprint / sizing: Documented. The installation requirements list an AWS production example using t3.xlarge (4 vCPU, 16 GB RAM) and 100 GB storage. Database requirements are separate, and enterprise/HA topology and workload can require larger or multiple servers. This server example does not include 1 TB of application data. Scope: General self-hosted application-server guidance; not a cost estimate or validated reference-workload HA design. Source: https://documentation.decisions.com/docs/installation-requirements (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## django-helpdesk

Django-based helpdesk for tickets, queues and support communication.

- Listing: https://launchinyourcloud.com/directory/django-helpdesk/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Django application, database and persistent files in a cloudimg Azure VM.
- 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/django-helpdesk/django-helpdesk
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The third-party VM is distinct from an upstream-supported appliance; confirm installed package versions and apply security updates. Use django-helpdesk 2.6.1 or a later compatible fixed build and review the public ticket and non-staff permission settings.

BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Django application, database and persistent files in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Django-based helpdesk for tickets, queues and support communication.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.django-helpdesk-ubuntu-24-04
  Django application, database and persistent files in a cloudimg Azure VM. The third-party VM is distinct from an upstream-supported appliance; confirm installed package versions and apply security updates.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes gwasser, rossp, uhurusurfa, 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/django-helpdesk/django-helpdesk/graphs/contributors

- Upstream project: https://github.com/django-helpdesk/django-helpdesk

### Sources

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

- GitHub LICENSE (BSD-3-Clause): https://raw.githubusercontent.com/django-helpdesk/django-helpdesk/main/LICENSE

- GitHub Releases (v2.6.1): https://github.com/django-helpdesk/django-helpdesk/releases

- GitHub Commits: https://github.com/django-helpdesk/django-helpdesk/commits/main

- django-helpdesk public ticket access checks: https://github.com/django-helpdesk/django-helpdesk/security/advisories/GHSA-9g24-qf73-cjxh

### Licensing sources

- https://raw.githubusercontent.com/django-helpdesk/django-helpdesk/main/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The published v2.6.1 package integrates Django users and login views, but its installation/settings material does not establish a specific SAML/OIDC identity-provider integration. Using Django authentication backends is a customization path, not confirmation that a marketplace image includes configured SSO. Verify the backend, callback and user/permission mapping. Scope: Published Django application authentication hooks; external federation remains unconfirmed. Source: https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/docs/settings.rst (reviewed 2026-11-20). Supporting source: Published application login routes — https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/src/helpdesk/urls.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v2.6.1 standalone guide supplies a setup script and Compose stack; it separately documents installation as a package in an existing Django application. Configure database, secrets, mail, site URL, reverse proxy and production settings. The demo server and default demo credentials are not a production deployment. Scope: Published standalone versus embedded Django installation. Source: https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/docs/standalone.rst (reviewed 2026-11-20). Deployment artifact: https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/standalone/docker-compose.yml. Artifact reference: v2.6.1. Supporting source: Integration into an existing Django application — https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/docs/install.rst.

- Minimum footprint / sizing: Sources checked — unresolved. The published installation material identifies the Python/Django application, database and production services but gives no complete CPU/RAM/storage minimum. Development/demo allocations do not establish capacity for ticket mail, attachments, concurrency or HA; obtain a workload-specific sizing plan for the selected image/version. Scope: Published application topology; numeric production sizing remains unconfirmed. Source: https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/docs/standalone.rst (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- django-helpdesk public ticket access checks (security-advisory): The advisory describes a public ticket lookup that did not validate its secret key. Scope: Versions 0.3.0–2.6.0; patched in 2.6.1 (GHSA-9g24-qf73-cjxh). Conditions: Affected public-ticket configuration can disclose a ticket to a visitor who knows the ID and submitter email; see the full advisory for conditions. Action: Use django-helpdesk 2.6.1 or a later compatible fixed build and review the public ticket and non-staff permission settings. Source: https://github.com/django-helpdesk/django-helpdesk/security/advisories/GHSA-9g24-qf73-cjxh; reviewed 2026-11-19.




## DMPRoadmap

Open-source institutional data-management planning software used for research and funder requirements.

- Listing: https://launchinyourcloud.com/directory/dmproadmap/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: A third-party cloudimg Azure VM containing the DMPRoadmap application and required services.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/DMPRoadmap/roadmap
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application supports research data-management plans, templates and institutional review, rather than grant payments or awards. The Azure package is from cloudimg; its application/OS versions and support are separate from the upstream project.

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

A third-party cloudimg Azure VM containing the DMPRoadmap application and required services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- research-grant-administration: Open-source institutional data-management planning software used for research and funder requirements.

### Deployment boundaries


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


### Cloud deployment evidence

- Azure Marketplace Offer (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.dmproadmap
  A third-party cloudimg Azure VM containing the DMPRoadmap application and required services. The application supports research data-management plans, templates and institutional review, rather than grant payments or awards. The Azure package is from cloudimg; its application/OS versions and support are separate from the upstream project.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes briri, xsrust, raycarrick-ed, 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/DMPRoadmap/roadmap/graphs/contributors

- Upstream project: https://github.com/DMPRoadmap/roadmap

### Sources

- Azure Marketplace Offer: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.dmproadmap

- GitHub README: https://raw.githubusercontent.com/DMPRoadmap/roadmap/development/README.md

- MIT LICENSE: https://raw.githubusercontent.com/DMPRoadmap/roadmap/development/LICENSE.md

- GitHub Releases: https://github.com/DMPRoadmap/roadmap/releases

- GitHub Commits: https://github.com/DMPRoadmap/roadmap/commits/development

### Licensing sources

- https://raw.githubusercontent.com/DMPRoadmap/roadmap/development/LICENSE.md

### Infrastructure sources

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.dmproadmap


### Buyer diligence


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

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


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: DMPRoadmap selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.dmproadmap?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.dmproadmap: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.dmproadmap.

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

- Single sign-on: Documented. The v6.0.0 callback implementation signs mapped Shibboleth users into the application and handles identity linking. The same code explicitly treats ORCID as identifier linking rather than a supported sign-in method. Configure the institutional Shibboleth provider, attributes and account policy for the selected package. Scope: DMPRoadmap v6.0.0 institutional Shibboleth user login; ORCID login excluded. Source: https://github.com/DMPRoadmap/roadmap/blob/v6.0.0/app/controllers/users/omniauth_callbacks_controller.rb (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 reviewed cloudimg offer delivers the DMPRoadmap application and dependencies as a customer Azure VM. This is a marketplace image, separate from upstream Rails source and release versions. Scope: Selected third-party Azure VM deployment artifact. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.dmproadmap?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Deployment artifact: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.dmproadmap. Artifact reference: cloudimg DMPRoadmap public Azure VM offer; verify the selected package version at provisioning.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed upstream README identifies Rails/database deployment context, but no quantitative production CPU/RAM/storage baseline was established. A third-party marketplace image must be sized and version-checked separately for users, plans, files, database, jobs, backups and HA. Scope: DMPRoadmap complete production sizing remains unconfirmed. Source: https://github.com/DMPRoadmap/roadmap/blob/development/README.md (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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







## DocuSeal Self-Hosted

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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

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

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

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

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

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

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


### Cloud deployment evidence

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

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

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

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

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

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

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

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

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

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

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

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


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

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

### Sources

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### Licensing sources

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

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

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

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

### Infrastructure sources

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

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

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

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


### Buyer diligence


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

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


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

- Cloud commitment eligibility: Not researched.

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

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

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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



### Vendor alternative positioning

Positioning is not a finding of feature parity.

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

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


### Security and lifecycle reviews

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

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




## DocuWare On-Premise

Customer-operated document repository, email capture and document-workflow platform on Azure VMs.

- Listing: https://launchinyourcloud.com/directory/docuware-on-premises/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: azure
- 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: Licensed DocuWare installation on Azure Windows Server VMs
- Architecture: Windows Server application VMs and a database on the same or separate VM.
- 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://support.docuware.com/en-us/knowledgebase/article/KBA-37193
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure knowledge-base article excludes Azure SQL and Azure Blob Storage. Its MSMQ/Azure Service Bus workaround applies to older versions; the vendor's clarification says messaging changed in 7.13 and later. This is a configurable document workflow, rather than a packaged public-correspondence case system.

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

Windows Server application VMs and a database on the same or separate VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Customer-operated document repository, email capture and document-workflow platform on Azure VMs.

- workflow-automation: Customer-operated document repository, email capture and document-workflow platform on Azure VMs.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.docuware.com/en-us/knowledgebase/article/KBA-37193 (checked 2026-11-19). 


### Cloud deployment evidence

- Azure VM KBA-37193 (azure): https://support.docuware.com/en-us/knowledgebase/article/KBA-37193
  Windows Server application VMs and a database on the same or separate VM. The Azure knowledge-base article excludes Azure SQL and Azure Blob Storage. Its MSMQ/Azure Service Bus workaround applies to older versions; the vendor's clarification says messaging changed in 7.13 and later. This is a configurable document workflow, rather than a packaged public-correspondence case system.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure VM KBA-37193: https://support.docuware.com/en-us/knowledgebase/article/KBA-37193

- Connect to Mail: https://knowledgecenter.docuware.com/docs/connect-to-mail.md

- Workflow Designer: https://knowledgecenter.docuware.com/docs/web-based-workflow-designer.md

- Client Licenses: https://knowledgecenter.docuware.com/docs/docuware-license-model.md

- DocuWare 7.15: https://knowledgecenter.docuware.com/docs/news-docuware-version-715.md

- 7.15 Release Notes: https://knowledgecenter.docuware.com/docs/news-715-technical-release-notes.md

### Licensing sources

- https://knowledgecenter.docuware.com/docs/docuware-license-model.md

### Infrastructure sources

- https://support.docuware.com/en-us/knowledgebase/article/KBA-37193


### 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 Identity Service supports OIDC sign-on with external identity providers for locally installed DocuWare systems. Configure provider integration and review enforcement, local exceptions and edition/version requirements. Scope: DocuWare on-premises Identity Service; hosted Cloud is a separate deployment. Source: https://knowledgecenter.docuware.com/docs/integration-embedding-in-itinfrastructure (reviewed 2026-11-20). Supporting source: Entra ID setup applies to on-premises organizations — https://support.docuware.com/en-US/knowledgebase/article/KBA-36308.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The documented installation uses a vendor-supplied software ZIP and licence file, with frontend, backend and full-text roles. The package is supplied to the customer; the public guide is not a public Terraform or CloudFormation artifact. Scope: Vendor 7.12 installation/package delivery; verify version-specific installation guide. Source: https://knowledgecenter.docuware.com/docs/install-docuware-on-premises-version-712 (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. The 7.14 matrix lists DocuWare Services at 4 CPU cores/8 GB RAM/64 GB disk minimum, with 8 cores/16 GB recommended. Database resources, full-text service, document storage and HA are additional; recheck the matrix for a different version. Scope: DocuWare 7.14 service minimum; not a complete production or HA footprint. Source: https://knowledgecenter.docuware.com/docs/docuware-version-714-on-premises-system-requirements (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## dotCMS Cloud Anywhere

Vendor-operated content platform deployed into a customer cloud account.

- Listing: https://launchinyourcloud.com/directory/dotcms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.
- Licensing model: commercial-only
- Installation: Cloud Anywhere onboarding and vendor management through customer-cloud access roles
- Architecture: dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles.
- Operations: Vendor operates the Cloud Anywhere application through its management plane and scoped customer-cloud access; agree support access, logs, egress and exit procedures.
- Product website: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide
- 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 operates the installation through its control plane and AWS role or GCP service account. Public core code and Cloud Anywhere service licensing are different; this is not a fully customer-operated instance.

Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.

dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Vendor-operated content platform deployed into a customer cloud account.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (checked 2026-11-19). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (checked 2026-11-19). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (checked 2026-11-19). 

Operating responsibility: dotCMS provisions and operates Cloud Anywhere through its automation and delegated access to a dedicated customer account, subscription or project. The separately customer-operated self-hosted edition is outside this listing. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (checked 2026-11-20).


### Cloud deployment evidence

- Cloud Anywhere Quickstart (aws, azure, gcp): https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide
  dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles. The vendor operates the installation through its control plane and AWS role or GCP service account. Public core code and Cloud Anywhere service licensing are different; this is not a fully customer-operated instance.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Cloud Anywhere Quickstart: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide

- Azure Setup Guide: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-azure-setup-guide

- BSL-1.1 LICENSE: https://github.com/dotCMS/core/blob/master/LICENSE

- Releases v26.11.18: https://github.com/dotCMS/core/releases

### Licensing sources

- https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide

- https://github.com/dotCMS/core/blob/master/LICENSE

### Infrastructure sources

- https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The current dotAuth guide documents system/site SSO settings for OAuth2/OIDC and SAML, including separate redirects for site and administrator login. Validate the selected service plan, release and identity mapping; site inheritance is not the same as configuring every redirect at the IdP. Scope: Current dotCMS application authentication; Cloud Anywhere service entitlement/version must be confirmed. Source: https://dev.dotcms.com/docs/manage/access-and-security/dotauth/dotauth-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. Official container guidance provides Docker and multi-service Compose examples with persistent data volumes. The developer all-in-one image is for local evaluation; it is not the Cloud Anywhere managed-service architecture or a production HA baseline. Scope: Upstream application container examples; selected managed deployment follows its separate contract. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/docker/getting-started-with-dotcms-in-docker-containers (reviewed 2026-11-20). Deployment artifact: https://dev.dotcms.com/docs/manage/installation-and-deployment/docker/getting-started-with-dotcms-in-docker-containers. Artifact reference: Current reference examples; pin a supported application and backing-service release.

- Minimum footprint / sizing: Documented. The standard-stack requirements specify a multicore processor, dedicated 8+ GB RAM and 100 GB disk, with PostgreSQL and OpenSearch dependencies. These application-stack requirements do not size a contracted Cloud Anywhere topology or validate 100-user/1-TB HA capacity. Scope: Upstream standard-stack baseline; managed-service deployment sizing is separate. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/installation/requirements (reviewed 2026-11-20).

- License pricing: Sources checked — unresolved. The public core-code licence does not establish the Cloud Anywhere managed-service price, order or operating/support entitlements. Obtain the agreement for the customer-cloud service. Scope: Selected self-managed application or customer-cloud service; contract confirmation required. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Dremio Self-Managed

Self-managed distributed SQL and lakehouse analytics platform for customer-controlled data sources.

- Listing: https://launchinyourcloud.com/directory/dremio-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for Dremio Community; Dremio Enterprise uses separate commercial terms.
- Licensing model: open-source
- Installation: Community on Docker or Kubernetes; Enterprise on Kubernetes using vendor-tested EKS, AKS or GKE environments.
- Architecture: Customer-operated coordinator and executor services with metadata and distributed storage
- Operations: Customer manages Kubernetes or container capacity, storage, security, scaling, upgrades, backups and integration with data sources.
- Product website: https://www.dremio.com/
- Source review: 2026-11-17; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Dremio Community and self-managed Enterprise, not Dremio Cloud. Community and Enterprise feature, support and billing differences must be reviewed separately. Query engines require network and credential access to configured data sources. Dremio Enterprise 26.1.13 removes compromised eMudhra certificate roots, updates Brotli for CVE-2026-111497, fixes incorrect or missing query results, and addresses rare file deletion after a network partition. Certificates chaining only to the removed roots will fail after upgrading. These fixes are specific to the Enterprise release.

Dremio Community is Apache-2.0 licensed; self-managed Dremio Enterprise is commercially licensed. This classification covers the platform family and requires edition-specific feature review.

The self-managed platform runs distributed coordinator and executor services in containers or Kubernetes, with persistent metadata and distributed storage. It is a server/container workload even when managed cloud storage is used. Dremio Enterprise 26.1.13 adds configurable startup and liveness probes for Kubernetes executors.


### Category fit

- data-analytics: Provides distributed SQL queries, semantic modeling and lakehouse analytics over customer-controlled data sources.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.dremio.com/editions/ (checked 2026-11-13). Source: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/ (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.dremio.com/editions/ (checked 2026-11-13). Source: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/ (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.dremio.com/editions/ (checked 2026-11-13). Source: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/ (checked 2026-11-13). 


### Cloud deployment evidence

- Dremio self-managed editions on AWS, Azure and Google Cloud (aws, azure, gcp): https://docs.dremio.com/editions/
  Dremio identifies Community and Enterprise as self-managed on AWS, Azure and Google Cloud. Community supports Docker or Kubernetes; Enterprise self-managed uses Kubernetes. This is distinct from the fully managed Dremio Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Dremio-tested EKS, AKS and GKE environments (aws, azure, gcp): https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/
  Dremio documents active testing against Amazon EKS, Azure AKS and Google GKE and provides provider recommendations. Customers operate the selected cluster and configure storage, identity and network access.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- Dremio edition and deployment comparison: https://docs.dremio.com/editions/

- Vendor-tested Kubernetes environments: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/

- Dremio OSS Apache 2.0 license: https://github.com/dremio/dremio-oss/blob/master/LICENSE

- Dremio Enterprise 26.1.13 security and reliability fixes: https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise

### Licensing sources

- https://github.com/dremio/dremio-oss/blob/master/LICENSE

- https://docs.dremio.com/editions/

### Infrastructure sources

- https://docs.dremio.com/current/deploy-dremio/

- https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/

- https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise


### 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 current 26.x self-managed documentation marks OpenID Connect SSO as Enterprise. OIDC handles authentication; user and group memberships are provisioned separately through SCIM. Scope: Dremio self-managed Enterprise 26.x; not Community or Dremio Cloud. Source: https://docs.dremio.com/current/security/authentication/identity-providers/oidc/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Enterprise documents SCIM 2.0 user/group provisioning with header authentication. Identity-provider configuration and the customer-accessible SCIM endpoint are required. Scope: Dremio self-managed Enterprise 26.x. Source: https://docs.dremio.com/current/security/authentication/identity-providers/scim/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Current Dremio 26+ Kubernetes deployment uses the v3 OCI Helm chart at Quay; the older v2 chart is incompatible. Enterprise requires authorized registry access and a valid licence key. Configure chart values, object storage, cluster services and version compatibility before deployment. Scope: Official Dremio 26+ self-managed OCI Helm distribution. Source: https://docs.dremio.com/current/deploy-dremio/deploy-on-kubernetes/ (reviewed 2026-11-20). Deployment artifact: https://docs.dremio.com/current/deploy-dremio/deploy-on-kubernetes/. Artifact reference: oci://quay.io/dremio/dremio-helm; pin the selected v3 chart release.

- Minimum footprint / sizing: Documented. The current Kubernetes guide gives an 8-CPU/16-GB smallest production coordinator and executors with at least 64 GB memory. It recommends larger 32-CPU/64-GB coordinators and 128-GB executors. Catalog, search, messaging, storage and HA add substantial resources; these are component minima, not a complete cluster. Scope: Current self-managed Kubernetes component floors; topology and query workload additional. Source: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/ (reviewed 2026-11-20).

- License pricing: Documented. The vendor pricing page identifies Dremio Enterprise as self-hosted commercial software with pricing available from sales. Its displayed per-DCU Cloud price applies to the managed service, not this Enterprise licence. Agree capacity, term and support separately from the infrastructure bill. Scope: Self-managed Enterprise quote; managed Cloud rates excluded. Source: https://www.dremio.com/pricing/ (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.

- Dremio Enterprise trust-store and Brotli update (security-advisory): Enterprise 26.1.13 removes compromised CA trust roots and patches the Brotli dependency in its Open Catalog service. Scope: Dremio Enterprise 26.1.13; this release does not establish the same fixes for Community Edition. Conditions: Services whose certificates chain only to the removed roots will fail validation. Brotli applicability depends on the affected component. Action: Review certificates and the linked bulletins, then apply the appropriate Enterprise patch and test connectivity. Source: https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise; reviewed 2026-11-17.




## EarthSoft EQuIS Enterprise — Self-Hosted

Self-hosted environmental data management with compliance monitoring, data validation, workflow automation and reporting.

- Listing: https://launchinyourcloud.com/directory/earthsoft-equis/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary EarthSoft server and Active Client Access licenses; external viewer/service-provider terms differ
- Licensing model: commercial-only
- Installation: Licensed Enterprise installation on Windows Server/IIS and SQL Server, or the documented Azure Web App deployment
- Architecture: Persistent ASP.NET web application and workflow services backed by Microsoft SQL Server or Azure SQL Database
- Operations: Customer operates application hosting, database, network access, backups, user roles, licenses and upgrades. Obtain the installers and supported build details from EarthSoft.
- Product website: https://earthsoft.com/products/equis-hosting-options/
- 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 covers self-hosted Enterprise rather than EarthSoft-operated EQuIS Online. The official Azure installation guide deploys into client-managed Azure Web Apps and configures the database and licenses. Internal users and externally exposed viewers have different licensing arrangements. Review integrations and choose a supported build before installation.

The documented Enterprise server and named-user licenses are commercial. EarthSoft’s published example EULA identifies EQuIS as proprietary software; confirm the actual contract and external-user entitlements.

Windows/IIS or continuously running Azure Web App services with persistent database storage. The Azure guide enables Always On; this is a server-based application deployment.


### Category fit

- energy-environmental-compliance: Environmental data collection, validation, compliance monitoring and reporting for air, water, soil, waste and related project data.

- data-analytics: Environmental data quality checks, reporting, visualizations and configurable dashboards; its scope is environmental and geotechnical data rather than general-purpose BI.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.earthsoft.com/ent-new_installation_azure.htm (checked 2026-11-12). 


### Cloud deployment evidence

- EQuIS Enterprise application installation on Azure (azure): https://help.earthsoft.com/ent-new_installation_azure.htm
  EarthSoft documents creation and configuration of an Azure Web App and deployment of the licensed EQuIS Enterprise application package, rather than only an Azure SQL database. This is the customer-hosted Enterprise path; obtain the compatible package and required licenses from EarthSoft.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Enterprise installation prerequisites and installer: https://help.earthsoft.com/ent-new_installation.htm

- Client Azure Web App installation: https://help.earthsoft.com/ent-new_installation_azure.htm

- On-premises and hosted deployment options: https://earthsoft.com/products/equis-hosting-options/

- Environmental data and reporting scope: https://help.earthsoft.com/equis-introduction.htm

- Current runtime and database requirements: https://help.earthsoft.com/equis7-hardware-system.htm

- Server and named-user license model: https://help.earthsoft.com/ent-equis-licenses.htm

- Published example proprietary EULA: https://help.earthsoft.com/EQuIS%20EULA%20Example.pdf

### Licensing sources

- https://help.earthsoft.com/ent-equis-licenses.htm

- https://help.earthsoft.com/EQuIS%20EULA%20Example.pdf

### Infrastructure sources

- https://help.earthsoft.com/ent-new_installation.htm

- https://help.earthsoft.com/ent-new_installation_azure.htm

- https://help.earthsoft.com/equis7-hardware-system.htm


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. EQuIS Enterprise documents browser OIDC login with a registered identity-provider application and redirect, plus an existing Enterprise account with matching identity and roles. Federation does not automatically grant repository access. This does not imply that separate Professional Browser Mode has the same authentication capabilities. Scope: EQuIS Enterprise OIDC user login; separate product surfaces retain their limits. Source: https://help.earthsoft.com/adm-openid-connect-auth.htm (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 Enterprise 7 installation guide covers a Windows/IIS installation with an EQuIS SQL Server database, service account and network licenses. Use the licensed installer and the linked prerequisites; this is not a public Terraform or container artifact. Scope: EQuIS Enterprise 7 new installation; installer entitlement and current requirements must be checked. Source: https://help.earthsoft.com/ent-new_installation.htm (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The current hardware/system page lists supported Windows, SQL/database and runtime dependencies, but does not establish numeric Enterprise application/database CPU/RAM/storage sizing. Size ingestion, reporting, spatial widgets and HA beyond operating-system minimums. Scope: EQuIS Enterprise production hardware capacity remains unconfirmed. Source: https://help.earthsoft.com/equis7-hardware-system.htm (reviewed 2026-11-21).

- License pricing: Documented. Enterprise uses Server plus Active Client Access Licences, available as perpetual or term licences for internal users. External access has separate Viewer or service-provider agreements, and Enterprise 7 requires network rather than local keys for the described self-hosted licensing. Confirm the order and authorised server/user counts. Scope: EQuIS Enterprise 7 ACAL/server licensing; external-user and service-provider rights separate. Source: https://help.earthsoft.com/ent-equis-licenses.htm (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Elastic Cloud Enterprise

Commercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.

- Listing: https://launchinyourcloud.com/directory/elastic-cloud-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Elastic Cloud Enterprise license required after the trial.
- Licensing model: commercial-only
- Installation: Official ECE installation script on prepared AWS, Azure or Google Cloud Linux hosts
- Architecture: Multi-host orchestration layer with coordinators, proxies, allocators and managed Elasticsearch and Kibana deployments
- Operations: Customer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.
- Product website: https://www.elastic.co/cloud/cloud-enterprise
- Source review: 2026-11-19; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers Elastic Cloud Enterprise, not Elastic Cloud Hosted or Elastic Cloud Serverless. ECE requires supported Linux and container-engine combinations, dedicated storage planning and coordinated host maintenance; automatic cloud VM patching can disrupt the platform. Elastic Cloud Enterprise 3.8.6 and 4.2.1 fix seven platform-role, retained credential and CA key, cross-deployment symlink, role-token, and platform-setting issues. Certificate-rotation users must complete the documented cleanup after upgrade, and operators should review or revoke persistent role tokens. Elastic's CVE-2026-114938 advisory states Elasticsearch 7.17.3 and later can be affected on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Planned ECE 4.2.2 and 3.8.7 were not yet released at review time; until fixed images are available, apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's rollout guidance.

ECE starts with a 30-day trial and then requires a valid Elastic Cloud Enterprise orchestration license.

ECE uses multiple persistent Linux hosts for orchestration, proxies and workload allocators and then runs Elastic Stack clusters on those hosts.


### Category fit

- data-analytics: Orchestrates self-managed Elasticsearch and Kibana deployments for search, analytical and data-exploration workloads.

- databases-vector: Operates Elasticsearch clusters that provide document, full-text and vector search in customer infrastructure.

- observability: Operates Elastic Stack deployments used to ingest, search and analyze logs, metrics, traces and security telemetry.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (checked 2026-11-15). 


### Cloud deployment evidence

- Elastic Cloud Enterprise on public cloud hosts (aws, azure, gcp): https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install
  Elastic's current ECE installation guide explicitly supports public-cloud hosts on AWS, Google Cloud and Microsoft Azure and installs ECE on customer-prepared virtual machines.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Install Elastic Cloud Enterprise: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install

- Elastic Cloud Enterprise overview: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise

- Manage an Elastic Cloud Enterprise license: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece

- Elastic Cloud Enterprise release notes: https://www.elastic.co/docs/release-notes/cloud-enterprise

- Elastic Cloud Enterprise 4.2.1 security update ESA-2026-216: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263

- Elastic Java4Shell advisory for ECE: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703

### Licensing sources

- https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece

### Infrastructure sources

- https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install


### 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. ECE supports SAML 2.0 Web Browser SSO for the orchestrator/Cloud UI, with attribute and role mappings. It does not apply to ordinary API clients or automatically configure every hosted Elasticsearch/Kibana deployment; those access policies are separate. Scope: Self-managed ECE orchestrator browser federation. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cloud-enterprise-orchestrator/saml (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization. Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens. Current review: CVE-2026-114938 can affect Elasticsearch 7.17.3 and later on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Elastic planned ECE 4.2.2 and 3.8.7 but had not released them when reviewed. Use -XX:-UseBASE64Intrinsics, restart every deployment and follow the vendor advisory until fixed ECE images are available. Scope: ECE-hosted Elasticsearch deployments on affected x86-64 AVX512_VBMI hardware; planned ECE versions are not recorded as released. Source: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263. Supporting source: ESA-2026-211 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260. Supporting source: ESA-2026-212 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-212/391261. Supporting source: ESA-2026-215 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-215/391262. Supporting source: ESA-2026-218 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-218/391264. Supporting source: ESA-2026-221 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-221/391265. Supporting source: ESA-2026-222 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. ECE installation prepares supported Linux hosts, Docker or Podman, XFS quotas and mount points before installing the orchestrator. Follow the supported OS/container-engine matrix and deployment-specific prerequisites; generic cloud VMs alone are insufficient. Scope: Elastic Cloud Enterprise installation guide; orchestrator hosts, not Elastic Cloud Hosted. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. ECE lists an 8-GB installation floor per host role, but recommends 128–256 GB for allocator hosts and distinct control/proxy sizing. HA needs at least three hosts across three availability zones. Fast SSDs, deployment memory/storage ratios and cluster workloads materially affect the footprint; the installer floor is not production capacity. Scope: ECE host-role requirements; hosted deployment capacity and HA additional. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/ece-hardware-prereq (reviewed 2026-11-20).

- License pricing: Documented. ECE requires an Elastic-issued licence; installation activates a 30-day trial. A full ECE licence enables managed deployments at the stated Enterprise subscription feature/support level for their stack version. The page does not quote a price; obtain ECE terms separately from hosted Elastic Cloud rates and infrastructure. Scope: Commercial ECE platform/deployment licensing; numeric price requires a quote. Source: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Elastic Cloud Enterprise 4.2.1 was released October 20, 2026; 3.8.6 is the parallel fixed release for that maintained line. The updates address multiple platform-role, credential, certificate, token, and cross-deployment issues. Scope: Elastic Cloud Enterprise 3.8 and 4.2 maintained lines. Source: https://www.elastic.co/docs/release-notes/cloud-enterprise (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Elastic Cloud Enterprise 3.8.6 and 4.2.1 security update (security-advisory): ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization. Scope: Most issues affect releases through 3.8.5 and 4.2.0. ESA-2026-222 affects 4.1.0 through 4.2.0 when Enterprise Search is present. Fixed releases are 3.8.6 and 4.2.1. Conditions: Several issues require particular platform roles, certificate rotation, persistent tokens, symlink paths, or Enterprise Search. Multiple advisories have no workaround. Action: Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens. Source: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263; reviewed 2026-11-18. Supporting source: ESA-2026-211 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260. Supporting source: ESA-2026-212 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-212/391261. Supporting source: ESA-2026-215 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-215/391262. Supporting source: ESA-2026-218 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-218/391264. Supporting source: ESA-2026-221 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-221/391265. Supporting source: ESA-2026-222 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266.

- Elastic Cloud Enterprise CVE-2026-114938 guidance (security-advisory): Elastic says affected Elasticsearch on x86-64 AVX512_VBMI CPUs can permit authenticated RCE and unauthenticated denial of service. Scope: ECE-hosted Elasticsearch 7.17.3 and later on affected hardware; planned ECE 4.2.2 and 3.8.7 were not yet released when reviewed. Conditions: CPU features, JDK and deployed Elasticsearch version determine exposure. Action: Apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's advisory until fixed ECE images are released and deployed. Source: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703; reviewed 2026-11-19.




## Elastic Cloud on Kubernetes

Elastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.

- Listing: https://launchinyourcloud.com/directory/elastic-cloud-on-kubernetes/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support.
- Licensing model: source-available
- Installation: Official ECK Helm chart or Kubernetes manifests on EKS, AKS or GKE
- Architecture: Customer-operated Kubernetes operator and Elastic Stack stateful workloads with persistent storage.
- Operations: Customer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.
- Product website: https://www.elastic.co/elastic-cloud-kubernetes
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers self-managed Elastic Cloud on Kubernetes, not Elastic Cloud Hosted or Elastic Cloud Enterprise. ECK automates application lifecycle but does not transfer cluster, storage, backup or upgrade responsibility to Elastic. The free Basic license and paid Enterprise feature set differ; optional Cloud Connect services create separate external dependencies. ECK 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. CVE-2026-72648 has no workaround; after upgrading, rotate the affected service token as Elastic directs.

The ECK and Elastic Stack distribution is governed by Elastic License 2.0 rather than an OSI-approved open-source license. A free Basic tier is available; Enterprise features and support require a subscription.

ECK manages persistent Elasticsearch and related container workloads on customer Kubernetes with durable volumes and operator reconciliation.


### Category fit

- databases-vector: Elasticsearch provides distributed document storage, full-text search and vector search in a customer cluster.

- observability: Elastic Stack collects and analyzes logs, metrics and traces; exact integrations and features depend on the selected license.

- data-analytics: Search, aggregations and Kibana visualizations support interactive analysis of indexed data.

- ai-tools: Vector search and licensed machine-learning capabilities support retrieval and AI-oriented workloads.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 


### Cloud deployment evidence

- Elastic Cloud on Kubernetes on EKS, AKS and GKE (aws, azure, gcp): https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s
  Elastic documents ECK for managed Kubernetes services including Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. The customer owns and operates the cluster and persistent storage.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Deploy Elastic Cloud on Kubernetes: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s

- Install ECK with Helm or manifests: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install

- Manage the ECK license: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck

- Self-managed Elastic pricing and editions: https://www.elastic.co/pricing/self-managed

- ECK 3.5.0 security update ESA-2026-113: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493

- ECK 3.5.0 security update ESA-2026-145: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105

- ECK 3.5.0 security update ESA-2026-146: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106

### Licensing sources

- https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck

- https://www.elastic.co/pricing/self-managed

### Infrastructure sources

- https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s

- https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install


### 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: Edition-dependent. Elastic documents an ECK BYOL offering inside Google Distributed Cloud air-gapped Marketplace. This is a specific isolated GDC deployment route, not proof that an Elastic Cloud Hosted marketplace subscription delivers ECK in a customer AWS account. Scope: ECK in GDC air-gapped Marketplace; separate from hosted Elastic procurement. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. A GDC air-gapped BYOL Marketplace route does not establish AWS Marketplace commitment treatment for a self-managed ECK Enterprise subscription. Scope: Reviewed public evidence for Elastic Cloud on Kubernetes; unresolved within this edition/deployment. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. ECK deployments can configure Elasticsearch/Kibana external SAML or OIDC realms, with the applicable self-managed subscription. Elastic Cloud organization SSO is a separate control plane. Scope: ECK application authentication; subscription eligibility must be checked. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17). Supporting source: Self-managed subscription feature matrix — https://www.elastic.co/pricing/self-managed.

- SCIM provisioning: Sources checked — unresolved. ECK documents external realms and native/file user management, but a native ECK application SCIM provisioning endpoint was not established. Ingesting another product’s SCIM audit logs is not SCIM support. Scope: Reviewed public evidence for Elastic Cloud on Kubernetes; unresolved within this edition/deployment. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Elastic Cloud on Kubernetes 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://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17).

- Security controls: Documented. ECK manages credentials in Kubernetes secrets and supports rotation and disabling the default elastic superuser when using external identity. Restrict secret/RBAC access and configure application roles. Current advisory review: ESA-2026-113, 145, and 146 fix service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Upgrade to ECK 3.5.0 or later and rotate the service token where directed. Scope: ECK managed credentials and external realms Affected ECK releases before 3.5.0; exact component and configuration ranges follow the three advisories.. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck. Supporting source: ESA-2026-145 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105. Supporting source: ESA-2026-146 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106.

- Air-gapped operation: Documented. ECK documents offline operation with locally mirrored operator and Elastic Stack images. Integrations also need local package, artifact and endpoint repositories; mirroring the operator alone is insufficient. Scope: ECK isolated deployment with all selected dependencies staged. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/air-gapped-install (reviewed 2026-11-17). Supporting source: Additional offline dependency repositories — https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch.

- Deployment artifact / IaC: Documented. Elastic supplies ECK installation through Helm or Kubernetes manifests. Pin the operator and compatible Elastic application versions and configure persistent storage and RBAC; the operator is not a vendor-operated service. Scope: Self-managed ECK operator installation. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. HA guidance calls for three master-eligible nodes, multiple nodes per data tier and at least one index replica. CPU, memory, shard layout and disk headroom depend on indexing/search workload; no universal 100-user minimum is established. Scope: ECK availability topology, not benchmarked resource sizing. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration (reviewed 2026-11-17).

- License pricing: Documented. The ECK and Elastic Stack distribution is governed by Elastic License 2.0 rather than an OSI-approved open-source license. A free Basic tier is available; Enterprise features and support require a subscription. Scope: Elastic Cloud on Kubernetes: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 1,428.76/month. Three 8-vCPU/64-GiB workers across three AZs host three master/data nodes and two Kibana replicas. The storage assumption is 1,000 GB primary indexed data plus one replica, with 3,000 GB total data capacity and 150 GB boot capacity. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Editorial ECK scenario; load/ingest rate and indexed-data expansion must be measured. Separate shard/zone placement and failure testing are required. No Savings Plans, Spot or credits.. 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-17). Supporting source: Product topology/sizing basis — https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration. Supporting source: Current AWS documentation: 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: EKS standard versus extended support pricing — https://aws.amazon.com/eks/pricing/.

- Release snapshot / cadence: Documented. Elastic Cloud on Kubernetes 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Rotate the service token after upgrade where ESA-2026-113 requires it. Scope: ECK operator 3.5.0 security update. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Elastic Cloud on Kubernetes 3.5.0 security update (security-advisory): ESA-2026-113, 145, and 146 fix service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Scope: Affected ECK releases before 3.5.0; exact component and configuration ranges follow the three advisories. Conditions: Namespace boundaries, service tokens, and managed resource lifecycle determine exposure. CVE-2026-72648 has no workaround. Action: Upgrade to ECK 3.5.0 or later and rotate the service token where directed. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493; reviewed 2026-11-18. Supporting source: ESA-2026-145 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105. Supporting source: ESA-2026-146 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106.




## Ente Photos

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

- Listing: https://launchinyourcloud.com/directory/ente-photos/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Application platform deployment; Docker / Compose
- Architecture: Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://ente.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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


### Cloud deployment evidence

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

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

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


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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

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


### Buyer diligence


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

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


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

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

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## eramba (Enterprise Self-Hosted)

Source-available commercial GRC software with supplier-assessment and policy workflows.

- Listing: https://launchinyourcloud.com/directory/eramba-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial source-available Enterprise terms; source access does not permit unrestricted modification or redistribution.
- Licensing model: source-available
- Installation: Docker / Compose
- Architecture: Eramba's persistent Docker stack on customer AWS or Azure 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://www.eramba.org/learning/courses/12/episodes/274
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor explicitly says Community and Enterprise code are not open source and restrict modification and redistribution. This entry selects licensed Enterprise Online Assessments; questionnaires and linked third-party evidence require configuration.

Commercial source-available Enterprise terms; source access does not permit unrestricted modification or redistribution.

Eramba's persistent Docker stack on customer AWS or Azure infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- vendor-supplier-document-management: Source-available commercial GRC software with supplier-assessment and policy workflows.

- policy-procedure-management: Source-available commercial GRC software with supplier-assessment and policy workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.eramba.org/learning/courses/12/episodes/274 (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.eramba.org/learning/courses/12/episodes/274 (checked 2026-11-19). 


### Cloud deployment evidence

- Docker Install Guide (aws, azure): https://www.eramba.org/learning/courses/12/episodes/274
  Eramba's persistent Docker stack on customer AWS or Azure infrastructure. The vendor explicitly says Community and Enterprise code are not open source and restrict modification and redistribution. This entry selects licensed Enterprise Online Assessments; questionnaires and linked third-party evidence require configuration.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Docker Install Guide: https://www.eramba.org/learning/courses/12/episodes/274

- Vendor Assessments: https://www.eramba.org/learning/courses/81

- License FAQs: https://www.eramba.org/faqs

- Release History: https://www.eramba.org/releases

### Licensing sources

- https://www.eramba.org/faqs

### Infrastructure sources

- https://www.eramba.org/learning/courses/12/episodes/274


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted user-administration guide documents SAML and Google OAuth alongside LDAP, with one remote connector active at a time and separately enabled portal access. Local recovery accounts may remain. Configure/test the connector and selected edition rather than treating LDAP password validation alone as federation. Scope: eramba on-premises documented user identity connectors and portal configuration. Source: https://www.eramba.org/learning/courses/78 (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 Docker installation course explicitly covers Community and Enterprise on premises, deployment configuration, Enterprise activation, updates and backups. Use its supported Compose repository and compatible images, protect secrets and validate storage/permissions; SaaS deployment is a separate offering. Scope: eramba Enterprise on-premises Docker installation and lifecycle guide. Source: https://www.eramba.org/learning/courses/12/episodes/274 (reviewed 2026-11-21). Deployment artifact: https://www.eramba.org/learning/courses/12/episodes/274. Artifact reference: Current vendor Docker installation course.

- Minimum footprint / sizing: Documented. The Docker guide lists minimum 1 vCPU, 4 GB RAM plus 10 GB swap and at least 3 GB data storage; recommended compute is 2 vCPU/8 GB RAM. Provide extra database/attachments, background/PDF work and backups. These host baselines are not a benchmark or complete HA deployment. Scope: eramba Docker host minimum/recommended resources; complete workload capacity separate. Source: https://www.eramba.org/learning/courses/12/episodes/274 (reviewed 2026-11-21).

- License pricing: Documented. Commercial source-available Enterprise terms; source access does not permit unrestricted modification or redistribution. Scope: eramba (Enterprise Self-Hosted); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.eramba.org/faqs (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Esri ArcGIS Enterprise (BYOL)

Commercial customer-operated geospatial application and analytics platform.

- Listing: https://launchinyourcloud.com/directory/esri-arcgis-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: ArcGIS Enterprise Cloud Builder application deployments and licensed server components on AWS or Azure VMs.
- 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.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloud Builder uses the customer's account/subscription and software licences. Geospatial analysis and environmental mapping do not establish a packaged environmental permits, filings or compliance-record workflow.

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

ArcGIS Enterprise Cloud Builder application deployments and licensed server components on AWS or Azure VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Commercial customer-operated geospatial application and analytics platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/azure/overview-arcgis-server-on-microsoft-azure.html (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Cloud Builder (aws): https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html
  ArcGIS Enterprise Cloud Builder application deployments and licensed server components on AWS or Azure VMs. Cloud Builder uses the customer's account/subscription and software licences. Geospatial analysis and environmental mapping do not establish a packaged environmental permits, filings or compliance-record workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Cloud Builder (azure): https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/azure/overview-arcgis-server-on-microsoft-azure.html
  ArcGIS Enterprise Cloud Builder application deployments and licensed server components on AWS or Azure VMs. Cloud Builder uses the customer's account/subscription and software licences. Geospatial analysis and environmental mapping do not establish a packaged environmental permits, filings or compliance-record workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Cloud Builder: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html

- Azure Cloud Builder: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/azure/overview-arcgis-server-on-microsoft-azure.html

- Esri Master Agreement: https://www.esri.com/en-us/legal/terms/full-master-agreement

- Product Lifecycle: https://support.esri.com/en-us/products/arcgis-enterprise/life-cycle

### Licensing sources

- https://www.esri.com/en-us/legal/terms/full-master-agreement

### Infrastructure sources

- https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html

- https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/azure/overview-arcgis-server-on-microsoft-azure.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Esri documents portal identities backed by organisational stores including SAML providers, with role/group permissions and federated ArcGIS Server access. Configure the actual portal/IdP and supported release. Cloud-provider IAM and ArcGIS Online accounts are distinct from the self-managed portal identity design. Scope: ArcGIS Enterprise 12.0 self-managed portal identity model. Source: https://enterprise.arcgis.com/en/get-started/12.0/windows/the-arcgis-enterprise-security-model.htm (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. Esri Cloud Builder for AWS provisions a selected ArcGIS Enterprise deployment using customer licences and cloud configuration. Select compatible cloud-tool/product versions, certificates, networking and storage; supported base deployment, specialised roles and HA require separate design. Scope: Esri AWS Cloud Builder application/infrastructure delivery; licensed components and topology selection. Source: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html (reviewed 2026-11-21). Deployment artifact: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html. Artifact reference: Current Esri AWS Cloud Builder guide reviewed on this date.

- Minimum footprint / sizing: Sources checked — unresolved. The accessible Cloud Builder guidance establishes deployment tooling but not complete workload-sized CPU/RAM/storage for Portal, Server and Data Store roles. Legacy requirement URLs redirect to moved documentation; obtain the selected release component requirements and GIS workload/HA plan rather than applying an old all-in-one development example. Scope: ArcGIS Enterprise complete current production sizing remains unconfirmed. Source: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Esri ArcGIS Enterprise (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.esri.com/en-us/legal/terms/full-master-agreement (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Estuary BYOC

Managed data capture, transformation, and delivery with a dedicated data plane in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/estuary-byoc/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial BYOC under an annual Enterprise agreement with custom pricing.
- Licensing model: commercial-only
- Installation: Arrange Enterprise BYOC onboarding and grant the documented permissions in a separate AWS account, Azure subscription, or Google Cloud project.
- Architecture: Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.
- Operations: Estuary provisions and manages data-plane resources, including patching, scaling, and deletion. The customer owns the cloud environment and manages its surrounding firewall, routing, and policies.
- Product website: https://estuary.dev/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-21; infrastructure review: 2026-11-21

### Scope and qualifications

The data plane accepts connections from Estuary's control plane and authorized users. Pipeline specifications can be pulled with flowctl. Confirm storage export and account teardown with Estuary.

Commercial BYOC under an annual Enterprise agreement with custom pricing.

Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.


### Category fit

- data-analytics: Captures, transforms, and delivers data to analytical destinations through managed connectors.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/ (checked 2026-11-21). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/ (checked 2026-11-21). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/ (checked 2026-11-21). 

Operating responsibility: Estuary provisions, patches, scales and removes the customer-account data plane. Its vendor-operated control plane starts connectors and applies task configuration; the customer governs the surrounding cloud account, permissions and network policies. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/ (checked 2026-11-21). Supporting source: Control-plane and management connectivity — https://docs.estuary.dev/private-byoc/networking/.


### Cloud deployment evidence

- Estuary BYOC on AWS (aws): https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/
  The documented cross-account IAM role uses an external ID and grants AmazonEC2FullAccess.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Estuary BYOC on Azure (azure): https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/
  The guide adds Estuary's deployment application and grants a role scoped to the customer's subscription.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Estuary BYOC on Google Cloud (gcp): https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/
  The guide asks for project-level Editor access for Estuary's controller principal.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- BYOC operating model: https://docs.estuary.dev/private-byoc/byoc-deployments/

- Data-plane network requirements: https://docs.estuary.dev/private-byoc/networking/

- Enterprise BYOC pricing: https://docs.estuary.dev/getting-started/pricing/

- Pull published specifications: https://docs.estuary.dev/guides/flowctl/edit-specification-locally/

- Estuary BYOC on AWS: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/

- Estuary BYOC on Azure: https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/

- Estuary BYOC on Google Cloud: https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/

### Licensing sources

- https://docs.estuary.dev/getting-started/pricing/

### Infrastructure sources

- https://docs.estuary.dev/private-byoc/networking/


### 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: Documented. Enterprise plans, including BYOC, include SSO. Estuary documents support-assisted SAML 2.0 configuration for its hosted dashboard, with domain metadata and just-in-time account creation. This is control-plane user identity, separate from connector credentials and data-plane authentication. Scope: Enterprise BYOC dashboard SSO; coordinate domain and IdP configuration with Estuary.. Source: https://docs.estuary.dev/getting-started/sso-setup/ (reviewed 2026-11-21). Supporting source: Enterprise BYOC and SSO entitlement — https://docs.estuary.dev/getting-started/pricing/.

- SCIM provisioning: Explicitly unsupported. Estuary explicitly documents just-in-time SSO account creation rather than SCIM. Tenant administrators invite users and assign access after the SSO account is created. SAML support does not establish SCIM lifecycle provisioning. Scope: Documented Estuary dashboard provisioning flow for Enterprise BYOC.. Source: https://docs.estuary.dev/getting-started/sso-setup/ (reviewed 2026-11-21).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The provider guides document permissions and vendor-assisted provisioning. The AWS example creates a delegated IAM role with an external ID and AmazonEC2FullAccess; it does not expose a reviewed, versioned data-plane deployment template. Obtain the actual provisioning artifact, permission scope and rollback procedure from Estuary. An IAM policy example alone does not establish a reusable runtime installer. Scope: Estuary-managed BYOC runtime deployment artifact unresolved.. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/ (reviewed 2026-11-21). Supporting source: Azure onboarding permissions — https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/. Supporting source: Google Cloud onboarding permissions — https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/.

- Minimum footprint / sizing: Sources checked — unresolved. The networking guide identifies broker/reactor instances, coordination and management access, but does not publish a quantitative CPU/RAM/storage baseline or HA topology. Estuary sizes the managed data plane during onboarding. Obtain connector counts, data rates, retention, replay and recovery requirements before selecting resources; 100 users and 1 TB alone do not size a streaming pipeline. Scope: Dedicated Enterprise BYOC data plane; quantitative production sizing unresolved.. Source: https://docs.estuary.dev/private-byoc/networking/ (reviewed 2026-11-21).

- License pricing: Documented. BYOC is available on annual or multi-year Enterprise contracts with custom pricing based on data volume, connector instances, deployment model, term and support. The customer pays the cloud provider directly for infrastructure. Public Cloud-plan per-GB/task-hour examples do not quote the BYOC contract. Scope: Enterprise managed BYOC commercial terms and separate cloud bill; request a quote.. Source: https://docs.estuary.dev/getting-started/pricing/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## FileCloud Server — Self-Hosted VDR

Commercial customer-hosted file platform with virtual data-room controls for confidential business documents.

- Listing: https://launchinyourcloud.com/directory/filecloud-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, oci, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial FileCloud Server license; edition-dependent capabilities
- Licensing model: commercial-only
- Installation: FileCloud Server installation on supported customer infrastructure
- Architecture: Persistent customer-operated server application and file storage; follow the Server system requirements and selected deployment package.
- Operations: Customer maintains server infrastructure, storage, backups, configuration and upgrades under the selected FileCloud support arrangement.
- Product website: https://www.filecloud.com/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The VDR page explicitly supports on-premises deployment. This listing selects FileCloud Server, not FileCloud Online or the separately scoped Community Edition. Verify VDR controls, access features and governance requirements against the selected Server license. FileCloud’s November 13, 2026 advisories say high-availability deployments using MongoDB replica sets through 23.263.3 are affected by critical CVE-2026-118383; restrict port 27017 to trusted hosts until 23.264. RHEL deployments should also verify that Apache mod_http2 is not exposed to HTTP/2 because CVE-2026-119618 applies when it is loaded.

Commercial FileCloud Server software under the vendor EULA. A separate free Community Edition does not establish open-source licensing or business VDR feature entitlement.

Persistent customer-operated server application and file storage; follow the Server system requirements and selected deployment package.


### Category fit

- data-rooms-ma-document-management: Self-hosted virtual data rooms for transaction due diligence and controlled external document sharing; confirm the required governance edition.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/amazon-web-services-aws-installation (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/microsoft-azure-installation (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/oracle-cloud-installation (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/alibaba-cloud-installation (checked 2026-11-12). 


### Cloud deployment evidence

- FileCloud Server installation on AWS (aws): https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/amazon-web-services-aws-installation
  The vendor documents FileCloud Server deployment using its vendor AMI on EC2. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- FileCloud Server installation on Azure (azure): https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/microsoft-azure-installation
  The vendor documents FileCloud Server deployment using its vendor virtual machine image. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- FileCloud Server installation on Oracle Cloud Infrastructure (oci): https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/oracle-cloud-installation
  The vendor documents FileCloud Server deployment using its Marketplace image in a customer compartment. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- FileCloud Server installation on Alibaba Cloud (alibaba): https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/alibaba-cloud-installation
  The vendor documents FileCloud Server deployment using its ECS instance in the customer account. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- VDR functions and on-premises deployment: https://www.filecloud.com/vdr/

- Server system requirements: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/about-filecloud-for-administrators/requirements

- Server license purchasing and editions: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/filecloud-site-maintenance/managing-filecloud-licenses/filecloud-license-purchase-and-renewal

- Software end-user license agreement: https://www.filecloud.com/eula/

- FileCloud Apache HTTP Server security advisory: https://docs.filecloud.com/fcdoc/latest/server/security-advisories/2026-security-advisories/filecloud-release-23-263-security-advisories/advisory-2026-11-02-apache-http-server-remote-code-execution-cve-2026-119618

- FileCloud MongoDB replica-set security advisory: https://docs.filecloud.com/fcdoc/latest/server/security-advisories/2026-security-advisories/filecloud-release-23-263-security-advisories/advisory-2026-11-03-mongodb-replica-set-remote-code-execution-cve-2026-118383

### Licensing sources

- https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/filecloud-site-maintenance/managing-filecloud-licenses/filecloud-license-purchase-and-renewal

- https://www.filecloud.com/eula/

### Infrastructure sources

- https://www.filecloud.com/vdr/

- https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/about-filecloud-for-administrators/requirements


### 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 Server administrator guide documents SAML 2.0 web SSO. It records upgrade-specific SimpleSAML configuration changes; configure the customer identity provider and deployment keys rather than assuming hosted-service settings apply. Scope: FileCloud Server web authentication; specific commercial entitlement must be confirmed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/filecloud-site-setup/user-authentication-settings/single-sign-on-sso/saml-single-sign-on-support (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Edition-dependent. The vendor VDR deployment page explicitly includes air-gapped environments and FileCloud Server. This establishes an offered deployment option, not proof that every integration, license activation or update workflow works offline. Scope: Vendor-described FileCloud Server/VDR option; agree the offline implementation scope. Source: https://www.filecloud.com/vdr/ (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The vendor installation index provides supported Linux/Windows installation and cloud deployment paths. Select a release-compatible package, operating system/database and licence, then configure TLS, persistent storage, backups and updates; application installation is separate from a complete HA design. Scope: FileCloud Server supported installation paths; platform prerequisites and HA separate. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation (reviewed 2026-11-21). Deployment artifact: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation. Artifact reference: Current vendor installation index reviewed on this date.

- Minimum footprint / sizing: Documented. The sizing model publishes a 3,000-user/API-rate HA example using roughly three 8-vCPU/32-GB web nodes, a load balancer and a three-node MongoDB replica set with separate resources. Its older m4-instance references and usage assumptions are illustrative, not a current 100-user minimum; check AVX/runtime support and size storage, sync devices and backups. Scope: FileCloud Server documented workload/HA example; not a modern instance quote or universal minimum. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/about-filecloud-for-administrators/filecloud-sizing-guide (reviewed 2026-11-21).

- License pricing: Documented. The vendor describes Server licence purchase/renewal through its portal, plan selection, licensed site and user-seat additions, with support options and quotes. Select the self-hosted Server entitlement rather than assuming FileCloud Online hosting terms; retain the applicable EULA and renewal order. Scope: FileCloud Server commercial site/user licensing and renewal process. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/filecloud-site-maintenance/managing-filecloud-licenses/filecloud-license-purchase-and-renewal (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## FileRun

Commercial self-hosted file management and sharing platform.

- Listing: https://launchinyourcloud.com/directory/filerun/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, alibaba
- 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: Application platform deployment; Docker / Compose
- Architecture: FileRun application and database on a Websoft9 customer-cloud VM.
- 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://support.websoft9.com/en/docs/filerun/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application package sits on a separately installed Websoft9 platform. FileRun annual subscriptions and licensed domain terms are separate from platform and cloud bills.

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

FileRun application and database on a Websoft9 customer-cloud VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial self-hosted file management and sharing platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.websoft9.com/en/docs/filerun/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.websoft9.com/en/docs/filerun/ (checked 2026-11-19). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.websoft9.com/en/docs/filerun/ (checked 2026-11-19). 


### Cloud deployment evidence

- Websoft9 FileRun (aws, azure, alibaba): https://support.websoft9.com/en/docs/filerun/
  FileRun application and database on a Websoft9 customer-cloud VM. The application package sits on a separately installed Websoft9 platform. FileRun annual subscriptions and licensed domain terms are separate from platform and cloud bills.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Websoft9 FileRun: https://support.websoft9.com/en/docs/filerun/

- Websoft9 AWS: https://support.websoft9.com/en/docs/install-aws/

- Websoft9 Azure: https://support.websoft9.com/en/docs/install-azure/

- Websoft9 Alibaba: https://support.websoft9.com/en/docs/install-alibabacloud/

- FileRun Pricing & Terms: https://filerun.com/pricing

- FileRun 2026 Updates: https://docs.filerun.com/api_2026_3_changes

### Licensing sources

- https://filerun.com/pricing

### Infrastructure sources

- https://support.websoft9.com/en/docs/filerun/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Current FileRun ships OpenID Connect and OAuth2 plugins, with SAML available through SimpleSAMLphp. Only one authentication plugin can be active at once; test its configuration and review local-superuser exceptions and licence entitlement. Scope: FileRun 2026.3 authentication plugins. Source: https://docs.filerun.com/authentication_integration (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide publishes Compose YAML for FileRun and MariaDB with persistent directories, and optional Tika/Elasticsearch. Its application image floats; pin a compatible release, replace example secrets and configure HTTPS and backups. Scope: Official self-hosted Compose recipe; not HA. Source: https://docs.filerun.com/docker (reviewed 2026-11-20). Deployment artifact: https://docs.filerun.com/docker. Artifact reference: Moving documentation; select a versioned application image.

- Minimum footprint / sizing: Sources checked — unresolved. The current guide gives a PHP floor of 20 MB per request and a 256-MB Docker PHP limit, with database memory additional. The Docker guide requires at least 2 GB for optional Elasticsearch. It does not establish total CPU/RAM sizing for a production or HA workload; previews and indexing materially change capacity. Scope: FileRun 2026.3 component guidance; total production minimum unresolved. Source: https://docs.filerun.com/requirements (reviewed 2026-11-20). Supporting source: Optional indexing memory — https://docs.filerun.com/docker.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Finmars CE (Community Edition)

Open-source investment accounting, portfolio data and reporting software.

- Listing: https://launchinyourcloud.com/directory/finmars-ce/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: EUPL-1.2 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Docker / Compose
- Architecture: Finmars CE application services in the vendor's customer EC2 image or documented installation.
- 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://finmars.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The reviewed AWS offer has no software licence charge; infrastructure still costs money. Portfolio analytics and accounting are not a complete private-equity investor or portfolio-company workflow suite. Keep backend, UI and provider-package versions separate.

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

Finmars CE application services in the vendor's customer EC2 image or documented installation. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- pe-portfolio-operations: Open-source investment accounting, portfolio data and reporting software.

- data-analytics: Open-source investment accounting, portfolio data and reporting software.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2
  Finmars CE application services in the vendor's customer EC2 image or documented installation. The reviewed AWS offer has no software licence charge; infrastructure still costs money. Portfolio analytics and accounting are not a complete private-equity investor or portfolio-company workflow suite. Keep backend, UI and provider-package versions separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Install Finmars Platform | Finmars (azure): https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform
  Finmars CE application services in the vendor's customer EC2 image or documented installation. The reviewed AWS offer has no software licence charge; infrastructure still costs money. Portfolio analytics and accounting are not a complete private-equity investor or portfolio-company workflow suite. Keep backend, UI and provider-package versions separate.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes falendary, sokolovdp, paktusov, 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/finmars-platform/finmars-core/graphs/contributors

- Upstream project: https://github.com/finmars-platform/finmars-core

### Sources

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

- Install Finmars Platform | Finmars: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform

- AWS Guide: https://docs.finmars.com/books/installation-guide-with-aws-simple

- Azure Guide: https://docs.finmars.com/books/installation-guide-with-azure-advanced

- EUPL-1.2: https://github.com/finmars-platform/finmars-core/blob/main/LICENSE.md

- Commits: https://github.com/finmars-platform/finmars-core/commits/main

### Licensing sources

- https://github.com/finmars-platform/finmars-core/blob/main/LICENSE.md

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2

- https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform


### 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 Finmars. Its package version is 1.23.0; verify the contained application and required entitlements separately. Scope: Finmars CE (Community Edition) selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2 (reviewed 2026-11-19). Offer prodview-55ptwgyybwzp2: Finmars; Amazon Machine Image (AMI); package 1.23.0; https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The CE installation guide initialises a bundled Keycloak realm and explicitly describes Login redirecting to the deployment authentication host and back to the Finmars dashboard. Configure domains, certificates, realm/users and secrets. External enterprise IdP brokering is a separate requirement, not automatically established by the bundled SSO flow. Scope: Finmars Community Edition documented bundled-Keycloak application-user SSO. Source: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform (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 vendor CE guide clones the community-edition deployment repository, generates environment settings, initialises certificates/Keycloak, runs migrations and starts Docker services. Replace examples and pin compatible releases; the guide does not make every independently versioned core/frontend/image current automatically. Scope: Finmars Community Edition vendor Docker/Make installation; application and deployment versions separate. Source: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform (reviewed 2026-11-21). Deployment artifact: https://github.com/finmars-platform/finmars-community-edition. Artifact reference: Current vendor CE installation workflow reviewed on this date.

- Minimum footprint / sizing: Documented. The Azure guide chooses a B2ms Ubuntu 24.04 VM with 2 vCPU/8 GiB RAM and a 256-GiB Premium SSD OS volume. This is an installation-example host, not a measured minimum or HA recommendation; finance data, database, Keycloak, workers, storage and backups need workload validation. Scope: Finmars CE vendor Azure VM installation example, not workload/HA capacity. Source: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/create-virtual-machine (reviewed 2026-11-21).

- License pricing: Documented. EUPL-1.2 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Finmars CE (Community Edition); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/finmars-platform/finmars-core/blob/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







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




## Flarum

Self-hosted discussion forum and community workspace.

- Listing: https://launchinyourcloud.com/directory/flarum/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Docker / Compose
- Architecture: Flarum PHP application, database, attachments and extension configuration.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.hostinger.com/applications/flarum
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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


### Cloud deployment evidence

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

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


### Community and maintenance

The reviewed upstream contributor history includes tobyzerner, franzliedke, flarum-bot, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


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

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

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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







## Flowable Enterprise Platform

Commercial workflow and case-management platform with vendor Terraform and Helm deployments.

- Listing: https://launchinyourcloud.com/directory/flowable-platform/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- 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: Terraform; Kubernetes manifests
- Architecture: Flowable application services, database, search and persistent storage on EKS or AKS.
- 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://documentation.flowable.com/latest/admin/cloud-deployment/terraform-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 Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.

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

Flowable application services, database, search and persistent storage on EKS or AKS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- workflow-automation: Commercial workflow and case-management platform with vendor Terraform and Helm deployments.

- case-management: Commercial workflow and case-management platform with vendor Terraform and Helm deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-azure (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Terraform (aws): https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws
  Flowable application services, database, search and persistent storage on EKS or AKS. The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Terraform (azure): https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-azure
  Flowable application services, database, search and persistent storage on EKS or AKS. The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Terraform: https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws

- Azure Terraform: https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-azure

- Helm Guide: https://documentation.flowable.com/latest/admin/cloud-deployment/helm

- Supplier Onboarding: https://www.flowable.com/solutions/manufacturing

- Supplier LEAN Alert: https://www.flowable.com/success-stories/great-dane/digitalized-automated-order-lifecycle-management-manufacturing

- Case Management: https://www.flowable.com/solutions/case-management

- License File Renewal: https://documentation.flowable.com/latest/admin/maintenance/license-renewal

- Trial Terms: https://www.flowable.com/flowable-trial-terms-of-use

- Latest Releases (2026.1.5.1): https://documentation.flowable.com/latest/admin/release-notes/latest

- 2026.1.x Release Notes: https://documentation.flowable.com/latest/admin/release-notes/2026.1.0-release

### Licensing sources

- https://documentation.flowable.com/latest/admin/maintenance/license-renewal

- https://www.flowable.com/flowable-trial-terms-of-use

### Infrastructure sources

- https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws

- https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-azure


### 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 Enterprise guide configures user SSO for Work/Engage, Design and Hub using OAuth 2.0 with Keycloak, including separate clients, redirect URIs and application security settings. This is application-specific configuration, not automatic SSO from merely installing Spring Security. Scope: Flowable Enterprise applications; validate current product and IdP versions and replace demonstration credentials. Source: https://documentation.flowable.com/latest/howto/howto/howto-oauth2-keycloak (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. Flowable publishes authenticated Helm charts and separate AWS/Azure Terraform guides. The chart configures licensed product images, database and search connections, secrets and persistent services; repository credentials and compatible chart/application versions are required. Scope: Enterprise Kubernetes chart and deployment guides; not an unrestricted open-source Flowable engine entitlement. Source: https://documentation.flowable.com/latest/admin/cloud-deployment/helm (reviewed 2026-11-20). Deployment artifact: https://repo.flowable.com/flowable-helm. Artifact reference: authenticated Helm repository; select a chart matching the licensed product release. Supporting source: AWS Terraform guide — https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws.

- Minimum footprint / sizing: Documented. The Enterprise requirements give Flowable Work a production minimum of 2 CPU and 8 GB RAM. Application disk guidance differs for files persisted in the database (10 GB) versus the filesystem (100 GB). The separate database minimum without file BLOBs is 4 CPU, 16 GB RAM and 100 GB disk; HA generally needs at least two application instances plus separately sized search, database and storage services. Scope: Product-specific average-scenario guidance; per-application figures are not a total HA footprint. Source: https://documentation.flowable.com/latest/admin/installs/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Flowable Enterprise Platform; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://documentation.flowable.com/latest/admin/maintenance/license-renewal (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## FOIAXpress On-Premise

Public-records request management with intake, redaction and fulfillment in a documented on-premise deployment option.

- Listing: https://launchinyourcloud.com/directory/foiaxpress/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial packages; vendor quote required.
- Licensing model: commercial-only
- Installation: Vendor-supplied installation package on Windows/IIS and SQL Server; published manual includes Azure and AWS prerequisites.
- Architecture: Customer-installed Windows/IIS application with SQL Server and file-repository services
- Operations: Customer-hosted operation is available; agree installation, maintenance and support ownership with the vendor.
- Product website: https://www.casepoint.com/products/government/foiaxpress/
- 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 the customer-installed option, not the vendor-hosted service. Casepoint is the current FOIAXpress vendor; the retained OPEXUS-hosted manual remains the latest public deployment manual found. The public v11.13.1 deployment manual documents Windows/IIS/SQL Server installation and Azure and AWS prerequisites. Confirm the current supported release, cloud configuration and contract support before installation; the manual is dated August 2025 and is not a promise that every present edition supports the same topology. No cloud-provider certification or regulatory certification is implied.

The listed vendor-owned packaged product uses commercial packages and installation license activation. The reviewed materials do not establish an open-source edition; the deployment manual describes product licensing and proprietary ownership.

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.


Deployment qualification: A public vendor Deployment Manual documents installation packages, Windows/IIS/SQL Server prerequisites, Azure installation prerequisites and AWS RDS/FSx prerequisites. This supplies a portable self-installation path beyond the marketing on-premise claim. The reviewed manual is v11.13.1 (August 2025); buyers must obtain the current supported package and requirements.

### Category fit

- freedom-of-information: Dedicated public-records and FOIA request-management alternative covering intake, redaction, collaboration and fulfillment. Confirm jurisdiction-specific workflows and the currently sold on-premise configuration.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.opexustech.com/docs/foiaxpress/11.13.0/FOIAXpress_Deployment_Manual_11.13.1.0.pdf (checked 2026-11-14). 


### Cloud deployment evidence

- FOIAXpress v11.13.1 Azure application deployment manual (azure): https://docs.opexustech.com/docs/foiaxpress/11.13.0/FOIAXpress_Deployment_Manual_11.13.1.0.pdf
  Sections 11.1 and 11.2 of the vendor v11.13.1 manual create an Azure App Service and deploy the supplied AzureApp.zip application package. This confirms application hosting rather than database connectivity alone. Obtain the currently supported package, topology and license from Casepoint; the published manual is not a certification of every present edition. AWS prerequisites alone are not used for an AWS badge.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- Current FOIAXpress product and customer resources: https://www.casepoint.com/products/government/foiaxpress/

- Deployment manual with Azure and AWS prerequisites (v11.13.1): https://docs.opexustech.com/docs/foiaxpress/11.13.0/FOIAXpress_Deployment_Manual_11.13.1.0.pdf

### Licensing sources

- https://docs.opexustech.com/docs/foiaxpress/11.13.0/FOIAXpress_Deployment_Manual_11.13.1.0.pdf

### Infrastructure sources

- https://docs.opexustech.com/docs/foiaxpress/11.13.0/FOIAXpress_Deployment_Manual_11.13.1.0.pdf


### Buyer diligence


Research coverage: 4/12 fields (33%); 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed product material does not establish a version-matched SAML/OIDC path and entitlement for the on-premises installation. Verify staff login, public-requester portal and any hosted-government service separately; the linked deployment PDF could not be retrieved for this check. Scope: FOIAXpress on-premises user identity remains unconfirmed; inaccessible manual is not positive evidence. Source: https://www.casepoint.com/products/government/foiaxpress/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The current customer-resources page points to a separate resource library for release notes, implementation and administrator manuals. The older deployment-manual endpoint timed out during review. A current customer-download installer or IaC artifact was not confirmed; request the version-specific package and deployment prerequisites. Scope: Current customer-operated product; installer/artifact remains unconfirmed. Source: https://www.casepoint.com/products/government/foiaxpress/ (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. A quantitative current on-premises CPU/RAM/storage and HA baseline was not established from the accessible product material. The deployment-manual download timed out; obtain its applicable server/database/search/redaction sizing and release compatibility before estimating capacity. Scope: FOIAXpress on-premises sizing remains unconfirmed. Source: https://www.casepoint.com/products/government/foiaxpress/ (reviewed 2026-11-21).

- License pricing: Sources checked — unresolved. The accessible product page does not establish current on-premises licence metrics, included modules, support/renewal or disaster-recovery rights. Obtain the applicable software agreement and quote; hosted-service procurement terms cannot be assumed to cover customer operations. Scope: FOIAXpress on-premises commercial terms remain unconfirmed. Source: https://www.casepoint.com/products/government/foiaxpress/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Foswiki

Self-hosted enterprise wiki with structured forms, revision history and attachments.

- Listing: https://launchinyourcloud.com/directory/foswiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0-or-later for Foswiki; bundled extensions can have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Foswiki application, web server and persistent wiki data.
- 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://foswiki.org/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AWS TurnKey and Azure cloudimg are independent repackagers. Appliance and upstream Foswiki version numbers must remain separate. Verify the packaged Foswiki version and apply the access-control corrections supplied in 2.1.11 or a compatible later release.

GNU GPL-2.0-or-later for Foswiki; bundled extensions can have separate terms.

Foswiki application, web server and persistent wiki data. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted enterprise wiki with structured forms, revision history and attachments.

### Deployment boundaries


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

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


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-lz2gv45alfwki
  Foswiki application, web server and persistent wiki data. AWS TurnKey and Azure cloudimg are independent repackagers. Appliance and upstream Foswiki version numbers must remain separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.foswiki
  Foswiki application, web server and persistent wiki data. AWS TurnKey and Azure cloudimg are independent repackagers. Appliance and upstream Foswiki version numbers must remain separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes gac410, MichaelDaum, LievenLitaer, 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/foswiki/distro/graphs/contributors

- Upstream project: https://github.com/foswiki/distro

### Sources

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

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.foswiki

- GPL-2.0 COPYING: https://raw.githubusercontent.com/foswiki/distro/master/core/COPYING

- GitHub Tags: https://github.com/foswiki/distro/tags

- Selected edition licence text: https://raw.githubusercontent.com/foswiki/distro/master/core/LICENSE

- Foswiki access-control corrections: https://github.com/foswiki/distro/releases/tag/FoswikiRelease02x01x11

### Licensing sources

- https://raw.githubusercontent.com/foswiki/distro/master/core/COPYING

- https://raw.githubusercontent.com/foswiki/distro/master/core/LICENSE

### Infrastructure sources

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

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.foswiki


### Buyer diligence


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

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


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. 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: Foswiki selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.foswiki?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Supporting source: AWS delivery and package version — https://aws.amazon.com/marketplace/pp/prodview-lz2gv45alfwki. Offer cloudimg1647283583153.foswiki: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.foswiki. Offer prodview-lz2gv45alfwki: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-lz2gv45alfwki.

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

- Single sign-on: Documented. Foswiki's published SamlLoginContrib extension documents SAML 2.0 authentication, service-provider metadata, signing keys and a SAML LoginManager. Install and configure the extension separately; this is an extension path, not evidence that a particular marketplace image has it enabled or that LDAP alone supplies SSO. Scope: Foswiki with SamlLoginContrib version 14 documentation (December 2025); verify extension/dependency compatibility with the selected package. Source: https://foswiki.org/Extensions/SamlLoginContrib (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project publishes the 2.1.11 source/archive distribution and an installation guide covering the Perl/web-server dependencies, archive extraction, Apache configuration and configure workflow. This is upstream application installation; the Azure/AWS repackager images have separate package versions and defaults. Scope: Foswiki upstream installation; verify the selected OS, Perl modules, extensions and provider package separately. Source: https://foswiki.org/System/InstallationGuide (reviewed 2026-11-20). Deployment artifact: https://foswiki.org/Download/FoswikiRelease02x01x11. Artifact reference: FoswikiRelease02x01x11 / Foswiki 2.1.11 upstream distribution.

- Minimum footprint / sizing: Sources checked — unresolved. The official installation guide lists web-server/Perl dependencies and configuration steps but does not establish a quantitative whole-host CPU/RAM/storage floor for the proposed wiki. Content, attachments, search/extensions, concurrent users and backups require workload sizing. Scope: Foswiki application and chosen extensions; dependency prerequisites and marketplace VM sizes are not universal production/HA minima. Source: https://foswiki.org/System/InstallationGuide (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-2.0-or-later for Foswiki; bundled extensions can have separate terms. Scope: Foswiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/foswiki/distro/master/core/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Foswiki access-control corrections (security-advisory): Foswiki 2.1.11 fixes access checks in changes, preview, viewfile and oops handling. Scope: CVE-2026-2861 and the Foswiki 2.1.11 release notes; check individual scripts and the installed application version. Conditions: Third-party appliance and VM package labels do not by themselves establish the included Foswiki patch level. Action: Verify the packaged Foswiki version and apply the access-control corrections supplied in 2.1.11 or a compatible later release. Source: https://github.com/foswiki/distro/releases/tag/FoswikiRelease02x01x11; reviewed 2026-11-19.




## Frappe Helpdesk

Self-hosted support desk for tickets, knowledge content and service operations.

- Listing: https://launchinyourcloud.com/directory/frappe-helpdesk/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Frappe Helpdesk and Frappe framework services, database, queues and files on an Azure VM.
- 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://frappe.io/helpdesk
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The cloudimg image is a third-party package. Helpdesk application releases and Frappe framework versions are separate.

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

Frappe Helpdesk and Frappe framework services, database, queues and files on an Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted support desk for tickets, knowledge content and service operations.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04
  Frappe Helpdesk and Frappe framework services, database, queues and files on an Azure VM. The cloudimg image is a third-party package. Helpdesk application releases and Frappe framework versions are separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes RitvikSardana, kamaljohnson, aerodeval, 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/frappe/helpdesk/graphs/contributors

- Upstream project: https://github.com/frappe/helpdesk

### Sources

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

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

- GitHub Releases: https://github.com/frappe/helpdesk/releases

### Licensing sources

- https://raw.githubusercontent.com/frappe/helpdesk/main/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Documented. Helpdesk v16.2.0 redirects unauthenticated agents to the Frappe site /login page and uses the resulting Frappe session and Helpdesk roles. The framework documents Social Login Key providers including Google, Microsoft and custom providers. Configure the provider/callback and existing user/Agent records; this source-based integration finding is not a SCIM or universal SAML claim. Scope: Published Helpdesk login routing plus official framework identity configuration. Source: https://github.com/frappe/helpdesk/blob/v16.2.0/desk/src/router/index.ts (reviewed 2026-11-20). Supporting source: Framework Social Login Key configuration — https://docs.frappe.io/framework/user/en/guides/integration/social_login_key. Supporting source: Helpdesk application user and role mapping — https://github.com/frappe/helpdesk/blob/v16.2.0/helpdesk/api/auth.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v16.2.0 README documents self-hosting through the Frappe easy-install script and Helpdesk container. Its example selects the moving stable image; pin a compatible application/framework image, review the downloaded script, and configure the site, TLS, secrets, database, workers and backups. Its development Compose recipe is a different path. Scope: Published production instructions; unversioned installer URL and stable image require separate pinning. Source: https://github.com/frappe/helpdesk/blob/v16.2.0/README.md (reviewed 2026-11-20). Deployment artifact: https://frappe.io/easy-install.py. Artifact reference: easy-install.py (moving URL), referenced by Helpdesk v16.2.0 production instructions. Supporting source: Official Helpdesk installation guide — https://docs.frappe.io/helpdesk/installation.

- Minimum footprint / sizing: Sources checked — unresolved. The Helpdesk production recipe establishes the application/framework deployment but does not specify a complete CPU/RAM/storage minimum for agents, workers, database and attachments. Hosting plan allocations and development containers do not establish 100-user, 1 TB HA sizing; confirm ticket load, concurrency, mail processing and redundancy. Scope: Helpdesk-specific self-hosting guidance; whole-system production sizing remains unconfirmed. Source: https://docs.frappe.io/helpdesk/installation (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Frappe Lending Self-Hosted

Loan application and servicing software with borrower records, supporting documents and approval workflows.

- Listing: https://launchinyourcloud.com/directory/frappe-lending/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source GPL-3.0; implementation and support separately arranged
- Licensing model: open-source
- Installation: Frappe/ERPNext installation scripts
- Architecture: Customer-operated Frappe application and database
- Operations: Customer or implementation partner operates the server, applies updates and maintains backups.
- Product website: https://frappe.io/lending
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

A loan-focused application and servicing product. Applications capture borrower documents, co-applicants and proposed collateral before loan creation. A complete retail agreement or eSignature workflow is not established by the reviewed sources.

The listed Frappe Lending application is GPLv3 in the official repository and is offered for self-hosting. Paid hosting, implementation and support do not by themselves make this an open-core application.

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

- financial-application-management: Loan-focused application and servicing comparator with borrower documents and approval workflows; a complete retail agreement or eSignature workflow is not established.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/frappe-lending-on-ubuntu-24-04-azure/ (checked 2026-11-12). 


### Cloud deployment evidence

- Frappe Lending v16 Azure VM deployment guide by cloudimg (azure): https://www.cloudimg.co.uk/guides/frappe-lending-on-ubuntu-24-04-azure/
  Third-party image publisher cloudimg documents a complete Frappe Lending v16.4.0/ERPNext v16 Azure VM deployment in the customer subscription, including database, workers, loan workflows, HTTPS and backups. This is a packaged distribution, not an upstream-endorsed image. Check image charges, component versions and publisher support separately from upstream GPLv3 terms; this review inspected the guide and did not deploy or audit the image.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Versions: Frappe Lending 16.4.0 / ERPNext 16.


### Sources

- Self-hosting and licensing: https://frappe.io/lending/pricing

- Loan application workflow: https://docs.frappe.io/lending/loan-application

- Product scope: https://docs.frappe.io/lending/introduction

- Licensing and edition terms: https://raw.githubusercontent.com/frappe/lending/develop/license.txt

### Licensing sources

- https://raw.githubusercontent.com/frappe/lending/develop/license.txt

- https://frappe.io/lending/pricing

### Infrastructure sources

- https://frappe.io/lending/pricing


### 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: Documented. The shared Frappe login system accepts external OAuth/OpenID logins configured with Social Login Key, including Google and Office 365. Configure the provider and permitted users for the installed Frappe version; this is framework login, not a separate application-specific SAML implementation. Scope: Self-hosted Frappe-based application login; provider configuration and matching framework/app versions required. Source: https://docs.frappe.io/framework/user/en/guides/integration/social_login_key (reviewed 2026-11-20). Supporting source: Frappe login handlers — https://github.com/frappe/frappe/blob/develop/frappe/integrations/oauth2_logins.py. Supporting source: Application framework dependency — https://github.com/frappe/lending/blob/develop/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Frappe publishes production Compose bases and custom-app image guidance, but this pass did not establish a complete, release-matched Lending deployment artifact. Confirm the Lending image, required apps and database migration sequence. Scope: Framework deployment checked; Lending-specific production packaging unresolved. Source: https://github.com/frappe/frappe_docker (reviewed 2026-11-14). Supporting source: Frappe Lending upstream — https://github.com/frappe/lending.

- Minimum footprint / sizing: Sources checked — unresolved. The underlying Frappe Docker ERPNext example recommends two vCPUs, 4 GB RAM and 50 GB SSD for a small single bench. It does not size this additional application or establish its whole-stack production/HA minimum; application jobs, database, attachments and replicas still require sizing. Scope: Platform recipe only, not an application-specific Frappe HR/Lending benchmark or Frappe Cloud hosting allocation. Source: https://github.com/frappe/frappe_docker/blob/main/docs/02-setup/08-single-server-nginxproxy-example.md (reviewed 2026-11-20). Supporting source: Application dependencies — https://github.com/frappe/lending/blob/develop/README.md.

- License pricing: Documented. The reviewed Lending source is GPLv3. The pricing page offers self-hosting separately from paid Frappe Cloud hosting and implementation. Cloud site/server prices do not establish a self-hosted software subscription or an infrastructure estimate. Scope: Frappe Lending open-source application; ERPNext/Frappe dependencies and services must be evaluated separately. Source: https://github.com/frappe/lending/blob/develop/license.txt (reviewed 2026-11-20). Supporting source: Hosting and self-hosting options — https://frappe.io/lending/pricing.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v16.8.1, 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 frappe/lending release record; commercial editions and deployment packages may differ. Source: https://github.com/frappe/lending/releases/tag/v16.8.1 (reviewed 2026-11-14).







## FundCount Self-Hosted

Installed portfolio, partnership accounting and reporting software serving private-equity firms and investment offices.

- Listing: https://launchinyourcloud.com/directory/fundcount/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial; annual solution pricing and implementation or hosting fees depend on scope.
- Licensing model: commercial-only
- Installation: Vendor-guided or managed implementation of installed Java application, SQL database and thin client.
- Architecture: Customer-operated SQL database, application server and thin client
- Operations: Customer can operate the installed option; vendor-hosted and managed-service alternatives have a different responsibility split.
- Product website: https://fundcount.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

FundCount publicly offers public/private-cloud deployment separately from fully managed SaaS. Its infrastructure guidance applies to customer-installed core software and add-ons, and the FAQ documents a host-agnostic Java application and SQL database. Confirm the account owner and operational split in your implementation agreement. Its PE accounting/reporting scope is adjacent to portfolio-company document workflows, not equivalent; no named hyperscaler badge is asserted.

The listed installed product is offered through annual commercial platform licensing, with the selected solution and deployment scoped in its quotation. The reviewed materials do not identify an open-source edition of this product.

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.


Deployment qualification: Current pricing distinguishes on-site, public/private-cloud deployment from fully managed SaaS. Published IT infrastructure guidance covers core software and add-ons in a private cloud; the FAQ documents a host-agnostic Java/SQL/application-server stack. Suitable as generic portable self-hosting, without a named-provider badge.

### Category fit

- pe-portfolio-operations: Adjacent private-equity accounting and reporting alternative. Covers portfolio/partnership accounting and investor reporting; it is not a reusable document-workflow deployment across separately owned portfolio-company accounts.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fundcount.com/fund-administrators-sleep-easy-with-secure-ai-on-their-side/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fundcount.com/fund-administrators-sleep-easy-with-secure-ai-on-their-side/ (checked 2026-11-12). 


### Cloud deployment evidence

- FundCount customer-controlled private cloud options (aws, azure): https://fundcount.com/fund-administrators-sleep-easy-with-secure-ai-on-their-side/
  The vendor explicitly describes hosting the FundCount stack in a customer-controlled AWS or Azure virtual network with keys, storage and IAM in the customer tenant. It distinguishes this option from FundCount Cloud and fully managed FC Hosted; confirm the contracted topology and support responsibilities.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installed and hosted deployment FAQ: https://fundcount.com/faq/

- Private equity functionality: https://fundcount.com/industries/private-equity-software

- Implementation services: https://fundcount.com/implementation/

- Licensing and deployment pricing: https://fundcount.com/pricing

- Private-cloud infrastructure guidance: https://fundcount.com/https-fundcount-com-knowledge_center-it-infrastructure-guidelines/

### Licensing sources

- https://fundcount.com/pricing

- https://fundcount.com/faq/

### Infrastructure sources

- https://fundcount.com/faq/

- https://fundcount.com/pricing


### 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: Edition-dependent. The vendor security center offers SSO integration as an option and states that authentication capabilities depend on configuration and plan. Confirm the protocol, compatible IdP, customer-managed edition, account lifecycle and purchased entitlement; it is not advertised as universal default SSO. Scope: FundCount vendor-stated optional SSO; selected plan and deployment require confirmation. Source: https://fundcount.com/security-compliance-center/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The vendor describes a staged implementation and installed on-premises/private-hosting option, but these public pages do not supply a supported installer, automation artifact or reproducible backend installation procedure. Obtain the delivery package and supported stack for the contracted deployment. Scope: FundCount implementation process; customer-managed installation artifact unconfirmed. Source: https://fundcount.com/implementation/ (reviewed 2026-11-21). Supporting source: Installed versus hosted deployment — https://fundcount.com/faq/.

- Minimum footprint / sizing: Sources checked — unresolved. The infrastructure-guidelines landing page covers core software and add-on modules on-premises/private cloud, but the detailed brochure is behind a download flow. A numeric minimum footprint was not established from the public page inspected. Scope: Customer-operated FundCount; not Digital Edge managed hosting. Source: https://fundcount.com/https-fundcount-com-knowledge_center-it-infrastructure-guidelines/ (reviewed 2026-11-16).

- License pricing: Documented. The current pricing page describes an annual platform licence rather than a simple per-seat fee, with entity/user/asset inputs and implementation/hosting scoped in a quote. Older FAQ figures are not treated as current quotations. Confirm self-hosted scope, modules and support in the applicable order. Scope: Current FundCount platform-licence framework; actual customer-managed price is quote-specific. Source: https://fundcount.com/pricing (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## GitHub Enterprise Server

Customer-operated GitHub software-development platform deployed as a licensed virtual appliance.

- Listing: https://launchinyourcloud.com/directory/github-enterprise-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial GitHub Enterprise license required.
- Licensing model: commercial-only
- Installation: Official virtual-machine image on AWS, Azure or Google Cloud
- Architecture: Customer-operated appliance VM with persistent data storage and optional high-availability nodes
- Operations: Customer provisions infrastructure and manages networking, storage, backups, upgrades, monitoring and high availability.
- Product website: https://github.com/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers GitHub Enterprise Server, not GitHub Enterprise Cloud. A valid license file is required. Review supported instance types, storage, backup utilities, upgrade paths and version support before deployment. GitHub Enterprise Server 3.22.4 fixes critical Active Storage file-read and remote-code-execution CVE-2026-66066, several high-severity Git vulnerabilities, and Brotli CVE-2026-111497. Upgrade to 3.22.4 or a later supported patch. GitHub Enterprise Server 3.22.5 adds support-bundle and backup metrics, defaults new AWS roots to gp3, updates system packages for security, and fixes operational issues. Follow the documented upgrade path and reapply custom firewall rules when required.

GitHub Enterprise Server requires a purchased GitHub Enterprise license file that controls access and licensed users.

The platform runs as one or more persistent virtual-machine appliances with attached data storage. Customer-cloud placement does not remove appliance sizing, backup, upgrade or availability responsibilities. GHES upgrades remove custom firewall rules; reapply any custom rules after upgrading.


### Category fit

- devops: Provides customer-operated source control, pull requests, collaboration and software delivery workflows as a licensed virtual appliance.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform (checked 2026-11-14). 


### Cloud deployment evidence

- GitHub Enterprise Server on AWS (aws): https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws
  GitHub documents launching its published appliance image on EC2 and attaching an EBS data volume in the customer's AWS account.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- GitHub Enterprise Server on Azure (azure): https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure
  GitHub documents deploying the appliance to a supported Azure VM with premium storage in the customer's subscription.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- GitHub Enterprise Server on Google Cloud (gcp): https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform
  GitHub documents deploying its appliance image to a supported Compute Engine VM with persistent disks in the customer's project.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- GitHub Enterprise Server overview: https://docs.github.com/en/enterprise-server@latest/admin/overview/about-github-enterprise-server

- AWS installation: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws

- Azure installation: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure

- Google Cloud installation: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform

- Enterprise Server license files: https://docs.github.com/en/enterprise-server@latest/billing/concepts/enterprise-billing/ghes-license-files

- GitHub Enterprise Server 3.22 release notes: https://docs.github.com/en/enterprise-server@3.22/admin/release-notes

### Licensing sources

- https://docs.github.com/en/enterprise-server@latest/billing/concepts/enterprise-billing/ghes-license-files

### Infrastructure sources

- https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance

- https://docs.github.com/en/enterprise-server@latest/admin/overview/about-github-enterprise-server

- https://docs.github.com/en/enterprise-server@3.22/admin/release-notes


### 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 versioned appliance overview documents external authentication with CAS, LDAP or SAML. Authentication, identity-provider reachability and account lifecycle need configuration. Scope: GitHub Enterprise Server 3.22 appliance; not GitHub.com Enterprise Cloud. Source: https://docs.github.com/en/enterprise-server@3.22/admin/overview/about-github-enterprise-server (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 AWS guide deploys the GitHub Enterprise Server appliance AMI into a customer VPC with configured instance, storage and security groups. Select the release-specific regional AMI and supply the Enterprise licence; this is a vendor appliance deployment guide rather than a public Terraform module. Scope: Official GHES 3.21 AWS appliance installation. Source: https://docs.github.com/en/enterprise-server%403.21/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws (reviewed 2026-11-20). Deployment artifact: https://enterprise.github.com/releases. Artifact reference: Release-specific regional image; choose a supported GHES version.

- Minimum footprint / sizing: Documented. The GHES 3.21 AWS guide recommends 8 x86-64 vCPUs, 48 GB RAM, 400 GB root and 500 GB data disk at 3,000 IOPS for up to 1,000 user licences. Its 4-vCPU/32-GB tier is trial/demo or ten light users. Actions, code security, growth and HA replicas require extra resources. Scope: GHES 3.21 AWS sizing by licensed users; feature and HA overhead additional. Source: https://docs.github.com/en/enterprise-server%403.21/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws (reviewed 2026-11-20).

- License pricing: Documented. A GitHub Enterprise account can include both Server and Cloud under enterprise licensing, with unique users counted across deployments when usage is synchronized. The appliance requires a licence file; agree seats, billing model and optional security products. This is not a hosting or runner-cost quote. Scope: GitHub Enterprise licensing across Server/Cloud; infrastructure additional. Source: https://docs.github.com/en/enterprise-server@3.21/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. GitHub Enterprise Server 3.22.5 was released November 17, 2026. It adds support-bundle and backup metrics, defaults new AWS roots to gp3, updates system packages for security, and fixes operational issues. Scope: GitHub Enterprise Server 3.22 appliance line. Source: https://docs.github.com/en/enterprise-server@3.22/admin/release-notes (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- GitHub Enterprise Server appliance security patch (security-advisory): GHES 3.22.4 patches Active Storage file-read/code-execution, Git and Brotli vulnerabilities. Scope: GitHub Enterprise Server 3.22.4 security release; other supported lines need their own branch-specific patch guidance. Conditions: Appliance component and network exposure determine applicability. The release notes also identify dependency updates that are only partial remediations. Action: Install a patched supported appliance release, follow the upgrade sequence and reapply custom firewall rules where required. Source: https://docs.github.com/en/enterprise-server@3.22/admin/release-notes; reviewed 2026-11-17.




## GitLab Self-Managed

Source control and CI/CD on infrastructure you operate.

- Listing: https://launchinyourcloud.com/directory/gitlab/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, oci, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Free and paid tiers
- Licensing model: open-source
- Installation: Linux package, container or Helm chart
- Architecture: Customer-operated application and storage
- Operations: Your team operates, upgrades and backs up the installation.
- Product website: https://about.gitlab.com/
- Source review: 2026-11-20; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

GitLab documents AWS, Azure and Google Cloud installations. Oracle and Alibaba Cloud also publish deployment guides. These are documented deployment paths, not a promise of identical support or feature availability. Check operating system, edition and region requirements. GitLab 19.5.4, 19.4.6, and 19.3.8 patch critical CVE-2026-105437 in the bundled Git. Affected self-managed versions are 16.2 through versions before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Upgrade immediately. Self-compiled deployments must also rebuild the Git binaries embedded in Gitaly and the Git installation referenced by git.bin_path, or use a distribution-patched Git 2.56.1 or later. GitLab 19.5.6, 19.4.8, and 19.3.9 address a high-severity cross-site scripting issue plus CI/CD and workspace authorization flaws. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.

Community Edition uses MIT terms; Enterprise Edition adds components under a more restrictive commercial license.

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

- devops: Source control and CI/CD on infrastructure you operate.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gitlab.com/install/cloud_providers/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gitlab.com/install/cloud_providers/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gitlab.com/install/cloud_providers/ (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab (checked 2026-11-12). 


### Cloud deployment evidence

- GitLab Self-Managed cloud installation guides (aws, azure, gcp): https://docs.gitlab.com/install/cloud_providers/
  The upstream installation index links full GitLab Self-Managed deployment on AWS, Azure and Google Cloud. Choose the Linux package, chart or reference architecture appropriate to the selected edition, scale and supported release; a GitLab Runner alone is not the GitLab application.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- GitLab Community Edition on Alibaba Cloud ECS (alibaba): https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab
  Alibaba documents GitLab Community Edition Docker deployment on Alibaba Cloud Linux 3 ECS as well as older package-based examples. Use the Community Edition path for this listing; JiHu GitLab is a separately distributed edition and old CentOS examples are not a current production recommendation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Oracle GitLab application deployment in an OCI tenancy (oci): https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html
  Oracle explicitly documents the GitLab application VM, customer tenancy, region, compartment, compute and VCN configuration, and administrator login. This confirms the provider deployment model. Its linked quick-start architecture has been retired, so these instructions do not establish a currently maintained one-click stack; validate the installer and supported GitLab release before using the legacy automation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- GitLab cloud installation: https://docs.gitlab.com/install/cloud_providers/

- Alibaba Cloud deployment: https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab

- Licensing and edition terms: https://docs.gitlab.com/development/licensing/

- Oracle GitLab application deployment in an OCI tenancy: https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html

- GitLab critical patch release for CVE-2026-105437: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/

- GitLab 19.5.6 security patch release: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/

- GitLab 19.6.1 critical Ruby patch announcement: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1

- Upstream Ruby security advisory: https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/

### Licensing sources

- https://docs.gitlab.com/development/licensing/

### Infrastructure sources

- https://docs.gitlab.com/install/cloud_providers/

- https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab

- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/


### Buyer diligence


Research coverage: 10/12 fields (83%); 10 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: Edition-dependent. GitLab documents AWS Marketplace self-service/private offers and Google Cloud Marketplace private offers for paid subscriptions. Delivery/billing does not by itself change where a selected GitLab installation runs. Scope: Premium/Ultimate subscription procurement; self-hosting and SaaS offers must be distinguished. Source: https://about.gitlab.com/cloud-partner-marketplaces/ (reviewed 2026-11-14).

- Cloud commitment eligibility: Edition-dependent. GitLab states eligible cloud-marketplace purchases can count toward committed spend on AWS or Google Cloud. Confirm the specific offer, billing account and buyer agreement; this is not an unconditional credit guarantee. Scope: Vendor procurement statement; actual provider commitment terms govern eligibility. Source: https://about.gitlab.com/cloud-partner-marketplaces/ (reviewed 2026-11-14).

- Single sign-on: Documented. Instance-wide SAML SSO is documented for Self-Managed Free, Premium and Ultimate. Group SAML and advanced group mapping have separate tier requirements. Scope: GitLab Self-Managed instance authentication; not GitLab.com group SSO. Source: https://docs.gitlab.com/integration/saml/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. SCIM is documented for Self-Managed Premium and Ultimate, with SAML configured. The API implements part of RFC7644; verify the supported identity provider and operations. Scope: GitLab Self-Managed / Dedicated, Premium and Ultimate. Source: https://docs.gitlab.com/administration/settings/scim_setup/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Documented. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series. Scope: GitLab Self-Managed CE/EE, including Linux packages, containers and self-compiled installations. The separate bundled Git fix has its own requirements.. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1 (reviewed 2026-11-20). Supporting source: Upstream Ruby security advisory — https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/.

- Air-gapped operation: Edition-dependent. Self-Managed Free, Premium and Ultimate have an offline installation workflow. Transfer the correct packages/images and handle scanners, AI and update dependencies separately. Scope: Documented offline Self-Managed configuration, not default online installation. Source: https://docs.gitlab.com/topics/offline/ (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The official self-managed guide publishes Compose YAML for versioned Community or Enterprise images with persistent configuration, logs and data. It warns against placing the all-in-one Docker image in Kubernetes; use the Helm chart/operator there. Configure hostname, TLS, secrets, backups and runner capacity separately. Scope: Official self-managed Docker/Compose installation. Source: https://docs.gitlab.com/install/docker/installation/ (reviewed 2026-11-20). Deployment artifact: https://docs.gitlab.com/install/docker/installation/#install-gitlab-by-using-docker-compose. Artifact reference: Select explicit version-ce.0 or version-ee.0 image tag.

- Minimum footprint / sizing: Documented. The single-node baseline is 8 vCPU and 16 GB RAM. A memory-constrained configuration can use at least 8 GB; distributed sizing is component- and workload-specific. Scope: Self-Managed single-node baseline; not a total production cost estimate. Source: https://docs.gitlab.com/install/requirements/ (reviewed 2026-11-14).

- License pricing: Documented. GitLab Self-Managed offers tier-based subscriptions applying to the whole instance; all instance users share the selected features. A GitLab.com subscription cannot be transferred to Self-Managed. Select the required tier, seats and add-ons; this does not establish a complete hosting/support cost. Scope: GitLab Self-Managed instance-wide commercial tiers. Source: https://docs.gitlab.com/subscriptions/choosing_subscription/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. GitLab published 19.6.1 on November 20, 2026, with parallel Ruby security patches 19.5.8 and 19.4.10. Scope: GitLab Self-Managed Community and Enterprise editions. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1 (reviewed 2026-11-20).




### Security and lifecycle reviews

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

- GitLab bundled Git command-execution advisory (security-advisory): CVE-2026-105437 concerns a Git heap-write flaw that can reach command execution inside Gitaly. Scope: GitLab CE/EE 16.2 to before 19.3.8, 19.4 to before 19.4.6, and 19.5 to before 19.5.4. Conditions: All installation types are covered unless the vendor identifies an exception. Source builds need both Gitaly-embedded Git and git.bin_path checked. Action: Install the patched release for the deployed branch. Rebuild the required Git binaries for source installations, or use a distribution fix for the CVE. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/; reviewed 2026-11-17.

- GitLab 19.5.6 security update (security-advisory): GitLab 19.5.6, 19.4.8, and 19.3.9 fix a high-severity cross-site scripting issue and authorization weaknesses in CI/CD and workspaces. Scope: GitLab CE/EE patch lines 19.3, 19.4, and 19.5; consult the vendor table for the affected versions. Conditions: Impact depends on enabled features, user roles, and exposed endpoints. This record does not replace the separate bundled-Git CVE review. Action: Upgrade to 19.5.6, 19.4.8, or 19.3.9 for the deployed branch, or a later supported patch. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/; reviewed 2026-11-18.

- GitLab critical bundled Ruby security update (security-advisory): GitLab updated bundled Ruby for CVE-2026-132825 and related upstream Ruby security issues. Scope: Self-managed GitLab CE/EE releases before 19.4.10, 19.5 releases before 19.5.8, and 19.6 releases before 19.6.1, per GitLab. Conditions: Official Linux packages and container images carry the fixed Ruby. Self-compiled installations manage Ruby separately. Action: Upgrade to 19.6.1, 19.5.8, or 19.4.10 as appropriate. For source builds, rebuild GitLab’s Ruby with 3.3.14, 3.4.13, or a later patch in the same minor series. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1; reviewed 2026-11-20. Supporting source: Upstream Ruby security advisory — https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/.




## Gravitee API Management Self-Hosted

Open-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.

- Listing: https://launchinyourcloud.com/directory/gravitee-apim-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 Community Edition; Enterprise Edition requires a commercial license.
- Licensing model: open-source
- Installation: Official Helm chart, Docker deployment or Linux packages on customer infrastructure
- Architecture: Self-hosted management API and user interfaces, API gateways, MongoDB and Elasticsearch, with optional Redis, PostgreSQL and enterprise services
- Operations: Customer manages Kubernetes or hosts, databases, search, networking, ingress, TLS, identity, secrets, monitoring, backups, scaling, upgrades and any Enterprise license.
- Product website: https://www.gravitee.io/platform/api-management
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Gravitee APIM with both control and data planes self-hosted. Gravitee recommends its cloud option for new installations, and multi-environment self-hosted configuration requires a connection to Gravitee Cloud. The provider-specific Kubernetes guides are development and quick-start material, not production reference architectures. Gravitee APIM 4.10.36 fixes Kafka OAUTHBEARER reauthentication, subscription metadata deletion, dead-letter-queue failure handling, and health-check POST bodies. Supported 4.13.4 also fixes upgrade and Redis-cache behavior; v2 APIs are scheduled for removal in October 2027, and unqualified images move from Alpine to Debian in March 2027 before Alpine images stop in June 2027.

Gravitee APIM Community Edition is Apache-2.0 licensed. Enterprise Edition capabilities require a separate commercial license.

Gravitee APIM runs persistent management, gateway, portal, database and analytics services on customer hosts or Kubernetes.


### Category fit

- backend-platforms: Provides a self-hosted API gateway, management control plane, developer portal, policy engine and API lifecycle tooling.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides (checked 2026-11-16). 


### Cloud deployment evidence

- Gravitee APIM self-hosted deployment on EKS, AKS or GKE (aws, azure, gcp): https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides
  Gravitee's current self-hosted guide lists AWS EKS, Azure AKS and Google GKE as Kubernetes deployment methods and states that the customer manages both the control plane and data plane. Provider quick starts are development guidance rather than production architecture commitments.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Versions: 4.10.


### Community and maintenance

Gravitee maintains public releases and contributor history for its Apache-licensed API Management project. This evidence establishes continuing upstream activity, not Enterprise support or production support for a particular cloud configuration.

Reviewed 2026-11-16.

- Gravitee APIM releases: https://github.com/gravitee-io/gravitee-api-management/releases

- Gravitee APIM contributor history: https://github.com/gravitee-io/gravitee-api-management/graphs/contributors

### Sources

- Gravitee APIM self-hosted installation guides: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides

- Gravitee APIM Enterprise Edition: https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition

- Gravitee APIM editions: https://documentation.gravitee.io/apim/4.10/getting-started

- Gravitee APIM Apache 2.0 license: https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt

- Gravitee APIM releases: https://github.com/gravitee-io/gravitee-api-management/releases

- Gravitee APIM contributor history: https://github.com/gravitee-io/gravitee-api-management/graphs/contributors

- Gravitee APIM 4.10 changelog: https://documentation.gravitee.io/apim/4.10/release-information/changelog/apim-4.10.x

- Gravitee APIM 4.13 changelog: https://documentation.gravitee.io/apim/4.13/release-information/changelog/apim-4.13.x

- Gravitee APIM support model: https://documentation.gravitee.io/apim/release-information/support-model

- Gravitee APIM 4.13 release notes: https://github.com/gravitee-io/gravitee-platform-docs/blob/main/docs/gamma/4.13/platform-management/gamma-release-notes.md

### Licensing sources

- https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt

- https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition

### Infrastructure sources

- https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides

- https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides/kubernetes/azure-aks


### 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: Documented. APIM documents delegating Console and Portal authentication to a corporate OAuth2/OIDC provider or LDAP, with role/group mapping. The New Developer Portal has its own SSO configuration and requires APIM 4.10+. Scope: Self-hosted APIM 4.10 Console/Portal; not a blanket entitlement to the separate Access Management product. Source: https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/production-best-practices/authentication (reviewed 2026-11-16). Supporting source: New Portal SSO setup — https://documentation.gravitee.io/apim/4.10/developer-portal/new-developer-portal/configure-authentication/configure-authentication-with-sso.

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The security page’s printed certificate scope describes a marketing platform rather than APIM. That mismatch does not establish assurance for this listing; obtain a current certificate/report identifying the APIM organization, product boundary and validity dates. Scope: Published certificate-scope mismatch; current self-hosted APIM assurance remains unresolved. Source: https://www.gravitee.io/security-at-gravitee (reviewed 2026-11-16).

- Security controls: Documented. Production guidance recommends external identity, least-privilege roles/groups and signed session cookies. Operators must replace example JWT/cookie secrets and scope cookies to the correct environment. These are configuration requirements, not a compliance attestation. Scope: APIM 4.10 production authentication configuration. Source: https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/production-best-practices/authentication (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The current APIM chart source is in the API Management repository; the older standalone helm-charts repository points there. Use the versioned installation guide and a compatible chart release, database and search backend. Scope: Self-hosted APIM 4.10 installation guidance; chart repository moves independently. Source: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides/kubernetes (reviewed 2026-11-16). Deployment artifact: https://github.com/gravitee-io/gravitee-api-management/tree/master/helm. Artifact reference: master (moving branch; select a chart compatible with APIM 4.10). Supporting source: APIM chart relocation — https://github.com/gravitee-io/helm-charts.

- Minimum footprint / sizing: Documented. The APIM 4.10 guide gives the combined Portal/Console/REST API a baseline of 2 vCPU, 4 GB RAM and 20 GB disk. Gateways, analytics and configuration databases are additional; production HA recommends multiple nodes and traffic-dependent sizing. Scope: Self-hosted component baselines, not the total platform footprint or guaranteed throughput. Source: https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/gateway-resource-sizing-guidelines (reviewed 2026-11-16).

- License pricing: Documented. Gravitee APIM Community Edition is Apache-2.0 licensed. Enterprise Edition capabilities require a separate commercial license. Scope: Gravitee API Management Self-Hosted: software license terms; infrastructure and operating costs are separate. Source: https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Gravitee APIM 4.10.36 and supported 4.13.4 were released November 13, 2026. Plan separately for v2 API removal in October 2027 and the 2027 Alpine-to-Debian image transition. Scope: Gravitee APIM self-hosted 4.10 branch, with 4.13 support and migration context. Source: https://documentation.gravitee.io/apim/4.10/release-information/changelog/apim-4.10.x (reviewed 2026-11-18). Supporting source: 4.13.4 changelog — https://documentation.gravitee.io/apim/4.13/release-information/changelog/apim-4.13.x.







## Grist Self-Hosted

Relational spreadsheet platform for collaborative business data and configurable operational applications.

- Listing: https://launchinyourcloud.com/directory/grist/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for grist-core; Grist Labs sells an edition with additional features under separate terms.
- Licensing model: open-source
- Installation: Run the documented Grist server container and configure persistent storage, authentication and production settings.
- Architecture: Customer-operated Grist web service with document storage and configured authentication/storage services
- Operations: Customer manages authentication, access rules, document and metadata storage, backups, sandboxing and upgrades.
- Product website: https://www.getgrist.com/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The listing covers the self-hosted server and its configured edition. Hosted billing features and commercial additions are not automatically part of grist-core. External widgets, integrations and AI services require separate review. Grist v1.7.22 is the first numbered release whose Docker images include Node.js 22.23.4, fixing CVE-2026-111497 remote code execution through Brotli-compressed responses, removing trust for compromised eMudhra certificate authorities, and updating vulnerable dependencies. Images pulled since October 22 already included these fixes; otherwise upgrade to v1.7.22 or later and refresh the deployed image.

Apache License 2.0 for grist-core; Grist Labs sells an edition with additional features under separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Grist web service with document storage and configured authentication/storage services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- no-code-databases: Relational spreadsheet with linked tables, formulas, record views and access rules.

- internal-tools: Configurable data applications such as a team CRM combine linked tables, custom layouts and record access rules; advanced commercial features are separate.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.getgrist.com/install/grist-builder-edition/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.getgrist.com/install/grist-builder-edition/ (checked 2026-11-12). 


### Cloud deployment evidence

- Grist Builder Edition cloud installation (aws, azure): https://support.getgrist.com/install/grist-builder-edition/
  The project provides its self-hosted Builder Edition VM image through AWS and Azure Marketplace. Review the selected image, edition terms and authentication setup; this is not an assurance that every Marketplace component is under the grist-core license.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The project documents significant code contributions by French government organizations ANCT and DINUM alongside Grist Labs. Its public release history continues through v1.7.22 in October 2026, including a Node.js remote-code-execution fix and dependency security updates.

Reviewed 2026-11-16.

- Named institutional contributors and edition boundaries: https://github.com/gristlabs/grist-core

- Current Grist release history: https://github.com/gristlabs/grist-core/releases

- Grist v1.7.22 security release: https://github.com/gristlabs/grist-core/releases/tag/v1.7.22

### Sources

- Official installation and runtime: https://support.getgrist.com/self-managed/

- Upstream project and capabilities: https://github.com/gristlabs/grist-core

- Current upstream license: https://raw.githubusercontent.com/gristlabs/grist-core/main/LICENSE.txt

- Example internal CRM application: https://support.getgrist.com/lightweight-crm/

- Grist v1.7.22 security release: https://github.com/gristlabs/grist-core/releases/tag/v1.7.22

### Licensing sources

- https://raw.githubusercontent.com/gristlabs/grist-core/main/LICENSE.txt

### Infrastructure sources

- https://support.getgrist.com/self-managed/


### 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. OIDC sign-in is fully supported in the full edition with an activation key. Free activation keys are available only for qualifying users/organizations; configure the issuer, client and callback settings. Scope: Full self-managed Grist with activation; not an unconditional Community entitlement. Source: https://support.getgrist.com/install/oidc/ (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 self-managed guide documents container deployment, persistent document storage and authentication configuration. Full-edition activation and identity features must be distinguished from Community and the desktop app. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://support.getgrist.com/self-managed/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The self-hosted guide gives a known-good Linux-container configuration of 2 CPUs, 8 GB RAM and 20 GB disk for moderate workloads. Its much smaller template test is per-document evidence, not a host minimum; simultaneous documents and sandboxing affect capacity. HA requires full-edition activation and a separate design. Scope: Moderate-workload container guidance, not a 100-user/1-TB or HA guarantee. Source: https://support.getgrist.com/self-managed/ (reviewed 2026-11-20).

- License pricing: Documented. The v1.7.22 Community core is Apache-2.0. The full self-managed edition is a licensed application enabled by activation key, with additional governance/identity features and support; obtain the applicable full-edition terms rather than treating every feature as included in Community. Scope: Community source versus full self-managed edition; excludes infrastructure and optional services. Source: https://github.com/gristlabs/grist-core/blob/v1.7.22/LICENSE.txt (reviewed 2026-11-20). Supporting source: Self-hosted editions and activation — https://support.getgrist.com/self-managed/.

- Operating cost estimate: Not researched.

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







## HashiCorp Boundary Enterprise

Commercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.

- Listing: https://launchinyourcloud.com/directory/hashicorp-boundary-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Boundary Enterprise license required; HCP Boundary is a separate hosted service.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform architectures plus supported apt, yum or binary packages
- Architecture: Customer-operated Boundary controllers and workers with external PostgreSQL, KMS or HSM integration and PKI.
- Operations: Customer manages controllers, workers, PostgreSQL, KMS, PKI, networking, identity integrations, backups, upgrades and availability.
- Product website: https://www.hashicorp.com/en/products/boundary
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers self-managed Boundary Enterprise, not HCP Boundary. Production deployment requires multiple controllers and workers, an external PostgreSQL database, KMS or HSM-backed key management, TLS and a deliberate worker topology. Validate provider modules, identity integrations and recovery procedures before rollout. HCSEC-2026-54 covers CVE-2026-13303, a Vault credential-store SSRF issue. Fixed Enterprise builds are 1.0.2 and 0.21.6; upgrade the installed maintained branch and restrict credential-store network reachability.

Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features.

Boundary Enterprise runs persistent controller and worker services on customer virtual machines and depends on external PostgreSQL, key management and TLS infrastructure.


### Category fit

- identity-access-management: Provides identity-aware, policy-controlled access to infrastructure targets without exposing long-lived network credentials.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 


### Cloud deployment evidence

- Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment
  HashiCorp documents self-managed Boundary Enterprise architectures and Terraform deployments in customer AWS, Azure and Google Cloud environments. Customers operate controllers, workers, PostgreSQL and key management.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Boundary self-managed deployment: https://developer.hashicorp.com/boundary/docs/deploy/self-managed

- Boundary Validated Design deployment: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment

- Boundary pricing and editions: https://www.hashicorp.com/en/products/boundary/pricing

- HCSEC-2026-54: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932

### Licensing sources

- https://www.hashicorp.com/en/products/boundary/pricing

### Infrastructure sources

- https://developer.hashicorp.com/boundary/docs/deploy/self-managed

- https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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. Self-managed Enterprise deployment and pricing do not establish a current Marketplace offer matching this edition. HCP Boundary is a different operating model. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Boundary Enterprise pricing did not establish eligible software charges under the buyer’s cloud commitment agreement. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Single sign-on: Documented. Boundary supports OIDC through external providers such as Okta and Entra ID, plus separate password/LDAP methods. A primary auth method can create users on first login; this is not evidence of SCIM lifecycle synchronization. Scope: Self-managed Boundary identity methods. Source: https://developer.hashicorp.com/boundary/docs/authentication (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Boundary documents OIDC/LDAP and first-login account creation, but a self-managed Enterprise SCIM endpoint and deprovisioning semantics were not established. HCP SCIM is separate. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/boundary/docs/authentication (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Boundary Enterprise 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://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Security controls: Documented. The deployment design separates controller and worker paths with database and key-management dependencies. Configure TLS, network access and recovery, and protect credentials used for provisioning. Current advisory review: HCSEC-2026-54 covers CVE-2026-13303, a server-side request forgery issue in the Vault credential store. Upgrade to the applicable fixed or later Enterprise build and restrict credential-store egress. Scope: Boundary Enterprise deployment security Fixed in Boundary Enterprise 1.0.2 and 0.21.6.. Source: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment.

- Air-gapped operation: Sources checked — unresolved. The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation. Scope: Self-managed Boundary Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/boundary/docs/enterprise/automated-license-reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design provides Terraform deployment of Boundary controllers and workers in AWS, Azure or Google Cloud. PostgreSQL, key management and network configuration are required; this is not HCP Boundary. Scope: Self-managed Boundary Enterprise validated design. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Controllers, workers, PostgreSQL and KMS are separate components. Session concurrency and recording/egress requirements determine worker and storage capacity; 100 identities alone do not establish an HA sizing model. Scope: Boundary Enterprise architecture; workload capacity requires session metrics. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- License pricing: Documented. Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features. Scope: HashiCorp Boundary Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Specify concurrent sessions, recording retention, controller/worker topology, HA PostgreSQL and KMS. Data transfer/session volume and commercial entitlements remain unpriced. 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://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The vendor release API identifies 1.1.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-11-05. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/boundary/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/boundary/1.1.1+ent/.




### Security and lifecycle reviews

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

- HashiCorp Boundary Vault credential-store SSRF (security-advisory): HCSEC-2026-54 covers CVE-2026-13303, a server-side request forgery issue in the Vault credential store. Scope: Fixed in Boundary Enterprise 1.0.2 and 0.21.6. Conditions: Requires the affected Vault credential-store path and reachable network targets. Action: Upgrade to the applicable fixed or later Enterprise build and restrict credential-store egress. Source: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932; reviewed 2026-11-18.




## HashiCorp Consul Enterprise

Commercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/hashicorp-consul-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Consul Enterprise license required for the selected validated design.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform modules for AWS, Azure or Google Cloud
- Architecture: Customer-operated Consul server quorum and clients with provider load balancers, KMS, secrets and snapshot storage.
- Operations: Customer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.
- Product website: https://www.hashicorp.com/en/products/consul
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Consul Enterprise, not HCP Consul and not the separately licensed Community Edition. The validated designs require a commercial license and production security material, including TLS certificates, ACL configuration and gossip encryption. Protect bootstrap tokens and snapshot storage and validate the selected module release before deployment. HCSEC-2026-49 and 50 cover a health-check registration authorization bypass and a consul-k8s cross-namespace ACL binding-rule bypass. Fixed builds are Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.

Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement.

Consul Enterprise runs persistent server and client agents on customer infrastructure with consensus state, snapshots and network dependencies.


### Category fit

- backend-platforms: Provides service discovery, configuration, connectivity and service-mesh control for distributed application platforms.

- devops: Automates service networking, health discovery and policy across deployment environments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 


### Cloud deployment evidence

- Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform
  HashiCorp provides validated Terraform deployment paths for Consul Enterprise in customer AWS, Azure and Google Cloud environments. Customers manage the deployed cluster, security material and backups.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Deploy Consul Enterprise using Terraform on AWS, Azure and Google Cloud: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform

- Consul pricing and editions: https://www.hashicorp.com/en/products/consul/pricing

- HCSEC-2026-49: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914

- HCSEC-2026-50: https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915

### Licensing sources

- https://www.hashicorp.com/en/products/consul/pricing

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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 Enterprise pricing and Terraform deployment establish the licensed product, but not a current Consul Enterprise-specific Marketplace offer. HCP procurement is separate. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Consul Enterprise price/edition material did not establish qualifying Marketplace charges and commitment treatment for the buyer agreement. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. The OIDC authentication method requires self-managed Consul Enterprise 1.8.0+. It supports browser-based UI/CLI login through a configured IdP, with ACL tokens and claim mappings. Scope: Self-managed Consul Enterprise, not HCP account SSO. Source: https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Enterprise OIDC exchanges claims for ACL tokens; it does not establish a SCIM user/group lifecycle endpoint. HCP account SCIM was excluded. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Consul Enterprise 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://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Security controls: Documented. The Enterprise Terraform workflow configures cluster secrets and cloud permissions. Apply ACL, TLS/gossip, backup and key-management requirements rather than treating provisioning completion as a security review. Current advisory review: HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds. Scope: Consul Enterprise deployment controls Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.. Source: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform. Supporting source: HCSEC-2026-50 — https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915.

- Air-gapped operation: Sources checked — unresolved. The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation. Scope: Self-managed Consul Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/consul/docs/enterprise/license/reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design provides provider-specific Terraform deployment for Consul Enterprise on AWS, Azure and Google Cloud. Configure the licence, secrets, network access and snapshot storage before production use. Scope: Self-managed Enterprise validated Terraform deployment. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The design deploys a fault-tolerant Consul server cluster; service count, agent placement, traffic, mesh gateways and availability requirements determine total capacity. Human-user count does not size the service mesh. Scope: Consul topology and workload boundary. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- License pricing: Documented. Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement. Scope: HashiCorp Consul Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Specify service/agent count, mesh traffic, gateways and Enterprise server topology. Human users and 1 TB application data do not size a Consul service mesh. 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://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The vendor release API identifies 2.1.0+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-22. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/consul/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/consul/2.1.0+ent/.




### Security and lifecycle reviews

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

- HashiCorp Consul authorization-bypass updates (security-advisory): HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Scope: Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18. Conditions: Health-check registration permissions and Kubernetes component ACL binding rules determine exposure. Action: Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds. Source: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914; reviewed 2026-11-18. Supporting source: HCSEC-2026-50 — https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915.




## HashiCorp Nomad Enterprise

Commercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.

- Listing: https://launchinyourcloud.com/directory/hashicorp-nomad-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform modules where available or manual package and binary installation
- Architecture: Customer-operated Nomad server quorum and client nodes with persistent state, networking and workload drivers.
- Operations: Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.
- Product website: https://www.hashicorp.com/en/products/nomad
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.

Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support.

Production Nomad uses persistent server nodes for consensus and state plus client nodes that execute workloads on customer virtual machines.


### Category fit

- devops: Schedules and operates application, batch and system workloads across customer infrastructure.

- workflow-orchestration: Coordinates long-running services, batch jobs and parameterized workload execution through declarative job specifications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 


### Cloud deployment evidence

- Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment
  HashiCorp's Validated Design documents production Nomad deployment on customer AWS, Azure and Google Cloud infrastructure. The operator supplies the Enterprise license and manages the resulting cluster.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Nomad validated cloud deployment: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment

- Nomad pricing and editions: https://www.hashicorp.com/en/products/nomad/pricing

- HCSEC-2026-51: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929

- HCSEC-2026-52: https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930

- HCSEC-2026-53: https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931

### Licensing sources

- https://www.hashicorp.com/en/products/nomad/pricing

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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 Enterprise pricing and deployment material establishes licensed self-management, but not a current Nomad Enterprise-specific Marketplace offer. HCP/Vault offers were excluded. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Nomad Enterprise pricing did not establish offer-specific eligible charges against the buyer cloud agreement; infrastructure discounts are separate. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Single sign-on: Documented. Nomad documents OIDC SSO through external IdPs with ACL policies, roles and binding rules. Human and machine authentication are different flows; short-lived ACL tokens replace distributing static tokens. Scope: Self-managed Nomad Enterprise identity design. Source: https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Nomad OIDC maps identity claims to short-lived ACL tokens. A Nomad Enterprise SCIM lifecycle service was not established; HCP Terraform SCIM is a different product. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Nomad Enterprise 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://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- Security controls: Documented. The validated identity design requires appropriate ACL policies and mapped roles. Protect management tokens, configure TLS/gossip and snapshot recovery, and isolate workload client permissions from server administration. Current advisory review: HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths. Upgrade the installed maintained Enterprise branch to the listed fixed or later build. Scope: Nomad customer-managed cluster controls Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.. Source: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929 (reviewed 2026-11-18). Supporting source: Identity and access management — https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management. Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment. Supporting source: HCSEC-2026-52 — https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930. Supporting source: HCSEC-2026-53 — https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931.

- Air-gapped operation: Sources checked — unresolved. The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation. Scope: Self-managed Nomad Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/nomad/docs/enterprise/license/utilization-reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design documents customer-cloud Nomad installation on AWS, Azure and Google Cloud with servers, clients, networking and enterprise licensing. Review the design and pin the chosen deployment tooling before applying it. Scope: Self-managed Enterprise validated cloud design. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The cloud design separates voting/non-voting servers from workload clients across availability zones. Server count alone does not size user jobs, 1 TB application data, storage plugins or client failover capacity. Scope: Nomad cluster topology versus workload capacity. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- License pricing: Documented. Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support. Scope: HashiCorp Nomad Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 864.96/month. Six 4-vCPU/16-GiB server VMs follow the validated three-voting/three-non-voting design, with 50 GB gp3 each. This prices the control plane only; workload clients and their 1 TB data are unpriced. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Nomad Enterprise server control-plane subtotal; 100 identities do not size jobs, task concurrency or workload clients. Price applications and replicated workload storage separately.. 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-17). Supporting source: Product topology/sizing basis — https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment. Supporting source: Current AWS documentation: 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/.

- Release snapshot / cadence: Documented. The vendor release API identifies 2.1.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-29. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/nomad/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/nomad/2.1.1+ent/.




### Security and lifecycle reviews

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

- HashiCorp Nomad Enterprise October 2026 security updates (security-advisory): HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths. Scope: Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18. Conditions: Namespace permissions, dispatch payload writes, allocation migration, and symlink handling determine exposure. Action: Upgrade the installed maintained Enterprise branch to the listed fixed or later build. Source: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929; reviewed 2026-11-18. Supporting source: HCSEC-2026-52 — https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930. Supporting source: HCSEC-2026-53 — https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931.




## Hasura GraphQL Engine v2

GraphQL API engine that exposes connected databases through permission-aware application APIs.

- Listing: https://launchinyourcloud.com/directory/hasura-graphql-engine/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream open-source GraphQL Engine components. Default distributions can include separately licensed enterprise components; -ce images contain open-source components.
- Licensing model: open-source
- Installation: Deploy the documented v2 Docker Compose setup; select the versioned -ce image when only open-source components are required.
- Architecture: Customer-operated API engine with PostgreSQL metadata database and connected data sources
- Operations: Customer manages engine and metadata storage, database access, admin secrets, authorization, TLS, and coordinated engine/database upgrades.
- Product website: https://hasura.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

This listing is specifically for the self-operated v2 engine, not Hasura Cloud or DDN. Authentication webhooks, remote schemas, event handlers and database destinations can cross account boundaries. GraphQL Engine v2.51.6 and v2.50.9 fix source-catalog initialization and upgrades when PostgreSQL 15.15, 16.11, 17.7, or 18 and later enforce replica identity for INSERT ... ON CONFLICT DO UPDATE in a logical-replication publication. Upgrade GraphQL Engine before PostgreSQL. For older engine versions, the documented workaround is ALTER TABLE hdb_catalog.hdb_source_catalog_version REPLICA IDENTITY FULL on every data source, repeated whenever a new source is added.

Apache License 2.0 for upstream open-source GraphQL Engine components. Default distributions can include separately licensed enterprise components; -ce images contain open-source components. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated API engine with PostgreSQL metadata database and connected data sources. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. Coordinate PostgreSQL patch upgrades with the GraphQL Engine version. Older engines can break source-catalog initialization or logical replication after upgrading to PostgreSQL 15.15, 16.11, 17.7, or 18 and later.


### Category fit

- backend-platforms: Database-backed GraphQL API layer with authorization, subscriptions and configured remote actions. It does not supply a complete standalone application database or identity provider.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/azure-container-instances-postgres/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/google-kubernetes-engine-cloud-sql/ (checked 2026-11-12). 


### Cloud deployment evidence

- Hasura GraphQL Engine on Azure Container Instances (azure): https://hasura.io/docs/2.0/deployment/deployment-guides/azure-container-instances-postgres/
  The v2 project documentation deploys the GraphQL Engine container on Azure Container Instances with PostgreSQL. Review secrets, database access and production hardening; Hasura Cloud regions are not used as evidence.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Hasura GraphQL Engine on Google Kubernetes Engine (gcp): https://hasura.io/docs/2.0/deployment/deployment-guides/google-kubernetes-engine-cloud-sql/
  The v2 project documentation deploys the GraphQL Engine on GKE with Cloud SQL. This establishes application hosting in the customer project, not just connectivity to a Google-hosted database.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream v2 release stream includes current security maintenance. Hasura documents a long-running developer community, public community calls and community contributions around GraphQL Engine.

Reviewed 2026-11-10.

- Current GraphQL Engine release maintenance: https://github.com/hasura/graphql-engine/releases

- Public developer community and calls: https://hasura.io/help/

- GraphQL Engine contribution history: https://hasura.io/blog/call-for-open-source-contributions

### Sources

- Official installation and runtime: https://hasura.io/docs/2.0/deployment/deployment-guides/docker/

- Upstream project and capabilities: https://github.com/hasura/graphql-engine

- Current upstream license: https://raw.githubusercontent.com/hasura/graphql-engine/master/LICENSE

- Official image and -ce licensing distinction: https://hub.docker.com/r/hasura/graphql-engine/

- v2 capabilities and Community Edition: https://hasura.io/docs/2.0/index/

- Hasura v2.51.6 PostgreSQL upgrade-order fix: https://github.com/hasura/graphql-engine/releases/tag/v2.51.6

- Hasura v2.50.9 PostgreSQL upgrade-order fix: https://github.com/hasura/graphql-engine/releases/tag/v2.50.9

### Licensing sources

- https://raw.githubusercontent.com/hasura/graphql-engine/master/LICENSE

### Infrastructure sources

- https://hasura.io/docs/2.0/deployment/deployment-guides/docker/

- https://github.com/hasura/graphql-engine/releases/tag/v2.51.6

- https://github.com/hasura/graphql-engine/releases/tag/v2.50.9


### 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. Self-hosted Enterprise Console can integrate ADFS SAML through Dex from v2.25.0, with a valid license key. Console authentication is separate from GraphQL API JWT/webhook authorization and is not a CE entitlement. Scope: Hasura v2 Enterprise administrative Console, not every API client. Source: https://hasura.io/docs/2.0/enterprise/sso/adfs/ (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 v2 guide links an upstream Compose manifest with PostgreSQL metadata storage. Select the appropriate community/commercial image and set administrator/database credentials rather than exposing the defaults. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/docker/ (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/hasura/graphql-engine/master/install-manifests/docker-compose/docker-compose.yaml. Artifact reference: master v2 example (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The v2 production checklist and subscription-tuning guide require database connection/concurrency planning and CPU/memory monitoring, but do not establish a numeric whole-stack minimum. Query complexity, live subscriptions, metadata/source databases and replicas determine capacity. Old tutorial VM allocations or Cloud auto-scaling are not a current 100-user, 1 TB HA sizing guarantee. Scope: Hasura v2 production and tuning guidance; current workload-specific compute/storage sizing remains unconfirmed. Source: https://hasura.io/docs/2.0/deployment/production-checklist/ (reviewed 2026-11-20). Supporting source: v2 subscription saturation and performance tuning — https://hasura.io/docs/2.0/subscriptions/observability-and-performance/.

- License pricing: Documented. The v2.51.6 open-source GraphQL Engine core is Apache-2.0 licensed. Hasura v2 Enterprise has separate commercial entitlements; the official image distribution distinguishes the -ce variant from images that include Enterprise components. Enterprise Console SSO is not granted by the CE licence, and DDN/Cloud pricing is not a self-hosted v2 quote. Scope: GraphQL Engine v2 CE versus commercial image/features; not Hasura v3 DDN. Source: https://github.com/hasura/graphql-engine/blob/v2.51.6/LICENSE (reviewed 2026-11-20). Supporting source: Official image and CE variant distinction — https://hub.docker.com/r/hasura/graphql-engine/. Supporting source: Self-Hosted Enterprise v2 scope — https://hasura.io/docs/2.0/enterprise/overview/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v2.51.6, 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 hasura/graphql-engine release record; commercial editions and deployment packages may differ. Source: https://github.com/hasura/graphql-engine/releases/tag/v2.51.6 (reviewed 2026-11-14).







## HCL Digital Experience Cloud Native 9.5

Commercial web content and digital asset management platform deployed by Helm to customer-operated Kubernetes.

- Listing: https://launchinyourcloud.com/directory/hcl-digital-experience-cloud-native/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial HCL Digital Experience Cloud Native subscription measured by user sessions and associated production processing capacity.
- Licensing model: commercial-only
- Installation: Official HCL Digital Experience Helm chart on customer Amazon EKS, Microsoft AKS or Google GKE
- Architecture: Customer-operated Kubernetes deployment with persistent application, content and asset services plus external platform dependencies.
- Operations: Customer manages Kubernetes, storage, databases and integrations, ingress, certificates, capacity, backups, upgrades and version compatibility.
- Product website: https://www.hcl-software.com/digital-experience
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

Beginning with HCL DX 9.5 CF200, operator-based deployments are discontinued and Helm is the supported container method. Supported cloud Kubernetes deployments require x86-64 hardware, compatible Kubernetes and Helm versions, persistent storage and production sizing. HCL tests Amazon EKS, Microsoft AKS and Google GKE; exact storage and version support must be checked for the selected release.

Current HCL Digital Experience Cloud Native entitlements are commercial subscriptions. The User Session metric includes an associated production virtual-processing-capacity allowance; exact rights follow the order and License Information document.

The supported deployment runs persistent HCL DX containers on customer Kubernetes with persistent volumes and supporting stateful services. Helm is supported for CF200 and later.


### Category fit

- content-management: A web content management system with authoring, presentation templates, headless APIs and publishing workflows.

- digital-asset-management: Integrated digital asset management organizes, controls and reuses images, video and other web-ready assets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/ (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/ (checked 2026-11-17). 


### Cloud deployment evidence

- HCL Digital Experience on Amazon EKS (aws): https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/
  HCL documents deploying the entitled DX Helm chart to Amazon-managed Kubernetes in the customer's AWS environment.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- HCL Digital Experience on Microsoft Azure AKS (azure): https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/
  HCL's current support matrix explicitly lists Microsoft Azure AKS as a tested and supported full-container platform.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- HCL Digital Experience on Google GKE (gcp): https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/
  HCL's current support matrix explicitly lists Google GKE as a tested and supported full-container platform.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Current Kubernetes runtime and cloud support matrix: https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/

- AWS Marketplace Helm deployment: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/

- Azure Kubernetes Service Helm deployment: https://help.hcl-software.com/digital-experience/9.5/CF238/guide_me/howto/install/DeployOnAzure/

- Container deployment requirements and limitations: https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/

- HCL DX content management: https://www.help.hcl-software.com/digital-experience/9.5/CF239/get_started/product_overview/content_management/

- HCL DX digital asset management: https://www.help.hcl-software.com/digital-experience/9.5/CF239/get_started/product_overview/asset_management/

- User Session licensing: https://www.hcl-software.com/resources/license-agreements/user-session-licensing

### Licensing sources

- https://www.hcl-software.com/resources/license-agreements/user-session-licensing

### Infrastructure sources

- https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/

- https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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. HCL documents DX 9.5 Helm deployment through AWS Marketplace. Obtain the matching subscription and container access; licensing and image versions must match the selected cumulative fix. Scope: HCL DX 9.5 AWS Marketplace Helm route. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The AWS Marketplace installation guide does not establish qualifying fees or commitment treatment for the selected DX offer and buyer agreement. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Single sign-on: Sources checked — unresolved. The CF239 docs establish People Service OIDC and a DX/Leap SSO integration, but the complete primary DX authentication configuration and entitlement for this deployment were not established. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/extend_dx/integration/people_service/deployment/configuration/oidc_configuration/ (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. People Service documents LDAP synchronization limitations, not a DX-wide SCIM service. A supported SCIM endpoint and licence scope for the selected cumulative fix were not established. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/extend_dx/integration/people_service/limitations/ (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HCL Digital Experience Cloud Native 9.5 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://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Security controls: Documented. The Helm workflow requires image access, configured credentials and persistent service configuration. Restrict Kubernetes and registry permissions and use the matching deployment security guidance. Scope: DX Helm deployment access; not an attestation. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. The Helm installation requires entitled images and chart configuration; a supported complete offline licence, image/dependency transfer and update workflow was not established. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The Marketplace installation uses the HCL Helm chart with configured values, container images and persistent volumes. Review the matching CF requirements; the former Operator path is not the current Helm workflow. Scope: HCL DX 9.5 CF239 Helm installation. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The container requirements distinguish supported Kubernetes platforms, CPU architecture, persistence and component limitations. Size Portal, content and asset services separately for the selected cumulative fix. Scope: DX cloud-native CF239 requirements; topology-specific sizing. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/ (reviewed 2026-11-17).

- License pricing: Documented. Current HCL Digital Experience Cloud Native entitlements are commercial subscriptions. The User Session metric includes an associated production virtual-processing-capacity allowance; exact rights follow the order and License Information document. Scope: HCL Digital Experience Cloud Native 9.5: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hcl-software.com/resources/license-agreements/user-session-licensing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm Portal, content/asset components, cumulative-fix images, database/search/persistence and session-licence unit. A generic EKS fleet would omit required services and the HA design. 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://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/ (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. CF239-scoped deployment documentation and a separately resolved current compatibility matrix were reviewed. The latest entitled CF/chart/image bundle and precise release date require confirmation. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).







## Hyland OnBase On-Premise

Customer-hosted enterprise content and case platform for document-heavy business processes.

- Listing: https://launchinyourcloud.com/directory/onbase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial OnBase licenses and separately scoped modules
- Licensing model: commercial-only
- Installation: Vendor or partner-assisted on-premises installation
- Architecture: Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.
- Operations: Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.
- Product website: https://www.hyland.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers licensed OnBase on-premises deployments. Category memberships describe documented platform configurations and integrations, not separately included turnkey applications. Loan tracking, claims integrations and other service solutions need scope and licensing confirmation.

The selected OnBase on-premises product is commercially licensed. Its current on-premises terms restrict production copies and require applicable fees for additional environments and certain access; modules and integrations follow the contracted scope.

Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.


### Category fit

- document-management: Enterprise content repository with capture, document workflows and integration with business applications.

- records-management: Retention and destruction workflows for electronic documents; WorkView also supports tracking physical records.

- contract-management: Configurable WorkView contract applications and document workflows; confirm modules and implementation scope.

- financial-application-management: Loan-document tracking and integration with loan origination systems; this supports the document process rather than replacing a lending core.

- case-management: Configurable case applications connect case data, documents, tasks and approvals.

- correspondence-management: Configurable OnBase workflows can store and route correspondence documents with related case work; implementation is solution-specific.

- vendor-supplier-document-management: Vendor case records and supporting documents in WorkView and accounts-payable workflows; not a dedicated supplier-risk service.

- hr-employee-records-management: Employee-file access, applicant-document routing and employee onboarding/offboarding workflows.

- policy-procedure-management: Electronic policy distribution and policy/procedure sign-off workflows in the HR document-management scope.

- claims-management: Document capture and workflows integrated with insurance claims systems; not a replacement for claims adjudication software.

- workflow-automation: Content and case workflows with routing, rules and low-code WorkView applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 


### Cloud deployment evidence

- Hyland partner statement on customer-managed OnBase cloud deployments (aws, azure, gcp): https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/
  Hyland-authorized integration partner Reveille explicitly describes OnBase 18+ in customer-managed AWS, Azure and Google Cloud environments, separately from OnBase Cloud. This is the partner's compatibility statement, not a Hyland installation guide or cloud-support certification. Confirm the current OnBase release, Windows/database topology, licenses and vendor support agreement; Reveille itself is not required for self-hosting.
  Source type: partner-evidence; reviewed: 2026-11-12; vendor support: not-assessed. Versions: OnBase 18+ in partner statement; confirm current release.

- Hyland identification of Reveille as an authorized integration partner (aws, azure, gcp): https://www.hyland.com/en/partners/reveille
  Hyland identifies Reveille as an authorized build partner for OnBase and other Hyland platforms. This corroborates the source relationship, not an independent certification of every deployment listed by the partner; use its customer-managed-cloud statement together with OnBase installation and commercial requirements.
  Source type: partner-relationship; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- OnBase platform capabilities: https://www.hyland.com/en/solutions/products/onbase

- On-premises product terms: https://legal.hyland.com/pst-on-premise-multi-products

- WorkView business application examples: https://www.hyland.com/en/resources/articles/workview-product-overview

- HR files and policy sign-offs: https://www.hyland.com/en/resources/terminology/human-resources/document-management

- OnBase workflow routing: https://docs.hyland.com/r/OnBase/Workflow/Foundation-23.1/Workflow/Overview/Workflow-Overview

- Correspondence document integration: https://docs.hyland.com/r/OnBase/Application-Client-Connector/Foundation-24.1/Application-Client-Connector/Overview/Introduction

- Loan-document tracking solution: https://community.hyland.com/kb/articles/1332-hyland-services-loan-document-tracking

- Insurance claims integration case study: https://www.hyland.com/en/customers/p-c-insurer

### Licensing sources

- https://legal.hyland.com/pst-on-premise-multi-products

### Infrastructure sources

- https://legal.hyland.com/pst-on-premise-multi-products


### 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 Foundation 26.1 Web Client documents Integration for Single Sign-On and configuration of automatic login. Hyland identity-service authentication is also module-specific; confirm client coverage, identity-provider compatibility and licensed integrations for the selected solution. Scope: OnBase Foundation 26.1 Web Client configuration; not a blanket claim for every module. Source: https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Configuration/Web.config-Configuration/appSettings?contentId=stz0b9kK0lYB~c4sf1hbkA (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 Foundation 26.1 Web Server is delivered through vendor setup.exe/MSI installation media with documented interactive and silent configuration. Application Server installation is a prerequisite; no public cloud-provisioning template is established by this installer guide. Scope: Vendor-supplied OnBase Web Server installation media, not public IaC. Source: https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Installation/Installation/Running-the-Installer?contentId=6JGslGq~Cra0GizajFYkbA (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. Foundation 26.1 lists a 2.4-GHz dual-core minimum, 4 GB RAM for Web Server and 8 GB for 64-bit Application Server, with 16 GB recommended for each. These are dedicated-role requirements; database, files, other modules, HA and workload capacity are additional. Scope: OnBase Foundation 26.1 Web/Application role minima; not the complete solution. Source: https://docs.hyland.com/r/OnBase/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Foundation-26.1/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Part-6-Web/Application-Server-and-Core-Services-Hardware-Requirements/64-Bit-Server-Hardware-Requirements?contentId=UToZTDrd9HvkQpjb7tURJQ (reviewed 2026-11-20).

- License pricing: Documented. The current on-premises terms distinguish production, disaster-recovery and separately licensed non-production use. Confirm the purchased product/client/API permissions and environments in the agreement; these terms do not supply a public total price. Scope: OnBase on-premises terms v1.2, effective 2026-06-23; customer order may add conditions. Source: https://legal.hyland.com/pst-on-premise-multi-products (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Hyperscience Hypercell

Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/hyperscience/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard.
- 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://help.hyperscience.ai/deployment/docs/helm-chart
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor. Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds.

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

Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- correspondence-management: Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

- ai-tools: Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (checked 2026-11-19). 


### Cloud deployment evidence

- Helm Chart (AWS/GCP) (aws, gcp): https://help.hyperscience.ai/deployment/docs/helm-chart
  Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Kubernetes Installation Overview (azure): https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview
  Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Helm Chart (AWS/GCP): https://help.hyperscience.ai/deployment/docs/helm-chart

- Kubernetes Installation Overview: https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview

- hsk8s CLI (ECR/GAR): https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli

- Gov Mailrooms & Correspondence: https://www.hyperscience.ai/blog/the-trusted-ai-infrastructure-behind-modern-government/

- Hyperscience EULA: https://www.hyperscience.ai/legal-documents/eula/

- V44 Release Notes (2026-11-18): https://help.hyperscience.ai/docs/v44-release-notes

- Security Advisory (2026-10-30): https://help.hyperscience.ai/docs/security-advisory

- Helm Releases: https://help.hyperscience.ai/deployment/docs/news-and-release-notes

- Hypercell Brotli decoder remediation: https://help.hyperscience.ai/docs/security-advisory

### Licensing sources

- https://www.hyperscience.ai/legal-documents/eula/

### Infrastructure sources

- https://help.hyperscience.ai/deployment/docs/helm-chart

- https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The private-cloud deployment guide documents SP-initiated SAML federation using IdP metadata, attribute mapping and signed/encrypted assertion settings. Only one of SAML, OIDC, LDAP or Google authentication can be enabled. Confirm the application/chart version and licensed integration before rollout. Scope: Private-cloud/on-premises Hyperscience identity configuration. Source: https://help.hyperscience.ai/deployment/docs/saml.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 vendor supplies an entitled Helm chart and hsk8s tooling, with AWS/GCP values examples and separate application-image delivery. Pin chart and application versions independently; configure external secrets, database, storage and worker/GPU tiers. Sample image tags do not establish the current supported release. Scope: Commercial Hypercell Kubernetes distribution; entitled artifacts required. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (reviewed 2026-11-20). Deployment artifact: https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli. Artifact reference: Vendor-provided HS_HELM_CHART; choose compatible application/chart releases.

- Minimum footprint / sizing: Sources checked — unresolved. The VM guide requires at least 8 logical cores with a 1:4 CPU-to-GB-RAM ratio and documents throughput examples. These VM numbers do not establish the complete Helm/Kubernetes namespace, trainer, database and object-store footprint. Obtain current chart resource values and workload/HA sizing; ORCA GPU requirements are separate. Scope: VM baseline documented; selected Kubernetes production footprint unresolved. Source: https://help.hyperscience.ai/deployment/docs/infrastructure-requirements.md (reviewed 2026-11-20). Supporting source: Kubernetes dependencies and deployment boundary — https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview.md.

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

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

- Hypercell Brotli decoder remediation (security-advisory): The vendor documents CVE-2026-111497 and version-dependent PDF/HTTP response exposure. Scope: Hypercell v33.0–v44.0; the vendor lists fixes 44.0.2, 43.2.5, 42.3.19, 42.0.27, 41.0.39 and 40.0.39. Other or archived lines need an agreed upgrade path. Conditions: PDF decoding is an additional path in v42–v44; earlier listed versions have configured HTTP-response exposure. SaaS patching does not patch customer installations. Action: Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds. Source: https://help.hyperscience.ai/docs/security-advisory; reviewed 2026-11-19.




## IBM Cognos Analytics Certified Containers

Customer-managed enterprise reporting and analytics deployed by Helm to a Kubernetes cluster in the customer's cloud.

- Listing: https://launchinyourcloud.com/directory/ibm-cognos-analytics-certified-containers/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial, separately licensed Cognos Analytics Certified Containers entitlement.
- Licensing model: commercial-only
- Installation: Install IBM's entitled Cognos Analytics Helm chart on customer-managed Kubernetes
- Architecture: Customer-operated Kubernetes cluster running IBM Cognos containers with external databases, authentication, storage and ingress.
- Operations: Customer manages Kubernetes, databases, authentication, storage, ingress, capacity, backups and upgrades; IBM support scope varies by platform.
- Product website: https://www.ibm.com/products/cognos-analytics
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Cognos Analytics Certified Containers, not IBM-hosted or on-demand Cognos offerings. Installation requires an IBM entitlement key and registry access. Support on EKS, AKS, GKE and other non-OpenShift platforms is narrower than on Red Hat OpenShift and is focused on the Cognos software, certified images, Helm orchestration, deployment and updates.

Certified Containers are a separately licensed IBM product. Installation retrieves entitled images and Helm artifacts with an IBM entitlement key.

The product runs as persistent containerized services on a customer Kubernetes cluster and requires external stateful services, ingress and production capacity planning.


### Category fit

- data-analytics: Enterprise reporting, dashboards, governed analytics and data exploration delivered by customer-managed Cognos containers.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration (checked 2026-11-17). 


### Cloud deployment evidence

- Cognos Certified Containers on EKS, AKS and GKE (aws, azure, gcp): https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models
  IBM documents the certified Cognos containers on Amazon EKS, Microsoft AKS and Google GKE. Non-OpenShift support is narrower than the OpenShift delivery model.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Cognos Certified Containers on IBM Cloud Kubernetes Service (ibm): https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration
  IBM's Cognos ingress framework explicitly names IBM Cloud Kubernetes Service alongside EKS, AKS and GKE. The customer operates the cluster and external dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Cognos Analytics offerings: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings

- Certified Containers overview: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=containers-overview

- Container delivery support policy: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models

- Ingress configuration for named Kubernetes services: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration

- Installing and deploying Certified Containers: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers

### Licensing sources

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers

### Infrastructure sources

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=containers-overview

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers


### Buyer diligence


Research coverage: 12/12 fields (100%); 4 documented, 8 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. Entitled registry images and Helm installation are documented; a current Marketplace offer for this Certified Containers edition was not established. Cognos hosted offerings are separate. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Container entitlement and registry access do not establish qualifying Marketplace spend or contract-specific cloud credit eligibility. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Single sign-on: Documented. Cognos 12.1.x documents dynamic OpenID Connect namespaces with a configured supported IdP and administrative capabilities. Confirm the namespace/provider settings for the selected container deployment. Scope: Cognos 12.1.x identity configuration; not a Cloud-only entitlement. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=providers-creating-dynamic-namespace-in-manage-component (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The reviewed 12.1.x namespace guide supports LDAP/OIDC providers, but does not establish a Certified Containers SCIM endpoint and lifecycle operations. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=providers-creating-dynamic-namespace-in-manage-component (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed IBM Cognos Analytics Certified Containers 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://www.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).

- Security controls: Documented. IBM bulletin 7250395 identifies Certified Containers 12.1.0 vulnerabilities and names 12.1.1 as the fix. Check the deployed container release against current bulletins; this historical fix is not a claim that newer releases have no vulnerabilities. Scope: Certified Containers 12.1.0-specific security bulletin; historical affected/fixed scope. Source: https://www.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. Registry entitlement and Helm deployment alone do not establish the complete offline image, licence, dependency and update workflow for Certified Containers. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. IBM supplies entitled container images and Helm deployment for Certified Containers. Obtain the registry entitlement and configure ingress, persistent storage and the selected cluster; OpenShift and other Kubernetes platforms have different support boundaries. Scope: Cognos Analytics 12.1.x Certified Containers. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed container installation requires cluster, storage and deployment configuration, but did not establish a complete numerical HA sizing model for 100 users/1 TB, including reporting concurrency and auxiliary services. Scope: Certified Containers sizing; desktop/agent-only requirements excluded. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- License pricing: Documented. Certified Containers are a separately licensed IBM product. Installation retrieves entitled images and Helm artifacts with an IBM entitlement key. Scope: IBM Cognos Analytics Certified Containers: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Obtain the current entitled container bundle, report concurrency, HA services, content-store database, storage and licence metric. User count and data volume do not size reporting/AI dependencies. 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://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. IBM identifies container release-specific fixes, including 12.1.0 to 12.1.1 remediation, but the reviewed public records did not establish the latest entitled container/chart bundle and publication date. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Cognos Certified Containers 12.1.0 fixes available (security-advisory): IBM bulletin 7250395 identifies PostgreSQL JDBC and information-disclosure vulnerabilities in Certified Containers 12.1.0, with 12.1.1 named as the fix. Scope: IBM bulletin published 2025-11-07 for Certified Containers 12.1.0; not a claim that every newer Cognos release or deployment is affected. Conditions: Exposure depends on the affected components and CVE-specific prerequisites in the bulletin. The reviewed record does not establish the current entitled container bundle. Action: Check the installed container version and current IBM bulletins. For affected 12.1.0 deployments, obtain the designated fixed or later supported bundle and follow the vendor upgrade procedure. Source: https://www.ibm.com/support/pages/node/7250395; reviewed 2026-11-17.




## IBM Planning Analytics Cartridge

Licensed self-managed planning, budgeting and multidimensional analytics cartridge.

- Listing: https://launchinyourcloud.com/directory/ibm-planning-analytics/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: ibm, aws, azure, gcp
- 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: Kubernetes manifests
- Architecture: Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/ibm-cloud-docs/cloud-pak-data
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current Software Hub 5.4 guidance provides an application-specific install-components workflow and explicitly supports IBM Cloud, AWS, Azure and Google Cloud platform installations. Keep the platform/cartridge release aligned and verify permitted storage. The older Azure PDF is historical background; Local, SaaS, TM1 and cartridge versions and licences are separate.

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

Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Licensed self-managed planning, budgeting and multidimensional analytics cartridge.

### Deployment boundaries


- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 


### Cloud deployment evidence

- Application deployment guidance (ibm, aws, azure, gcp): https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing
  Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage. Current Software Hub 5.4 guidance provides an application-specific install-components workflow and explicitly supports IBM Cloud, AWS, Azure and Google Cloud platform installations. Keep the platform/cartridge release aligned and verify permitted storage. The older Azure PDF is historical background; Local, SaaS, TM1 and cartridge versions and licences are separate.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Additional reviewed source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing

- IBM Cloud CP4D Services: https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md

- Azure ARO PA Guide (PDF): https://cp4dazuremarketplacedoc.blob.core.windows.net/ibmcp4dazuremarketplace/CP4D_MS_ARO_Deployment_Guide.pdf

- PA Pricing & CP4D Cartridge: https://www.ibm.com/products/planning-analytics/pricing

- CP4D Docs Commits: https://github.com/ibm-cloud-docs/cloud-pak-data/commits/master

- PA CASE Index (v5.4.5): https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml

- PA CASE Commits: https://github.com/IBM/cloud-pak/commits/master/repo/case/ibm-planning-analytics

- Current Software Hub cloud installation environments: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=cluster-installing-red-hat-openshift

- License information for IBM Software Hub 5.4 and related services: https://www.ibm.com/support/pages/node/7275162/

### Licensing sources

- https://www.ibm.com/products/planning-analytics/pricing

### Infrastructure sources

- https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing


### 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. The reviewed Software Hub cartridge installation context does not establish its exact user SSO configuration. Separate Planning Analytics Cloud IBMid and Advanced Certified Containers OIDC guides apply to different offerings; confirm the cartridge release, platform/user mapping and configured provider before transferring those claims. Scope: Planning Analytics cartridge on Software Hub; selected-edition user federation remains unconfirmed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (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. IBM publishes a CASE package index for Planning Analytics, separate from Local and SaaS releases. Use the application-specific install-components workflow and keep the cartridge and Software Hub refresh aligned. Scope: Planning Analytics CASE package metadata; select a compatible release and licensed image source. Source: https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml (reviewed 2026-11-19). Deployment artifact: https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml. Artifact reference: master (moving CASE package index).

- Minimum footprint / sizing: Sources checked — unresolved. Software Hub/OpenShift platform requirements are additional to the Planning Analytics cartridge and model/data resources. A complete current cartridge-specific CPU/RAM/storage and HA baseline was not verified from accessible material; standalone/TM1 or vendor-hosted sizing must not be substituted. Scope: Planning Analytics cartridge current full production sizing remains unconfirmed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Jedox Unmanaged Private Cloud

Commercial customer-operated planning, consolidation and business-reporting platform.

- Listing: https://launchinyourcloud.com/directory/jedox/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Vendor-provided Jedox Helm chart and persistent services on customer Azure Kubernetes 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://knowledgebase.jedox.com/jedox/cloud/unmanaged-private-cloud.htm
- 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's tested Azure deployment is distinct from Jedox SaaS. General multientity planning does not establish a packaged private-equity workflow. Validate the documented Kubernetes, gateway, storage and licence requirements for the selected chart.

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

Vendor-provided Jedox Helm chart and persistent services on customer Azure Kubernetes infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Commercial customer-operated planning, consolidation and business-reporting platform.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://knowledgebase.jedox.com/jedox/cloud/unmanaged-private-cloud.htm (checked 2026-11-19). 


### Cloud deployment evidence

- Unmanaged Private Cloud (azure): https://knowledgebase.jedox.com/jedox/cloud/unmanaged-private-cloud.htm
  Vendor-provided Jedox Helm chart and persistent services on customer Azure Kubernetes infrastructure. The vendor's tested Azure deployment is distinct from Jedox SaaS. General multientity planning does not establish a packaged private-equity workflow. Validate the documented Kubernetes, gateway, storage and licence requirements for the selected chart.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Unmanaged Private Cloud: https://knowledgebase.jedox.com/jedox/cloud/unmanaged-private-cloud.htm

- Jedox Licenses: https://knowledgebase.jedox.com/jedox/licenses.htm

- Release Notes: https://knowledgebase.jedox.com/jedox/release-notes.htm

- Support Lifecycle: https://knowledgebase.jedox.com/jedox/support-lifecycle.htm

### Licensing sources

- https://knowledgebase.jedox.com/jedox/licenses.htm

### Infrastructure sources

- https://knowledgebase.jedox.com/jedox/cloud/unmanaged-private-cloud.htm


### 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: Edition-dependent. Jedox documents native SAML2 with configured SP/IdP metadata, user/group mapping and authentication versus authorisation modes, and requires purchasing the service. Confirm availability and secure configuration for the contracted Unmanaged Private Cloud release; hosted/desktop identities and every client are not automatically equivalent. Scope: Jedox user SAML service; purchased entitlement and Unmanaged deployment confirmation required. Source: https://knowledgebase.jedox.com/jedox/security/saml.htm (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 Unmanaged Private Cloud guide uses an entitled OCI-registry Helm chart, vendor-provided credentials and a separately selected Jedox platform version. Configure values, storage, database, ingress/TLS and secrets; chart and application versions are explicitly different and customer Kubernetes operations remain required. Scope: Jedox Unmanaged Private Cloud licensed Helm deployment. Source: https://knowledgebase.jedox.com/jedox/cloud/deploy-unmanaged-private-cloud.htm (reviewed 2026-11-21). Deployment artifact: https://knowledgebase.jedox.com/jedox/cloud/deploy-unmanaged-private-cloud.htm. Artifact reference: Current vendor Unmanaged deployment guide; chart/platform versions selected separately.

- Minimum footprint / sizing: Sources checked — unresolved. The Unmanaged guide requires customer Kubernetes and configurable resources but does not establish a complete quantitative production baseline for this deployment. The separate Jedox Cloud sizing tables describe vendor-provisioned SaaS resources; do not apply them as a guaranteed Unmanaged footprint for models, users and HA. Scope: Jedox Unmanaged Private Cloud complete workload sizing remains unconfirmed. Source: https://knowledgebase.jedox.com/jedox/cloud/deploy-unmanaged-private-cloud.htm (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Jenkins

Automation server for building, testing and delivering software through configured pipelines.

- Listing: https://launchinyourcloud.com/directory/jenkins/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses.
- Licensing model: open-source
- Installation: Run the official Jenkins Docker image or supported server package and attach appropriately isolated build agents.
- Architecture: Customer-operated Jenkins controller and build agents with persistent configuration
- Operations: Customer manages controller and agents, plugins, secrets, job permissions, storage, backups and security updates.
- Product website: https://www.jenkins.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Pipeline code, agents and plugins can access external source hosts, registries and deployment targets. A controller installed in an account does not contain every pipeline integration. Jenkins weekly 2.591 enables Content Security Policy enforcement on the Jenkins UI by default. Test installed plugins and custom UI integrations before adopting this weekly release; compatibility is tracked upstream. Administrators can use report-only mode while resolving incompatibilities, but disabling enforcement removes the protection.

MIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Jenkins controller and build agents with persistent configuration. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- devops: Automation server for continuous integration, build, test and delivery pipelines; agents and plugins provide workload-specific integrations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/developer/jenkins/configure-on-linux-vm (checked 2026-11-12). 


### Cloud deployment evidence

- Jenkins installation on AWS (aws): https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/
  The Jenkins project documents installing the Jenkins server on a customer EC2 instance, not merely deploying build output to AWS.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Jenkins installation on an Azure Linux VM (azure): https://learn.microsoft.com/en-us/azure/developer/jenkins/configure-on-linux-vm
  Microsoft documents installing Jenkins on an Ubuntu VM in the customer subscription. Harden public access and review the current Jenkins and Java versions rather than copying old version pins.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Jenkins publishes community governance, contributor recognition and a release changelog updated in November 2026; these show sustained maintenance and community participation.

Reviewed 2026-11-10.

- Project governance: https://www.jenkins.io/project/governance/

- Current release changelog: https://www.jenkins.io/changelog/

- Community contributor recognition: https://www.jenkins.io/

### Sources

- Official installation and runtime: https://www.jenkins.io/doc/book/installing/docker/

- Upstream project and capabilities: https://github.com/jenkinsci/jenkins

- Current upstream license: https://www.jenkins.io/license/

- Jenkins weekly 2.591 release: https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.591

- Jenkins CSP default and upgrade guidance: https://github.com/jenkinsci/jenkins/pull/27727

### Licensing sources

- https://www.jenkins.io/license/

### Infrastructure sources

- https://www.jenkins.io/doc/book/installing/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: Documented. The security guide documents delegating authentication to an external identity provider using SAML/OIDC. The relevant plugins are not necessarily installed; match supported plugin/controller versions and configure authorization separately. Scope: Jenkins plugin-based security realm; not automatic core federation. Source: https://www.jenkins.io/doc/book/security/managing-security/ (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 installation guide identifies the official Jenkins image and persistent controller home. Build agents, privileged Docker access, plugins and workload resources require a separate security/capacity plan. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://www.jenkins.io/doc/book/installing/docker/ (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/jenkins/jenkins. Artifact reference: select an LTS or weekly versioned image tag.

- Minimum footprint / sizing: Documented. The guide lists 256 MB RAM and 1 GB disk as basic minima, with 10 GB suggested for Docker. A small team is recommended 4 GB+ RAM and 50 GB+ disk; build-agent resources are separate. Scope: Controller baseline, not total CI/build infrastructure. Source: https://www.jenkins.io/doc/book/installing/docker/ (reviewed 2026-11-14).

- License pricing: Documented. Jenkins core is MIT licensed. Plugins and bundled components have their own licences; commercial distributions, support, agents and infrastructure are separate costs. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/jenkinsci/jenkins/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is jenkins-2.591, 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 jenkinsci/jenkins release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.591 (reviewed 2026-11-17).







## JetBrains YouTrack Server

Customer-hosted project and issue management application from JetBrains.

- Listing: https://launchinyourcloud.com/directory/youtrack-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary YouTrack Server subscription; a limited free-user tier is available
- Licensing model: commercial-only
- Installation: Official YouTrack Docker image and Server installation documentation
- Architecture: Persistent Docker server deployment with mounted application data, configuration, logs and backup directories.
- Operations: Customer manages Docker/server resources, persistent data, backups, TLS/network configuration and upgrades.
- Product website: https://www.jetbrains.com/youtrack/
- 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 selects YouTrack Server. Free user allowances do not make the application open source, and each installation requires its own license. Review optional integrations and AI services separately from the self-hosted project-tracking deployment.

YouTrack Server is proprietary subscription software, including when used within its free-user allowance. The Server agreement and selected plan determine install rights, updates and user/agent entitlements.

Persistent Docker server deployment with mounted application data, configuration, logs and backup directories.


### Category fit

- project-management: Task and issue tracking with Scrum/Kanban boards, planning and progress reporting for project teams.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 


### Cloud deployment evidence

- YouTrack Server Kubernetes deployment on named cloud services (aws, azure, gcp, oci): https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html
  JetBrains names Amazon EKS, Azure Kubernetes Service, Oracle Container Engine for Kubernetes and Google Kubernetes Engine for YouTrack Server, with a worked GKE deployment. The instructions deploy a single YouTrack node with persistent volumes; multi-node application installations are not supported. Check the current image, license, storage and backup requirements rather than treating Kubernetes as application clustering.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official server installation and updates: https://www.jetbrains.com/help/youtrack/server/installation-and-upgrade.html

- Docker deployment and persistent directories: https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html

- Project-management functionality: https://www.jetbrains.com/youtrack/features/agile_project_management.html

- Server software subscription agreement: https://www.jetbrains.com/legal/docs/youtrack/subscription/

- Server/free-tier license scope: https://www.jetbrains.com/youtrack/buy/?section=server&with-helpdesk=true

### Licensing sources

- https://www.jetbrains.com/legal/docs/youtrack/subscription/

- https://www.jetbrains.com/youtrack/buy/?section=server&with-helpdesk=true

### Infrastructure sources

- https://www.jetbrains.com/help/youtrack/server/installation-and-upgrade.html

- https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The Server SAML 2.0 module configures YouTrack as a service provider for an external identity provider. Configure metadata, certificate trust and callback URLs; login-time user/group updates differ from separately configured SCIM provisioning. Scope: YouTrack Server 2026.2 user authentication, not a Cloud-only claim. Source: https://www.jetbrains.com/help/youtrack/server/saml-authentication-module.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. JetBrains distributes YouTrack Server as an official Docker image for evaluation and production. Configure persistent data/conf/log/backup directories and use a selected versioned image. Scope: YouTrack Server 2026.2 installation guide. Source: https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/jetbrains/youtrack. Artifact reference: versioned image tag must be selected.

- Minimum footprint / sizing: Documented. The Server 2026.2 guide states 1.5 GB minimum RAM with JVM minimums of 1,024 MB heap and 250 MB Metaspace. Storage guidance is roughly 1 GB per 5,000 issues before attachment variation. Database growth and transactions drive sizing; this is not a 1-TB HA topology. Scope: Upstream Server sizing guidelines; issue and attachment workload are material. Source: https://www.jetbrains.com/help/youtrack/server/youtrack-supported-environments.html (reviewed 2026-11-20).

- License pricing: Documented. The current Server license guide grants free use for up to ten users and three helpdesk agents. New commercial purchases from June 23, 2026 use annual user-pack subscriptions; earlier perpetual licenses have different terms. Each installation needs its own license; confirm the current pack price and renewal terms. Scope: Current Server licensing; historical perpetual-license and Cloud pricing are separate. Source: https://www.jetbrains.com/help/youtrack/server/manage-youtrack-server-license.html (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## JFrog Artifactory Self-Hosted

Universal artifact repository installed on Kubernetes clusters or servers you operate.

- Listing: https://launchinyourcloud.com/directory/jfrog-artifactory-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source Artifactory OSS; commercial Pro X, Enterprise X and Enterprise+ editions.
- Licensing model: open-source
- Installation: Helm chart, Docker or Docker Compose, or native OS package or archive
- Architecture: Customer-operated Artifactory service with persistent filestore and database.
- Operations: Customer operates the cluster or servers, database, filestore, backups, upgrades and availability configuration.
- Product website: https://jfrog.com/artifactory/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers self-hosted Artifactory, not JFrog SaaS. Edition capabilities differ substantially: Artifactory OSS is limited and does not include cloud object storage, while high availability and broader repository, security and platform capabilities require the applicable commercial entitlement. Production deployments should use an external PostgreSQL database and durable filestore. The separate Amazon ECS path is single-node, limited to 16 vCPUs and cannot connect to Xray or Distribution. CVE-2026-82329 is a critical unauthenticated authentication bypass under default configuration. JFrog lists fixed builds across maintained branches, including 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21; move to a fixed or later supported build.

JFrog publishes Artifactory OSS as an open-source edition and separately sells proprietary self-managed Pro X, Enterprise X and Enterprise+ subscriptions. Other community editions have different capability limits.

Artifactory runs as server or container workloads with persistent database and filestore dependencies; the listed Helm path uses customer-operated Kubernetes infrastructure.


### Category fit

- devops: Artifact, package and container registry for software delivery pipelines.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.jfrog.com/installation/docs/helm-charts (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.jfrog.com/installation/docs/helm-charts (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.jfrog.com/installation/docs/helm-charts (checked 2026-11-17). 


### Cloud deployment evidence

- Artifactory Helm installation on EKS, AKS and GKE (aws, azure, gcp): https://docs.jfrog.com/installation/docs/helm-charts
  JFrog's current Artifactory Helm guide explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as cluster types and documents installation into the customer's cluster. Provider storage, database, ingress and support details vary by edition.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Artifactory installation with Helm charts: https://docs.jfrog.com/installation/docs/helm-charts

- Artifactory installation methods and Amazon ECS limits: https://docs.jfrog.com/installation/docs/installing-artifactory

- Self-managed edition feature comparison: https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds

- JFrog open-source offerings: https://jfrog.com/community/open-source/

- JFrog security advisories: https://docs.jfrog.com/releases/docs/jfrog-security-advisories

- Artifactory release notes: https://docs.jfrog.com/releases/docs/artifactory-release-notes

### Licensing sources

- https://jfrog.com/community/open-source/

- https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds

### Infrastructure sources

- https://docs.jfrog.com/installation/docs/helm-charts

- https://docs.jfrog.com/installation/docs/installing-artifactory


### 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: Edition-dependent. The self-hosted subscription agreement explicitly permits procurement through supported cloud marketplaces, with fees and terms in the offer/order form. This is software procurement, not proof that a SaaS offer deploys in the buyer account. Scope: Self-hosted subscription procurement. Source: https://jfrog.com/self-hosted-terms-and-conditions-10-01-2024/ (reviewed 2026-11-17).

- Cloud commitment eligibility: Edition-dependent. JFrog states approved cloud Marketplace purchases can draw down committed spend. Obtain confirmation for the self-hosted offer and buyer agreement; this is a conditional procurement statement, not universal credit eligibility. Scope: JFrog Marketplace purchasing; provider contract and selected offer govern. Source: https://jfrog.com/cloud/ (reviewed 2026-11-17). Supporting source: Self-hosted Marketplace contracting — https://jfrog.com/self-hosted-terms-and-conditions-10-01-2024/.

- Single sign-on: Edition-dependent. SAML SSO is included from Pro X, including Enterprise X and Enterprise+; it is excluded from the non-commercial editions in the reviewed matrix. Scope: Self-managed Artifactory edition matrix. Source: https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds (reviewed 2026-11-17). Supporting source: SAML configuration — https://docs.jfrog.com/administration/docs/saml-sso.

- SCIM provisioning: Edition-dependent. SCIM identity management is included in Enterprise X and Enterprise+, and excluded from Pro X and non-commercial editions. The API uses the Access SCIM v2 endpoint and a restricted identity-management token. Scope: Self-managed Enterprise X / Enterprise+. Source: https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds (reviewed 2026-11-17). Supporting source: SCIM endpoint and token permissions — https://docs.jfrog.com/administration/docs/scim.

- Compliance attestations: Sources checked — unresolved. The reviewed JFrog Artifactory Self-Hosted 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.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds (reviewed 2026-11-17).

- Security controls: Documented. The edition matrix distinguishes LDAP/RBAC from paid SAML, identity management, HA and scanning features. Xray and Advanced Security are separately entitled capabilities; do not assume the free Artifactory distribution includes them. Current advisory review: CVE-2026-82329 is a critical unauthenticated authentication bypass affecting default-configured Artifactory deployments. Upgrade to the fixed or later supported build for the installed branch and review administrative access. Scope: Self-managed component and feature entitlements; not an attestation JFrog lists fixed builds 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21 across maintained branches.. Source: https://docs.jfrog.com/releases/docs/jfrog-security-advisories (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds.

- Air-gapped operation: Edition-dependent. Artifactory 7.77+ documents an air-gap setting and offline entitlement-file workflow. Obtain and renew the correct entitlement files and stage all dependencies; the 14-day license grace period can end in service disruption. Scope: Licensed self-managed air-gap configuration. Source: https://docs.jfrog.com/installation/docs/configure-jfrog-platform-in-an-air-gapped-environment (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. JFrog supplies Helm installation paths for EKS, AKS and GKE. Configure master/join keys, persistent storage and the database, and pin compatible chart/application versions rather than treating Helm defaults as production sizing. Scope: Self-managed Artifactory Helm installation. Source: https://docs.jfrog.com/installation/docs/helm-charts (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Artifactory sizing is based on active clients: the baseline starts at 4 cores/6 GB RAM for up to 20 clients, rising to 8 cores/18 GB for 101–200 clients. Database, HA, Xray and storage are additional sizing decisions. Scope: Artifactory active-client matrix; users are not necessarily simultaneous clients. Source: https://docs.jfrog.com/installation/docs/hardware-sizing-matrix (reviewed 2026-11-17).

- License pricing: Documented. JFrog publishes Artifactory OSS as an open-source edition and separately sells proprietary self-managed Pro X, Enterprise X and Enterprise+ subscriptions. Other community editions have different capability limits. Scope: JFrog Artifactory Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://jfrog.com/community/open-source/ (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Determine active artifact clients, package traffic, HA edition, database/filestore design and whether Xray/Workers are included. A 100-person headcount does not determine concurrent repository clients or scanning load. 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.jfrog.com/installation/docs/hardware-sizing-matrix (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The reviewed current self-managed Artifactory release is 7.173.21. Older maintained branches have separate CVE-2026-82329 fixed builds; verify the selected branch before upgrading. Scope: JFrog Artifactory self-managed release notes. Source: https://docs.jfrog.com/releases/docs/artifactory-release-notes (reviewed 2026-11-18). Supporting source: Self-managed lifecycle policy — https://docs.jfrog.com/releases/docs/artifactory-end-of-life.




### Security and lifecycle reviews

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

- JFrog Artifactory unauthenticated authentication bypass (security-advisory): CVE-2026-82329 is a critical unauthenticated authentication bypass affecting default-configured Artifactory deployments. Scope: JFrog lists fixed builds 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21 across maintained branches. Conditions: The vendor identifies default configuration as affected; exact branch applicability follows the advisory matrix. Action: Upgrade to the fixed or later supported build for the installed branch and review administrative access. Source: https://docs.jfrog.com/releases/docs/jfrog-security-advisories; reviewed 2026-11-18.




## Jira Service Management Data Center

Commercial self-managed IT service management platform deployed on customer-operated infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/jira-service-management-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based Jira Data Center installation
- Architecture: Single-node or clustered Jira Service Management application nodes with an external database, load balancer, shared home, indexes and optional dedicated nodes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, email, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/jira/service-management/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Jira Service Management Data Center, not Atlassian Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Service Management Data Center versions before the fixed 5.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.

Jira Service Management Data Center runs persistent Jira application services with durable database, shared-home and local-index storage.


### Category fit

- customer-support: Provides self-managed service desks, request portals, queues, knowledge integration and service-management workflows.

- devops: Supports IT service management, incident response, change coordination and development-to-operations workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html (checked 2026-11-16). 


### Cloud deployment evidence

- Jira Service Management Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html
  Atlassian documents Jira Service Management Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Install Jira Data Center: https://confluence.atlassian.com/security/installing-jira-data-center-1409092898.html

- Run Jira Service Management Data Center on Kubernetes: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html

- Jira Service Management Data Center architecture: https://confluence.atlassian.com/security/jira-service-management-data-center-architecture-and-infrastructure-options-1409093042.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian product-specific end-of-life and purchase eligibility: https://www.atlassian.com/licensing/data-center-end-of-life

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

### Infrastructure sources

- https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html

- https://confluence.atlassian.com/security/jira-service-management-data-center-architecture-and-infrastructure-options-1409093042.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 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 Data Center SSO guide explicitly covers Jira Service Management 5.15+. SAML login can include customer-portal logins when enabled; application access remains separately configured. Scope: Jira Service Management Data Center 5.15+; not Atlassian Guard cloud customer provisioning. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16).

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Jira Service Management Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The vendor’s 11.3.x extra-large benchmark uses three r5.8xlarge application nodes, 30 GB Java heap per node and a separate db.m6i.4xlarge PostgreSQL 16.9 database in AWS ap-southeast-2. Its dataset includes about 3.1 million issues and 6,471 agents. This is a test configuration, not a universal minimum or a performance/cost guarantee. Scope: JSM 11.3.x extra-large benchmark; representative workload sizing remains necessary. Source: https://confluence.atlassian.com/servicemanagement/jira-service-management-11-3-x-long-term-support-release-performance-report-1689289059.html (reviewed 2026-11-16).

- License pricing: Documented. New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies. Scope: Jira Service Management Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 11.3.13, released 2026-11-05. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/jira-servicedesk.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/SERVICEDESK/JIRA+Service+Management+11.3.x+release+notes.




### Security and lifecycle reviews

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

- Data Center purchase restrictions and 2029 retirement (lifecycle): Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window. Scope: Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement. Conditions: Existing-customer status and the purchased product determine eligibility. Action: Confirm purchase eligibility, migration timing and any written exception before evaluation. Source: https://www.atlassian.com/licensing/data-center-end-of-life; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




## Jira Software Data Center

Commercial self-managed Jira Software edition deployed on customer-operated cloud or Kubernetes infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/jira-software-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation
- Architecture: Single-node or clustered Jira application nodes with an external database, load balancer, shared home, local indexes and optional dedicated nodes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/jira/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Jira Software Data Center, not Jira Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained, so they are not listed as current install methods. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Software Data Center versions before the fixed 9.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.

Jira Data Center runs persistent application nodes with durable database, shared-home and index storage; managed Kubernetes supplies the cluster control plane but not a serverless application runtime.


### Category fit

- project-management: Provides self-managed issue, project, planning and work-tracking capabilities for enterprise teams.

- devops: Supports software-delivery planning, issue tracking, release coordination and integrations with development toolchains.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html (checked 2026-11-16). 


### Cloud deployment evidence

- Jira Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html
  Atlassian documents Jira Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Atlassian supports the product and Helm chart, but not the underlying Kubernetes platform.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Install Jira Data Center: https://confluence.atlassian.com/security/installing-jira-data-center-1409092898.html

- Run Jira Data Center on Kubernetes: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html

- Jira Data Center architecture and infrastructure: https://confluence.atlassian.com/security/jira-data-center-architecture-and-infrastructure-options-1409092890.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian product-specific end-of-life and purchase eligibility: https://www.atlassian.com/licensing/data-center-end-of-life

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

### Infrastructure sources

- https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html

- https://confluence.atlassian.com/security/jira-data-center-architecture-and-infrastructure-options-1409092890.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 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. Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Jira Software 8.15+; authentication does not assign application access or permissions. Scope: Jira Software 8.15+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16). Supporting source: OIDC product/version scope — https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html.

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Jira Software Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The installation guide, last modified in 2021, gives a multicore server with 8 GB available RAM for 100 projects, 1,000–5,000 issues and 100–200 users. This is a legacy small-installation example, not a current Data Center cluster minimum; size production nodes, supported database and storage separately. Scope: Legacy small-installation example; not a current Data Center production sizing recommendation. Source: https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.html (reviewed 2026-11-16).

- License pricing: Documented. New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies. Scope: Jira Software Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 11.3.13, released 2026-11-05. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/jira-software.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+11.3.x+release+notes.




### Security and lifecycle reviews

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

- Data Center purchase restrictions and 2029 retirement (lifecycle): Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window. Scope: Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement. Conditions: Existing-customer status and the purchased product determine eligibility. Action: Confirm purchase eligibility, migration timing and any written exception before evaluation. Source: https://www.atlassian.com/licensing/data-center-end-of-life; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




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




## Keycloak Self-Hosted

Identity and access management for application sign-on, federation and authorization.

- Listing: https://launchinyourcloud.com/directory/keycloak/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source project; commercial support/distribution arrangements are separate
- Licensing model: open-source
- Installation: Official server/container distribution or Kubernetes Operator; configure production database and TLS.
- Architecture: Customer-operated identity server, database and optional clustered caches
- Operations: Customer manages identity-server availability, configuration, updates, database and backups.
- Product website: https://www.keycloak.org/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The official guides cover physical/virtual servers, containers and Kubernetes. Development defaults are separate from the production configuration. Connections to external identity providers are customer-configured; hosting the server does not eliminate those dependencies. Keycloak 26.8.2 is a security release addressing authentication, token issuance and revocation, authorization, account takeover, admin API, stored XSS, denial-of-service, and bundled Brotli issues. Review the migration guide and upgrade to 26.8.2 or later.

This entry covers the open-source Keycloak server. Separately purchased support or a commercial distribution does not change this entry’s code-license classification.

The documented self-hosted runtime uses an application server or container with persistent state services. Hosted vendor editions are outside this listing.


### Category fit

- identity-access-management: Identity and access management with SSO, identity brokering, federation and OpenID Connect/OAuth 2.0/SAML support.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.keycloak.org/server/supported-configurations (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.keycloak.org/server/supported-configurations (checked 2026-11-12). 


### Cloud deployment evidence

- Keycloak supported configurations (aws, azure): https://www.keycloak.org/server/supported-configurations
  The project names Amazon EKS and Azure Kubernetes Service as non-OpenShift Kubernetes deployments supported on a best-effort basis. Distribution-specific issues may fall outside that support; check the documented Kubernetes API versions.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Container deployment: https://www.keycloak.org/server/containers

- Installation and production guide index: https://www.keycloak.org/guides

- Identity capabilities: https://www.keycloak.org/

- Keycloak 26.8.2 security release: https://www.keycloak.org/2026/11/keycloak-2682-released

- Keycloak 26.8.2 release details: https://github.com/keycloak/keycloak/releases/tag/26.8.2

### Licensing sources

- https://www.keycloak.org/

### Infrastructure sources

- https://www.keycloak.org/server/containers


### 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. Keycloak acts as an OAuth 2.0, OpenID Connect and SAML identity server. Applications must be configured as compatible clients; this is not automatic SSO for every application. Scope: Keycloak identity-provider role and client integration. Source: https://www.keycloak.org/securing-apps/overview (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 container guide builds and starts an optimized Keycloak server image, with external database and hostname/TLS configuration for production. Select a released image and compatible database; start-dev and an ephemeral local database are separate evaluation paths. Operator deployment is another supported installation option. Scope: Official self-hosted server/container deployment; configure production persistence and recovery separately. Source: https://www.keycloak.org/server/containers (reviewed 2026-11-20). Deployment artifact: https://github.com/keycloak/keycloak/releases/tag/26.8.2. Artifact reference: 26.8.2 upstream server distribution and matching container tag.

- Minimum footprint / sizing: Documented. The HA sizing guide starts at about 1,250 MB per pod including realm caches and 10,000 cached sessions. Its tested password-login profile budgets 1 vCPU per 15 logins/second plus 150% CPU headroom; database capacity is separate. These are load-test assumptions, not a universal host minimum or a 100-user, 1 TB HA guarantee. Scope: Official tested HA sizing model; login rate, password hashing, caches, topology and database determine capacity. Source: https://www.keycloak.org/high-availability/multi-cluster/concepts-memory-and-cpu-sizing (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: Keycloak 26.8.2 upstream distribution; software terms only, excluding infrastructure and operations. Source: https://github.com/keycloak/keycloak/blob/26.8.2/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.

- Keycloak 26.8.2 security release review (security-advisory): The release fixes authentication, token, authorization, account-takeover, XSS and dependency issues. Scope: Upstream Keycloak 26.8.2 security release; affected ranges and configurations vary by linked CVE. Conditions: Identity-provider, database, organization and authentication-flow settings determine applicability; a single blanket affected range is not established. Action: Review the linked CVEs and migration guide, then install a fixed supported release. Source: https://www.keycloak.org/2026/11/keycloak-2682-released; reviewed 2026-11-17.




## KNIME Business Hub

Commercial workflow collaboration and automation platform launched from AWS, Azure or Google Cloud Marketplace VM images.

- Listing: https://launchinyourcloud.com/directory/knime-business-hub/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial KNIME Business Hub license or Marketplace software subscription required.
- Licensing model: commercial-only
- Installation: Official AWS, Azure or Google Cloud Marketplace virtual-machine image
- Architecture: Single Marketplace virtual machine containing KNIME Business Hub services and execution infrastructure with persistent customer storage
- Operations: Customer manages the cloud account, virtual machine, networking, DNS, TLS, identity, storage, backups, capacity, upgrades and Business Hub license.
- Product website: https://www.knime.com/knime-hub
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers customer-hosted KNIME Business Hub, not the open-source KNIME Analytics Platform or KNIME's managed Hub offering. Marketplace deployments use single VM images; production capacity, availability and recovery requirements must be assessed separately. Customer-provisioned Kubernetes installation requires the applicable Self Hosted Premium package. Cloud infrastructure charges are separate from KNIME software pricing.

KNIME Business Hub Basic, Standard and Enterprise are commercial offerings. Marketplace software pricing or a separately obtained BYOL license applies, depending on the selected image.

The reviewed Marketplace paths run KNIME Business Hub and its execution services on a persistent virtual machine in the customer's cloud account.


### Category fit

- data-analytics: Provides governed collaboration, automation, execution and deployment for analytical workflows and data applications.

- ai-tools: Provides customer-operated execution and governance for data-science, machine-learning and generative-AI workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/ (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/ (checked 2026-11-16). 


### Cloud deployment evidence

- KNIME Business Hub on AWS Marketplace (aws): https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/
  KNIME documents launching Business Hub from an AWS Marketplace AMI into the customer's AWS account, with Marketplace or BYOL software licensing.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- KNIME Business Hub on Azure Marketplace (azure): https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/
  KNIME documents launching Business Hub from an Azure Marketplace single-VM image into the customer's Azure subscription.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- KNIME Business Hub on Google Cloud Marketplace (gcp): https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/
  KNIME documents launching Business Hub through Google Cloud Marketplace using a Google Compute VM image in the customer's project.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- KNIME Business Hub on AWS Marketplace: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/

- KNIME Business Hub on Azure Marketplace: https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/

- KNIME Business Hub on Google Cloud Marketplace: https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/

- KNIME Business Hub installation guide: https://docs.knime.com/hub/latest/business_hub_installation_guide/

- KNIME Business Hub pricing and licensing: https://www.knime.com/knime-hub-pricing

### Licensing sources

- https://www.knime.com/knime-hub-pricing

- https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/

### Infrastructure sources

- https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/

- https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/

- https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/


### Buyer diligence


Research coverage: 10/12 fields (83%); 9 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: Edition-dependent. The official AWS and Azure guides link Basic, Standard and BYOL VM offers. PAYG software charges or a separate BYOL entitlement apply; cloud infrastructure charges are additional. Availability does not establish cloud-commitment eligibility. Scope: Vendor-linked AWS/Azure VM offers; region, edition and agreement govern purchase. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (reviewed 2026-11-16). Supporting source: Azure Marketplace offer links — https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/. Offer prodview-nzgqreu746eq2: KNIME; Single-instance AMI; Basic PAYG; https://aws.amazon.com/marketplace/pp/prodview-nzgqreu746eq2. Offer prodview-cd3xzq7m5fqjg: KNIME; Single-instance AMI; Standard PAYG; https://aws.amazon.com/marketplace/pp/prodview-cd3xzq7m5fqjg. Offer prodview-gwty5knsn4bp2: KNIME; Single-instance AMI; BYOL; https://aws.amazon.com/marketplace/pp/prodview-gwty5knsn4bp2. Offer knime.knime-business-hub-basic: KNIME; Virtual-machine image; Basic; https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-basic?tab=Overview. Offer knime.knime-business-hub-standard: KNIME; Virtual-machine image; Standard; https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-standard?tab=Overview. Offer knime.knime-business-hub-byol: KNIME; Virtual-machine image; BYOL; https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-byol?tab=Overview.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The customer-managed installation uses Keycloak and can federate to an external identity provider through SAML 2.0, OIDC or OAuth 2.0. Map required username, email and name attributes in the knime realm. Scope: Customer-managed Business Hub identity setup; not the Knime-managed SaaS setup. Source: https://docs.knime.com/hub/latest/business_hub_installation_guide/ (reviewed 2026-11-16).

- SCIM provisioning: Edition-dependent. Standard and Enterprise document SCIM user/group provisioning, tested with Okta and Microsoft Entra ID. An administrator creates an application password/token; align usernames with the SSO mappings. Other SCIM clients are not covered by the stated test matrix. Scope: Business Hub Standard/Enterprise; excludes Basic. Source: https://docs.knime.com/hub/latest/business_hub_advanced_admin_guide/ (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. The reviewed security manual explicitly describes a Knime-managed AWS/Azure account. Its ISO and encryption statements therefore do not establish a current attestation for this customer-managed Business Hub installation; obtain the applicable report/certificate scope. Scope: Knime-managed service documentation versus customer-managed Business Hub. Source: https://docs.knime.com/admin/security/ (reviewed 2026-11-16).

- Security controls: Documented. The AWS guide says its default security group exposes application and administration ports to all IPs, and its default EBS volume is unencrypted. Restrict administrative access and configure encryption before production use. Scope: AWS Marketplace guide defaults; deployment configuration remains the customer’s responsibility. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (reviewed 2026-11-16).

- Air-gapped operation: Edition-dependent. The customer-managed Argo CD guide supplies an airgap bundle containing images and Helm charts. Obtain the target-version bundle from KNIME, import it into private registries and apply registry overrides. The guide requires Self Hosted Premium for the covered on-premises installation. Scope: Customer-managed Argo CD installation; not an automatic entitlement or procedure for every Marketplace VM. Source: https://docs.knime.com/hub/latest/business_hub_argocd_installation_guide/prerequisites (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. KNIME documents single-VM Marketplace images for AWS, Azure and Google Cloud. These contain a local Kubernetes installation; custom infrastructure follows a separate installation path. Select an offer and region matching the intended edition and license. Scope: Marketplace VM delivery, not a multi-node reference architecture. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (reviewed 2026-11-16). Supporting source: Azure VM image deployment — https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/. Supporting source: Google Cloud VM image deployment — https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/.

- Minimum footprint / sizing: Documented. The AWS AMI guide recommends m5.4xlarge and one 512 GiB EBS volume as the starting minimum. Workflow load, backup and failover needs can require more. Scope: AWS Marketplace single-VM starting configuration; not a cost or HA estimate. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (reviewed 2026-11-16).

- License pricing: Documented. KNIME Business Hub Basic, Standard and Enterprise are commercial offerings. Marketplace software pricing or a separately obtained BYOL license applies, depending on the selected image. Scope: KNIME Business Hub: software license terms; infrastructure and operating costs are separate. Source: https://www.knime.com/knime-hub-pricing (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor release is 1.19.0, published 2026-09-03. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Scope: Business Hub application release; Marketplace VM and installation-package versions require separate checks; source supplies a publication day, not a timestamp. Source: https://docs.knime.com/hub/latest/business_hub_release_notes/1.19/ (reviewed 2026-11-16).







## Kong Gateway Self-Managed

Open-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.

- Listing: https://launchinyourcloud.com/directory/kong-gateway/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the open-source core; Enterprise features use separate commercial licensing.
- Licensing model: open-source
- Installation: Official Linux packages, Docker images, Helm chart or Kubernetes Operator
- Architecture: Gateway proxy and administration services in database-backed, database-less or hybrid topologies on customer compute or Kubernetes
- Operations: Customer manages compute or Kubernetes, datastore topology, networking, TLS, plugins, secrets, configuration, monitoring, backups, scaling and upgrades. Enterprise users also manage subscription and license configuration.
- Product website: https://www.konghq.com/products/kong-gateway
- Source review: 2026-11-19; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-managed Kong Gateway, not Kong Konnect or Kong-managed cloud gateways. The open-source core and Enterprise distribution have different features and support entitlements. Validate the selected topology, package version, datastore mode and cloud-platform compatibility before deployment. Kong Gateway Enterprise 3.16.0.2 fixes authentication-context cache leakage, request-callout cache keys, SAML audience validation, Admin API RBAC self-protection, unsafe forwarded paths, and LLM usage-counter SQL injection. This Enterprise plugin guidance is separate from the listing's community/core 3.9.4 snapshot; exact SAML Audience and issuer matching may require configuration changes. Kong Gateway community/core 3.9.5 applies nginx patches for CVE-2026-123007 and CVE-2026-123633, HTTP/2 memory-corruption and use-after-free vulnerabilities. Upgrade the applicable maintained core line and separately follow Enterprise guidance for the installed edition.

Kong Gateway's upstream core is Apache-2.0 licensed. Kong Gateway Enterprise adds separately licensed proprietary features and commercial support.

Kong Gateway runs persistent proxy and administration processes on Linux, Docker or Kubernetes, with an optional customer-managed datastore and control-plane services.


### Category fit

- backend-platforms: Provides a self-managed API gateway for routing, authentication, traffic control, transformation, observability and extensible API policies.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.konghq.com/gateway/version-support-policy/ (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.konghq.com/gateway/version-support-policy/ (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.konghq.com/gateway/version-support-policy/ (checked 2026-11-16). 


### Cloud deployment evidence

- Kong Gateway supported public-cloud deployment platforms (aws, azure, gcp): https://developer.konghq.com/gateway/version-support-policy/
  Kong lists supported self-managed deployment platforms including Amazon EKS, ECS and Fargate; Azure AKS, Container Instances and Container Apps; and Google GKE, GKE Autopilot and Cloud Run. Edition-specific support entitlements should be confirmed separately.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Community and maintenance

Kong maintains public upstream releases and contributor history for the Apache-licensed Kong Gateway core. This evidence establishes continuing project activity, not Enterprise support or support for every listed cloud topology.

Reviewed 2026-11-16.

- Kong Gateway releases: https://github.com/Kong/kong/releases

- Kong Gateway contributor history: https://github.com/Kong/kong/graphs/contributors

### Sources

- Install Kong Gateway: https://developer.konghq.com/gateway/install/

- Kong Gateway public-cloud platform support: https://developer.konghq.com/gateway/version-support-policy/

- Kong Gateway edition comparison: https://www.konghq.com/products/kong-gateway

- Kong Gateway Apache 2.0 license: https://github.com/Kong/kong/blob/master/LICENSE

- Kong Gateway releases: https://github.com/Kong/kong/releases

- Kong Gateway contributor history: https://github.com/Kong/kong/graphs/contributors

- Kong Gateway Enterprise changelog: https://developer.konghq.com/gateway/changelog/

- Kong Gateway 3.9.5 release: https://github.com/Kong/kong/releases/tag/3.9.5

- Kong Gateway 3.9.5 changelog: https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395

- nginx security advisories: https://nginx.org/en/security_advisories.html

### Licensing sources

- https://github.com/Kong/kong/blob/master/LICENSE

- https://www.konghq.com/products/kong-gateway

### Infrastructure sources

- https://developer.konghq.com/gateway/install/

- https://developer.konghq.com/gateway/version-support-policy/


### Buyer diligence


Research coverage: 9/12 fields (75%); 8 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: Sources checked — unresolved. Kong’s Gateway policy names AWS, Azure and Google Cloud marketplaces. The reviewed policy does not identify exact offers, publishers, delivery types or packaged versions. Confirm those records and the Gateway entitlement before treating a Konnect or third-party offer as the self-managed product. Scope: Vendor Marketplace availability statement; exact self-managed offer records remain unverified. Source: https://developer.konghq.com/gateway/version-support-policy/ (reviewed 2026-11-16).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Self-managed Kong Manager can authenticate administrators through OIDC using the Enterprise-only OpenID Connect plugin. The v3.6+ procedure uses kong.conf and differs from Konnect SSO and from authenticating API consumers. Scope: Kong Gateway Enterprise Manager, v3.6+; not the Apache-licensed core alone. Source: https://developer.konghq.com/gateway/kong-manager/openid-connect/ (reviewed 2026-11-16). Supporting source: Enterprise-only OIDC plugin — https://developer.konghq.com/plugins/openid-connect/.

- SCIM provisioning: Not researched.

- Compliance attestations: Documented. Kong explicitly says the Gateway FIPS package has not itself been submitted to a NIST testing lab for product validation. Its use of a validated cryptographic provider must not be presented as a certificate for the entire customer deployment. Scope: Vendor-stated product-versus-module validation boundary; not an assessment of other certifications. Source: https://developer.konghq.com/gateway/fips-support/ (reviewed 2026-11-16).

- Security controls: Edition-dependent. Enterprise v3.14+ offers an AMD64 FIPS 140-3 package using approved algorithms and an OpenSSL FIPS provider. Kong explicitly distinguishes its compliant package from a product submitted for NIST validation; configure the supported distribution and FIPS mode. Current advisory review: Enterprise 3.16.0.2 fixes cache leakage across authentication contexts, request-callout cache keys, SAML audience validation, Admin API RBAC bypass, unsafe forwarded paths, and LLM usage-counter SQL injection. Upgrade Enterprise deployments to 3.16.0.2 or later and retest exact SAML Audience and issuer matching. Current review: Community/core 3.9.5 applies nginx fixes for CVE-2026-123007 and CVE-2026-123633, HTTP/2 memory-corruption and use-after-free vulnerabilities. Upgrade the applicable maintained branch; do not substitute the 3.9 core tag for separately versioned Enterprise guidance. Scope: Kong Gateway community/core 3.9 line with affected nginx HTTP/2 code. Source: https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://developer.konghq.com/gateway/changelog/. Supporting source: Prior security-controls source — https://developer.konghq.com/gateway/fips-support/. Supporting source: 3.9.5 release — https://github.com/Kong/kong/releases/tag/3.9.5. Supporting source: nginx advisories — https://nginx.org/en/security_advisories.html.

- Air-gapped operation: Documented. Self-managed Enterprise license validation does not require network connectivity: each node reads a supplied license at startup. This resolves offline license validation, but does not certify every plugin, integration, image source or update workflow as disconnected. Scope: Enterprise offline license validation only; not Konnect or blanket end-to-end air-gap certification. Source: https://developer.konghq.com/gateway/entities/license/ (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. The upstream Kong Helm chart deploys Gateway on Kubernetes. Select compatible chart, image and database settings; an Enterprise image/license does not follow automatically from installing the chart. Scope: Kong Gateway chart; open-source and Enterprise image entitlements differ. Source: https://developer.konghq.com/gateway/install/ (reviewed 2026-11-16). Deployment artifact: https://github.com/Kong/charts/tree/main/charts/kong. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. Kong publishes workload-based sizing rather than a fixed universal minimum. Its small per-node starting example is 1–2 CPU cores and 2–4 GB RAM; database/Redis, enabled plugins, configuration size and traffic must be sized separately. Scope: Self-managed Gateway sizing guidelines, v3.4+; example resources are not throughput guarantees. Source: https://developer.konghq.com/gateway/resource-sizing-guidelines/ (reviewed 2026-11-16).

- License pricing: Documented. Kong Gateway's upstream core is Apache-2.0 licensed. Kong Gateway Enterprise adds separately licensed proprietary features and commercial support. Scope: Kong Gateway Self-Managed: software license terms; infrastructure and operating costs are separate. Source: https://github.com/Kong/kong/blob/master/LICENSE (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.konghq.com/products/kong-gateway.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Kong Gateway community/core 3.9.5 was published November 19, 2026. It applies nginx patches for CVE-2026-123007 and CVE-2026-123633. Enterprise releases, plugins and cloud packages remain separately versioned. Scope: Upstream Kong Gateway community/core 3.9 line; Enterprise and deployment packages may differ. Source: https://github.com/Kong/kong/releases/tag/3.9.5 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/Kong/kong/releases/tag/3.9.4. Supporting source: 3.9.5 changelog — https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395.




### Security and lifecycle reviews

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

- Kong Gateway Enterprise 3.16.0.2 security patch (security-advisory): Enterprise 3.16.0.2 fixes cache leakage across authentication contexts, request-callout cache keys, SAML audience validation, Admin API RBAC bypass, unsafe forwarded paths, and LLM usage-counter SQL injection. Scope: Kong Gateway Enterprise plugins and features; the listing's separate community/core release snapshot is not replaced by this Enterprise build. Conditions: Applicability depends on the enabled Enterprise authentication, cache, SAML, RBAC, forwarded-path, and LLM plugins. Action: Upgrade Enterprise deployments to 3.16.0.2 or later and retest exact SAML Audience and issuer matching. Source: https://developer.konghq.com/gateway/changelog/; reviewed 2026-11-18.

- Kong Gateway 3.9.5 nginx HTTP/2 fixes (security-advisory): Kong Gateway community/core 3.9.5 applies nginx patches for CVE-2026-123007 and CVE-2026-123633. Scope: Kong Gateway community/core 3.9 line with affected nginx HTTP/2 code; Enterprise and other branches are separately versioned. Conditions: HTTP/2 exposure and the exact bundled nginx build determine applicability. Action: Upgrade the applicable maintained core branch and separately follow Enterprise guidance for the installed edition. Source: https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395; reviewed 2026-11-19. Supporting source: Kong Gateway 3.9.5 — https://github.com/Kong/kong/releases/tag/3.9.5. Supporting source: nginx security advisories — https://nginx.org/en/security_advisories.html.




## Langflow Self-Hosted

Visual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.

- Listing: https://launchinyourcloud.com/directory/langflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the upstream project; connected models, providers and bundles have their own terms.
- Licensing model: open-source
- Installation: Official Docker image or Docker Compose; Python installation and Kubernetes options are also documented.
- Architecture: Customer-operated flow application with persistent database and configured model/tool endpoints
- Operations: Customer manages the application, database, access controls, installed components, backups and version upgrades.
- Product website: https://www.langflow.org/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The reviewed model-component docs support Ollama and configurable OpenAI-compatible endpoints as well as commercial providers. External models, embeddings, tools or custom components can move data beyond the host. Hosting Langflow is distinct from hosting those dependencies and from any vendor-managed service. Langflow 1.13.3 enforces custom-component policy in background workflows, invalidates native sessions after password changes, updates security dependencies, and aligns Docker and wheel packaging. Recheck custom components and session behavior after upgrading.

The reviewed upstream Langflow project uses the MIT license. This classification covers that project; connected model weights, provider services and third-party components have their own terms.

Official images run the application on a Docker host; the Compose deployment adds persistent PostgreSQL storage. Model-serving hardware is a separate requirement if inference is also self-hosted.


### Category fit

- ai-applications-rag: Visual builder and runtime for AI flows, agents and model integrations. Local model endpoints are configurable; a flow can also call externally hosted providers.

- ai-tools: Visual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.langflow.org/deployment-architecture (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.langflow.org/deployment-architecture (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.langflow.org/deployment-architecture (checked 2026-11-12). 


### Cloud deployment evidence

- Langflow Kubernetes deployment architecture (aws, azure, gcp): https://docs.langflow.org/deployment-architecture
  The project explicitly identifies EKS, AKS and GKE for its Helm deployment. Separate the development IDE from the production runtime, and review PostgreSQL, model endpoints and external vector stores.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker and Docker Compose deployment: https://docs.langflow.org/deployment-docker

- Model components and local endpoints: https://docs.langflow.org/components-models

- Upstream MIT license: https://github.com/langflow-ai/langflow/blob/main/LICENSE

- Langflow 1.13.3 release: https://github.com/langflow-ai/langflow/releases/tag/v1.13.3

### Licensing sources

- https://github.com/langflow-ai/langflow/blob/main/LICENSE

### Infrastructure sources

- https://docs.langflow.org/deployment-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: Documented. Current 1.13 documentation supports an upstream OIDC proxy/SSO gateway forwarding tokens that Langflow validates using issuer, audience and JWKS. It can provision a local user; built-in credentials remain a separate path. Configure the gateway and validation explicitly and replace development identity-provider examples. Scope: Langflow 1.13 external-token validation with a separately operated SSO gateway. Source: https://docs.langflow.org/external-authentication (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Langflow 1.13.3 extends custom-component policy enforcement to background workflows and invalidates native sessions after password changes. Upgrade to 1.13.3 or later and retest component policy and session revocation. Scope: Upstream 1.13.3 release notes; no consolidated affected-version range is asserted.. Source: https://github.com/langflow-ai/langflow/releases/tag/v1.13.3 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide provides an official image and Compose with persistent PostgreSQL, plus custom-image options. Preserve database/flow data and configure secrets, access controls and model-provider credentials. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.langflow.org/deployment-docker (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. Langflow OSS lists a dual-core CPU and 2 GB RAM minimum, recommending a multi-core CPU and at least 4 GB. This covers the Python application; external databases, model inference, workflow concurrency and HA are additional. Scope: Langflow OSS application baseline; model and production topology excluded. Source: https://docs.langflow.org/get-started-installation (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/langflow-ai/langflow/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Langflow v1.13.3 was published November 17, 2026. It applies custom-component policy to background workflows, invalidates native sessions after password changes, updates security dependencies, and aligns Docker and wheel packaging. Scope: Upstream Langflow self-hosted release. Source: https://github.com/langflow-ai/langflow/releases/tag/v1.13.3 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Langflow 1.13.3 policy and session hardening (security-advisory): Langflow 1.13.3 extends custom-component policy enforcement to background workflows and invalidates native sessions after password changes. Scope: Upstream 1.13.3 release notes; no consolidated affected-version range is asserted. Conditions: Applicability depends on custom components, workflow execution mode, and native authentication. Action: Upgrade to 1.13.3 or later and retest component policy and session revocation. Source: https://github.com/langflow-ai/langflow/releases/tag/v1.13.3; reviewed 2026-11-18.




## Langfuse Self-Hosted

Self-hosted LLM observability, evaluations and prompt-management platform.

- Listing: https://launchinyourcloud.com/directory/langfuse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
- Licensing model: open-source
- Installation: Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.
- Architecture: Application and worker containers with PostgreSQL, ClickHouse, Redis/Valkey and object storage
- Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
- Product website: https://langfuse.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.

The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.

The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.


Cloud evidence scope: Documented provider-specific deployment

### Category fit

- ai-observability: LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.

- ai-tools: Self-hosted LLM observability, evaluations and prompt-management platform.

- observability: Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

### Deployment boundaries


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

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

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

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/railway (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/render (checked 2026-11-12). 


### Cloud deployment evidence

- Langfuse customer cloud deployment on AWS (aws): https://langfuse.com/self-hosting/deployment/aws
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Azure (azure): https://langfuse.com/self-hosting/deployment/azure
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Google Cloud (gcp): https://langfuse.com/self-hosting/deployment/gcp
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v3 community Railway deployment (railway): https://langfuse.com/self-hosting/deployment/railway
  The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v4 community Render Blueprint (render): https://langfuse.com/self-hosting/deployment/render
  The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker Compose on a VM: https://langfuse.com/self-hosting/deployment/docker-compose

- Self-hosting architecture and provider dependencies: https://langfuse.com/self-hosting

- AWS account Terraform deployment: https://langfuse.com/self-hosting/deployment/aws

- Azure account Terraform deployment: https://langfuse.com/self-hosting/deployment/azure

- Google Cloud account Terraform deployment: https://langfuse.com/self-hosting/deployment/gcp

- Core and enterprise licensing: https://github.com/langfuse/langfuse/blob/main/LICENSE

- Licensing and edition terms: https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

- Langfuse v3 community Railway deployment: https://langfuse.com/self-hosting/deployment/railway

- Langfuse v4 community Render Blueprint: https://langfuse.com/self-hosting/deployment/render

- Langfuse v4.82.0 release: https://github.com/langfuse/langfuse/releases/tag/v4.82.0

### Licensing sources

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

- https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

### Infrastructure sources

- https://langfuse.com/self-hosting/deployment/docker-compose

- https://langfuse.com/self-hosting/deployment/aws

- https://langfuse.com/self-hosting/deployment/azure

- https://langfuse.com/self-hosting/deployment/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 self-hosted guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review. Scope: Self-hosted OAuth/OIDC sign-in. Source: https://langfuse.com/self-hosting/security/authentication-and-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports. Scope: Upstream Compose recipe; supporting-service operations remain customer responsibilities. Source: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint. Scope: Langfuse Web/Worker resource recommendation; backing services additional. Source: https://langfuse.com/self-hosting/deployment/infrastructure/containers (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/langfuse/langfuse/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Scope: Upstream Langfuse self-hosted release. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Langfuse GitHub Enterprise SSO SSRF fix (security-advisory): Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note. Conditions: Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target. Action: Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0; reviewed 2026-11-18.




## Laserfiche Self-Hosted

Self-hosted document and records platform with forms and configurable business process automation.

- Listing: https://launchinyourcloud.com/directory/laserfiche-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial self-hosted software; license and module entitlements apply
- Licensing model: commercial-only
- Installation: Licensed Laserfiche 12 Windows installers
- Architecture: Persistent Windows Server applications, repository storage and database; current support guidance excludes containerized self-hosted applications.
- Operations: Customer operates supported Windows servers, repository/database backups and product updates; follow the chosen modules installation requirements.
- Product website: https://www.laserfiche.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the self-hosted product. Use-case pages describe platform workflows; confirm availability and licensing for the chosen version and modules. The current support matrix requires Windows Server Desktop Experience and explicitly excludes Docker and Kubernetes deployment for self-hosted applications.

This record covers the commercial self-hosted Laserfiche product. Installation and activation require licensed application entitlements; marketplace templates do not confer a license to the underlying platform.

Persistent Windows Server applications, repository storage and database; current support guidance excludes containerized self-hosted applications.


### Category fit

- document-management: Repository, capture, search and document process automation on customer-operated servers.

- records-management: Document lifecycle, retention, access controls and disposition; configure schedules for the organization.

- contract-management: Configurable contract creation, approval and records workflows; confirm the selected self-hosted modules.

- financial-application-management: Document routing and automation for loan applications, illustrated by the vendor banking case study.

- case-management: Forms, repository content and process workflows for service case management; implementation is configured to the case process.

- hr-employee-records-management: Employee records, onboarding approvals and access controls for HR processes.

- claims-management: Low-code claims review and approval workflows; does not establish an insurance policy or adjudication core.

- workflow-automation: Forms and document workflows for routing, approvals and task automation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf (checked 2026-11-12). 


### Cloud deployment evidence

- Laserfiche reseller installation terms for customer AWS and Azure environments (aws, azure): https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf
  Cities Digital installation terms, published in the municipal meeting packet on PDF page 40, explicitly cover new Azure or AWS environments and exclude Laserfiche Cloud from that section. The client supplies Windows, SQL Server and network configuration and validates workflows. This documents a reseller-assisted self-hosted path; confirm the current server version, license, support scope and implementation fees.
  Source type: public-procurement-record; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted installation overview: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- Current operating system and deployment support: https://support.laserfiche.com/kb/1012418/raw

- Business process solutions: https://www.laserfiche.com/solutions/

- Document and records capabilities: https://www.laserfiche.com/products/document-and-records-management/

- Loan application automation case study: https://www.laserfiche.com/resources/customer-stories/growin-bank-expedites-loan/

- Insurance claims workflows: https://www.laserfiche.com/solutions/financial-services/insurance/

- Software license agreement and legal resources: https://www.laserfiche.com/legal/

### Licensing sources

- https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- https://www.laserfiche.com/legal/

### Infrastructure sources

- https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- https://support.laserfiche.com/kb/1012418/raw


### 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: Documented. Laserfiche 12 Directory Server accepts SAML 2.0 identity providers using imported metadata and claim mappings. Configure the licensing site, client integrations and local-account policy; this does not establish every optional module or Cloud entitlement. Scope: Laserfiche 12 self-hosted Directory Server federation. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/admin-lfds-saml-identity-provider.htm (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. Laserfiche 12 uses a product installer that selects applications, detects installed versions and offers updates. Follow new-installation, repository and system-specification instructions; this page is not a public IaC package. Scope: Laserfiche self-hosted version 12 installer and initial configuration. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The current supported-platforms list establishes Windows Server and database compatibility, but does not supply a complete Laserfiche 12 CPU/RAM topology. Public numeric checklists found cover version 11 or older. Obtain a version-12 component and HA sizing design rather than applying those legacy minima. Scope: Laserfiche 12 self-hosted hardware sizing unresolved. Source: https://support.laserfiche.com/kb/1012418/pdf (reviewed 2026-11-20). Supporting source: Older version-11 server minimum is not a version-12 sizing recommendation — https://doc.laserfiche.com/laserfiche.documentation/11/administration/en-us/Subsystems/LFAdmin/Content/Installation/Laserfiche_Server_%28United%29_pre_check.htm.

- License pricing: Sources checked — unresolved. The self-hosted Directory Server workflow requires a licensing site registering the repository server. The reviewed integration documentation does not establish current licence prices, user metrics or maintenance terms; obtain an on-premises quote rather than applying Laserfiche Cloud prices. Scope: Self-hosted licence delivery established; commercial pricing and terms unresolved. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/config-lfm-configuration-page-connection.htm (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Liferay DXP Cloud Native Experience

Commercial digital experience, content management and digital asset platform deployed into customer cloud infrastructure with Liferay's Cloud Native Experience toolkit.

- Listing: https://launchinyourcloud.com/directory/liferay-dxp-cloud-native-experience/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Liferay DXP subscription; Cloud Native Experience provider-ready capabilities require Enterprise Subscription entitlement.
- Licensing model: commercial-only
- Installation: Provider-ready Terraform bootstrap with Kubernetes, Helm and Argo CD GitOps deployment
- Architecture: Customer-operated EKS, AKS or GKE deployment integrated with provider database, object storage and search services.
- Operations: Customer manages the cloud account, GitOps repository, Kubernetes platform, secrets, domains, certificates, capacity, backups, upgrades and application customizations.
- Product website: https://www.liferay.com/products/dxp
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

Cloud Native Experience supports Liferay DXP 2024.Q1 and later. Provider architectures differ: AWS Ready integrates RDS, S3 and OpenSearch; Azure Ready uses AKS, Azure PostgreSQL Flexible Server, Blob Storage and Elasticsearch through ECK; GCP Ready uses GKE, Cloud SQL, Cloud Storage and ECK. The customer must provide cloud permissions, a Git repository, secret storage, compatible tools and a valid activation key. Starting with DXP 2026.Q1, all installations require an activation key.

This entry is scoped to commercial Liferay DXP Cloud Native Experience, not Liferay Portal Community Edition. Provider-ready capabilities require Enterprise Subscription entitlement and DXP requires an activation key.

Provider-ready CNE provisions managed Kubernetes and supporting stateful services in the customer's cloud. Liferay runs as persistent workloads managed through Helm and Argo CD.


### Category fit

- content-management: Liferay DXP provides web and headless content authoring, publishing, sites and digital-experience delivery on customer infrastructure.

- digital-asset-management: The DXP includes digital asset management for organizing and reusing documents and media; exact entitlement follows the selected subscription.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-azure-ready (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-gcp-ready (checked 2026-11-17). 


### Cloud deployment evidence

- Liferay DXP Cloud Native Experience AWS Ready (aws): https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready
  Liferay documents automated deployment in the customer's AWS account with EKS, RDS, S3 and OpenSearch. Enterprise Subscription entitlement and customer cloud permissions are required.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Liferay DXP Cloud Native Experience Azure Ready (azure): https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-azure-ready
  Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Azure subscription, including AKS and managed data services.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Liferay DXP Cloud Native Experience GCP Ready (gcp): https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-gcp-ready
  Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Google Cloud environment, including GKE and managed data services.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Cloud Native Experience overview: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience

- AWS Ready deployment: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready

- Azure Ready deployment: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-azure-ready

- GCP Ready deployment: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-gcp-ready

- Liferay DXP activation and subscription keys: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp

- AWS Ready Enterprise Subscription requirement: https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q2/features/cloud-native-aws-ready-2026-q2-2

- GCP Ready Enterprise Subscription requirement: https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q3/features/cloud-native-gcp-ready

### Licensing sources

- https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp

- https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q3/features/cloud-native-gcp-ready

### Infrastructure sources

- https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience

- https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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. CNE licensing refers to Liferay Marketplace add-ons, not a provider billing offer. A current cloud Marketplace offer for the selected CNE Enterprise path was not established. Scope: Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/automatic-environment-licensing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. DXP Enterprise activation and add-on delivery do not establish cloud-provider Marketplace commitment treatment. Scope: Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp (reviewed 2026-11-17).

- Single sign-on: Documented. The DXP compatibility matrix documents SAML 2.0 and OIDC provider standards. Match the IdP and certified runtime components to the actual DXP release used by CNE. Scope: Self-hosted DXP identity compatibility; reviewed 2025.Q2 matrix. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/reference/compatibility-matrices/liferay-dxp-2025-q2-compatibility-matrix (reviewed 2026-11-17).

- SCIM provisioning: Edition-dependent. DXP SCIM was introduced behind a flag in 2024.Q1, moved to a release flag in 2024.Q4 and became GA in 2025.Q1. Verify the deployed release and supported RFC operations; it does not implement arbitrary vendor schema extensions. Scope: DXP subscription/version-specific provisioning. Source: https://learn.liferay.com/es/w/dxp/security-and-administration/security/system-for-cross-domain-identity-management-scim (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Liferay DXP Cloud Native Experience 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://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready (reviewed 2026-11-17).

- Security controls: Documented. The CNE deployment requires controlled GitOps access, cloud credentials and activation keys. Configure secrets, network boundaries and the certified identity/runtime components rather than treating cloud provisioning as hardening. Scope: AWS Ready deployment access and secrets. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. CNE documents offline activation bundles for AWS/GCP Ready, but Azure Ready 0.3.0 lacks the required Marketplace volume. This establishes offline licensing for selected paths; complete dependency mirroring, updates and integrations still need validation. Scope: Path/version-specific offline licensing, not unconditional air-gap support. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/automatic-environment-licensing/licensing-an-offline-environment (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. CNE Kubernetes Ready supplies the liferay-default Helm chart; supporting Kubernetes, database, search and object storage are customer-managed. This complements provider-specific Ready automation. Pin a chart compatible with the chosen DXP release. Scope: Official Helm artifact for customer Kubernetes. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready (reviewed 2026-11-17). Deployment artifact: https://github.com/liferay/liferay-portal/tree/master/cloud/helm/default. Artifact reference: master (moving branch; select a compatible chart/image release).

- Minimum footprint / sizing: Documented. The Kubernetes Ready Small tier uses two Liferay replicas, each requesting 2 CPU/12 GiB (limits 4 CPU/16 GiB), 20 GiB PVC per pod, an HA database, three search nodes and object storage. It targets up to 500 concurrent users but requires workload load testing. Scope: Kubernetes Ready Small production starting tier; AWS Ready infrastructure defaults may differ. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready/architecture-sizing-and-support-model (reviewed 2026-11-17).

- License pricing: Documented. This entry is scoped to commercial Liferay DXP Cloud Native Experience, not Liferay Portal Community Edition. Provider-ready capabilities require Enterprise Subscription entitlement and DXP requires an activation key. Scope: Liferay DXP Cloud Native Experience: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. The Small tier supplies app/search/HA-database starting requirements, but the complete provider bill of materials, DXP entitlement and measured content/search workload still need confirmation. 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://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready/architecture-sizing-and-support-model (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. CNE supports DXP 2024.Q1+ and provider tooling has independent revisions. The complete latest supported DXP/chart/operator/provider-Ready combination and publication dates were not established. Scope: Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience (reviewed 2026-11-17).







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







## LiteLLM Proxy Self-Hosted

Self-hosted AI API gateway providing model routing, access controls and usage tracking.

- Listing: https://launchinyourcloud.com/directory/litellm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT outside the enterprise directory; enterprise code and features have separate license terms.
- Licensing model: open-source
- Installation: Official container image, Docker Compose or Kubernetes deployment; production infrastructure examples are documented.
- Architecture: Customer-operated gateway with optional PostgreSQL persistence and configured model endpoints
- Operations: Customer manages gateway availability, credentials, database, access policies, logs and upgrades, including pinning versions and verifying release artifacts with the documented version-appropriate Cosign method; model providers remain separate services.
- Product website: https://www.litellm.ai/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The gateway forwards each request to its configured model provider. Self-hosting the proxy does not ensure prompts stay inside the account: external model APIs, guardrail services and logging integrations can receive data. Use appropriate self-hosted inference endpoints and explicitly review outbound integrations when required. For release integrity, release images and the Helm chart starting with v1.111.0-dev.3 use keyless Cosign signatures bound to LiteLLM's release workflow; earlier releases require the documented historical public keys. The October 21 incident affected PyPI v1.107.0 and Docker Hub/GHCR v1.107.0 plus mutable latest, main-latest and main-stable tags during the documented exposure windows. Check the incident's artifact digests and remediation instructions; the compromised images carried valid historical signatures, so signature verification alone does not establish safety. LiteLLM v1.110.0 changes authentication, guardrail, accounting, and S3 behavior. The 1.108.11 LTS patch also fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators; review both the selected release line and existing incident-response or image-signing guidance. LiteLLM v1.108.12 LTS fixes tool_policy allowing blocked /v1/messages tool names longer than 64 characters. The standard v1.110.1 UI image changes to slim nginx and removes curl while retaining wget and nc, so retest health probes and scripts that assume curl.

The gateway has an MIT-licensed base and separately licensed enterprise features. The enterprise documentation describes a license key enabling restricted capabilities in the gateway, beyond paid hosting or support alone.

The gateway runs as provisioned application containers or Kubernetes workloads; persistent key/spend storage can use PostgreSQL. Inference compute is a separate dependency rather than included in the gateway.


### Category fit

- ai-inference-gateways: Self-hosted model API gateway for routing, virtual keys, spend tracking and policy enforcement. It routes inference requests; it is not an inference engine for all supported models.

- ai-tools: Self-hosted AI API gateway providing model routing, access controls and usage tracking.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 


### Cloud deployment evidence

- LiteLLM production deployment (aws, azure, gcp): https://docs.litellm.ai/docs/proxy/deploy
  Official production guidance covers EKS, AKS and GKE with Helm, plus Terraform on AWS and Google Cloud. The proxy, database and Redis deployment is separate from the model services it calls.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- LiteLLM Railway and Render deployment options (railway, render): https://docs.litellm.ai/docs/proxy/deploy
  The current upstream deployment guide supplies Railway and Render deployment buttons in addition to its EKS/AKS/GKE instructions, followed by readiness and Admin UI verification. These are customer application deployments on managed platforms; configure persistent data, secrets and external model-provider endpoints separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production deployment: https://docs.litellm.ai/docs/proxy/deploy

- Gateway request flow and functionality: https://docs.litellm.ai/docs/simple_proxy

- MIT core and enterprise exception: https://github.com/BerriAI/litellm/blob/main/LICENSE

- Licensing and edition terms: https://docs.litellm.ai/docs/enterprise

- Supply-chain incident and Cosign verification guidance: https://docs.litellm.ai/blog/security-incident-oct-21-2026

- Canonical LiteLLM incident investigation: https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain

- LiteLLM v1.110.0 release: https://github.com/BerriAI/litellm/releases/tag/v1.110.0

- LiteLLM v1.108.11 LTS release: https://github.com/BerriAI/litellm/releases/tag/v1.108.11

- LiteLLM v1.110.1: https://github.com/BerriAI/litellm/releases/tag/v1.110.1

- LiteLLM v1.108.12 LTS: https://github.com/BerriAI/litellm/releases/tag/v1.108.12

### Licensing sources

- https://github.com/BerriAI/litellm/blob/main/LICENSE

- https://docs.litellm.ai/docs/enterprise

### Infrastructure sources

- https://docs.litellm.ai/docs/proxy/deploy


### 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 Admin UI documents OIDC SSO. From 1.76.0, it is free for up to five users; larger deployments require an Enterprise licence. Configure issuer, callbacks, roles and database/master-key prerequisites. This is Admin UI identity, distinct from model API virtual keys. Scope: LiteLLM Admin UI OIDC; user-count/Enterprise entitlement applies. Source: https://docs.litellm.ai/docs/proxy/admin_ui_sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Release images and Helm charts use keyless Cosign from v1.111.0-dev.3; verify the documented workflow identity and issuer. Earlier releases use historical keys. The October 21 v1.107.0 compromise also affected mutable image tags; compare digests and exposure windows because affected images had valid historical signatures. Follow the incident remediation guidance for executed artifacts. Current advisory review: LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Current review: v1.108.12 LTS fixes tool_policy allowing a /v1/messages request through when a blocked tool name exceeded 64 characters. Upgrade the maintained LTS line and retest tool-policy enforcement. Scope: LiteLLM 1.108 LTS /v1/messages tool_policy; standard and other maintained lines require their own release review. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: Canonical incident investigation — https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain. Supporting source: Prior security-controls source — https://docs.litellm.ai/blog/security-incident-oct-21-2026.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Helm guide documents Kubernetes installation and configurable database/secret settings. Select matching chart/image versions and review the separate scaling and production-readiness guidance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.litellm.ai/docs/proxy/deploy/helm (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current production guide starts load testing at 1 vCPU and 4 GiB per worker, preferably one worker per Kubernetes pod. Memory depends on queued requests, payloads, stream duration and logging. PostgreSQL, Redis for multiple workers/instances, HA and model inference are additional. Scope: Gateway per-worker load-test starting point; backing services and inference excluded. Source: https://docs.litellm.ai/docs/proxy/prod (reviewed 2026-11-20).

- License pricing: Documented. Core code outside litellm/enterprise is MIT licensed; the enterprise directory has separate terms. Enterprise features and support need separate entitlement and pricing. Upstream model APIs, infrastructure and operating labour are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/BerriAI/litellm/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. LiteLLM v1.110.1 was published November 19, 2026. It refreshes the Wolfi base and changes the UI image to slim nginx, removing curl. The maintained v1.108.12 LTS line fixes a tool_policy bypass for blocked tool names longer than 64 characters. Scope: Upstream LiteLLM standard release; select and maintain either the standard or LTS line. Source: https://github.com/BerriAI/litellm/releases/tag/v1.110.1 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/BerriAI/litellm/releases/tag/v1.110.0. Supporting source: LiteLLM v1.108.11 LTS — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: v1.108.12 LTS security fix — https://github.com/BerriAI/litellm/releases/tag/v1.108.12.




### Security and lifecycle reviews

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

- LiteLLM LTS proxy security fixes (security-advisory): LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Scope: LiteLLM 1.108 LTS line; standard-line deployments should use their corresponding maintained release. Conditions: Applicability depends on Bedrock guardrails and team-setting permissions. Action: Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.11; reviewed 2026-11-18.

- LiteLLM 1.108.12 LTS tool-policy fix (security-advisory): LiteLLM 1.108.12 LTS prevents blocked tool names longer than 64 characters from bypassing tool_policy on /v1/messages. Scope: LiteLLM 1.108 LTS /v1/messages tool-policy enforcement. Conditions: The request must use a blocked tool name longer than 64 characters. Action: Upgrade the maintained LTS line to 1.108.12 or later and retest tool-policy enforcement. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12; reviewed 2026-11-19.




## LogicalDOC Commercial On-Premise

Customer-hosted commercial document platform for controlled business files and supplier documentation.

- Listing: https://launchinyourcloud.com/directory/logicaldoc-commercial/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial edition under LogicalDOC EULA; separate Community Edition exists
- Licensing model: commercial-only
- Installation: Licensed on-premises server installation
- Architecture: Persistent application with relational metadata database, document file storage and search services; selected components depend on edition.
- Operations: Customer manages application, database, document storage, backups and upgrades; agree support scope and required commercial capabilities.
- Product website: https://www.logicaldoc.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is a licensed commercial on-premises edition, not Community Edition feature parity. The supplier-document example uses configured metadata, expiry dates and periodic reports; it is a document process rather than a supplier-assessment service.

The selected licensed commercial edition follows LogicalDOC EULA restrictions. This classification does not cover the separate open-source Community Edition.

Persistent application with relational metadata database, document file storage and search services; selected components depend on edition.


### Category fit

- document-management: Searchable repository, metadata, versioning and configurable document workflows in a commercial on-premises deployment.

- vendor-supplier-document-management: Supplier certificate storage, expiry tracking and configured reports, documented in the Lesepidado implementation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 


### Cloud deployment evidence

- LogicalDOC private-cloud deployment options (aws, azure, gcp): https://www.logicaldoc.com/
  The vendor explicitly offers private-cloud installation on AWS, Azure and Google Cloud, separately from its managed LogicalDOC Cloud service. Confirm the commercial edition, system requirements and support agreement.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- On-premises deployment: https://www.logicaldoc.com/product/on-premise-dms

- Application and storage architecture: https://www.logicaldoc.com/product/architecture

- On-premises supplier certificate implementation: https://www.logicaldoc.com/blog/660-lesepidado-logicaldoc-case-study

- Commercial end-user license: https://www.logicaldoc.com/eula

### Licensing sources

- https://www.logicaldoc.com/eula

### Infrastructure sources

- https://www.logicaldoc.com/product/on-premise-dms

- https://www.logicaldoc.com/product/architecture


### 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 commercial administration guide documents SAML 2.0 service-provider integration, login-time account creation and optional single logout. It does not establish that every Business/Enterprise license includes the feature; confirm licensed features and test the identity provider. Scope: Commercial LogicalDOC documentation; edition/contract entitlement not established. Source: https://docs.logicaldoc.com/en/access-control/saml-single-sign-on (reviewed 2026-11-14).

- SCIM provisioning: Sources checked — unresolved. The SAML guide describes user creation at first login. It does not establish a SCIM provisioning/deprovisioning API or licensed entitlement; login-time account creation must not be labeled SCIM. Scope: SAML/JIT documentation checked; SCIM remains unresolved. Source: https://docs.logicaldoc.com/en/access-control/saml-single-sign-on (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes a logicaldoc/logicaldoc image and links its Docker distribution source. A licence activation code is required, including for evaluation. The catalog entry is dated 2018; confirm a currently supported image tag and matching database/Java requirements before adopting it. Scope: Vendor commercial Docker distribution; current supported artifact version must be confirmed. Source: https://www.logicaldoc.com/download/docker-images (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/logicaldoc/logicaldoc/. Artifact reference: Select a vendor-supported immutable image; catalog entry date is not a current release.

- Minimum footprint / sizing: Documented. The current vendor matrix specifies a dedicated 64-bit 2.5-GHz eight-core server, 24 GB memory and 512 GB fast disk for application deployment. It lists JDK 25 and current OS baselines. Concurrency, repository data, configuration and HA require additional sizing; older installation guides show different minima. Scope: Current vendor commercial-server requirements; verify against selected release. Source: https://www.logicaldoc.com/resources/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. The on-premises offer requires commercial licences and directs buyers to request a quote. No numeric price is established by the reviewed product page. Agree user counts, edition, term and maintenance separately from hosting and operating costs. Scope: Commercial on-premises offer; quoted licence terms, not Community pricing. Source: https://www.logicaldoc.com/product/on-premise-dms (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## M-Files On-Premises

Customer-operated document vault and information-governance platform with metadata-driven workflows.

- Listing: https://launchinyourcloud.com/directory/m-files-on-premises/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription software; on-premises and support entitlements follow the order
- Licensing model: commercial-only
- Installation: Licensed Windows Server installation; vendor implementation planning
- Architecture: Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.
- Operations: Customer maintains server infrastructure, vault backups and upgrades; review server requirements and the contracted support and licensing connections.
- Product website: https://www.m-files.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Only customer-operated M-Files deployment is listed. The documented SOP and records patterns require configuration and possibly selected components. Confirm the available edition, deployment scope and integrations rather than assuming that every separately packaged cloud solution is included.

Commercial M-Files server subscription software. The EULA covers ordered on-premises or cloud software and associated licenses/support; this entry selects on-premises operation.

Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.


### Category fit

- document-management: Metadata-driven document vaults with controlled access, document relationships and workflows.

- records-management: Configurable records retention and disposition rules with document history and audit trails.

- policy-procedure-management: Configured SOP, compliance and training workflows supported by metadata, permissions and document lifecycle controls; not a separately verified turnkey policy module.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 


### Cloud deployment evidence

- M-Files self-managed cloud deployment (aws, azure, gcp): https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html
  The vendor documents customer-managed Windows Server virtual machines on AWS, Azure and Google Cloud as the same server deployment model used on-premises. This is distinct from M-Files Cloud; confirm server, vault/database and licensing requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Customer-operated deployment options: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html

- Records retention and disposition: https://www.m-files.com/supplemental/records-management/

- SOP, training and governance application patterns: https://www.m-files.com/wp-content/uploads/2023/07/How-M-Files-Mitigates-Risks-for-Accounting-Firms.pdf

- Software subscription license agreement: https://empower.m-files.com/sfc/servlet.shepherd/version/download/068QA00000Y5dQGYAZ

### Licensing sources

- https://empower.m-files.com/sfc/servlet.shepherd/version/download/068QA00000Y5dQGYAZ

### Infrastructure sources

- https://userguide.m-files.com/user-guide/latest/eng/deployment_options.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 vault authentication guide explicitly links on-premises Microsoft Entra configuration and OAuth 2.0/OIDC providers for any environment. Client/web-add-in configuration and licensed implementation requirements remain separate. Scope: M-Files document-vault authentication; not Hubshare or automatic cloud login setup. Source: https://userguide.m-files.com/user-guide/latest/eng/document_vault_authentication.html (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. The guide documents subscription-level SCIM for on-premises servers joined to M-Files Manage. A separate vault-level Entra SCIM method requires Entra ID Premium and limits Entra authentication to Desktop; on-premises plugin-based synchronization is also documented. Scope: M-Files on-premises provisioning; Manage connection, method and client limitations differ. Source: https://userguide.m-files.com/user-guide/latest/eng/user_synchronization_entra_id.html (reviewed 2026-11-16).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies an installation package containing Server, Admin and optional desktop components. The guide links the latest package through the vendor download portal and documents advanced installation options. Package access and entitlements must be obtained; this is not a public infrastructure template. Scope: Current on-premises Windows installer distribution. Source: https://www.userguide.m-files.com/user-guide/latest/eng/Installing_the_software.html (reviewed 2026-11-20). Deployment artifact: https://product.m-files.com/downloads/. Artifact reference: Vendor latest-download portal; authenticated or entitled access may be required.

- Minimum footprint / sizing: Documented. The single-server guide lists 2 CPU cores, 1 GB RAM and 300 MB for M-Files Server itself. Its examples scale to 4 cores/4 GB for 50,000 objects and 8 cores/16 GB plus SQL Server for one million. File storage, database, backups and HA need separate sizing; these are object-count examples, not a 100-user guarantee. Scope: Vendor single-server guidelines; application storage and HA excluded. Source: https://userguide.m-files.com/user-guide/latest/eng/hardware_guidelines_for_single_server_environments.html (reviewed 2026-11-20).

- License pricing: Documented. The on-premises server is linked to a customer subscription using an initial licence from M-Files Manage. Automated renewal needs outbound licensing endpoints. This establishes subscription/licence delivery, not a published per-user price or infrastructure cost. Scope: On-premises server subscription and licence automation. Source: https://userguide.m-files.com/user-guide/latest/eng/?contextId=133304 (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## MailStore Service Provider Edition (SPE)

Commercial multitenant email archive operated by service providers in their own cloud accounts.

- Listing: https://launchinyourcloud.com/directory/mailstore-spe/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage.
- Operations: The service provider operates SPE in its own cloud account and serves its customers; this is not an end-customer-owned mailbox archive.
- Product website: https://help.mailstore.com/en/spe/Frequently_Asked_Questions
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The buyer/operator is the service provider. Its end customers do not thereby own the provider's cloud account. SPE licensing and tenant operations are separate from MailStore Server and from a vendor-hosted archive subscription; account for the documented storage and I/O demands.

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

MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- records-management: Commercial multitenant email archive operated by service providers in their own cloud accounts.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.mailstore.com/en/spe/Frequently_Asked_Questions (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.mailstore.com/en/spe/Frequently_Asked_Questions (checked 2026-11-19). 


### Cloud deployment evidence

- MailStore SPE FAQ (aws, azure): https://help.mailstore.com/en/spe/Frequently_Asked_Questions
  MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage. The buyer/operator is the service provider. Its end customers do not thereby own the provider's cloud account. SPE licensing and tenant operations are separate from MailStore Server and from a vendor-hosted archive subscription; account for the documented storage and I/O demands.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- MailStore SPE FAQ: https://help.mailstore.com/en/spe/Frequently_Asked_Questions

- MailStore SPE Product: https://www.mailstore.com/en/products/mailstore-spe/

- SPE Changelog (v26.4): https://www.mailstore.com/en/products/mailstore-spe/changelog/

### Licensing sources

- https://www.mailstore.com/en/products/mailstore-spe/

### Infrastructure sources

- https://help.mailstore.com/en/spe/Frequently_Asked_Questions


### 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. SPE end-user access documents redirecting synchronised Microsoft 365 or Google Workspace users to the provider for authentication, including client and web access. Configure the tenant instance and directory integration. This does not establish the same mechanism for the service-provider management console. Scope: MailStore SPE tenant archive-user federated login; infrastructure administrators separate. Source: https://help.mailstore.com/en/spe/End_User_Access (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. SPE supplies a Windows installer through its partner portal that installs binaries for any server role; initial configuration assigns single-server or distributed roles. Obtain partner access and licence, then configure instances, TLS, firewall, persistent storage and updates. Scope: MailStore SPE partner-delivered role installer; operational configuration separate. Source: https://help.mailstore.com/en/spe/Installing_MailStore_Service_Provider_Edition (reviewed 2026-11-21). Deployment artifact: https://help.mailstore.com/en/spe/Installing_MailStore_Service_Provider_Edition. Artifact reference: Current vendor SPE installation instructions.

- Minimum footprint / sizing: Documented. The SPE requirements give each standalone Management Server and Client Access Server 2 GB RAM and 150 MB installation disk, with x64 CPU; archive Instance Hosts have separate workload-dependent requirements. These role baselines exclude stored mail/indexes, database working sets, replicas and HA capacity. Scope: MailStore SPE management/access role minimums; not a whole archive host or HA footprint. Source: https://help.mailstore.com/en/spe/System_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: MailStore Service Provider Edition (SPE); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.mailstore.com/en/products/mailstore-spe/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Matomo On-Premise

Self-hosted web analytics with visitor, campaign and website reporting on customer servers.

- Listing: https://launchinyourcloud.com/directory/matomo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3-or-later core; premium plugins use separate commercial EULA and subscription terms
- Licensing model: open-source
- Installation: PHP web-server installation or official Docker image
- Architecture: Customer-operated analytics application and MySQL/MariaDB database with scheduled report processing
- Operations: Customer manages hosting, upgrades, security, backups, tracking configuration and scheduled report processing.
- Product website: https://matomo.org/
- 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 covers Matomo On-Premise rather than Matomo Cloud. Core analytics can be self-hosted, while premium capabilities and support may require separate purchases. Configure collection, consent and retention deliberately rather than treating the deployment model as a privacy-compliance guarantee.

Matomo On-Premise combines a GPLv3 core and open-source plugins with separately licensed commercial premium plugins. Premium plugin source and redistribution rights are governed by the InnoCraft EULA rather than the core GPL license.

Official installation runs on a web/shared/dedicated server with a database, or using the official Docker image. Higher-volume reporting uses a scheduled cron task rather than an event-driven application runtime.


### Category fit

- web-analytics: Website traffic, campaign and behavior analytics on customer-controlled servers; premium analytics plugins have separate commercial licensing.

- data-analytics: Website analytics and reporting over collected visitor and event data; scope is web measurement rather than a general data warehouse.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://matomo.org/faq/how-to-install/faq_31411/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://matomo.org/faq/how-to-install/faq_31411/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://matomo.org/faq/how-to-install/faq_31411/ (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://matomo.org/faq/how-to-install/faq_31411/ (checked 2026-11-12). 


### Cloud deployment evidence

- Matomo named-cloud compatibility FAQ (aws, azure, gcp, alibaba): https://matomo.org/faq/how-to-install/faq_31411/
  The vendor explicitly confirms Matomo On-Premise compatibility with AWS, Azure, Google Cloud and Alibaba Cloud, and links its installation requirements. This is a compatibility statement, not a cloud-provider certification or a managed Matomo Cloud offering.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- On-Premise product scope: https://matomo.org/matomo-on-premise/

- Official installation instructions: https://matomo.org/faq/on-premise/installing-matomo/

- Core and premium plugin licenses: https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/

- Core legal notice: https://raw.githubusercontent.com/matomo-org/matomo/5.x-dev/LEGALNOTICE

- Licensing and edition terms: https://matomo.org/faq/general/faq_22573/

### Licensing sources

- https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/

- https://matomo.org/faq/general/faq_22573/

- https://raw.githubusercontent.com/matomo-org/matomo/5.x-dev/LEGALNOTICE

### Infrastructure sources

- https://matomo.org/faq/on-premise/installing-matomo/


### 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. On-premises SAML uses the paid LoginSAML premium feature from Matomo Marketplace. Provider setup and user provisioning options require configuration; this is separate from a Matomo Cloud subscription. Scope: Self-hosted Matomo with LoginSAML premium feature. Source: https://matomo.org/faq/general/set-up-login-with-saml-authentication/ (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 Matomo-maintained Docker repository supplies application/web-server and database examples. Persistent data, TLS, scheduled archiving and plugin/edition choices require deployment-specific configuration. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/matomo-org/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/matomo-org/docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. For up to 100k monthly page views the vendor suggests one server with 2 CPUs, 2 GB RAM and 50 GB SSD; at 1 million, 4 CPUs, 8 GB and 250 GB SSD. Larger workloads separate database and application roles. Tracking requests, segments and retention govern sizing; 100 internal users and 1 TB alone do not define an HA analytics workload. Scope: On-premises traffic-tier recommendations; not a benchmark or total operating-cost estimate. Source: https://matomo.org/faq/on-premise/matomo-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. The On-Premise core is free to download under GPLv3; premium plugins and support have separate commercial terms. The paid LoginSAML feature is not implied by the free core. Select the plugin/site entitlements and current quote separately from server and operations costs. Scope: Core versus commercial plugin software terms; excludes Matomo Cloud and infrastructure. Source: https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/ (reviewed 2026-11-20). Supporting source: On-Premise product and free core — https://matomo.org/matomo-on-premise/.

- Operating cost estimate: Not researched.

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







## Mattermost Self-Hosted

Self-hosted team messaging and collaborative operational workflows on customer infrastructure.

- Listing: https://launchinyourcloud.com/directory/mattermost/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, oci, aws, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Team Edition; commercial Enterprise offerings and separately licensed components; inspect the selected edition
- Licensing model: open-source
- Installation: Linux binary/packages or Mattermost Kubernetes Operator; provider architectures and Azure/OCI Marketplace guides
- Architecture: Customer-operated application with PostgreSQL and file/object storage
- Operations: Customer maintains the deployment, database, storage, upgrades and availability; subscriptions govern supported enterprise capabilities.
- Product website: https://mattermost.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

Team Edition is intended for small teams and lacks the commercial governance and enterprise identity capabilities. Enterprise Entry has limits; paid features require the applicable subscription. The current Docker Compose guide is for evaluation/testing and is not recommended for production/HA. The vendor provides AWS and Google Cloud self-hosted architectures alongside Azure VM and OCI OKE deployment guides. Mattermost 12.0.2 and the November 5 patches for maintained 11.x branches contain medium-to-high severity security fixes. For v12 upgrades, verify community and custom plugin compatibility.

The listed self-hosted family includes MIT Team Edition and commercial Enterprise offerings with proprietary capabilities and feature entitlements. The license of a public core, community build or plugin must not be applied to the complete Enterprise distribution.

Production documentation uses persistent Linux application hosts or Kubernetes, PostgreSQL and file storage. Azure provisions a VM scale set; the OCI option provisions OKE and managed database/storage components. Mattermost 12 drops RHEL 7 and 8, requires glibc 2.34 or later, PostgreSQL 15 or later, and OpenSearch 2.x or later.


Cloud evidence scope: Official customer-subscription Azure VM and customer-tenancy Oracle OKE guides establish these paths; unreviewed provider badges are omitted.

### Category fit

- collaboration: Team channels, messaging, file sharing and collaborative operational workflows; production scale, identity and governance capabilities depend on edition.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke (checked 2026-11-12). 

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

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


### Cloud deployment evidence

- Mattermost customer cloud deployment on Azure (azure): https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm
  The vendor documents the full Mattermost application in the customer Azure subscription or OCI tenancy. The OKE Marketplace option uses Enterprise Edition; Kubernetes/Operator and enterprise features require their applicable plan, separate from Team Edition and the evaluation-only Compose example.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Mattermost customer cloud deployment on Oracle Cloud (oci): https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke
  The vendor documents the full Mattermost application in the customer Azure subscription or OCI tenancy. The OKE Marketplace option uses Enterprise Edition; Kubernetes/Operator and enterprise features require their applicable plan, separate from Team Edition and the evaluation-only Compose example.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Mattermost self-hosted provider architecture and sizing (aws, gcp): https://docs.mattermost.com/deployment-guide/deployment-architecture
  The vendor architecture builder explicitly includes AWS and Google Cloud hosting for the self-hosted application, with separate VM and Kubernetes deployment options and linked installation instructions. These are application hosting architectures, not Mattermost Cloud residency or storage adapters. Provider SKU suggestions are illustrative; size and validate the selected deployment and edition.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Editions and feature restrictions: https://docs.mattermost.com/product-overview/editions-and-offerings

- Business and licensing: https://docs.mattermost.com/product-overview/faq-license

- Linux deployment: https://docs.mattermost.com/deployment-guide/server/deploy-linux

- Kubernetes deployment: https://docs.mattermost.com/deployment-guide/server/deploy-kubernetes

- Container deployment caveats: https://docs.mattermost.com/deployment-guide/server/deploy-containers

- Azure Native VM deployment: https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm

- Oracle OKE deployment: https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke

- Licensing and edition terms: https://docs.mattermost.com/developers/integrate/plugins/source-available-license

- Mattermost self-hosted provider architecture and sizing: https://docs.mattermost.com/deployment-guide/deployment-architecture

- Mattermost v12 security and upgrade changelog: https://docs.mattermost.com/product-overview/mattermost-v12-changelog

### Licensing sources

- https://docs.mattermost.com/product-overview/editions-and-offerings

- https://docs.mattermost.com/product-overview/faq-license

- https://docs.mattermost.com/developers/integrate/plugins/source-available-license

### Infrastructure sources

- https://docs.mattermost.com/deployment-guide/server/deploy-linux

- https://docs.mattermost.com/deployment-guide/server/deploy-kubernetes

- https://docs.mattermost.com/product-overview/mattermost-v12-changelog


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The current SAML documentation lists Entry, Professional, Enterprise and Enterprise Advanced. It distinguishes tested Okta, OneLogin and ADFS integrations from custom identity providers that require validation. Scope: Current Mattermost commercial distribution plan names; not a blanket Team Edition entitlement. Source: https://docs.mattermost.com/onboard/sso-saml (reviewed 2026-11-14).

- SCIM provisioning: Explicitly unsupported. The SAML provisioning FAQ explicitly states SCIM is not supported and refers administrators to AD/LDAP for provisioning/deactivation. This is a documented limitation, rather than an unanswered field. Scope: Current SAML user-lifecycle documentation; recheck for the selected release. Source: https://docs.mattermost.com/administration-guide/onboard/sso-saml-entraid (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official container guide uses the mattermost/docker Compose repository with application and PostgreSQL containers and an optional NGINX proxy. Configure secrets, persistent paths, domain and TLS; the quick-start Compose stack is not automatically a clustered production deployment. Scope: Self-managed Docker deployment; HA architecture is a separate design. Source: https://docs.mattermost.com/deployment-guide/server/deploy-containers.html (reviewed 2026-11-20). Deployment artifact: https://github.com/mattermost/docker. Artifact reference: Moving deployment repository; pin supported server and PostgreSQL versions.

- Minimum footprint / sizing: Documented. The upstream traditional-deployment guide gives a small-team baseline of 1 vCPU and 2 GB RAM for 1–1,000 registered users. Activity, peak file sharing, database/storage and multi-server HA alter sizing; this is not a complete 1-TB HA design. Scope: Upstream small/medium single-server baseline; enterprise multi-server sizing is separate. Source: https://docs.mattermost.com/deployment-guide/software-hardware-requirements.html (reviewed 2026-11-20).

- License pricing: Documented. The current offerings guide distinguishes commercial self-hosted Enterprise Edition from its free Entry mode and paid subscriptions. Entry has server-wide feature/usage limits; advanced entitlements require a trial or subscription. Exact paid-plan pricing and infrastructure costs remain separate. Scope: Current self-hosted Entry/Enterprise offerings; do not reuse historical Team Edition or SaaS pricing. Source: https://docs.mattermost.com/product-overview/editions-and-offerings.html (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.

- Mattermost maintained-line security review (security-advisory): The v12 changelog records medium/high security fixes and important runtime and plugin compatibility changes. Scope: Mattermost 12.0.2 and the maintained 11.x patches identified in the November 5 security notice. Conditions: Individual vulnerability details follow the vendor disclosure schedule; plugins, PostgreSQL and optional search integrations have separate compatibility requirements. Action: Use the appropriate maintained-line patch. For v12, review plugin compatibility, glibc 2.34+, PostgreSQL 15+ and OpenSearch 2.x+ where used. Source: https://docs.mattermost.com/product-overview/mattermost-v12-changelog; reviewed 2026-11-17.




## Medplum Self-Hosted

Open-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/medplum-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: hybrid
- License: Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate.
- Licensing model: open-source
- Installation: AWS CDK, or Terraform and Helm on Azure AKS or Google GKE
- Architecture: Containerized API and web application with PostgreSQL, cache, object storage, secrets and load-balancing or CDN services
- Operations: Customer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.
- Product website: https://www.medplum.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 official AWS, Azure and GCP guides deploy both backend and frontend components. Enterprise support is optional and does not change the Apache-2.0 classification of the selected Community software; validate healthcare compliance scope and local operating controls separately. The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling. Upgrade a compatible server/application bundle to v5.2.17 or later and test identity/delegation flows. Assess whether application secrets were exposed and rotate them where appropriate.

The Community software is Apache-2.0; Enterprise Self-Hosted support is a separate commercial service.

The deployment combines customer Kubernetes or container compute with managed database, cache, storage, secrets and network services.


### Category fit

- backend-platforms: Provides a FHIR datastore, APIs, OAuth identity, application SDKs and clinical backend services on customer infrastructure.

- workflow-automation: Medplum Bots, cron jobs, subscriptions and triggers automate clinical and operational workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-gcp (checked 2026-11-19). 


### Cloud deployment evidence

- Complete Medplum installation in a customer AWS account (aws): https://www.medplum.com/docs/self-hosting/install-on-aws
  Medplum describes a complete production-ready installation in the customer's AWS environment and deploys the application and supporting AWS resources with CDK.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Production-validated Medplum deployment on Azure (azure): https://www.medplum.com/docs/self-hosting/install-on-azure
  The official Terraform and Helm workflow deploys Medplum into the customer's Azure subscription with AKS, PostgreSQL, Redis, storage, gateway and frontend resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Production-validated Medplum deployment on Google Cloud (gcp): https://www.medplum.com/docs/self-hosting/install-on-gcp
  The official Terraform and Helm workflow deploys Medplum into the customer's Google Cloud project with GKE, Cloud SQL, Redis, storage and frontend resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes codyebberson, mattwiller, ThatOneBro, 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/medplum/medplum/graphs/contributors

- Reviewed upstream application release: https://github.com/medplum/medplum/releases/tag/v5.2.17

### Sources

- Medplum production installation on AWS: https://www.medplum.com/docs/self-hosting/install-on-aws

- Medplum production installation on Azure: https://www.medplum.com/docs/self-hosting/install-on-azure

- Medplum production installation on Google Cloud: https://www.medplum.com/docs/self-hosting/install-on-gcp

- Medplum open-source terms: https://www.medplum.com/open-source

- Medplum self-hosted support plans: https://www.medplum.com/pricing

- Reviewed deployment artifact reference: https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk

- Buyer evidence: release: https://github.com/medplum/medplum/releases/tag/v5.2.17

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

### Licensing sources

- https://www.medplum.com/open-source

- https://www.medplum.com/pricing

### Infrastructure sources

- https://www.medplum.com/docs/self-hosting/install-on-aws

- https://www.medplum.com/docs/self-hosting/install-on-azure

- https://www.medplum.com/docs/self-hosting/install-on-gcp


### Buyer diligence


Research coverage: 12/12 fields (100%); 4 documented, 8 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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Security controls: Edition-dependent. The production guides deploy secrets, TLS termination, identity and private data services within the customer's cloud environment. Healthcare compliance still depends on the buyer's configuration, agreements, audit controls and operating procedures. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- 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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The tagged @medplum/cdk 5.2.17 source supplies the AWS CDK application used by the installation guide. The CLI, server image, frontend build and Azure/GCP Terraform/Helm packages remain separately selected artifacts; one CDK tag does not pin the whole stack. Scope: Medplum Community AWS IaC source, independently versioned from other deployment components. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19). Deployment artifact: https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk. Artifact reference: @medplum/cdk 5.2.17 at upstream tag v5.2.17.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed sources describe the deployment components but do not provide one complete production sizing model for the buyer's users, data volume, traffic, retention and availability target. Size every application and managed-service dependency. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- License pricing: Documented. Medplum Community is Apache-2.0 and can be self-hosted without a software license fee; the Enterprise Self-Hosted support plan is separately commercial. Infrastructure, support and healthcare compliance work are separate. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/open-source (reviewed 2026-11-19). Supporting source: Commercial support plans — https://www.medplum.com/pricing.

- 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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The reviewed upstream v5.2.17 release was published 2026-11-11. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence. It includes authentication-response secret removal and on-behalf-of delegation hardening. Scope: Medplum Self-Hosted upstream application, independently versioned from provider packages. Source: https://github.com/medplum/medplum/releases/tag/v5.2.17 (reviewed 2026-11-19).




### Security and lifecycle reviews

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

- Medplum 5.2.17 authentication and delegation hardening (security-advisory): The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling. Scope: The authentication/me and delegation paths named in the v5.2.17 release; no universal affected-version range or CVE is asserted. Conditions: Applicability depends on the installed server build and use of the affected authentication/delegation endpoints. Action: Upgrade a compatible server/application bundle to v5.2.17 or later and test identity/delegation flows. Assess whether application secrets were exposed and rotate them where appropriate. Source: https://github.com/medplum/medplum/releases/tag/v5.2.17; reviewed 2026-11-19.




## Mendix on Kubernetes

Commercial low-code application runtime operated in customer Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/mendix-private-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, stackit
- Operating model: Customer-operated · vendor control plane
- 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: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers.
- Operations: Customer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.
- Product website: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.

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

Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- internal-tools: Commercial low-code application runtime operated in customer Kubernetes infrastructure.

- workflow-automation: Commercial low-code application runtime operated in customer Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- stackit: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

Operating responsibility: In the selected Connected mode the customer supplies and operates the Kubernetes runtime, database, storage and backups. The Mendix Portal controls deployments through an in-cluster agent. This is not a vendor-operated application service. Source: https://docs.mendix.com/developerportal/deploy/private-cloud/ (checked 2026-11-20).


### Cloud deployment evidence

- Supported Clouds (aws, azure, gcp, stackit): https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/
  Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Supported Clouds: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/

- Private Cloud Deploy: https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/

- Insurance Claims: https://www.mendix.com/industries/insurance/

- Outside-Cloud Licensing: https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/

- Mendix Legal: https://www.mendix.com/legal/

- Mendix on K8s RN: https://docs.mendix.com/releasenotes/developer-portal/mendix-for-private-cloud/

### Licensing sources

- https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/

- https://www.mendix.com/legal/

### Infrastructure sources

- https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/


### 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. Mendix documents SAML and OIDC modules for end-users of deployed apps, with module/runtime compatibility and app-level configuration. The SAML guide explicitly addresses apps outside Mendix Cloud and requires external file storage. This is separate from developer-portal or Private Mendix Platform login. Scope: Application end-user federation on a compatible Mendix runtime; verify module dependencies and app configuration. Source: https://docs.mendix.com/appstore/modules/saml/ (reviewed 2026-11-20). Supporting source: OIDC module and supported runtime versions — https://docs.mendix.com/appstore/modules/oidc/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Kubernetes deployment guides register a cluster/namespace, install the Mendix Operator and deploy app environments from the Mendix Portal or Kubernetes custom resources. Database, file storage, registry, network access and licensed runtime configuration remain deployment inputs. Scope: Mendix on Kubernetes deployment workflow; operator, runtime and application releases are separate. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/ (reviewed 2026-11-20). Supporting source: Cluster and operator setup — https://docs.mendix.com/developerportal/deploy/private-cloud-cluster/.

- Minimum footprint / sizing: Documented. The supported-provider guide requires at least 2 CPU cores, 2 GB memory and 3 GB ephemeral storage available on a node for one simple app, excluding Kubernetes core components. Production databases, file storage, image building and multiple replicas need additional sizing; experimental ARM64 support is limited to non-production Connected Mode. Scope: One simple app baseline, excluding cluster overhead and HA/1-TB workload capacity. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Mendix on Kubernetes; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Merative Cúram Social Program Management

Commercial social-program case-management software with customer Kubernetes runbooks.

- Listing: https://launchinyourcloud.com/directory/merative-spm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: Kubernetes manifests
- Architecture: Licensed Cúram application and supported data services on EKS or AKS.
- 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/merative/curam-kubernetes
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The public containerization assets are not the commercial application licence. Keep runbook/container-packaging releases separate from the licensed Cúram release and validate the supported database/runtime matrix.

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

Licensed Cúram application and supported data services on EKS or AKS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- case-management: Commercial social-program case-management software with customer Kubernetes runbooks.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/eks-consideration/security.mdx (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/aks-consideration/security.mdx (checked 2026-11-19). 


### Cloud deployment evidence

- EKS Source (aws): https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/eks-consideration/security.mdx
  Licensed Cúram application and supported data services on EKS or AKS. The public containerization assets are not the commercial application licence. Keep runbook/container-packaging releases separate from the licensed Cúram release and validate the supported database/runtime matrix.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- AKS Source (azure): https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/aks-consideration/security.mdx
  Licensed Cúram application and supported data services on EKS or AKS. The public containerization assets are not the commercial application licence. Keep runbook/container-packaging releases separate from the licensed Cúram release and validate the supported database/runtime matrix.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- EKS Source: https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/eks-consideration/security.mdx

- AKS Source: https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/aks-consideration/security.mdx

- Curam K8s README: https://github.com/merative/curam-kubernetes/blob/main/README.md

- EKS Guide: https://merative.github.io/curam-kubernetes/architecture/eks-consideration/security/

- AKS Guide: https://merative.github.io/curam-kubernetes/architecture/aks-consideration/security/

- Cúram Site: https://www.curaminnovations.com/

- Merative Terms: https://www.merative.com/terms

- Cúram K8s Releases: https://github.com/merative/curam-kubernetes/releases

### Licensing sources

- https://www.merative.com/terms

### Infrastructure sources

- https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/eks-consideration/security.mdx

- https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/aks-consideration/security.mdx


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The chart includes an optional Keycloak/Liberty OIDC configuration for application paths, but its sample sets signatureAlgorithm to none. A secure, release-matched provider configuration, token-validation policy and supported login flow were not established. Kubernetes IAM authentication and older Universal Access portal examples do not settle current caseworker SSO. Scope: Cúram application identity candidate; secure production configuration and release support remain unconfirmed. Source: https://github.com/merative/curam-kubernetes/blob/main/helm-charts/apps/templates/configmaps/configmap-oidc.yaml (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The public repository documents Kubernetes deployment and cloud architecture. Its Apache-2.0 documentation/assets do not establish access to a licensed, versioned Cúram application chart or image. Scope: Cúram deployment documentation versus licensed runtime artifacts. Source: https://github.com/merative/curam-kubernetes/blob/main/README.md (reviewed 2026-11-19).

- Minimum footprint / sizing: Documented. The active chart defaults enable the Cúram application with pod requests of 1 CPU/2.5 GiB and limits of 1.5 CPU/3 GiB; deployment templates consume these values. They exclude database, messaging, batch, other applications, OpenShift/Kubernetes overhead, replicas and persistent data. Commented examples are not counted as active defaults. Scope: Moving vendor Cúram chart application-pod defaults, not full production/HA capacity. Source: https://github.com/merative/curam-kubernetes/blob/main/helm-charts/apps/values.yaml (reviewed 2026-11-21). Supporting source: Resource-consuming deployment template — https://github.com/merative/curam-kubernetes/blob/main/helm-charts/apps/templates/deployment-producer.yaml.

- License pricing: Sources checked — unresolved. Current Cúram deployment assets do not establish the customer’s commercial runtime agreement or price; historical Merative website terms and the Apache-licensed deployment repository are separate scopes. Scope: Selected self-managed application or customer-cloud service; contract confirmation required. Source: https://www.curaminnovations.com/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## Milvus

Vector database for similarity search and retrieval over embedding collections.

- Listing: https://launchinyourcloud.com/directory/milvus/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Milvus.
- Licensing model: open-source
- Installation: Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements.
- Architecture: Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services
- Operations: Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.
- Product website: https://milvus.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Current installation scripts can track a different image than a selected stable release; use versioned configurations for reproducibility. Model inference and embedding generation are separate workloads. Managed Zilliz offerings are outside this listing.

Apache License 2.0 for upstream Milvus. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- databases-vector: Vector database for approximate nearest-neighbor retrieval over embeddings and associated metadata.

- ai-tools: Embedding storage and vector retrieval infrastructure for AI search and RAG applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/eks.md (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/azure.md (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/gcp.md (checked 2026-11-12). 


### Cloud deployment evidence

- Milvus deployment on Amazon EKS (aws): https://milvus.io/docs/eks.md
  Official instructions provision Amazon EKS and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Milvus deployment on Azure Kubernetes Service (azure): https://milvus.io/docs/azure.md
  Official instructions provision Azure Kubernetes Service and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Milvus deployment on Google Kubernetes Engine (gcp): https://milvus.io/docs/gcp.md
  Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Milvus documents governance under the LF AI & Data Foundation with Zilliz as a major contributor. Its public release stream records continuing October 2026 maintenance.

Reviewed 2026-11-10.

- Foundation and contributing community: https://github.com/milvus-io/milvus

- Current release maintenance: https://github.com/milvus-io/milvus/releases

### Sources

- Official installation and runtime: https://milvus.io/docs/install_standalone-docker.md

- Upstream project and capabilities: https://github.com/milvus-io/milvus

- Current upstream license: https://github.com/milvus-io/milvus/blob/master/LICENSE

### Licensing sources

- https://github.com/milvus-io/milvus/blob/master/LICENSE

### Infrastructure sources

- https://milvus.io/docs/install_standalone-docker.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: Sources checked — unresolved. The current core authentication guide uses username/password credentials and SDK token fields with explicitly enabled authorization. It does not establish native SAML/OIDC federation or automatic IdP/group mapping. Hosted Zilliz console SSO is a different deployment; confirm an upstream integration before relying on it. Scope: Self-hosted Milvus core user authentication; federation unresolved. Source: https://milvus.io/docs/authenticate.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official standalone Docker guide links a script fetched from master. Its image selection moves and its upgrade command does not validate arbitrary version transitions; inspect the script and use matching versioned Compose when required. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://milvus.io/docs/install_standalone-docker.md (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/milvus-io/milvus/master/scripts/standalone_embed.sh. Artifact reference: master script (moving; inspect its selected image).

- Minimum footprint / sizing: Documented. The standalone requirements specify 8 GB RAM, recommend 16 GB and recommend at least 4 CPU cores with a supported SIMD instruction set. Dataset/index size and storage performance govern actual resources; distributed requirements differ. Scope: Milvus 3.0.x standalone requirements as reviewed. Source: https://milvus.io/docs/prerequisite-docker.md (reviewed 2026-11-14).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v3.0.6, 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 milvus-io/milvus release record; commercial editions and deployment packages may differ. Source: https://github.com/milvus-io/milvus/releases/tag/v3.0.6 (reviewed 2026-11-14).







## MLflow Tracking Server Self-Hosted

Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.

- Listing: https://launchinyourcloud.com/directory/mlflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.
- Licensing model: open-source
- Installation: Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment.
- Architecture: Customer-operated tracking/API server with configurable metadata database and artifact storage
- Operations: Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.
- Product website: https://mlflow.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Traces can capture model inputs, outputs and intermediate metadata. Point clients at the customer-hosted server and review recording/redaction settings. Applications, evaluators and optional model integrations may still call external providers; hosting the tracking server does not host all training or inference runtimes. Production database, storage and security configuration differ from a local quickstart.

The upstream self-hosted tracking server is Apache-2.0 licensed. This classification does not extend to separate managed MLflow distributions, connected model providers or their commercial services.

The tracking server runs as a Python service or container with metadata/artifact stores. A local SQLite example is not a production architecture; separately plan persistent database, storage and application-runtime infrastructure.


### Category fit

- ai-observability: Experiment tracking and LLM/agent tracing server. This entry describes customer-hosted tracking/observability services, not every model runtime, managed MLflow product or inference backend.

- ai-tools: Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.

- observability: Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/ (checked 2026-11-12). 


### Cloud deployment evidence

- Self-hosted MLflow deployment on AWS (aws): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/
  The project documents deployment of the MLflow server, metadata database and artifact storage on AWS. This does not refer to a managed MLflow edition or to model serving alone.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Self-hosted MLflow deployment on Azure (azure): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/
  The project documents deployment of the MLflow server, metadata database and artifact storage on Azure. This does not refer to a managed MLflow edition or to model serving alone.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Self-hosted MLflow deployment on Google Cloud (gcp): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/
  The project documents deployment of the MLflow server, metadata database and artifact storage on Google Cloud. This does not refer to a managed MLflow edition or to model serving alone.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting server and deployment methods: https://mlflow.org/docs/latest/self-hosting/

- LLM/agent tracing and captured data: https://mlflow.org/docs/latest/genai/tracing/

- Apache 2.0 license: https://github.com/mlflow/mlflow/blob/master/LICENSE.txt

### Licensing sources

- https://github.com/mlflow/mlflow/blob/master/LICENSE.txt

### Infrastructure sources

- https://mlflow.org/docs/latest/self-hosting/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official guide documents the community-maintained mlflow-oidc-auth plugin and an SSO reverse-proxy pattern. This provides UI/API OIDC integration, but plugin maintenance, MLflow-version compatibility and client token behavior require separate review; it is not a claim of vendor-operated identity support. Scope: Officially documented community-plugin/proxy integration. Source: https://mlflow.org/docs/latest/self-hosting/security/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. The self-hosting guide links an upstream Compose bundle with MLflow, PostgreSQL and object storage, plus an official Helm option. Configure production credentials and persistence rather than retaining development defaults. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://mlflow.org/docs/latest/self-hosting/ (reviewed 2026-11-14). Deployment artifact: https://github.com/mlflow/mlflow/tree/master/docker-compose. Artifact reference: master Compose bundle (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted guide documents the UI/API tracking server, metadata backend and artifact-store configuration, but not a universal production CPU/RAM minimum. Size runs/traces, request concurrency, database, artifact storage and redundancy; starting the default local SQLite server does not establish production or HA capacity. Scope: Self-hosted tracking-server topology; numeric production sizing unresolved. Source: https://mlflow.org/docs/latest/self-hosting/architecture/tracking-server/ (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/mlflow/mlflow/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## MyWorkDrive

Commercial private-cloud file access and controlled sharing across organizations.

- Listing: https://launchinyourcloud.com/directory/myworkdrive/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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; Package / binary installer
- Architecture: MyWorkDrive application and controlled file shares on customer AWS or Azure Windows 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://www.myworkdrive.com/file-server/cloud/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 M&A use case concerns cross-organization access to files, including after a transaction. It is not a complete deal-process or legal-review application. Directory integration, share permissions, externally shared data and licence counts require deliberate configuration.

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

MyWorkDrive application and controlled file shares on customer AWS or Azure Windows infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial private-cloud file access and controlled sharing across organizations.

- data-rooms-ma-document-management: Commercial private-cloud file access and controlled sharing across organizations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.myworkdrive.com/file-server/cloud/aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.myworkdrive.com/file-server/azure (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Guide (aws): https://www.myworkdrive.com/file-server/cloud/aws
  MyWorkDrive application and controlled file shares on customer AWS or Azure Windows infrastructure. The M&A use case concerns cross-organization access to files, including after a transaction. It is not a complete deal-process or legal-review application. Directory integration, share permissions, externally shared data and licence counts require deliberate configuration.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://www.myworkdrive.com/file-server/azure
  MyWorkDrive application and controlled file shares on customer AWS or Azure Windows infrastructure. The M&A use case concerns cross-organization access to files, including after a transaction. It is not a complete deal-process or legal-review application. Directory integration, share permissions, externally shared data and licence counts require deliberate configuration.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Guide: https://www.myworkdrive.com/file-server/cloud/aws

- Azure Guide: https://www.myworkdrive.com/file-server/azure

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

- M&A Data Room: https://www.myworkdrive.com/mergers-acquisitions

- Pricing Plans: https://www.myworkdrive.com/pricing-plans

- Release Notes: https://www.myworkdrive.com/kb/articles/server-release-notes

### Licensing sources

- https://www.myworkdrive.com/pricing-plans

### Infrastructure sources

- https://www.myworkdrive.com/file-server/cloud/aws

- https://www.myworkdrive.com/file-server/azure


### 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 Amazon Machine Image (AMI) from MyWorkDrive. Its package version is MyWorkDrive File Sharing Server 7.3.1.48; verify the contained application and required entitlements separately. Scope: MyWorkDrive selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-6mpsk5rxrewac (reviewed 2026-11-19). Offer prodview-6mpsk5rxrewac: MyWorkDrive; Amazon Machine Image (AMI); package MyWorkDrive File Sharing Server 7.3.1.48; https://aws.amazon.com/marketplace/pp/prodview-6mpsk5rxrewac.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Active Directory mode supports SAML 2.0 providers, including Entra ID, Okta and OneLogin, with optional SSO enforcement. Entra ID directory mode uses native Microsoft login instead; select the identity mode at installation and review delegation and logout configuration. Scope: Server identity mode affects the authentication path. Source: https://www.myworkdrive.com/kb/articles/server-setup-guide (reviewed 2026-11-20). Supporting source: Entra ID mode differs from SAML mode — https://www.myworkdrive.com/kb/articles/getting-started-with-myworkdrive-version-7-using-entra-id-identity-and-azure-storage.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The server setup guide uses MyWorkDrive-Setup.exe downloaded from the customer portal, installing required IIS/.NET components. It documents administrator-run Windows installation and activation; this is customer-delivered software, not a public cloud provisioning template. Scope: Vendor Windows server installer delivery. Source: https://www.myworkdrive.com/kb/articles/server-setup-guide (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. The server guide requires a dedicated supported Windows server, at least 2 virtual CPUs and 4 GB RAM, and recommends 60 GB disk for OS, software, logs and temporary files. File storage, directory services and HA are additional; larger workloads require the vendor sizing guide. Scope: Dedicated access server minimum; file storage and HA excluded. Source: https://www.myworkdrive.com/kb/articles/server-setup-guide (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Neo4j Self-Managed

Self-managed graph database available in open-source Community and commercial Enterprise editions.

- Listing: https://launchinyourcloud.com/directory/neo4j-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3 Community Edition; Enterprise Edition uses a commercial Neo4j license.
- Licensing model: open-source
- Installation: Official Helm charts on EKS, AKS or GKE; cloud marketplace and VM options also exist
- Architecture: Customer-operated standalone or clustered graph database servers with persistent volumes
- Operations: Customer manages compute, storage, networking, security, backups, monitoring, capacity and upgrades.
- Product website: https://neo4j.com/
- Source review: 2026-11-18; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

Community Edition is designed for standalone deployments. Clustering, advanced security and online backup features require Enterprise Edition. This entry does not cover the managed Neo4j Aura service. Deployments that install Graph Data Science should use GDS 2026.10.2 or later, which moves Guava to 33.7.2 for CVE-2026-102554. The advisory concerns attacker-controlled Java deserialization in GDS's dependency; it does not establish that core Neo4j or a default deployment exposes the vulnerable path.

Neo4j Community Edition is GPLv3. Enterprise Edition is commercially licensed and adds clustering, advanced security and operational capabilities.

Neo4j runs persistent standalone or clustered database servers with attached storage. Kubernetes and cloud placement do not remove state, backup or upgrade responsibilities.


### Category fit

- databases-vector: Provides a graph database with Cypher queries, graph traversal and vector-index capabilities in customer-operated deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/ (checked 2026-11-14). 


### Cloud deployment evidence

- Neo4j Helm deployments on EKS, AKS and GKE (aws, azure, gcp): https://neo4j.com/docs/operations-manual/current/kubernetes/
  Neo4j's Operations Manual documents standalone and clustered Helm deployments on Amazon EKS, Microsoft AKS and Google GKE. Edition and license requirements differ between standalone Community and clustered Enterprise deployments.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

The upstream open-source project documents its public contribution process and sustained participation from multiple contributors. Vendor release notes record database 2026.10.2 on November 6, 2026, establishing current maintenance. This evidence concerns the project and database release history; it does not make Enterprise-only clustering, backup or bundled tools part of the Community license.

Reviewed 2026-11-14.

- Reviewed maintenance release 2026.10.2: https://neo4j.com/release-notes/database/neo4j-2026102/

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

- Open-source project and contributor participation: https://neo4j.com/open-source-project/

### Sources

- Self-managed editions: https://neo4j.com/docs/operations-manual/current/introduction/

- Kubernetes deployments: https://neo4j.com/docs/operations-manual/current/kubernetes/

- Cloud deployment options: https://neo4j.com/docs/operations-manual/current/cloud-deployments/

- Open-source project and contributor participation: https://neo4j.com/open-source-project/

- Neo4j 2026.10.2 release notes: https://neo4j.com/release-notes/database/neo4j-2026102/

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

- Graph Data Science 2026.10.2 release notes: https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/

- Guava CVE-2026-102554 advisory: https://github.com/advisories/GHSA-xxph-c9ww-hj94

### Licensing sources

- https://neo4j.com/open-source-project/

- https://neo4j.com/docs/operations-manual/current/introduction/

### Infrastructure sources

- https://neo4j.com/docs/operations-manual/current/kubernetes/

- https://neo4j.com/docs/operations-manual/current/introduction/


### 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. Neo4j documents OIDC single sign-on for Enterprise Edition, including role mapping and multiple providers. The server must be able to reach its identity provider; this is not a Community Edition entitlement. Scope: Self-managed Neo4j Enterprise Edition. Source: https://neo4j.com/docs/operations-manual/current/authentication-authorization/sso-integration/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Graph Data Science 2026.10.2 upgrades Guava to 33.7.2 to fix CVE-2026-102554, an uncontrolled-memory-allocation issue during attacker-controlled Java deserialization. Use GDS 2026.10.2 or later and assess whether any Java-deserialization path is exposed. Scope: Guava 4.0 through 33.7.1 is affected and 33.7.2 is fixed. Neo4j does not identify which earlier GDS releases expose the path or claim that core Neo4j is affected.. Source: https://github.com/advisories/GHSA-xxph-c9ww-hj94 (reviewed 2026-11-18). Supporting source: GDS 2026.10.2 notes — https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes Helm charts and values for a Kubernetes cluster, including an Enterprise three-member example and cloud storage classes. Enterprise requires licence acceptance; select compatible chart/database versions and configure secrets, volumes and backups. Scope: Official Enterprise cluster Helm deployment. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/quickstart-cluster/create-value-file/ (reviewed 2026-11-20). Deployment artifact: https://github.com/neo4j/helm-charts. Artifact reference: Choose compatible chart and Neo4j versions.

- Minimum footprint / sizing: Documented. The current Helm guide enforces at least 0.5 CPU and 2 GB memory per Neo4j instance and shows a three-member Enterprise cluster. These are deployment floors, not production sizing for a dataset. Graph/index size, page cache, query memory, storage and failure headroom require separate sizing. Scope: Helm per-instance floor; cluster and workload capacity not validated. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/quickstart-cluster/create-value-file/ (reviewed 2026-11-20).

- License pricing: Documented. The vendor separates Community GPLv3 terms from the self-managed Enterprise Software Agreement and commercial support terms. Enterprise clustering/features require the corresponding entitlement; do not apply Aura hosted per-GB rates or the Community licence to an Enterprise deployment. Obtain a self-managed quote. Scope: Self-managed Community versus commercial Enterprise licensing. Source: https://neo4j.com/licensing/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Neo4j 2026.10.2 was released November 6, 2026. Its compatible Graph Data Science 2026.10.2 component upgrades Guava to 33.7.2 for CVE-2026-102554; that conditional component finding is not a core DBMS claim. Scope: Neo4j Database and optional Graph Data Science 2026.10.2. Source: https://neo4j.com/release-notes/database/neo4j-2026102/ (reviewed 2026-11-18). Supporting source: GDS 2026.10.2 — https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/.




### Security and lifecycle reviews

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

- Neo4j Graph Data Science Guava denial-of-service dependency (security-advisory): Graph Data Science 2026.10.2 upgrades Guava to 33.7.2 to fix CVE-2026-102554, an uncontrolled-memory-allocation issue during attacker-controlled Java deserialization. Scope: Guava 4.0 through 33.7.1 is affected and 33.7.2 is fixed. Neo4j does not identify which earlier GDS releases expose the path or claim that core Neo4j is affected. Conditions: Requires the optional GDS component and a reachable attacker-controlled Java-deserialization path. Action: Use GDS 2026.10.2 or later and assess whether any Java-deserialization path is exposed. Source: https://github.com/advisories/GHSA-xxph-c9ww-hj94; reviewed 2026-11-18. Supporting source: GDS 2026.10.2 notes — https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/.




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







## NR PEACH (Natural Resources Permitting Exchange)

British Columbia's open-source natural-resource permitting exchange application.

- Listing: https://launchinyourcloud.com/directory/bcgov-nr-peach/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: Terraform
- Architecture: Azure application services, PostgreSQL, Key Vault and monitoring provisioned by the project's Terraform.
- 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/bcgov/nr-peach
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The repository establishes a government-operated Azure deployment. Reuse outside the originating organization requires replacing its identity, data-source and agency-specific integrations; public source does not make those institutional dependencies generally available.

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

Azure application services, PostgreSQL, Key Vault and monitoring provisioned by the project's Terraform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- licensing-permits-management: British Columbia's open-source natural-resource permitting exchange application.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- Azure Terraform (azure): https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md
  Azure application services, PostgreSQL, Key Vault and monitoring provisioned by the project's Terraform. The repository establishes a government-operated Azure deployment. Reuse outside the originating organization requires replacing its identity, data-source and agency-specific integrations; public source does not make those institutional dependencies generally available.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jujaga, qhanson55, 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/bcgov/nr-peach/graphs/contributors

- Upstream project: https://github.com/bcgov/nr-peach

### Sources

- Azure Terraform: https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md

- Apache-2.0: https://raw.githubusercontent.com/bcgov/nr-peach/main/LICENSE

- Commits: https://github.com/bcgov/nr-peach/commits

### Licensing sources

- https://raw.githubusercontent.com/bcgov/nr-peach/main/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md


### 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. The service implements OAuth bearer-token validation with OIDC discovery/JWKS. That confirms API access validation, not an end-user staff portal or browser SSO flow. Identify the consuming application and its login/mapping before asserting user federation for PEACH. Scope: NR PEACH API/service identity versus consuming-application user SSO. Source: https://github.com/bcgov/nr-peach/blob/main/src/middlewares/helpers/oauth.ts (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 reviewed source supplies deployment configuration for Azure application services, PostgreSQL, Key Vault and monitoring provisioned by the project's Terraform. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Reviewed deployment source collection; application images and infrastructure components have separate versions. Source: https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/bcgov/nr-peach/tree/main/infra. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The Azure Terraform separates shared platform and application instances and exposes deployment/environment-specific App Service SKU and scaling choices. These parameters do not establish a tested complete production CPU/RAM/storage baseline; database, traffic, logging, replicas and recovery require sizing. Scope: NR PEACH complete production workload sizing remains unconfirmed. Source: https://github.com/bcgov/nr-peach/blob/main/infra/core/variables.tf (reviewed 2026-11-21).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: NR PEACH (Natural Resources Permitting Exchange); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/bcgov/nr-peach/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## NVIDIA AI Enterprise

Commercial enterprise AI software suite deployed on customer cloud GPU instances or managed Kubernetes clusters.

- Listing: https://launchinyourcloud.com/directory/nvidia-ai-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci, alibaba, tencent, volcano
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial NVIDIA AI Enterprise subscription, consumption or perpetual license; most customer-cloud paths require BYOL.
- Licensing model: commercial-only
- Installation: NVIDIA AI Enterprise or GPU-optimized cloud VM images, standard instances with BYOL, or managed Kubernetes on supported cloud providers
- Architecture: Licensed NVIDIA AI containers and infrastructure software on customer GPU virtual machines, managed Kubernetes clusters or marketplace OpenShift
- Operations: Customer manages cloud GPU instances or Kubernetes, drivers, GPU Operator and container runtime, networking, storage, identities, NGC access, model services, monitoring, upgrades and license activation.
- Product website: https://www.nvidia.com/en-us/data-center/products/ai-enterprise/
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers customer-operated NVIDIA AI Enterprise software, not a managed AI service. A license is required and is not included with most standard, GPU-optimized VMI or managed-Kubernetes deployments; on-demand NVIDIA AI Enterprise VMIs and private offers use separate included-license processes. Not every component is available on every cloud or deployment model. GPU deployments are generally licensed per GPU, while CPU-only instances require an instance license. Tencent Cloud and ByteDance Volcano Engine have documented standard-instance BYOL paths. These guides require certified software and supported instance types; they do not establish that every GPU, component or provider image is eligible. Their per-instance wording differs from the general per-GPU licensing guidance, so confirm the applicable licensing unit. The November lifecycle matrix lists active 9.0/R620, 8.3/R595, and 7.9 LTSB/R580 branches with different end dates. NeMo Microservices support ended October 1, 2026, after 25.12 became the final GA release; select and patch each component branch independently.

NVIDIA AI Enterprise requires a commercial subscription, consumption or perpetual entitlement. Cloud instances are usually BYOL unless the selected on-demand VMI or private offer explicitly includes licensing. The Tencent and Volcano standard-instance guides state one license per cloud instance, while the general licensing guide describes per-GPU BYOL. Confirm the applicable unit for the selected instance, GPU count and agreement before purchase.

NVIDIA AI Enterprise runs licensed AI containers and infrastructure components on persistent customer GPU or CPU instances and Kubernetes worker nodes.


### Category fit

- ai-tools: Provides an enterprise-supported suite of AI frameworks, infrastructure software, operations components and development tools.

- ai-inference-gateways: Includes supported inference and model-serving components for deploying generative-AI and machine-learning workloads.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- tencent: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html (checked 2026-11-16). 

- volcano: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html (checked 2026-11-16). 


### Cloud deployment evidence

- NVIDIA AI Enterprise on AWS, Azure and Google Cloud (aws, azure, gcp): https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html
  NVIDIA documents standard instances, NVIDIA VM images, GPU-optimized VM images, managed Kubernetes and marketplace OpenShift paths across AWS, Azure and Google Cloud. License inclusion varies by image and offer; standard instances and managed Kubernetes generally require BYOL.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- NVIDIA AI Enterprise on Oracle Cloud and Alibaba Cloud (oci, alibaba): https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html
  NVIDIA's current cloud matrix includes standard instances on Oracle Cloud Infrastructure and Alibaba Cloud, NVIDIA AI Enterprise VM images on OCI and GPU-optimized VM images on Alibaba Cloud. Customers must confirm the supported component set, certified instance and license path.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- NVIDIA AI Enterprise on Tencent Cloud standard instances (tencent): https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html
  NVIDIA documents installing its licensed stack on customer standard instances using a certified Ubuntu operating system, supported NVIDIA drivers, Docker and Container Toolkit, then pulling NGC containers. This is a BYOL installation rather than an included-license marketplace image. Select an instance from the supported-cloud-services matrix; the guide states one license per cloud instance, which must be reconciled with the general licensing guide and the customer agreement.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Edition: NVIDIA AI Enterprise standard-instance BYOL.

- NVIDIA AI Enterprise on ByteDance Volcano Engine standard instances (volcano): https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html
  NVIDIA documents installing its licensed stack on customer standard instances using a certified Ubuntu operating system, supported NVIDIA drivers, Docker and Container Toolkit, then pulling NGC containers. This is a BYOL installation rather than an included-license marketplace image. Select an instance from the supported-cloud-services matrix; the guide states one license per cloud instance, which must be reconciled with the general licensing guide and the customer agreement.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Edition: NVIDIA AI Enterprise standard-instance BYOL.


### Sources

- NVIDIA AI Enterprise cloud deployment guide: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/index.html

- NVIDIA AI Enterprise cloud deployment overview: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html

- NVIDIA AI Enterprise on AWS: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/aws-overview.html

- NVIDIA AI Enterprise on Azure: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/azure-overview.html

- NVIDIA AI Enterprise on Google Cloud: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/google-overview.html

- NVIDIA AI Enterprise licensing: https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/licensing.html

- NVIDIA AI Enterprise on Tencent Cloud standard instances: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html

- NVIDIA AI Enterprise on ByteDance Volcano Engine standard instances: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html

- NVIDIA AI Enterprise documentation: https://docs.nvidia.com/ai-enterprise/

- NVIDIA AI Enterprise lifecycle: https://docs.nvidia.com/ai-enterprise/lifecycle/latest/index.html

### Licensing sources

- https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/licensing.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html

### Infrastructure sources

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/index.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html


### Buyer diligence


Research coverage: 10/12 fields (83%); 7 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. The deployment matrix distinguishes license-included AI Enterprise VM images/private offers from BYOL paths. A generic GPU-optimized image or Kubernetes installation does not include AI Enterprise licensing merely because it comes from a cloud provider. Scope: Offer-specific licensing; no cloud-commitment eligibility established. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (reviewed 2026-11-16).

- Cloud commitment eligibility: Edition-dependent. NVIDIA explicitly states that AI Enterprise AWS Marketplace private offers are eligible toward an AWS committed-spend agreement. Confirm the specific offer and buyer agreement; this statement does not establish Azure/GCP credit or eligibility for every image or BYOL purchase. Scope: Vendor statement for AI Enterprise AWS Marketplace private offers only. Source: https://www.nvidia.com/en-us/data-center/lp/aws-marketplace-offer/ (reviewed 2026-11-16).

- Single sign-on: Sources checked — unresolved. AI Enterprise is a suite with independently versioned application and infrastructure components. NGC/catalog account authentication does not establish SAML/OIDC for every deployed microservice or workload. Select the actual NIM/framework/management components and confirm their runtime identity integrations and entitlements. Scope: Suite-wide runtime SSO cannot be established from distribution/account access. Source: https://docs.nvidia.com/ai-enterprise/latest/user-guide/index.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. Government Ready, STIG-hardening and FIPS-library statements describe selected NVIDIA software branches. The reviewed page does not establish a current independent attestation for the complete customer-account deployment, third-party integrations or every suite component. Scope: Selected software-artifact assurances versus a customer-deployment audit. Source: https://docs.nvidia.com/ai-enterprise/planning-resource/ai-enterprise-infrastructure-software/latest/enterprise-software-built-on-open-source.html (reviewed 2026-11-16).

- Security controls: Documented. NVIDIA describes Government Ready infrastructure software and Production Branch application software using STIG-hardened containers, FIPS-compliant libraries and monthly security/maintenance patches. The statement is branch-specific; it does not certify every suite component, cloud image or customer deployment. Scope: AI Enterprise infrastructure software and application Production Branch; not an independent customer-environment attestation. Source: https://docs.nvidia.com/ai-enterprise/planning-resource/ai-enterprise-infrastructure-software/latest/enterprise-software-built-on-open-source.html (reviewed 2026-11-16).

- Air-gapped operation: Documented. NVIDIA documents registering a Delegated License Service appliance on an air-gapped network by manually transferring registration details through its Licensing Portal. This confirms an offline licensing workflow for applicable components, not disconnected compatibility of every AI Enterprise service or model. Scope: NVIDIA License System DLS workflow; component licensing and application dependencies differ. Source: https://docs.nvidia.com/license-system/latest/nvidia-license-system-quick-start-guide/ (reviewed 2026-11-16). Supporting source: When AI Enterprise requires the license system — https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/license-system.html.

- Deployment artifact / IaC: Documented. NVIDIA provides provider-specific image, standard-instance and Kubernetes procedures rather than one universal template. Tencent and Volcano standard-instance guides require a supported instance, certified Ubuntu, NVIDIA driver, Docker, Container Toolkit and NGC tooling, with BYOL. Scope: Supported cloud matrix; component, operating system and instance compatibility must all match. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (reviewed 2026-11-16). Supporting source: Tencent standard instance — https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html. Supporting source: Volcano Engine standard instance — https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html.

- Minimum footprint / sizing: Sources checked — unresolved. The suite includes multiple frameworks, drivers, operators and NIM services, each with its own support matrix. NIM directs buyers to model- and hardware-specific prerequisites. No suite-wide CPU/RAM/VRAM minimum is established; select components, model profiles, supported GPUs, concurrency and redundancy before sizing. Scope: Suite/component/model dependent; complete workload footprint unresolved. Source: https://docs.nvidia.com/ai-enterprise/latest/user-guide/index.html (reviewed 2026-11-20). Supporting source: NIM component-specific prerequisite path — https://docs.nvidia.com/nim/large-language-models/latest/get-started/index.html.

- License pricing: Documented. The current licensing guide lists a one-year self-managed subscription at USD 4,500 per GPU including standard support. Multi-year, perpetual, educational and partner terms differ. Cloud-marketplace and bundled-hardware entitlements have separate rules; this software list price excludes GPU infrastructure and is not a workload quote. For Tencent/Volcano BYOL paths, the previously noted per-instance versus per-GPU unit still needs contract confirmation. Scope: Self-managed NVIDIA Partner Network list price; CSP marketplace terms differ. Source: https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/pricing.html (reviewed 2026-11-20). Supporting source: Cloud BYOL unit requires separate confirmation — https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html. Supporting source: Volcano Engine BYOL path — https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. NVIDIA's November 2026 lifecycle material lists active 9.0/R620, 8.3/R595, and 7.9 LTSB/R580 branches with distinct support windows. NeMo Microservices support ended October 1, 2026, after 25.12 was designated the final GA release. Scope: AI Enterprise component and branch lifecycle; no single suite version covers every deployment. Source: https://docs.nvidia.com/ai-enterprise/lifecycle/latest/index.html (reviewed 2026-11-18).







## Octopus Server

Deployment automation and runbook platform installed on servers or Kubernetes infrastructure you operate.

- Listing: https://launchinyourcloud.com/directory/octopus-server/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary Free tier or annual Professional and Enterprise licenses.
- Licensing model: commercial-only
- Installation: Windows MSI, Docker or Docker Compose, or the official Helm chart on Kubernetes
- Architecture: Customer-operated stateful Octopus Server nodes with SQL Server and persistent storage.
- Operations: Customer operates the server or cluster, SQL database, persistent storage, backups, security, upgrades and availability configuration.
- Product website: https://octopus.com/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers self-hosted Octopus Server, not Octopus Cloud. Octopus Server requires SQL Server 2016 or later or Azure SQL and a license key, including for the Free tier. The Linux container is stateful and needs persistent storage and monitoring. Self-hosted releases trail the cloud product by at least one quarter; each self-hosted major.minor release receives critical patches and support for six months. Octopus advisories SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. The last issue has no mitigation; Octopus recommends current 2026.3.16117, with branch-specific fixed builds also documented.

Octopus Server is proprietary software governed by the Octopus Customer Agreement. Its no-cost Free tier is usage-limited and license-key activated; Professional and Enterprise are paid annual tiers.

Octopus Server runs as a Windows service or Linux container and depends on SQL Server plus persistent package, artifact, task-log and configuration storage.


### Category fit

- devops: Continuous delivery, release orchestration and operational runbook automation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://octopus.com/docs/installation (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes (checked 2026-11-17). 


### Cloud deployment evidence

- Octopus Server container on AWS ECS or EKS (aws): https://octopus.com/docs/installation
  Octopus explicitly lists Amazon ECS and EKS among supported underlying technologies for the Server Linux container. This is the server application in customer-operated AWS infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Octopus Server in customer Kubernetes clusters with AKS and GKE guidance (azure, gcp): https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes
  Octopus documents hosting the full Server application in the customer's Kubernetes cluster and calls out provider-specific AKS and GKE considerations. Customers supply supported database and storage architecture.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Install Octopus Server: https://octopus.com/docs/installation

- Run Octopus Server in Kubernetes: https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes

- Octopus Server installation requirements: https://octopus.com/docs/installation/requirements

- SQL database requirements: https://octopus.com/docs/installation/sql-database/

- Octopus licensing and purchasing FAQ: https://octopus.com/pricing/faq

- Octopus Server downloads: https://octopus.com/downloads

- Octopus SA2026-19: https://advisories.octopus.com/post/2026/sa2026-19/

- Octopus SA2026-22: https://advisories.octopus.com/post/2026/sa2026-22/

- Octopus SA2026-28: https://advisories.octopus.com/post/2026/sa2026-28/

### Licensing sources

- https://octopus.com/pricing/faq

- https://octopus.com/free

### Infrastructure sources

- https://octopus.com/docs/installation

- https://octopus.com/docs/installation/sql-database/


### 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 purchasing FAQ distinguishes Octopus Cloud and Server licences. A current Marketplace offer explicitly delivering/entitling self-hosted Server was not established. Scope: Reviewed public evidence for Octopus Server; unresolved within this edition/deployment. Source: https://octopus.com/pricing/faq (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Server purchasing terms did not establish an eligible offer or qualifying fees against an existing cloud commitment agreement. Scope: Reviewed public evidence for Octopus Server; unresolved within this edition/deployment. Source: https://octopus.com/pricing/faq (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. Octopus Server documents external identity providers and OpenID Connect. Provider compatibility and licence features vary; disabling a user in the IdP does not immediately revoke an already active Octopus session. Scope: Self-hosted Octopus authentication. Source: https://octopus.com/docs/security/authentication/ (reviewed 2026-11-17).

- SCIM provisioning: Edition-dependent. SCIM 2 is documented for the Microsoft Entra ID authentication provider with a licence including SCIM, such as Enterprise. The IdP needs inbound HTTPS access to the Octopus API. Scope: Self-hosted SCIM, supported provider and licence required. Source: https://octopus.com/docs/security/authentication/scim/ (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The PCI guidance describes deployment controls and network separation, not an attestation covering a customer-operated Server environment. Obtain the applicable report and deployment scope. Scope: Self-hosted PCI controls versus independent certification. Source: https://octopus.com/docs/security/pci-compliance-and-octopus-deploy (reviewed 2026-11-17).

- Security controls: Documented. External authentication creates an Octopus session cookie; immediate revocation also requires disabling the user in Octopus. Scope API keys and configure HTTPS, server encryption and target communication separately. Current advisory review: SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. Upgrade to the branch-specific fixed build or vendor-recommended 2026.3.16117 and review privileged sessions and delegated roles. Scope: Server sessions and access revocation CVE-2026-96414, CVE-2026-116835, and CVE-2026-116288; fixed builds differ between the 2026.2 and 2026.3 lines.. Source: https://advisories.octopus.com/post/2026/sa2026-28/ (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://octopus.com/docs/security/authentication/. Supporting source: SA2026-19 — https://advisories.octopus.com/post/2026/sa2026-19/. Supporting source: SA2026-22 — https://advisories.octopus.com/post/2026/sa2026-22/.

- Air-gapped operation: Sources checked — unresolved. The isolated-server guide covers separate networks and offline package-drop targets. It does not by itself establish a complete no-internet Server licensing, dependency and update workflow for the selected licence. Scope: Server isolation versus an offline deployment target. Source: https://octopus.com/docs/installation/isolated-octopus-deploy-servers/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The vendor supplies a Server Linux-container Kubernetes deployment workflow, with separate persistent storage and SQL database configuration. Pin compatible server images and configure the selected cluster and secrets. Scope: Octopus Server in customer Kubernetes. Source: https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The small 5–10 concurrent-task baseline is one Server with 2 cores/4 GB RAM plus SQL Server Express with 2 cores/4 GB, or Azure SQL with 25–50 DTUs. HA servers, workers, database and task load require separate sizing. Scope: Vendor small-workload baseline; not the total HA topology. Source: https://octopus.com/docs/administration/managing-infrastructure/performance/ (reviewed 2026-11-17).

- License pricing: Documented. Octopus Server is proprietary software governed by the Octopus Customer Agreement. Its no-cost Free tier is usage-limited and license-key activated; Professional and Enterprise are paid annual tiers. Scope: Octopus Server: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://octopus.com/pricing/faq (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm HA Server replicas, workers, concurrent tasks and a supported SQL Server HA/licensing design. The small single-server task baseline does not establish the requested HA topology. 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://octopus.com/docs/administration/managing-infrastructure/performance/ (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Octopus recommends 2026.3.16117 after November security advisories. Branch-specific minimum fixes include 2026.2.13487/2026.3.15875, 2026.2.13503/2026.3.15894, and 2026.2.13526/2026.3.15909. Scope: Octopus Server 2026.2 and 2026.3 maintained lines. Source: https://advisories.octopus.com/2026/ (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Octopus Server November 2026 privilege and authentication fixes (security-advisory): SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. Scope: CVE-2026-96414, CVE-2026-116835, and CVE-2026-116288; fixed builds differ between the 2026.2 and 2026.3 lines. Conditions: Authentication configuration, OIDC use, and delegated roles determine exposure. SA2026-28 has no mitigation. Action: Upgrade to the branch-specific fixed build or vendor-recommended 2026.3.16117 and review privileged sessions and delegated roles. Source: https://advisories.octopus.com/post/2026/sa2026-28/; reviewed 2026-11-18. Supporting source: SA2026-19 — https://advisories.octopus.com/post/2026/sa2026-19/. Supporting source: SA2026-22 — https://advisories.octopus.com/post/2026/sa2026-22/.




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







## Open WebUI Self-Hosted

Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.

- Listing: https://launchinyourcloud.com/directory/open-webui/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open WebUI license based on BSD-style terms with additional branding restrictions and defined exceptions; enterprise terms may be required for rebranding.
- Licensing model: source-available
- Installation: Official Docker image, Python installation or Kubernetes deployment.
- Architecture: Customer-operated web application and conversation storage connected to model providers
- Operations: Customer runs application storage, authentication, provider configuration, updates and backups.
- Product website: https://openwebui.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 UI sends messages to the model endpoint selected for a conversation. Local Ollama or vLLM endpoints can keep inference on customer infrastructure; cloud APIs, embeddings, tools and plugins have separate data flows. The current license restricts branding removal in larger deployments, with small-deployment, permission and enterprise-license exceptions; review the actual terms. Open WebUI v0.13.4 replaces Direct Connections and Integrations with Tether and migrates image settings. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. Tether introduces user-device and local-command paths that require explicit trust review.

The current Open WebUI license adds branding restrictions to BSD-style terms, with small-deployment and permission/license exceptions. Classified here as source-available rather than treating the current version as unmodified BSD-3-Clause.

The application runs as a Docker/Python server or Kubernetes workload with persistent conversation/user storage. Local inference is a separate server or accelerator workload, depending on the chosen model.


### Category fit

- ai-applications-rag: Deployable team chat and model-access interface with retrieval features. It is an interface and application layer, not an included license or runtime for every connected model.

- ai-tools: Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openwebui.com/deployment/aws-ecs/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openwebui.com/deployment/azure-container-apps/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openwebui.com/deployment/google-cloud-run/ (checked 2026-11-12). 


### Cloud deployment evidence

- Open WebUI deployment on AWS ECS / Fargate (aws): https://docs.openwebui.com/deployment/aws-ecs/
  Project deployment instructions cover the application on AWS ECS / Fargate with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Open WebUI deployment on Azure Container Apps (azure): https://docs.openwebui.com/deployment/azure-container-apps/
  Project deployment instructions cover the application on Azure Container Apps with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Open WebUI deployment on Google Cloud Run (gcp): https://docs.openwebui.com/deployment/google-cloud-run/
  Project deployment instructions cover the application on Google Cloud Run with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installation options: https://docs.openwebui.com/getting-started/quick-start/

- Local and cloud model connections: https://docs.openwebui.com/getting-started/quick-start/connect-a-provider/

- Current license and branding conditions: https://docs.openwebui.com/license/

- Licensing and edition terms: https://github.com/open-webui/open-webui/blob/main/LICENSE

- Open WebUI v0.13.4 release: https://github.com/open-webui/open-webui/releases/tag/v0.13.4

### Licensing sources

- https://github.com/open-webui/open-webui/blob/main/LICENSE

- https://docs.openwebui.com/license/

### Infrastructure sources

- https://docs.openwebui.com/getting-started/quick-start/


### 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. Upstream documents OAuth/OIDC and trusted-header authentication. Only one generic OIDC provider is configured through OPENID_PROVIDER_URL at a time; trusted-header use requires an isolated trusted proxy. Scope: Upstream authentication configuration; review provider and session settings. Source: https://docs.openwebui.com/features/authentication-access/auth/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 upstream Compose example includes Open WebUI and Ollama with persistent volumes. Its defaults use moving image references and an empty application secret; configure production credentials and pin versions. Scope: Upstream example; model resources and service exposure require separate review. Source: https://github.com/open-webui/open-webui/blob/main/docker-compose.yaml (reviewed 2026-11-14). Deployment artifact: https://github.com/open-webui/open-webui/blob/main/docker-compose.yaml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The performance guide shows a container example reserving 2 CPUs/4 GB RAM with limits of 4 CPUs/8 GB. Multi-user deployments need PostgreSQL; scaled replicas also require shared services. Local inference, embeddings, extraction, vector storage and HA are additional. This is an example allocation, not a validated 100-user or 1-TB minimum. Scope: Application-container example; full stack and workload sizing excluded. Source: https://docs.openwebui.com/troubleshooting/performance/ (reviewed 2026-11-20). Supporting source: Shared infrastructure for scaled deployments — https://docs.openwebui.com/enterprise/deployment/.

- License pricing: Documented. Current Open WebUI has custom terms restricting branding changes, with exceptions including deployments of at most 50 end users in a rolling 30-day period, written permission or an enterprise licence. A 100-user deployment cannot assume the small-deployment branding exception. Model and infrastructure costs are separate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/open-webui/open-webui/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Open WebUI v0.13.4 was published November 17, 2026. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. The release also replaces Direct Connections and Integrations with Tether and migrates image settings. Scope: Upstream Open WebUI self-hosted release; the Terminals version and migration requirements apply only to deployments using Terminals server connections. Source: https://github.com/open-webui/open-webui/releases/tag/v0.13.4 (reviewed 2026-11-18).







## OpenCATS

Source-available applicant tracking and recruiting records application.

- Listing: https://launchinyourcloud.com/directory/opencats/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mixed MPL-2.0 and CATS Public License 1.1a, including required attribution; review both grants.
- Licensing model: source-available
- Installation: VM image
- Architecture: OpenCATS application, database, candidate files and mail configuration on Azure.
- 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.microsoft.com/en-gb/product/cloudimg1647283583153.opencats-ubuntu-24-04
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Recruitment and CV records are its scope, rather than complete employee HR administration. The licence combines MPL-2.0 and CATSPL attribution terms; review required UI notices. Review the OpenCATS 0.12.0 Career Portal changes and configure the documented web-server or proxy throttling.

Mixed MPL-2.0 and CATS Public License 1.1a, including required attribution; review both grants.

OpenCATS application, database, candidate files and mail configuration on Azure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- hr-employee-records-management: Source-available applicant tracking and recruiting records application.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.opencats-ubuntu-24-04
  OpenCATS application, database, candidate files and mail configuration on Azure. Recruitment and CV records are its scope, rather than complete employee HR administration. The licence combines MPL-2.0 and CATSPL attribution terms; review required UI notices.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

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

- CATS Public License 1.1a Exhibit B: https://raw.githubusercontent.com/opencats/OpenCATS/master/LICENSE.md

- GitHub Commits: https://github.com/opencats/OpenCATS/commits/master

- OpenCATS Career Portal hardening: https://github.com/opencats/OpenCATS/releases/tag/v0.12.0

### Licensing sources

- https://raw.githubusercontent.com/opencats/OpenCATS/master/LICENSE.md

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The v0.12.0 staff session implementation and candidate-portal authentication notes do not establish a maintained SAML/OIDC staff login integration. Candidate access and application session tokens are different identity surfaces; a selected, version-matched federation path remains unconfirmed. Scope: OpenCATS v0.12.0 staff login; candidate-portal authentication is not proof of staff SSO. Source: https://github.com/opencats/OpenCATS/blob/v0.12.0/lib/Session.php (reviewed 2026-11-21). Supporting source: Candidate-portal authentication — https://github.com/opencats/OpenCATS/blob/v0.12.0/docs/career-portal-authentication.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream v0.12.0 repository supplies a Compose example with nginx, PHP, MariaDB and phpMyAdmin. It mounts test fixtures, exposes database/admin ports and contains sample development credentials; treat it as a development/reference stack requiring production hardening, secrets, persistence and a supported database/image selection. Scope: Versioned upstream Compose reference; not a production-ready cloud or HA template. Source: https://github.com/opencats/OpenCATS/blob/v0.12.0/docker/docker-compose.yml (reviewed 2026-11-21). Deployment artifact: https://github.com/opencats/OpenCATS/blob/v0.12.0/docker/docker-compose.yml. Artifact reference: v0.12.0.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed release and Compose stack identify the PHP/web/database topology but give no quantitative production CPU/RAM/storage baseline. Test data and development defaults cannot size concurrent recruiters, candidate records, attachments, backups or HA. Scope: OpenCATS v0.12.0; production hardware capacity remains unconfirmed. Source: https://github.com/opencats/OpenCATS/blob/v0.12.0/docker/docker-compose.yml (reviewed 2026-11-21).

- License pricing: Documented. Mixed MPL-2.0 and CATS Public License 1.1a, including required attribution; review both grants. Scope: OpenCATS; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/opencats/OpenCATS/master/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- OpenCATS Career Portal hardening (security-advisory): OpenCATS 0.12.0 addresses the Career Portal authentication path cited by CVE-2026-111874. Scope: OpenCATS 0.12.0 release changes; the source does not establish that every possible deployment condition is remediated. Conditions: Web-server/reverse-proxy throttling remains an operator configuration; application-level rate limiting was not added. Action: Review the OpenCATS 0.12.0 Career Portal changes and configure the documented web-server or proxy throttling. Source: https://github.com/opencats/OpenCATS/releases/tag/v0.12.0; reviewed 2026-11-19.




## OpenDocMan

Self-hosted document repository with check-in/out, revision and workflow controls.

- Listing: https://launchinyourcloud.com/directory/opendocman/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: OpenDocMan application, database and document storage in a cloudimg Azure VM.
- 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.opendocman.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 image publisher is cloudimg. Check its packaged application version against upstream 2.10 maintenance rather than assuming the image always contains the newest release.

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

OpenDocMan application, database and document storage in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted document repository with check-in/out, revision and workflow controls.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.opendocman-ubuntu-24-04
  OpenDocMan application, database and document storage in a cloudimg Azure VM. The image publisher is cloudimg. Check its packaged application version against upstream 2.10 maintenance rather than assuming the image always contains the newest release.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes stephenlawrence, gh-org-bot-odm, raralala14, 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/opendocman/opendocman/graphs/contributors

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

### Sources

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

- GPL-2.0 LICENSE.txt: https://raw.githubusercontent.com/opendocman/opendocman/master/LICENSE.txt

- GitHub Commits: https://github.com/opendocman/opendocman/commits/master

### Licensing sources

- https://raw.githubusercontent.com/opendocman/opendocman/master/LICENSE.txt

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The current upstream README and environment configuration describe local account credentials and installation but do not establish a supported SAML/OIDC workflow. Obtain a release-specific federation design and support statement before assuming corporate SSO; this is an open question, not a claim that integration is impossible. Scope: Upstream self-hosted authentication; federation unresolved. Source: https://raw.githubusercontent.com/opendocman/opendocman/master/README.md (reviewed 2026-11-20). Supporting source: Environment configuration reviewed — https://raw.githubusercontent.com/opendocman/opendocman/master/.env.sample.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream README documents Compose deployment with separate application/database services, persistent configuration and file data, and a secret-generation helper. Select a release, review the Compose configuration and protect the installer; this source recipe is separate from third-party marketplace image packaging. Scope: Upstream Compose installation; provider images may package a different release. Source: https://raw.githubusercontent.com/opendocman/opendocman/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/opendocman/opendocman/blob/master/docker-compose.yml. Artifact reference: master (moving branch; verify selected release artifact).

- Minimum footprint / sizing: Sources checked — unresolved. The environment template sets PHP_MEMORY_LIMIT=512M and the README identifies PHP 8.2 with MySQL/MariaDB. A PHP memory limit is not a total server minimum. No validated CPU/RAM, document-volume or HA profile is established by these sources. Scope: Upstream component configuration; total hardware sizing unresolved. Source: https://raw.githubusercontent.com/opendocman/opendocman/master/.env.sample (reviewed 2026-11-20). Supporting source: Runtime and database requirements — https://raw.githubusercontent.com/opendocman/opendocman/master/README.md.

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

- Operating cost estimate: Not researched.

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







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







## OpenMetadata

Open-source metadata catalog and data-governance platform deployed with customer-operated services.

- Listing: https://launchinyourcloud.com/directory/openmetadata/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: Official Helm charts on EKS, AKS or GKE
- Architecture: Customer-operated application, ingestion jobs, relational metadata database and search service
- Operations: Customer manages Kubernetes, database, search, ingestion orchestration, secrets, backups, scaling and upgrades.
- Product website: https://open-metadata.org/
- Source review: 2026-11-18; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers OpenMetadata self-hosting, not the managed Collate service. Production guides use provider-managed database and search options. GKE Autopilot is incompatible with the documented Elasticsearch dependency configuration. OpenMetadata 2.0.8 fixes authorization, revoked-token, SSO state and stale-credential, MCP consent, API-token session, impersonation, Airflow/backend authorization, unsafe URL-scheme, and dependency issues. Upgrade from 2.0.7 and retest identity and MCP flows.

The OpenMetadata repository is Apache-2.0 licensed. Collate's managed and enterprise services have separate commercial terms.

OpenMetadata runs persistent application and ingestion workloads backed by a relational database and search service. Managed dependencies do not make the application runtime serverless.


### Category fit

- data-analytics: Catalogs data assets, lineage, quality, governance and observability metadata across connected systems.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke (checked 2026-11-14). 


### Cloud deployment evidence

- OpenMetadata on Amazon EKS (aws): https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks
  The official guide deploys OpenMetadata with Helm on a customer EKS cluster and documents AWS database and search dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- OpenMetadata on Azure Kubernetes Service (azure): https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks
  The official guide deploys OpenMetadata with Helm on a customer AKS cluster and documents Azure database and search dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- OpenMetadata on Google Kubernetes Engine (gcp): https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke
  The official guide deploys OpenMetadata with Helm on GKE. It explicitly notes that GKE Autopilot is incompatible with the documented Elasticsearch configuration.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

The project community publishes recurring meetups and user spotlights describing OpenMetadata use at the Fire Department of New York and Wix. Substantive contributions from multiple participants and the November 13, 2026 release 2.0.8 establish continuing maintenance, including authorization, token, SSO, consent, impersonation and dependency fixes. The spotlights establish project adoption without certifying a particular cloud or commercial edition.

Reviewed 2026-11-18.

- OpenMetadata 2.0.8 release: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release

- Upstream contributor history: https://github.com/open-metadata/OpenMetadata/graphs/contributors

- Community meetups and FDNY/Wix user spotlights: https://open-metadata.org/community

### Sources

- Amazon EKS deployment: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks

- Azure AKS deployment: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks

- Google GKE deployment: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke

- Apache 2.0 license: https://github.com/open-metadata/OpenMetadata/blob/main/LICENSE

- Upstream contributor history: https://github.com/open-metadata/OpenMetadata/graphs/contributors

- Community meetups and FDNY/Wix user spotlights: https://open-metadata.org/community

- OpenMetadata 2.0.8 release: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release

### Licensing sources

- https://github.com/open-metadata/OpenMetadata/blob/main/LICENSE

### Infrastructure sources

- https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks

- https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks

- https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke


### 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 2.0.x deployment guide lists Google, Okta, Auth0, Azure, Cognito, OneLogin and custom OIDC. It states that multiple authentication mechanisms cannot be used simultaneously. Scope: OpenMetadata 2.0.x server authentication. Source: https://docs.open-metadata.org/v2.0.x/deployment/security (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: OpenMetadata 2.0.8 fixes incomplete authorization, revoked-token validity, SSO state and stale credentials, MCP consent, API-token sessions, impersonation boundaries, backend authorization, unsafe URL schemes, and security dependencies. Upgrade to 2.0.8 or later and retest authentication, token revocation, MCP consent, and impersonation. Scope: Upstream 2.0.8 release notes; the individual fixes do not share one universal affected-version range.. Source: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project publishes Helm deployment for OpenMetadata and external database, search and ingestion dependencies. Ingress and network policies are optional and disabled by default. Choose compatible chart/application versions and configure authentication, secrets, persistence and production network controls. Scope: Official Kubernetes Helm distribution. Source: https://docs.open-metadata.org/latest/deployment/kubernetes (reviewed 2026-11-20). Deployment artifact: https://github.com/open-metadata/openmetadata-helm-charts. Artifact reference: Select a release matching the chosen OpenMetadata version.

- Minimum footprint / sizing: Documented. The local Docker quickstart allocates at least 6 GiB memory and 4 vCPUs to Docker for the standalone stack. This is a local quickstart profile, not a production or HA minimum. External database, search, ingestion and concurrency need separate capacity planning. Scope: Local Docker stack allocation; production and HA excluded. Source: https://docs.open-metadata.org/latest/quick-start/local-docker-deployment (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/open-metadata/OpenMetadata/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. OpenMetadata 2.0.8-release, corresponding to product version 2.0.8, was published November 13, 2026. It contains material authorization, token, SSO, consent, impersonation, URL-scheme, and dependency security fixes. Scope: Upstream OpenMetadata 2.0 release. Source: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- OpenMetadata 2.0.8 security maintenance (security-advisory): OpenMetadata 2.0.8 fixes incomplete authorization, revoked-token validity, SSO state and stale credentials, MCP consent, API-token sessions, impersonation boundaries, backend authorization, unsafe URL schemes, and security dependencies. Scope: Upstream 2.0.8 release notes; the individual fixes do not share one universal affected-version range. Conditions: Applicability depends on enabled AI Context, MCP, SSO, impersonation, Airflow, and affected dependencies. Action: Upgrade to 2.0.8 or later and retest authentication, token revocation, MCP consent, and impersonation. Source: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release; reviewed 2026-11-18.




## OpenObserve Enterprise Self-Hosted

Self-hosted observability platform for ingesting, searching and analyzing logs, metrics and traces.

- Listing: https://launchinyourcloud.com/directory/openobserve-enterprise-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Enterprise End User License Agreement. The vendor publishes a free tier through 50 GB/day of ingestion, with a license required above that threshold.
- Licensing model: commercial-only
- Installation: Install the Enterprise Helm chart and CloudNativePG operator, then configure the cluster, object storage and application settings for the selected provider.
- Architecture: Customer-operated Kubernetes workloads use PostgreSQL for metadata, NATS for coordination and cloud object storage for Parquet telemetry.
- Operations: The customer runs the cluster, configures storage credentials and ingestion endpoints, sizes components, manages backups and retention, and applies chart and application upgrades.
- Product website: https://openobserve.ai/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

The documented paths cover Enterprise Edition. Feature access depends on the enterprise entitlement. OpenObserve documents outbound product usage reporting and a ZO_TELEMETRY opt-out. Plan for separate recovery of telemetry objects and PostgreSQL metadata. The reviewed chart 1.1.7 pins Enterprise image v1.1.2; do not substitute an OSS or release-candidate tag by name alone. Dex is optional and must be configured. The EKS node example is a sizing starting point, not an HA workload benchmark. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example.

The reviewed Enterprise build is proprietary under the vendor EULA. The separate open-source distribution uses AGPL-3.0.

Application services and dependencies run in Kubernetes. The provider-specific examples use object storage and persistent PostgreSQL and NATS workloads.


### Category fit

- observability: Collects and analyzes application and infrastructure telemetry, with dashboards and alerts for operational monitoring.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openobserve.ai/docs/enterprise-setup/amazon-eks/ (checked 2026-11-20). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openobserve.ai/docs/enterprise-setup/azure-aks/ (checked 2026-11-20). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openobserve.ai/docs/enterprise-setup/google-gke/ (checked 2026-11-20). 


### Cloud deployment evidence

- OpenObserve Enterprise on Amazon EKS (aws): https://openobserve.ai/docs/enterprise-setup/amazon-eks/
  The vendor walkthrough deploys the Enterprise application to the customer's EKS cluster, with S3 for telemetry and IAM permissions for storage access. The linked cluster sample pins Kubernetes 1.30; verify AWS availability and application compatibility and update that example version before use.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- OpenObserve Enterprise on Azure AKS (azure): https://openobserve.ai/docs/enterprise-setup/azure-aks/
  The vendor walkthrough deploys the Enterprise application to the customer's AKS cluster, with Azure Blob Storage, CloudNativePG and clustered NATS.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- OpenObserve Enterprise on Google GKE (gcp): https://openobserve.ai/docs/enterprise-setup/google-gke/
  The vendor walkthrough deploys the Enterprise application to a Standard GKE cluster in the customer's Google Cloud project. The documented Cloud Storage configuration uses S3 interoperability and HMAC credentials.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Sources

- Enterprise installation and architecture: https://openobserve.ai/docs/enterprise-setup/

- Enterprise EULA: https://openobserve.ai/legal/enterprise-license/

- Enterprise licensing, limits and feature entitlements: https://openobserve.ai/docs/enterprise-setup/license-and-pricing/

- Edition comparison and download channels: https://openobserve.ai/downloads/

- Application configuration and usage telemetry: https://openobserve.ai/docs/administration/configuration/environment-variables/

- OpenObserve Enterprise on Amazon EKS: https://openobserve.ai/docs/enterprise-setup/amazon-eks/

- OpenObserve Enterprise on Azure AKS: https://openobserve.ai/docs/enterprise-setup/azure-aks/

- OpenObserve Enterprise on Google GKE: https://openobserve.ai/docs/enterprise-setup/google-gke/

- Published chart index: https://charts.openobserve.ai/index.yaml

- Buyer evidence: sso: https://openobserve.ai/docs/user-guide/account-administration/identity-and-access-management/sso/

- Enterprise access-control features: https://openobserve.ai/docs/features/enterprise/

- EKS example node configuration: https://raw.githubusercontent.com/openobserve/eks-openobserve/main/o2-eks.yaml

- Capacity planning inputs: https://openobserve.ai/docs/enterprise-setup/capacity-planning/

- Inspected Enterprise-capable chart: https://charts.openobserve.ai/openobserve-1.1.7.tgz

- Current EKS version availability and lifecycle: https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html

### Licensing sources

- https://openobserve.ai/legal/enterprise-license/

- https://openobserve.ai/docs/enterprise-setup/license-and-pricing/

- https://openobserve.ai/downloads/

### Infrastructure sources

- https://openobserve.ai/docs/enterprise-setup/


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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 edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Single sign-on: Documented. Enterprise supports SSO through Dex with external identity providers. Configure the Dex client, redirect/callback URLs and provider connector; the EKS guide enables Dex explicitly. The feature is not available in the separate OSS edition. Scope: Configured self-hosted Enterprise authentication and licensed features. Source: https://openobserve.ai/docs/user-guide/account-administration/identity-and-access-management/sso/ (reviewed 2026-11-20).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Security controls: Documented. Enterprise documentation describes OpenFGA-based RBAC, Dex SSO and configurable secure authentication cookies. The cloud guides scope storage credentials through provider IAM. Operators must configure these controls and review telemetry, external connectors and optional AI/reporting services. Scope: Configurable Enterprise controls, not an independent deployment attestation. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20). Supporting source: Enterprise access-control features — https://openobserve.ai/docs/features/enterprise/. Supporting source: Configuration and telemetry opt-out — https://openobserve.ai/docs/administration/configuration/environment-variables/.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected Enterprise-capable Helm package is openobserve 1.1.7. Its values pin the Enterprise image to v1.1.2; chart, application, report-server and optional AI images have separate versions. Install CloudNativePG and provider storage prerequisites separately. Scope: Helm package and Enterprise image settings; not a complete production approval. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20). Deployment artifact: https://charts.openobserve.ai/openobserve-1.1.7.tgz. Artifact reference: openobserve 1.1.7; Enterprise image v1.1.2; sha256:394886d2c521acfc25012190d99c788814bf0a6f944674febd993ec8be40abe2. Supporting source: Published chart index — https://charts.openobserve.ai/index.yaml.

- Minimum footprint / sizing: Documented. The vendor-linked EKS example provisions three m7i.xlarge nodes, with desired/minimum count 3 and maximum 6, alongside a managed EKS control plane. PostgreSQL, NATS, storage and enabled application roles also require sizing. This example is not a universal minimum or a measured fit for 100 users/1 TB. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example. Scope: Reviewed AWS example, not a production workload benchmark. Source: https://openobserve.ai/docs/enterprise-setup/amazon-eks/ (reviewed 2026-11-20). Supporting source: EKS example node configuration — https://raw.githubusercontent.com/openobserve/eks-openobserve/main/o2-eks.yaml. Supporting source: Capacity planning inputs — https://openobserve.ai/docs/enterprise-setup/capacity-planning/. Supporting source: Current EKS version availability and lifecycle — https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html.

- License pricing: Documented. The Enterprise EULA and licensing guide describe a free tier up to 50 GB/day of ingestion, with registration/licensing above that level and feature-specific entitlements. The guide permits three monthly over-limit occurrences before restricting search. Infrastructure, operating labor and support are separate. Scope: Enterprise software entitlement and documented usage limits, not cloud operating cost. Source: https://openobserve.ai/docs/enterprise-setup/license-and-pricing/ (reviewed 2026-11-20). Supporting source: Enterprise EULA — https://openobserve.ai/legal/enterprise-license/.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Release snapshot / cadence: Sources checked — unresolved. Chart 1.1.7 pins o2cr.ai/openobserve/openobserve-enterprise:v1.1.2. This establishes a reviewed deployable image reference, but not its publication timestamp, a current Enterprise release/support designation or parity with public OSS/prerelease tags. Request the applicable Enterprise release notes and compatibility matrix. Scope: Partial Enterprise package/image evidence; application publication and supported bundle unresolved. Source: https://charts.openobserve.ai/index.yaml (reviewed 2026-11-20). Supporting source: Inspected Enterprise-capable chart — https://charts.openobserve.ai/openobserve-1.1.7.tgz.







## OpenVPN Access Server

Self-hosted business VPN and network-access server deployed in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/openvpn-access-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription, fixed and cloud-marketplace licenses; unlicensed mode is limited to two connections.
- Licensing model: commercial-only
- Installation: Official cloud marketplace image or AWS CloudFormation stack, or package or container on a supported Linux VM
- Architecture: Customer-operated Access Server VM or container with Admin Web UI, VPN data plane and optional multi-node clustering
- Operations: Customer manages compute, routing, network exposure, identity integration, certificates, upgrades, backups and availability.
- Product website: https://openvpn.net/access-server/
- 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 OpenVPN Access Server, not CloudConnexa or OpenVPN Community Edition. Bring-your-own-license, pay-as-you-go and fixed marketplace entitlements differ by provider.

Access Server is commercially licensed even though it permits two connections without a paid key; OpenVPN Community Edition is a separate product.

The full Access Server application runs on customer-operated compute; marketplace images and CloudFormation deployments create customer-cloud VMs and networking.


### Category fit

- identity-access-management: Provides a self-hosted business VPN and policy-controlled remote or site-to-site network access server.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openvpn.net/as-docs/v3/aws/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openvpn.net/as-docs/v3/azure/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openvpn.net/as-docs/v3/google-cloud/ (checked 2026-11-19). 


### Cloud deployment evidence

- Access Server AWS customer-account deployment (aws): https://openvpn.net/as-docs/v3/aws/
  Official documentation covers CloudFormation resources in the signed-in AWS account, Linux or Docker on customer AWS infrastructure, and Marketplace bring-your-own-license or pay-as-you-go options.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Access Server Azure Marketplace VM (azure): https://openvpn.net/as-docs/v3/azure/
  The official bring-your-own-license guide creates the Access Server VM, network interface, public IP and network security group in the selected Azure subscription and resource group.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Access Server Google Cloud Marketplace deployment (gcp): https://openvpn.net/as-docs/v3/google-cloud/
  The official guide deploys the self-hosted Access Server instance into the customer's selected Google Cloud project and VPC.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OpenVPN Access Server installation overview: https://openvpn.net/as-docs/installation-overview/

- OpenVPN Access Server on AWS: https://openvpn.net/as-docs/v3/aws/

- OpenVPN Access Server on Azure: https://openvpn.net/as-docs/v3/azure/

- OpenVPN Access Server on Google Cloud: https://openvpn.net/as-docs/v3/google-cloud/

- OpenVPN Access Server subscription licensing: https://openvpn.net/as-docs/subscription/

- Buyer evidence: iac: https://openvpn.net/as-docs/v3/docker/

- Reviewed deployment artifact reference: https://hub.docker.com/r/openvpn/openvpn-as/tags?name=3.2.4-f3c295a7-Ubuntu26

- Published tag and manifest digest: https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5

- Access Server pricing: https://openvpn.net/access-server/pricing/

### Licensing sources

- https://openvpn.net/as-docs/subscription/

- https://openvpn.net/access-server/pricing/

### Infrastructure sources

- https://openvpn.net/as-docs/installation-overview/


### Buyer diligence


Research coverage: 12/12 fields (100%); 4 documented, 8 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. OpenVPN documents Access Server Marketplace deployment for AWS, Azure and Google Cloud, with provider-specific bring-your-own-license, pay-as-you-go or fixed licensing choices. Confirm the exact offer and connection entitlement. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19). Supporting source: Azure Marketplace deployment — https://openvpn.net/as-docs/v3/azure/. Supporting source: Google Cloud Marketplace deployment — https://openvpn.net/as-docs/v3/google-cloud/.

- 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: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/installation-overview/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/installation-overview/ (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: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/installation-overview/ (reviewed 2026-11-19).

- Security controls: Edition-dependent. Access Server is deployed as a customer-controlled VPN data plane and administration service with customer-managed routing, identity, certificates and network exposure. The reviewed cloud guides require explicit security-group or firewall configuration; validate TLS, MFA, logging and administrator access for the chosen license and topology. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/installation-overview/ (reviewed 2026-11-19).

- 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: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. OpenVPN documents its official Access Server Docker image as an additional installation option. The registry identifies tag 3.2.4-f3c295a7-Ubuntu26 and its manifest digest. Persist /openvpn and review the TUN device and NET_ADMIN/MKNOD capabilities. This container reference does not establish the version of any provider marketplace VM image. Scope: Official commercial Access Server container, separate from the AWS/Azure/GCP marketplace AMIs. Source: https://openvpn.net/as-docs/v3/docker/ (reviewed 2026-11-19). Deployment artifact: https://hub.docker.com/r/openvpn/openvpn-as/tags?name=3.2.4-f3c295a7-Ubuntu26. Artifact reference: docker.io/openvpn/openvpn-as:3.2.4-f3c295a7-Ubuntu26; sha256:b5091b2b5dbebd302c1a61fe8154453e3ff84bd9df7894e530d45e22c76dcdf8. Supporting source: Published tag and manifest digest — https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed sources describe the deployment components but do not provide one complete production sizing model for the buyer's users, data volume, traffic, retention and availability target. Size every application and managed-service dependency. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19).

- License pricing: Edition-dependent. Access Server supports commercial subscription, fixed and marketplace licensing, while unlicensed mode is capped at two connections. Price the selected connection entitlement and HA nodes separately from cloud infrastructure. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/subscription/ (reviewed 2026-11-19). Supporting source: Access Server pricing — https://openvpn.net/access-server/pricing/.

- 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: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19).

- Release snapshot / cadence: Sources checked — unresolved. The official registry identifies Docker image 3.2.4-f3c295a7-Ubuntu26 and its manifest digest. Registry update time is not an application release-publication timestamp, and provider VM images are separately versioned. Confirm the intended application build, marketplace image and upgrade path before treating them as one release snapshot. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5 (reviewed 2026-11-19).







## Paramify

Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.

- Listing: https://launchinyourcloud.com/directory/paramify/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: EKS or AKS application containers, PostgreSQL, object storage and workload identity.
- 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/paramify/support
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.

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

EKS or AKS application containers, PostgreSQL, object storage and workload identity. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.paramify.com/deploy-ppi-eks.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.paramify.com/deploy-helm-azure.html (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EKS via PPI (aws): https://docs.paramify.com/deploy-ppi-eks.html
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure AKS via Helm (azure): https://docs.paramify.com/deploy-helm-azure.html
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- # Paramify configuration
#
# Example install:
#   helm registry login registry.paramify.com --username paramify@mycompan (gcp): https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS EKS via PPI: https://docs.paramify.com/deploy-ppi-eks.html

- Azure AKS via Helm: https://docs.paramify.com/deploy-helm-azure.html

- # Paramify configuration
#
# Example install:
#   helm registry login registry.paramify.com --username paramify@mycompan: https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example

- GCP GKE Terraform: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf

- Deployment Options: https://docs.paramify.com/deployment-options.html

- Paramify Policies & SSPs: https://www.paramify.com/

- Terms & Conditions: https://www.paramify.com/legal/terms-and-conditions

- Access & Services Agreement: https://www.paramify.com/legal/access-and-services-agreement

- Support Commits (`2026-10-29`): https://github.com/paramify/support/commits/main.atom

- Legacy Release Notes: https://docs.paramify.com/release-notes.html

### Licensing sources

- https://www.paramify.com/legal/terms-and-conditions

- https://www.paramify.com/legal/access-and-services-agreement

### Infrastructure sources

- https://docs.paramify.com/deploy-ppi-eks.html

- https://docs.paramify.com/deploy-helm-azure.html

- https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example


### 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: Documented. The vendor explicitly supports Google, Microsoft and Okta login in self-hosted environments, with provider/client setup guides and application-local permissions. The overview still describes SAML as planned; do not treat that date or email magic links as confirmation of current SAML capability. Scope: Paramify self-hosted documented provider login; planned SAML excluded. Source: https://docs.paramify.com/login-options.html (reviewed 2026-11-21). Supporting source: Okta configuration — https://docs.paramify.com/login-okta.html.

- 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 EKS or AKS application containers, PostgreSQL, object storage and workload identity. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Paramify deployment example; review the full linked installation instructions. Source: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf (reviewed 2026-11-19). Deployment artifact: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed installation examples identify Kubernetes, PostgreSQL and object storage, while an example Node heap option configures one process. They do not establish complete production CPU/RAM/storage capacity; document generation workers, database, cluster overhead and HA need workload sizing. Scope: Paramify complete production footprint remains unconfirmed. Source: https://docs.paramify.com/deploy-ppi-eks.html (reviewed 2026-11-21).

- License pricing: Sources checked — unresolved. Deployment requires a Paramify licence and registry credentials, but the public SaaS access agreement does not establish the self-hosted software order, price or support scope. Scope: Selected self-hosted commercial product; contract confirmation remains necessary. Source: https://www.paramify.com/legal/terms-and-conditions (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## PBS ContentLink (Azure)

SAP archive-content software operated by itesys in the customer’s Azure tenant.

- Listing: https://launchinyourcloud.com/directory/pbs-contentlink/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Partner-operated BYOC
- 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: Vendor-assisted provisioning
- Architecture: PBS ContentLink deployed by itesys into customer Azure and connected to immutable Azure Blob storage.
- Operations: itesys operates the archive service, including monitoring, support and regular updates. Select hosting in the customer’s Azure tenant. Agree the partner’s access, retention and deletion authority, backup and recovery scope, data egress and export/exit arrangements before provisioning.
- Product website: https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

PBS and itesys offer both customer-tenant and partner-hosted variants. This listing covers the customer-tenant service, operated by itesys. It is an SAP archive/content layer; supplier claims of audit-compliant storage do not establish the customer’s legal compliance or a complete replacement for every retired application.

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

PBS ContentLink deployed by itesys into customer Azure and connected to immutable Azure Blob storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- legacy-system-archive-access: Preserves SAP archive data, ArchiveLink documents and print lists; access to a retired non-SAP application is not established.

- records-management: SAP ILM integration and retention rules for archived SAP content; select the customer-tenant managed service.

### Deployment boundaries


- azure: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html (checked 2026-11-19). 

Operating responsibility: The selected customer-Azure-tenant option is operated by itesys, including monitoring, support and updates. The separate partner-hosted option is outside this listing. The public description does not establish the management-plane location. Source: https://itesys.expert/en/blog/sap-archivierung-in-der-azure-cloud/ (checked 2026-11-20). Supporting source: Publisher's customer-cloud and partner-hosted options — https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html.


### Cloud deployment evidence

- PBS ContentLink on Azure (azure): https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html
  PBS offers ContentLink with immutable Azure Blob storage in the customer’s Azure cloud. The linked itesys service description confirms customer-tenant hosting and partner operation, monitoring, support and updates. Partner-hosted service is a separate option.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- PBS ContentLink on Azure: https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html

- SAP Certifications (2026): https://www.pbs-software.com/en/products/licensing-certification.html

- ISO/IEC 27001:2022 Cert (2026 PDF): https://www.pbs-software.com/fileadmin/Medien/Unternehmen/ISO_Zertifizierung/pbs_r_eng_mit-anlage_isms_26.pdf

- itesys customer-tenant hosting and managed operations: https://itesys.expert/en/blog/sap-archivierung-in-der-azure-cloud/

### Licensing sources

- https://www.pbs-software.com/en/products/licensing-certification.html

### Infrastructure sources

- https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The Azure product overview describes SAP archive integration, but does not establish the administration-user login and supported federation path. SAP application-user identity and backend archive access are distinct; obtain the applicable component/identity design. Scope: PBS ContentLink administration SSO remains unconfirmed. Source: https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The Azure overview confirms deployment context but does not supply a release-matched customer installer or provisioning artifact. Obtain the supported ContentLink package and SAP/storage integration procedure; a provider compatibility statement is not executable deployment guidance. Scope: PBS ContentLink customer installation artifact remains unconfirmed. Source: https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html (reviewed 2026-11-21).

- Minimum footprint / sizing: Sources checked — unresolved. The Azure overview does not establish numeric production server, cache/index, network or storage requirements. Size SAP archive traffic, retention, retrieval, redundancy and recovery with the vendor for the selected release. Scope: PBS ContentLink complete production capacity remains unconfirmed. Source: https://www.pbs-software.com/en/products/pbs-tools/translate-to-englisch-pbs-contentlink-on-azure.html (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: PBS ContentLink (Azure); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.pbs-software.com/en/products/licensing-certification.html (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Pega Platform Client-Managed

Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/pega-platform-client-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- 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: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE.
- 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.pega.com/bundle/platform/page/platform/deployment/client-managed-cloud/containerized-deployments-kubernetes.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.

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

Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- workflow-automation: Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

- case-management: Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md (checked 2026-11-19). 


### Cloud deployment evidence

- EKS Runbook (aws): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- AKS Runbook (azure): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GKE Runbook (gcp): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- EKS Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md

- AKS Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md

- GKE Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md

- Pega Terms: https://www.pega.com/terms

- PGP Release Notes: https://docs.pega.com/bundle/pega-government-platform/page/pega-government-platform/releasenotes/constellation/cons-newfeatures.html

- Helm Releases: https://github.com/pegasystems/pega-helm-charts/releases

### Licensing sources

- https://www.pega.com/terms

### Infrastructure sources

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md


### 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. Pega Platform documents SAML 2.0 and OIDC authentication services for user SSO. A security administrator creates the service and configures identity/claim mapping and any operator provisioning; token credentials for API integrations are a separate authentication type. Scope: Pega Platform application user federation; confirm the chosen client-managed release and identity-service configuration. Source: https://docs.pega.com/bundle/platform/page/platform/security/create-authentication-service.html (reviewed 2026-11-20). Supporting source: Public documentation API with article body — https://docs-be.pega.com/api/bundle/platform/page/platform/security/create-authentication-service.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Pega publishes Helm charts and EKS/AKS/GKE runbooks for client-managed Kubernetes. The EKS guide requires separately obtained Pega images, registry access and a supported database. Match chart, application, search and database versions; chart source access does not grant platform software rights. Scope: Client-managed licensed platform deployment; no ECS support inferred from generic container capability. Source: https://github.com/pegasystems/pega-helm-charts/blob/master/docs/Deploying-Pega-on-EKS.md (reviewed 2026-11-20). Deployment artifact: https://github.com/pegasystems/pega-helm-charts/tree/master/charts/pega. Artifact reference: master (moving branch); select a chart compatible with the licensed Pega release.

- Minimum footprint / sizing: Documented. The reviewed upstream chart gives the web-user tier a per-pod request of 3 CPU and 12 GiB memory, with limits of 4 CPU and 12 GiB. These are configurable chart defaults; background/search tiers, database, autoscaling, replica counts and cluster overhead are additional. Scope: Moving chart web-tier defaults, not a vendor-certified minimum or a complete 100-user/1-TB HA sizing. Source: https://github.com/pegasystems/pega-helm-charts/blob/master/charts/pega/values.yaml (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Philter by Philterd (Self-Hosted / Cloud Marketplace)

Open-source API that identifies and redacts sensitive information in text and PDFs.

- Listing: https://launchinyourcloud.com/directory/philter/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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
- Architecture: Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application.
- 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.philterd.ai
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations. Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process.

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

Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- freedom-of-information: Open-source API that identifies and redacts sensitive information in text and PDFs.

- document-management: Open-source API that identifies and redacts sensitive information in text and PDFs.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.philterd.ai/philter/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy
  Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Marketplace VM (azure): https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter
  Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Philter: Open Source, Self-Hosted PII & PHI Redaction API (gcp): https://www.philterd.ai/philter/
  Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jzonthemtn, AzazelSensei, 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/philterd/philter/graphs/contributors

- Upstream project: https://github.com/philterd/philter

### Sources

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

- Azure Marketplace VM: https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter

- Philter: Open Source, Self-Hosted PII & PHI Redaction API: https://www.philterd.ai/philter/

- Apache-2.0 LICENSE.txt: https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt

- Philterd Pricing: https://philterd.ai/pricing/

- AWS Marketplace EULA PDF: https://d7umqicpi7263.cloudfront.net/eula/dKWyRA8OFGG7dZHQQ11-sVYBd8p0ZdR4ZLHVrytHdhs

- GitHub Releases: https://github.com/philterd/philter/releases

- Philter runtime and library corrections: https://github.com/philterd/philter/releases/tag/4.0.1

### Licensing sources

- https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt

- https://philterd.ai/pricing/

- https://d7umqicpi7263.cloudfront.net/eula/dKWyRA8OFGG7dZHQQ11-sVYBd8p0ZdR4ZLHVrytHdhs

### Infrastructure sources

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

- https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter

- https://www.philterd.ai/philter/


### Buyer diligence


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

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


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from Philterd, LLC. The publisher package and upstream application have separate maintenance. The reviewed AWS offer delivers Amazon Machine Image (AMI) from Philterd. Its package version is 4.0.1; verify the contained application and required entitlements separately. Scope: Philter by Philterd (Self-Hosted / Cloud Marketplace) selected Azure public offer. Source: https://catalogapi.azure.com/offers/philterdllc1687189098111.philter?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Supporting source: AWS delivery and package version — https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy. Offer philterdllc1687189098111.philter: Philterd, LLC; Virtual machine; https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter. Offer prodview-y32h6usoum7zy: Philterd; Amazon Machine Image (AMI); package 4.0.1; https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy.

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

- Single sign-on: Sources checked — unresolved. Philter documents API keys and optional password sign-in for its own users, while its separate UI is described as in development. The reviewed material does not establish an external SAML/OIDC user-federation path for the self-hosted redaction service. API bearer/session keys are not sufficient SSO evidence. Scope: Philter redaction API authentication; separate UI, cloud marketplace subscription and customer portal sign-in are distinct surfaces. Source: https://github.com/philterd/philter/blob/main/docs/docs/sign_in_security.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 publishes versioned philterd/philter Docker images, including 4.0.1, and a Compose recipe that builds the checked-out source. Use the released image for a release-specific deployment, configure API credentials and persistence/cache services, and distinguish source builds from the marketplace package. Scope: Philter 4.0.1 upstream runtime packaging; not a complete provider infrastructure or HA template. Source: https://github.com/philterd/philter/blob/4.0.1/README.md (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/philterd/philter. Artifact reference: philterd/philter:4.0.1; upstream documentation states there is no latest tag.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed runtime and configuration documentation does not establish a quantitative whole-host CPU/RAM/storage floor for the selected redaction workload. Document rendering, OCR/models, request concurrency, cache and durable data can change memory and storage needs; per-document limits are not host sizing. Scope: Self-hosted Philter application and selected processing/cache dependencies; marketplace VM size is not a universal minimum. Source: https://github.com/philterd/philter/blob/4.0.1/README.md (reviewed 2026-11-20). Supporting source: Runtime settings and processing limits — https://github.com/philterd/philter/blob/main/docs/docs/settings.md.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Philter by Philterd (Self-Hosted / Cloud Marketplace); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Philter runtime and library corrections (security-advisory): Philter 4.0.1 updates Brotli and Jackson-related dependencies. Scope: The Philter 4.0.1 release identifies corrected dependencies; no blanket affected range is inferred for independently patched systems. Conditions: Exposure depends on the actual Ubuntu/JVM libraries and configured document/API processing. Action: Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process. Source: https://github.com/philterd/philter/releases/tag/4.0.1; reviewed 2026-11-19.




## PiGallery2

Self-hosted directory-based photo and video gallery.

- Listing: https://launchinyourcloud.com/directory/pigallery2/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Docker / Compose
- Architecture: PiGallery2 application, directory storage and configured database/index.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.hostinger.com/applications/pigallery2
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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


### Cloud deployment evidence

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

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


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


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

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

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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







## PostgreSQL

Relational database server for transactional applications and structured SQL workloads.

- Listing: https://launchinyourcloud.com/directory/postgresql/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: PostgreSQL License, a permissive OSI-approved open-source license.
- Licensing model: open-source
- Installation: Install supported operating-system binary packages or build the official source distribution on customer-operated hosts.
- Architecture: Customer-operated PostgreSQL database processes with persistent database files
- Operations: Customer manages database users, network access, storage, backups, replication, query tuning and supported-version updates.
- Product website: https://www.postgresql.org/
- Source review: 2026-11-15; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This listing covers the upstream database rather than a managed cloud database service. Extensions, administration tools and third-party distributions have separate compatibility and licensing requirements. The 2026-11-12 security update fixes 52 vulnerabilities and requires operators to review several post-update actions, including conditional reindexing and taking a new full backup before subsequent incremental backups. PostgreSQL 14.25 is the final PostgreSQL 14 release; PostgreSQL 14 is end-of-life and should be upgraded to a supported major version.

PostgreSQL License, a permissive OSI-approved open-source license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated PostgreSQL database processes with persistent database files. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- databases-vector: General-purpose relational database with SQL, transactions and extensibility. Vector similarity search requires a separately selected extension; this listing does not imply built-in vector functionality.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-databases-postgresql-ec2/introduction.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/overview-postgres-choose-server-options (checked 2026-11-12). 


### Cloud deployment evidence

- Self-managed PostgreSQL migration to Amazon EC2 (aws): https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-databases-postgresql-ec2/introduction.html
  AWS documents rehosting PostgreSQL on EC2 with the customer retaining database operations. This is separate from Amazon RDS for PostgreSQL.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- PostgreSQL on Azure VMs versus managed PostgreSQL (azure): https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/overview-postgres-choose-server-options
  Microsoft explicitly documents PostgreSQL on customer-managed Azure VMs, including customer responsibility for patching, availability and backups. This listing does not claim the managed Flexible Server service.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Long-running PostgreSQL Global Development Group project with a named community core team, yearly major releases and a documented security/minor-release support policy.

Reviewed 2026-11-10.

- Community core team: https://www.postgresql.org/developer/core/

- Release maintenance and support policy: https://www.postgresql.org/support/versioning/

### Sources

- Official installation and runtime: https://www.postgresql.org/docs/current/install-binaries.html

- Upstream project and capabilities: https://github.com/postgres/postgres

- Current upstream license: https://www.postgresql.org/about/licence/

- PostgreSQL November 2026 security update and PostgreSQL 14 EOL: https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/

### Licensing sources

- https://www.postgresql.org/about/licence/

### Infrastructure sources

- https://www.postgresql.org/docs/current/install-binaries.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 server supports GSSAPI automatic authentication, including Kerberos service principals, when built with GSSAPI support. Clients, realms and principal mapping must be configured. This is database-client single sign-on, not an administrative web portal or a SAML assertion endpoint. Scope: PostgreSQL database-client GSSAPI/Kerberos authentication. Source: https://www.postgresql.org/docs/current/gssapi-auth.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 upstream installation guide directs operators to platform-specific binary packages or source installation. Packaging depends on operating system and release; authentication, storage, replication and backup configuration are separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://www.postgresql.org/docs/current/install-binaries.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The installation requirements specify build dependencies and supported platforms, not a workload-independent production CPU/RAM minimum. Size connections, query memory, indexes, WAL, backups and HA replicas against the workload; a successful source build does not establish 100-user or 1-TB capacity. Scope: Upstream build requirements; numeric production sizing unresolved. Source: https://www.postgresql.org/docs/current/install-requirements.html (reviewed 2026-11-20).

- License pricing: Documented. PostgreSQL uses the permissive PostgreSQL License and permits use and distribution without a software fee under its conditions. Commercial support, extensions and managed distributions have separate terms; infrastructure and operating labour are additional. Scope: Upstream PostgreSQL server licence. Source: https://www.postgresql.org/about/licence/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The project targets a major release about annually and minor fixes at least quarterly, with urgent fixes outside that schedule. Major versions are supported for five years. Scope: PostgreSQL upstream release/support policy; not a cloud vendor managed-service policy. Source: https://www.postgresql.org/support/versioning/ (reviewed 2026-11-14).







## Prefect Server

Self-hosted workflow server and Python framework for resilient task and data pipelines.

- Listing: https://launchinyourcloud.com/directory/prefect/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: northflank, aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering.
- Licensing model: open-source
- Installation: Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances.
- Architecture: Customer-operated API/UI, background services, database and execution workers
- Operations: Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.
- Product website: https://www.prefect.io/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Configure clients and workers against the self-hosted API. Task code and worker integrations can still use external compute and services. Self-hosted control-plane capacity is separate from any serverless execution target. Prefect 3.9.4.dev6 is a prerelease that stops GitRepository from exposing URL-embedded credentials in DEBUG logs and repr output and adds same-origin validation for UI v2 post-login redirects. No stable fixed release was published at review time. Avoid credential-bearing repository URLs, restrict DEBUG logs, rotate exposed tokens and validate the eventual stable release before production rollout.

Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated API/UI, background services, database and execution workers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- workflow-orchestration: Python flow/task orchestration with retries, scheduling, state tracking and workers that execute deployments on configured infrastructure.

### Deployment boundaries


- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/how-to-deploy-prefect (checked 2026-11-12). 


### Cloud deployment evidence

- Self-hosted Prefect server and worker on Northflank (northflank): https://northflank.com/guides/how-to-deploy-prefect
  Northflank documents the Prefect server/API/UI, PostgreSQL and worker in a customer project, with flow runs launched as separate jobs. This covers the self-hosted control plane, not a worker connected to Prefect Cloud. The hosted platform manages underlying infrastructure; customer project ownership does not imply ownership of its underlying hyperscaler account.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Prefect deployment through Northflank BYOC (aws, azure, gcp): https://northflank.com/guides/how-to-deploy-prefect
  The provider guide installs the self-hosted Prefect server/API/UI, PostgreSQL and worker and explicitly offers AWS, Google Cloud or Azure through Northflank Bring Your Own Cloud. These hyperscaler badges require the BYOC deployment option and its commercial/access prerequisites; a default Northflank hosted project does not run in the customer hyperscaler account. This is a Northflank deployment recipe, not a claim of Prefect vendor-managed BYOC.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release history records November 2026 maintenance, multiple named contributors and first-time contributions across successive releases.

Reviewed 2026-11-10.

- Release history and named contributor participation: https://github.com/PrefectHQ/prefect/releases

- Public project and self-hosted server usage: https://github.com/PrefectHQ/prefect

### Sources

- Official installation and runtime: https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx

- Upstream project and capabilities: https://github.com/PrefectHQ/prefect

- Current upstream license: https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE

- Self-hosted startup and workflow functionality: https://raw.githubusercontent.com/PrefectHQ/prefect/main/README.md

- Prefect deployment through Northflank BYOC: https://northflank.com/guides/how-to-deploy-prefect

- Prefect 3.9.4.dev6 prerelease: https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6

- GitRepository credential-log fix: https://github.com/PrefectHQ/prefect/pull/23969

- UI v2 redirect hardening: https://github.com/PrefectHQ/prefect/pull/23980

### Licensing sources

- https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The self-hosted security guide documents shared Basic authentication, proxy configuration and client headers, not a specific SAML/OIDC user federation integration. Prefect Cloud API keys and Cloud SSO are separate. An identity-aware proxy design would need verified UI/API coverage, individual account mapping and client/worker authorization. Scope: Prefect Server security settings; external user federation remains unconfirmed. Source: https://docs.prefect.io/v3/advanced/security-settings (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Prefect 3.9.4.dev6 prevents GitRepository credentials embedded in URLs from appearing in DEBUG logs or repr output and validates same-origin UI v2 post-login redirects. No stable fixed release was available at review time; avoid credential-bearing URLs, protect logs and rotate exposed tokens. Scope: Prefect GitRepository logging and UI v2 redirect behavior; remediation was prerelease-only when reviewed. Source: https://github.com/PrefectHQ/prefect/pull/23969 (reviewed 2026-11-19). Supporting source: 3.9.4.dev6 prerelease — https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6. Supporting source: Same-origin redirect hardening — https://github.com/PrefectHQ/prefect/pull/23980.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The self-hosted scaling guide supplies Compose with multiple API/background services, PostgreSQL, Redis and migrations. This scaled architecture is distinct from a single local SQLite instance and requires coordinated versions and persistence. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The scaling guide specifies multiple API/background-service instances, PostgreSQL and persistent Redis coordination, but no numeric whole-stack CPU/RAM/storage minimum. Workflow workers and execution infrastructure are separate. Size run/event rate, queues, database history/retention and failover before estimating the requested HA workload. Scope: Current multi-server topology; numeric production/worker sizing remains unconfirmed. Source: https://docs.prefect.io/v3/advanced/self-hosted (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: Prefect 3.9.3 upstream Server; not a Prefect Cloud subscription; software terms only, excluding infrastructure and operations. Source: https://github.com/PrefectHQ/prefect/blob/3.9.3/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 3.9.3, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The prerelease 3.9.4.dev6 contains credential-log and same-origin redirect hardening; it is not a stable upgrade target. Scope: Upstream PrefectHQ/prefect release record; commercial editions and deployment packages may differ. Source: https://github.com/PrefectHQ/prefect/releases/tag/3.9.3 (reviewed 2026-11-19). Supporting source: Prerelease-only security fixes — https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6.




### Security and lifecycle reviews

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

- Prefect GitRepository credential-log fix is prerelease-only (security-advisory): Prefect 3.9.4.dev6 stops GitRepository URL credentials from appearing in DEBUG logs and repr output and adds same-origin UI redirect validation. Scope: Prefect GitRepository logging and UI v2 redirects; no stable remediated release was available when reviewed. Conditions: Credential-bearing repository URLs, DEBUG logging and the UI v2 login redirect path determine exposure. Action: Avoid credentials in repository URLs, restrict logs, rotate exposed tokens and validate the eventual stable fixed release before production use. Source: https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6; reviewed 2026-11-19. Supporting source: Credential-log fix — https://github.com/PrefectHQ/prefect/pull/23969. Supporting source: Same-origin redirect validation — https://github.com/PrefectHQ/prefect/pull/23980.




## Pulumi Cloud Self-Hosted

Enterprise infrastructure-delivery control plane deployed and operated in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/pulumi-cloud-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Pulumi Enterprise subscription with the Self-Hosted deployment option
- Licensing model: commercial-only
- Installation: Official Pulumi programs for ECS or EKS, AKS or GKE
- Architecture: Customer-operated Pulumi Cloud frontend and API with customer networking, database, object storage and container infrastructure
- Operations: Customer operates backups, uptime, infrastructure and upgrades; Pulumi supplies the licensed application and deployment tooling.
- Product website: https://www.pulumi.com/product/pulumi-cloud/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Self-hosting is an Enterprise-only option. The installers bootstrap with a separate state backend because the self-hosted Pulumi service does not yet exist during its own deployment. Validate the supported database, storage and identity configuration for the selected release. The public October changelog removes trust in eight compromised eMudhra intermediate certificates and identifies a Go 1.27.3 API-service rebuild. Obtain and deploy the entitled API image containing the documented trust-store update, restart the service and verify its image/trust configuration. Review the separate OpenSearch 2.x-to-3.7.0 installer migration before redeployment.

The Self-Hosted option is available with Pulumi Enterprise; Pulumi's open-source CLI and SDK do not by themselves license this control plane.

The application runs on customer container compute and uses customer database, object storage, networking and key-management services.


### Category fit

- devops: Provides a customer-operated Pulumi control plane for infrastructure delivery, state, policy, access and deployment workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.pulumi.com/docs/administration/self-hosting/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/aks-hosted/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/gke-hosted/ (checked 2026-11-19). 


### Cloud deployment evidence

- Pulumi Cloud Self-Hosted on AWS ECS or EKS (aws): https://www.pulumi.com/docs/administration/self-hosting/
  Pulumi lists production self-hosting options for AWS ECS and EKS and links official deployment programs that create the application in the customer's AWS environment.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Pulumi Enterprise Self-Hosted.

- Pulumi Cloud Self-Hosted on Azure AKS (azure): https://www.pulumi.com/docs/administration/self-hosting/deployment-options/aks-hosted/
  The official deployment option installs the full self-hosted Pulumi Cloud service on customer Azure AKS and supporting Azure resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Pulumi Enterprise Self-Hosted.

- Pulumi Cloud Self-Hosted on Google GKE (gcp): https://www.pulumi.com/docs/administration/self-hosting/deployment-options/gke-hosted/
  The official deployment option installs the full self-hosted Pulumi Cloud service on customer Google GKE and supporting Google Cloud resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Pulumi Enterprise Self-Hosted.


### Sources

- Pulumi Cloud self-hosting overview: https://www.pulumi.com/docs/administration/self-hosting/

- Pulumi edition comparison: https://www.pulumi.com/docs/administration/get-started/choose-edition/

- Self-hosted Pulumi Cloud on ECS: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/

- Self-hosted Pulumi Cloud on EKS: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/eks-hosted/

- Self-hosted Pulumi Cloud on AKS: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/aks-hosted/

- Self-hosted Pulumi Cloud on GKE: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/gke-hosted/

- Buyer evidence: sso: https://www.pulumi.com/docs/administration/self-hosting/saml-sso/

- Self-hosted feature parity checked; no specific SCIM endpoint established: https://www.pulumi.com/docs/administration/self-hosting/feature-parity/

- Buyer evidence: securityControls: https://www.pulumi.com/docs/administration/self-hosting/operations/security-hardening/

- Buyer evidence: airGap: https://www.pulumi.com/docs/administration/self-hosting/airgapped/

- Reviewed deployment artifact reference: https://github.com/pulumi/pulumi-self-hosted-installers/tree/e7a8007335f692d5d343a16d121057bcabc2bab3

- Buyer evidence: footprint: https://www.pulumi.com/docs/administration/self-hosting/operations/compute-sizing/

- Buyer evidence: release: https://www.pulumi.com/docs/administration/self-hosting/changelog/

### Licensing sources

- https://www.pulumi.com/docs/administration/get-started/choose-edition/

- https://www.pulumi.com/docs/administration/self-hosting/

### Infrastructure sources

- https://www.pulumi.com/docs/administration/self-hosting/

- https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (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: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19).

- Single sign-on: Documented. Self-hosted Pulumi Enterprise supports SAML SSO. Configure the API service’s signing/validation key pair, enable SAML_SSO_ENABLED on the console, and complete the IdP and organization setup. The guide requires restarting the affected services after configuration changes. Scope: Licensed self-hosted Pulumi Enterprise console authentication; not an assertion of SCIM provisioning. Source: https://www.pulumi.com/docs/administration/self-hosting/saml-sso/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19). Supporting source: Self-hosted feature parity checked; no specific SCIM endpoint established — https://www.pulumi.com/docs/administration/self-hosting/feature-parity/.

- 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: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19).

- Security controls: Documented. The hardening guide specifies private application/database subnets, restricted inter-tier traffic, configurable CIDR ingress allowlists, encrypted database/object storage, encrypted Pulumi configuration secrets and TLS between clients, console, API and MySQL. These are controls the customer configures, not proof that an installation is hardened or independently attested. Scope: Documented self-hosted Enterprise controls and configuration responsibilities; compliance attestations are separate. Source: https://www.pulumi.com/docs/administration/self-hosting/operations/security-hardening/ (reviewed 2026-11-19).

- Air-gapped operation: Documented. Pulumi documents an air-gapped self-hosted Enterprise deployment using an entitled licence key and service images, internal infrastructure, and mirrors for CLI/SDK packages, provider plugins and container images. Configure all tools to use the mirrors and review identity and cloud-API connectivity for the selected workflows. Scope: Configured self-hosted Enterprise installation with staged licensed images and internal artifact mirrors. Source: https://www.pulumi.com/docs/administration/self-hosting/airgapped/ (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The official installer repository supplies ECS, EKS, AKS and GKE deployment programs. The reviewed repository commit is pinned independently of the licensed API/console images and licence key, which must be obtained from Pulumi. Pin compatible service images and review installer-specific changes before applying the code. Scope: Public self-hosted infrastructure/application deployment programs; not a licence to the commercial service images. Source: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/ (reviewed 2026-11-19). Deployment artifact: https://github.com/pulumi/pulumi-self-hosted-installers/tree/e7a8007335f692d5d343a16d121057bcabc2bab3. Artifact reference: e7a8007335f692d5d343a16d121057bcabc2bab3; installer source commit, not a Pulumi Cloud application version.

- Minimum footprint / sizing: Documented. The production baseline specifies two or more API instances across two or more AZs, at least 2 vCPU and 4 GB RAM per API instance, a 0.5-vCPU/512-Mi console, a MySQL writer/reader setup with 20 GB+ SSD, and 200 GB+ object storage. Add migrations, networking, backups and workload growth; this is a vendor baseline, not a validated 100-user/1-TB cost or performance model. Scope: Self-hosted Enterprise production component baseline; size every selected service and workload separately. Source: https://www.pulumi.com/docs/administration/self-hosting/operations/compute-sizing/ (reviewed 2026-11-19).

- License pricing: Edition-dependent. Commercial Pulumi Enterprise subscription with the Self-Hosted deployment option Infrastructure, support and operating labor are separate unless the order states otherwise. Scope: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/get-started/choose-edition/ (reviewed 2026-11-19).

- 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: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19).

- Release snapshot / cadence: Sources checked — unresolved. The public self-hosted changelog documents an October 2026 API trust-store update and a September OpenSearch 3.7.0 installer change, but does not identify one immutable licensed API/console image bundle and precise release timestamp. The public installer commit is separately pinned; obtain the entitled service image versions/digests and upgrade matrix from Pulumi. Scope: Licensed self-hosted service image release snapshot, distinct from the Pulumi CLI or public installer commit. Source: https://www.pulumi.com/docs/administration/self-hosting/changelog/ (reviewed 2026-11-19).




### Security and lifecycle reviews

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

- Pulumi self-hosted API October 2026 trust-store update (security-advisory): The public October changelog removes trust in eight compromised eMudhra intermediate certificates and identifies a Go 1.27.3 API-service rebuild. Scope: The licensed self-hosted API-service update described in the October 2026 changelog; an immutable patched image ID and exact release day are not published there. Conditions: The running API image and effective certificate trust store determine applicability. Pinning public installer source does not establish the private service image version. Action: Obtain and deploy the entitled API image containing the documented trust-store update, restart the service and verify its image/trust configuration. Review the separate OpenSearch 2.x-to-3.7.0 installer migration before redeployment. Source: https://www.pulumi.com/docs/administration/self-hosting/changelog/; reviewed 2026-11-19.




## Qlik Sense Enterprise Client-Managed

Commercial client-managed analytics platform installed on customer cloud Windows virtual machines.

- Listing: https://launchinyourcloud.com/directory/qlik-sense-enterprise-client-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Qlik Sense Enterprise license.
- Licensing model: commercial-only
- Installation: Qlik Sense Enterprise on Windows using provider-specific AWS, Azure or Google Cloud VM guidance
- Architecture: Single- or multi-node Windows services with repository database, shared storage, identity and load-balancing dependencies
- Operations: Customer manages Windows hosts, networking, certificates, identity, repository database, shared storage, load balancing, backups, scaling, upgrades and license activation.
- Product website: https://www.qlik.com/us/products/qlik-sense
- 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 Qlik Sense Enterprise Client-Managed on Windows, not Qlik Cloud. Review current system requirements, supported Windows and database versions, multi-node topology and licensing terms before deployment.

Qlik Sense Enterprise Client-Managed is activated through a commercial subscription, perpetual or capacity/core-based license model as applicable to the agreement.

Qlik Sense Enterprise Client-Managed runs persistent Windows services and repository components on customer virtual machines.


### Category fit

- data-analytics: Provides customer-operated business intelligence, associative analytics, dashboards and governed data applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Azure-deployment-instruction.htm (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/GCP-deployment-instruction.htm (checked 2026-11-15). 


### Cloud deployment evidence

- Qlik Sense Enterprise on AWS (aws): https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm
  Qlik documents preparing customer Amazon EC2 Windows infrastructure and installing Qlik Sense Enterprise on Windows.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Qlik Sense Enterprise on Azure (azure): https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Azure-deployment-instruction.htm
  Qlik documents preparing Azure virtual machines, resource groups and networking before installing Qlik Sense Enterprise on Windows.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Qlik Sense Enterprise on Google Cloud (gcp): https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/GCP-deployment-instruction.htm
  Qlik documents preparing Google Compute Engine Windows instances and installing Qlik Sense Enterprise on Windows.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Qlik Sense client-managed administration and deployment: https://help.qlik.com/en-US/sense-admin/May2026/Content/Sense_Helpsites/Home-deployadminister.htm

- Qlik Sense on AWS: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm

- Qlik Sense on Azure: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Azure-deployment-instruction.htm

- Qlik Sense on Google Cloud: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/GCP-deployment-instruction.htm

- Qlik product licenses: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm

### Licensing sources

- https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm

### Infrastructure sources

- https://help.qlik.com/en-US/sense-admin/May2026/Content/Sense_Helpsites/Home-deployadminister.htm


### 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 May 2026 client-managed guide documents SAML using a configured virtual proxy, linked proxy, IdP metadata and user attributes. Configure the selected proxy prefix and identity mapping; Qlik Cloud sign-in and database-connection SSO are separate concerns. Scope: Qlik Sense Enterprise on Windows May 2026 application-user SAML. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/Configure-SAML.htm (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 client-managed AWS guide documents Windows infrastructure and Qlik Sense deployment choices. Obtain the licensed installer and configure supported nodes, networking, repository/database and shared storage; cloud guidance is not a universal unattended or HA application template. Scope: Qlik Sense Enterprise on Windows May 2026 AWS installation guide. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm (reviewed 2026-11-21). Deployment artifact: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm. Artifact reference: May 2026 documentation.

- Minimum footprint / sizing: Documented. The May 2026 requirements list multi-core x64/AVX hardware, at least 8 GB RAM and 5 GB installation disk, with data-dependent additional memory/storage and shared storage for multi-server sites. These installation requirements do not size an in-memory 1-TB analytical workload, concurrency, repository database or HA replicas. Scope: Qlik Sense Enterprise client-managed installation baseline; production data/model capacity separate. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/system-requirements.htm (reviewed 2026-11-21).

- License pricing: Documented. Qlik Sense Enterprise supports access-type or token licensing. Professional/Analyzer user and Analyzer Capacity entitlements have different conditions. Signed license keys require access to the cloud license backend; confirm activation and usage terms for the customer-managed installation. Scope: Qlik Sense Enterprise client-managed, May 2026 administration guide. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## QuestDB Open Source Self-Hosted

Apache-licensed time-series database installed on customer virtual machines in AWS, Azure or Google Cloud.

- Listing: https://launchinyourcloud.com/directory/questdb-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: QuestDB Open Source is Apache License 2.0; QuestDB Enterprise is separately proprietary.
- Licensing model: open-source
- Installation: Vendor AWS OSS AMI 10.1.0, or customer VM binary/systemd/container installation; validate the AMI OS lifecycle; Azure Marketplace packaging is Enterprise
- Architecture: Persistent QuestDB process with dedicated data disks, network endpoints and customer-managed operating system.
- Operations: Customer manages VM and OS, data disks, networking, authentication, backups, monitoring, upgrades and capacity.
- Product website: https://questdb.com/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

QuestDB Open Source excludes native replication, automatic failover and OIDC SSO in the vendor edition matrix. The requested native HA scenario therefore requires a different edition or a separately validated external design. Azure Marketplace packaging is Enterprise, not OSS. The separate free upstream AWS OSS AMI is confirmed, but its Marketplace OS label is Amazon Linux 2, whose standard support ended June 30, 2026. Resolve the actual AMI and maintained OS before production.

QuestDB Open Source is Apache-2.0. QuestDB Enterprise uses separate commercial terms.

QuestDB runs as a persistent database process on provisioned compute with durable data disks.


### Category fit

- databases-vector: Provides a high-performance time-series database with SQL and ingestion protocols on customer infrastructure.

- data-analytics: Supports time-series ingestion, SQL analytics and operational analysis of large event datasets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://questdb.com/docs/deployment/aws/ (checked 2026-11-18). Source: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6 (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://questdb.com/docs/deployment/azure/ (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://questdb.com/docs/deployment/gcp/ (checked 2026-11-18). 


### Cloud deployment evidence

- QuestDB on AWS (aws): https://questdb.com/docs/deployment/aws/
  QuestDB documents manual installation of the full OSS application on customer EC2 with VPC, persistent storage and operating choices. Enterprise marketplace features are not inherited.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- QuestDB on Azure (azure): https://questdb.com/docs/deployment/azure/
  The Azure guide includes customer VM deployment. Its Marketplace offer is Enterprise; use the manual OSS path for this listing and do not transfer Enterprise entitlements.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- QuestDB on Google Cloud (gcp): https://questdb.com/docs/deployment/gcp/
  QuestDB documents deployment to customer Compute Engine with separate durable storage.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Vendor-published QuestDB Open Source AWS AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6
  The QuestDB-published AMI installs the OSS database on customer EC2. Package 10.1.0 lists Amazon Linux 2; verify the resolved image and replace unsupported OS packaging. Availability does not supply Enterprise HA, OIDC or a support entitlement.
  Source type: marketplace-offer; reviewed: 2026-11-18; vendor support: not-assessed. Edition: QuestDB Open Source. Versions: AMI package 10.1.0.


### Community and maintenance

QuestDB maintains an open source repository with contributor participation, installation instructions and current OSS releases. Enterprise customer stories do not establish OSS entitlements or customer-account hosting; provider-specific manual guides supply that evidence.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/questdb/questdb

- Official maintenance and adoption evidence: https://github.com/questdb/questdb/releases/tag/10.2.0

### Sources

- Deploy QuestDB on AWS: https://questdb.com/docs/deployment/aws/

- Deploy QuestDB on Azure: https://questdb.com/docs/deployment/azure/

- Deploy QuestDB on Google Cloud: https://questdb.com/docs/deployment/gcp/

- QuestDB repository and license: https://github.com/questdb/questdb

- Exact vendor AWS OSS AMI and package: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6

- Amazon Linux 2 lifecycle: https://aws.amazon.com/amazon-linux-2/faqs/

### Licensing sources

- https://github.com/questdb/questdb

- https://questdb.com/terms/

### Infrastructure sources

- https://questdb.com/docs/deployment/aws/

- https://questdb.com/docs/deployment/azure/

- https://questdb.com/docs/deployment/gcp/


### 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. QuestDB publishes the free QuestDB Open Source AMI prodview-cddeafdirexw6 on AWS Marketplace, package 10.1.0, x86. Infrastructure is charged separately. The offer lists Amazon Linux 2.0.20210318.0; AWS ended AL2 standard support on June 30, 2026. Verify the resolved AMI OS and use a maintained image before production. This offer is distinct from Azure Enterprise packaging and does not add OSS replication, HA or OIDC. Scope: Vendor-published QuestDB Open Source AWS AMI 10.1.0; package availability is not a production recommendation. Source: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6 (reviewed 2026-11-18). Supporting source: Manual customer EC2 installation — https://questdb.com/docs/deployment/aws/. Supporting source: Amazon Linux 2 end of support — https://aws.amazon.com/amazon-linux-2/faqs/. Offer prodview-cddeafdirexw6: QuestDB; Amazon Machine Image (AMI), x86; package 10.1.0; https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6.

- Cloud commitment eligibility: Explicitly unsupported. The exact reviewed QuestDB Open Source AWS AMI is free of charge in Marketplace. It supplies no billed software amount to apply toward a software-spend commitment through this offer. EC2/EBS, paid support, other editions and separately negotiated offers have separate charges and require the buyer’s applicable order and AWS agreement; the free software finding does not settle those charges. Scope: Software amount through the exact free AWS AMI prodview-cddeafdirexw6; infrastructure, paid support, other editions and private offers assessed separately. Source: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6 (reviewed 2026-11-18). Supporting source: AWS product-by-product commitment qualifications — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Explicitly unsupported. QuestDB’s edition comparison assigns OIDC SSO to Enterprise. Open Source has its documented local authentication controls and does not include that Enterprise OIDC feature. An external identity proxy would be a separate architecture. Scope: Native QuestDB Open Source OIDC SSO; Enterprise entitlement is excluded. Source: https://questdb.com/enterprise/ (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The governance comparison does not establish a native OSS SCIM endpoint or user/group deprovisioning operations. Enterprise RBAC/OIDC are not evidence that SCIM is supplied in Open Source. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. The current governance material advertises SOC 2 Type 2 while distinguishing Enterprise controls from OSS. No public audit period/system description established that the report covers this customer-operated OSS database and its external encryption/network controls. Obtain the full report and relevant customer-control scope; a footer badge is insufficient. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18).

- Security controls: Documented. The edition matrix distinguishes OSS controls from Enterprise TLS, RBAC and OIDC. The AWS guide directs operators to change HTTP/PG credentials, disable unused interfaces and restrict source IPs. Design encryption and network boundaries explicitly rather than inheriting Enterprise capabilities. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18). Supporting source: OSS instance hardening — https://questdb.com/docs/deployment/aws/. Supporting source: Disable Web Console usage telemetry — https://questdb.com/docs/configuration/telemetry/. Supporting source: AMI operating-system support boundary — https://aws.amazon.com/amazon-linux-2/faqs/.

- Air-gapped operation: Sources checked — unresolved. QuestDB documents telemetry.enabled=false, which stops Web Console usage telemetry and removes its Metrics View. Manual binaries are also available. These facts do not validate the complete disconnected OSS lifecycle: confirm a local JRE/artifact supply, restart/configuration, ingest/query clients, updates and backup/recovery. Enterprise offline-trial and backup claims are not inherited by OSS. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/configuration/telemetry/ (reviewed 2026-11-18). Supporting source: OSS installation and upgrade artifact — https://questdb.com/docs/deployment/aws/.

- Deployment artifact / IaC: Documented. The manual EC2 guide links the versioned QuestDB 10.2.0 no-JRE binary archive and systemd upgrade steps. Supply a compatible JRE and review service configuration. This is an application artifact, not a complete HA Terraform stack. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/deployment/aws/ (reviewed 2026-11-18). Deployment artifact: https://github.com/questdb/questdb/releases/download/10.2.0/questdb-10.2.0-no-jre-bin.tar.gz. Artifact reference: QuestDB OSS 10.2.0, no-JRE archive.

- Minimum footprint / sizing: Documented. Capacity guidance recommends 8 GB RAM for basic and 32 GB for advanced use, fast local/NVMe storage and workload-specific CPU planning. The edition comparison explicitly excludes replication and automatic failover from OSS, so this listing cannot satisfy the requested native HA design. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/getting-started/capacity-planning/ (reviewed 2026-11-18). Supporting source: OSS versus Enterprise availability features — https://questdb.com/enterprise/.

- License pricing: Documented. QuestDB Open Source is Apache 2.0 licensed. Enterprise adds commercial capabilities, including replication/HA and OIDC, under separate terms; those features and licence costs are outside this OSS listing. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://github.com/questdb/questdb (reviewed 2026-11-18). Supporting source: Commercial edition boundary — https://questdb.com/enterprise/.

- Operating cost estimate: Sources checked — unresolved. The requested HA architecture is not supplied by native QuestDB Open Source replication/failover. Decide whether to change edition or separately validate an external recovery design before costing. Then supply ingestion rate, series/cardinality, query concurrency, retained rows, storage compression and recovery objectives. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://questdb.com/enterprise/ (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. QuestDB OSS 10.2.0 was published November 10, 2026. Enterprise release numbers follow a separate line. Pin the OSS binary/container and dependencies; this snapshot does not establish a support SLA or future cadence. The reviewed AWS OSS AMI packages 10.1.0 rather than upstream 10.2.0 and lists AL2; check the actual OS image lifecycle. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://github.com/questdb/questdb/releases/tag/10.2.0 (reviewed 2026-11-18). Supporting source: Separate AWS OSS package and OS label — https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6. Supporting source: AL2 support ended June 30, 2026 — https://aws.amazon.com/amazon-linux-2/faqs/.




### Security and lifecycle reviews

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

- QuestDB OSS AWS offer lists an operating system past standard support (lifecycle): The reviewed QuestDB OSS AWS AMI package 10.1.0 lists Amazon Linux 2.0.20210318.0. AWS ended AL2 standard support on June 30, 2026. Scope: The OS label of AWS offer prodview-cddeafdirexw6; not all QuestDB versions, manual VM installs or other cloud packages. Conditions: Marketplace metadata can lag the actual AMI. Confirm the resolved image ID and OS before concluding that a deployed instance uses AL2; application version alone does not establish OS maintenance. Action: Verify the actual AMI OS and use maintained operating-system packaging before production. Migrate any confirmed AL2 host under the vendor/provider upgrade procedure and test backup/recovery. Source: https://aws.amazon.com/amazon-linux-2/faqs/; reviewed 2026-11-18. Supporting source: Exact QuestDB OSS offer, package and OS label — https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6.




## RADAR-base (ManagementPortal & Study Platform)

Open-source study-management and remote research-data collection platform.

- Listing: https://launchinyourcloud.com/directory/radar-base/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: Terraform; Kubernetes manifests
- Architecture: RADAR Kubernetes application services, databases and collection pipelines on Terraform-provisioned EKS or AKS.
- 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/RADAR-base/ManagementPortal
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

ManagementPortal, infrastructure modules and the full chart bundle have separate releases. Participant/data management does not establish grant administration or regulatory document-control functionality. Clinical-use validation, ethics and consent processes remain the operator's responsibility.

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

RADAR Kubernetes application services, databases and collection pipelines on Terraform-provisioned EKS or AKS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Open-source study-management and remote research-data collection platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/aws/cluster/README.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/azure/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EKS Terraform (aws): https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/aws/cluster/README.md
  RADAR Kubernetes application services, databases and collection pipelines on Terraform-provisioned EKS or AKS. ManagementPortal, infrastructure modules and the full chart bundle have separate releases. Participant/data management does not establish grant administration or regulatory document-control functionality. Clinical-use validation, ethics and consent processes remain the operator's responsibility.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Terraform (azure): https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/azure/README.md
  RADAR Kubernetes application services, databases and collection pipelines on Terraform-provisioned EKS or AKS. ManagementPortal, infrastructure modules and the full chart bundle have separate releases. Participant/data management does not establish grant administration or regulatory document-control functionality. Clinical-use validation, ethics and consent processes remain the operator's responsibility.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes nivemaham, blootsvoets, dennyverbeeck, 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/RADAR-base/ManagementPortal/graphs/contributors

- Upstream project: https://github.com/RADAR-base/ManagementPortal

### Sources

- AWS EKS Terraform: https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/aws/cluster/README.md

- Azure Terraform: https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/azure/README.md

- RADAR-Kubernetes: https://raw.githubusercontent.com/RADAR-base/RADAR-Kubernetes/main/README.md

- ManagementPortal Docs: https://radar-base.org/index.php/management-portal/

- Apache-2.0: https://raw.githubusercontent.com/RADAR-base/ManagementPortal/master/LICENSE.md

- ManagementPortal Releases: https://github.com/RADAR-base/ManagementPortal/releases

- K8s Releases: https://github.com/RADAR-base/RADAR-Kubernetes/releases

### Licensing sources

- https://raw.githubusercontent.com/RADAR-base/ManagementPortal/master/LICENSE.md

### Infrastructure sources

- https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/aws/cluster/README.md

- https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/azure/README.md


### 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 current ManagementPortal README describes browser login through an external Ory Hydra/Kratos stack and self-enrolment UI, which must run for redirects and login pages to work. Configure compatible portal/identity releases and users; this confirms the RADAR identity-stack login path, not every external enterprise SAML integration or mobile-device credential. Scope: Moving upstream RADAR ManagementPortal central identity-stack browser login. Source: https://github.com/RADAR-base/ManagementPortal/blob/master/README.md (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. RADAR-Kubernetes supplies application deployment resources; the separate AWS/Azure infrastructure repository provisions the cluster. Pin a compatible application/chart bundle and infrastructure revision rather than using the portal component version for the entire stack. Scope: Application deployment collection paired with the documented cloud infrastructure. Source: https://raw.githubusercontent.com/RADAR-base/RADAR-Kubernetes/main/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/RADAR-base/RADAR-Kubernetes. Artifact reference: main (moving application deployment collection).

- Minimum footprint / sizing: Documented. The Kubernetes deployment README gives a single-node minimum of 8 vCPU/32 GB RAM/200 GB storage, or a cluster of three nodes at 3 vCPU/16 GB/100 GB each plus 200 GB shared storage. These are infrastructure starting points; streaming, study/device volume, retention, external services and HA capacity still need validation. Scope: RADAR Kubernetes published topology minimums, not a reference-workload guarantee. Source: https://github.com/RADAR-base/RADAR-Kubernetes/blob/main/README.md (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## RAGFlow

Document processing and retrieval platform for building RAG and agentic knowledge applications.

- Listing: https://launchinyourcloud.com/directory/ragflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.
- Licensing model: open-source
- Installation: Versioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.
- Architecture: Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services
- Operations: Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
- Product website: https://ragflow.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Deployment options include customer AWS, Azure and Google Cloud infrastructure, Alibaba Compute Nest, and a Railway project. The evidence trail identifies the publishers and template versions. Hosting RAGFlow does not automatically self-host its LLM, embeddings or reranker; choose private or local model endpoints where required.

Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-applications-rag: Document understanding, knowledge ingestion and retrieval-augmented/agentic question answering with configurable LLM, embedding and reranking endpoints.

- ai-tools: Self-hosted document ingestion, retrieval and context infrastructure for AI applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/ragflow-ai (checked 2026-11-12). Source: https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Community RAGFlow deployment on AWS ECS Fargate through stdapi.ai (aws): https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow
  The sample provisions the RAGFlow application and workers, OpenSearch, Aurora PostgreSQL, Valkey, S3 and a Bedrock gateway in the customer AWS account. Source inspection confirms the v0.26.4 Python image pin; it does not establish compatibility with the 1.0 Go rewrite. This community integration also requires the separately billed stdapi.ai gateway and Bedrock access. Review its documented networking, client-security, availability and cost limitations before use.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.26.4.

- cloudimg RAGFlow Azure VM deployment and operations guide (azure): https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/
  The image publisher documents an Azure VM in the customer subscription running the complete Compose stack, including Elasticsearch, MySQL, MinIO, Redis and a local embedding service. Its guide pins RAGFlow v0.26.4, not 1.0. This is a third-party repackaged image with additional support charges, not an upstream-endorsed distribution. Confirm image access, current patch/migration requirements, TLS configuration and the separately configured chat-model endpoint.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.26.4.

- Techlatest RAGFlow VM deployment in a customer Google Cloud project (gcp): https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html
  The image publisher documents selecting the customer project, deployment service account, zone, network and Compute Engine VM, then completing RAGFlow initialization and configuring its bundled Ollama models. This is a third-party packaged deployment; the guide does not establish a specific current RAGFlow release or 1.0 compatibility. Confirm the image version, support charges, model licenses, resource sizing and network exposure before use.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted.

- RAGFlow Community deployment on Alibaba Cloud Compute Nest (alibaba): https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document
  Alibaba Cloud documents provisioning a RAGFlow Community service instance with customer ECS, VPC and vSwitch parameters. This is distinct from the managed AI-Native Database Service integration. Review image version, access controls, model endpoints and the broad example RAM permissions before production.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted.

- Community RAGFlow Railway application stack (railway): https://railway.com/deploy/ragflow-ai
  This community template deploys the application, Elasticsearch, MySQL, Redis, a local embedding service and object storage into the customer Railway project. Its linked Dockerfile pins upstream RAGFlow v0.27.1 with a Railway startup/configuration wrapper. The template is not proof of 1.0 compatibility or upstream support; review migrations and the separately configured chat-model endpoint. Railway manages the underlying infrastructure.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.27.1.

- Railway deployment image source and release pin (railway): https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile
  Source inspection confirms the v0.27.1 base image and the custom configuration, nginx and startup wrapper used by the linked Railway template. The upstream 1.0 release changes the architecture and requires its documented migration path; do not substitute a new image tag without reviewing the complete stack.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.27.1.


### Community and maintenance

Current release notes document continued 2026 releases and dozens of named contributors across successive versions; the upstream README records a 1.0.0 release on 6 November 2026.

Reviewed 2026-11-10.

- Current releases and contributors: https://github.com/infiniflow/ragflow/releases

- Release chronology and deployment instructions: https://raw.githubusercontent.com/infiniflow/ragflow/main/README.md

### Sources

- Upstream project and capabilities: https://github.com/infiniflow/ragflow

- Current upstream license: https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE

- RAGFlow 1.0 release and migration requirements: https://ragflow.io/docs/v1.0.0/release_notes

### Licensing sources

- https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE

### Infrastructure sources

- https://github.com/infiniflow/ragflow


### 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. A vendor maintainer identifies OAuth2/OIDC SSO in Enterprise, while the reviewed v1.0.0 Go deployment reference does not establish a supported federation configuration for that OSS release. Older OAuth configuration examples must not be assumed compatible with the new backend. Confirm edition, release and identity-provider configuration. Scope: RAGFlow v1.0 Go OSS versus Enterprise federation; current entitlement/configuration unresolved. Source: https://raw.githubusercontent.com/infiniflow/ragflow/v1.0.0/docker/README.md (reviewed 2026-11-20). Supporting source: Vendor-maintainer Enterprise SSO statement — https://github.com/infiniflow/ragflow/issues/15882.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v1.0.0 Compose file includes a separate dependency configuration and reads its image selection from the release environment. Use the matching release configuration; this artifact does not establish a migration path or compatibility for older provider packages. Scope: Upstream v1.0.0 Compose; not evidence of compatibility with the listed 0.x provider packages. Source: https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml. Artifact reference: v1.0.0. Supporting source: Versioned RAGFlow 1.0.0 quickstart — https://ragflow.io/docs/v1.0.0/.

- Minimum footprint / sizing: Documented. The 1.0 quickstart recommends a starting point of 4 CPU cores, 16 GB RAM and 50 GB free disk. Models, document engines and concurrency can require more; this does not size the older third-party cloud packages. Scope: Upstream 1.0 quickstart; provider packages may target 0.x. Source: https://ragflow.io/docs/v1.0.0/ (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. 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/infiniflow/ragflow/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v1.0.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 infiniflow/ragflow release record; commercial editions and deployment packages may differ. Source: https://github.com/infiniflow/ragflow/releases/tag/v1.0.0 (reviewed 2026-11-14).







## Rancher Manager

Open-source Kubernetes management platform deployed into a customer-operated cluster.

- Listing: https://launchinyourcloud.com/directory/rancher-manager/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0; commercial SUSE subscriptions and support are separate.
- Licensing model: open-source
- Installation: Official Helm chart on a supported Kubernetes cluster
- Architecture: Customer-operated Rancher management server, ingress and persistent Kubernetes resources
- Operations: Customer manages the management cluster, ingress, certificates, backups, upgrades, downstream-cluster credentials and availability.
- Product website: https://www.rancher.com/products/rancher
- 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-managed Rancher Manager, not separate hosted offerings. Rancher documents EKS, AKS and GKE installation paths. GKE Autopilot is not supported for the Rancher server because required kube-system changes are restricted.

Rancher Manager is Apache-2.0 licensed. SUSE subscriptions, hosted services and enterprise support use separate commercial terms.

Rancher runs as persistent management services inside Kubernetes and requires ingress, certificates and durable state. The hosted Kubernetes control plane does not make Rancher serverless.


### Category fit

- devops: Provides centralized provisioning, access control and lifecycle management for Kubernetes clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke (checked 2026-11-14). 


### Cloud deployment evidence

- Rancher Manager on Amazon EKS (aws): https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks
  The upstream guide installs the Rancher server with Helm into an EKS cluster controlled by the customer.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Rancher Manager on Azure Kubernetes Service (azure): https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks
  The upstream guide installs the Rancher server with Helm into an AKS cluster controlled by the customer.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Rancher Manager on Google Kubernetes Engine (gcp): https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke
  The upstream guide installs Rancher into a GKE Standard cluster. GKE Autopilot is explicitly unsupported for the Rancher server.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

Rancher has sustained code participation from multiple contributors and an established upstream user community. The reviewed Community release 2.15.3, published October 29, 2026, records maintenance and security fixes. Public contributor history and the official community program establish participation beyond repository popularity; commercial SUSE support remains separate.

Reviewed 2026-11-14.

- Reviewed maintenance release v2.15.3: https://github.com/rancher/rancher/releases/tag/v2.15.3

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

- Upstream user community and participation: https://www.rancher.com/community

### Sources

- Kubernetes installation overview: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster

- Rancher on Amazon EKS: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks

- Rancher on AKS: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks

- Rancher on GKE: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke

- Apache 2.0 license: https://github.com/rancher/rancher/blob/master/LICENSE

- Reviewed maintenance release v2.15.3: https://github.com/rancher/rancher/releases/tag/v2.15.3

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

- Upstream user community and participation: https://www.rancher.com/community

### Licensing sources

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

### Infrastructure sources

- https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The upstream authentication guide documents OIDC, SAML and OAuth integrations, including Keycloak, Okta, Entra ID, AD FS and a generic OIDC provider. Review version compatibility, local administrator access and downstream-cluster authorization separately from signing into Rancher. Scope: Rancher Manager console federation. Source: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config (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 Kubernetes guide publishes separate stable, latest and alpha Helm repositories. Stable is recommended for production; check the Kubernetes support matrix and certificate/HA prerequisites before installation. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster (reviewed 2026-11-14). Deployment artifact: https://releases.rancher.com/server-charts/stable/index.yaml. Artifact reference: stable Helm repository index (moving; select a supported chart version).

- Minimum footprint / sizing: Documented. For a small hosted-Kubernetes management cluster, the guide lists at least three nodes, each with 4 vCPUs and 16 GB RAM. Larger managed fleets need more. Single-node Docker is development/test only; downstream workload clusters, datastore/storage and HA headroom are additional. Scope: Upstream management-cluster starting profile; downstream applications excluded. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-requirements (reviewed 2026-11-20).

- License pricing: Documented. Rancher Manager core is Apache-2.0 licensed. This does not establish a SUSE support subscription price or the cost and licences of managed Kubernetes clusters and optional components. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/rancher/rancher/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Red Hat Ansible Automation Platform Self-Managed

Enterprise IT automation platform installed and managed by the customer in a public-cloud environment.

- Listing: https://launchinyourcloud.com/directory/ansible-automation-platform-self-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat Ansible Automation Platform subscription required.
- Licensing model: commercial-only
- Installation: Containerized installer on RHEL with Podman or the OpenShift Operator
- Architecture: Customer-operated automation controller, execution and platform services on RHEL or OpenShift.
- Operations: Customer manages the platform, execution capacity, infrastructure, secrets, backups and upgrades; Red Hat supplies subscribed software updates and support.
- Product website: https://www.redhat.com/en/technologies/management/ansible
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Red Hat Ansible Automation Platform, not the managed cloud service and not upstream Ansible Core or AWX. Current 2.7 deployment models use the containerized RHEL installer or OpenShift Operator; the RPM installer was removed in 2.7. Validate supported RHEL or OpenShift versions, execution environments and subscription manifests before installation.

The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification.

Self-managed Ansible Automation Platform uses persistent RHEL containers or customer-operated OpenShift workloads with databases and execution capacity.


### Category fit

- devops: Enterprise configuration, provisioning and operations automation across infrastructure and applications.

- workflow-automation: Controller, event-driven automation and reusable automation content coordinate governed operational workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 


### Cloud deployment evidence

- Self-managed Ansible Automation Platform in named public clouds (aws, azure, gcp): https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities
  Red Hat documents self-managed Ansible Automation Platform deployments on infrastructure hosted in AWS, Azure and Google Cloud. The customer operates the RHEL or OpenShift environment and supplies the subscription.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Named-cloud and self-managed installation overview: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities

- Current 2.7 deployment models: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/plan-ref_installation_deployment_models

- Set up the Ansible Automation Platform subscription: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription

### Licensing sources

- https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription

### Infrastructure sources

- https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/plan-ref_installation_deployment_models


### 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. AWS lists Red Hat subscriptions including AAP, alongside a different managed AAP service. Confirm an offer/order explicitly entitling this self-managed 2.7 installation. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://aws.amazon.com/marketplace/pp/prodview-4hz3uo55uaemk (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Managed AAP Marketplace committed-spend claims do not establish treatment of this self-managed subscription. Obtain the selected offer and buyer-agreement eligibility. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://aws.amazon.com/marketplace/pp/prodview-4hz3uo55uaemk (reviewed 2026-11-17).

- Single sign-on: Documented. AAP 2.7 documents SAML identity-provider configuration through platform gateway. External authentication must use the gateway; legacy direct component authentication is no longer supported. Scope: Self-managed AAP 2.7 platform gateway. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-proc_controller_set_up_saml (reviewed 2026-11-17). Supporting source: Mandatory gateway authentication — https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-mandatory_platform_gateway_authentication_in_ansible_automation_platform_2_7.

- SCIM provisioning: Sources checked — unresolved. Platform gateway documents SAML/LDAP/OIDC and group/role mapping, but a supported AAP 2.7 SCIM lifecycle endpoint was not established. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-proc_controller_set_up_saml (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Red Hat Ansible Automation Platform 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.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-configure_your_ansible_automation_platform_deployment (reviewed 2026-11-17).

- Security controls: Documented. AAP 2.7 centralizes external authentication at platform gateway and documents HTTPS redirects and CSRF settings. Restrict component access and configure the chosen identity provider and role mappings. Scope: AAP 2.7 gateway and deployment configuration. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-configure_your_ansible_automation_platform_deployment (reviewed 2026-11-17).

- Air-gapped operation: Documented. The containerized installer supports disconnected installation using a downloaded setup bundle, local RHEL RPM repositories and bundle_install=true. Required metrics service works without internet access; content and update transfers remain operator responsibilities. Scope: AAP 2.7 containerized disconnected installation. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-assembly_aap_containerized_disconnected_installation (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The subscription-gated containerized setup bundle uses a configured inventory to install platform components with Podman; OpenShift uses the supported Operator path. AAP 2.7 does not use the removed RPM installer. Scope: AAP 2.7 installation methods; not AWX or Ansible Core. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-con_choosing_installation_type (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The containerized system requirements distinguish the supported RHEL host, subscriptions, database and component resources. Use the deployment-model inventory and execution capacity to size each host; portal-only appliance requirements do not size the complete platform. Scope: AAP 2.7 containerized topology, not portal-only sizing. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-ref_cont_aap_system_requirements (reviewed 2026-11-17).

- License pricing: Documented. The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification. Scope: Red Hat Ansible Automation Platform Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Choose the supported HA inventory and count managed nodes, execution jobs, execution environments, controller/hub/database hosts and RHEL/AAP subscriptions. Human users and data size alone do not size automation capacity. 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.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-ref_cont_aap_system_requirements (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The reviewed self-managed documentation is the AAP 2.7 line, with separate patch-release notes and component updates. Select a supported patch and matching bundle; this is a version-line review, not a claim about a latest patch timestamp. Scope: Self-managed AAP documentation line and patch index. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/ (reviewed 2026-11-17).







## Red Hat OpenShift AI Self-Managed

Commercial AI and machine-learning platform installed as an Operator on a customer-operated Red Hat OpenShift cluster.

- Listing: https://launchinyourcloud.com/directory/red-hat-openshift-ai-self-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, oci, ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat OpenShift AI Self-Managed subscription; an eligible OpenShift subscription is also required.
- Licensing model: commercial-only
- Installation: OpenShift AI Operator through OperatorHub or the oc command-line interface
- Architecture: OpenShift operators and persistent AI workbench, pipeline, model-serving and supporting services on customer Kubernetes infrastructure.
- Operations: Customer manages the OpenShift cluster, storage, accelerators, identity, networking, model data, backups and upgrades within Red Hat's supported configuration matrix.
- Product website: https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-ai
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers OpenShift AI Self-Managed, not Red Hat's managed cloud-service add-on. Support depends on a compatible OpenShift Container Platform release, storage and accelerator matrix, and active subscriptions. Underlying OpenShift and cloud infrastructure are operated by the customer. RHSA-2026:95872 is a critical OpenShift AI 3.5.3 security update covering nine CVEs. Use Red Hat's package and deployment scope to determine affected components, then apply 3.5.3 or a later supported update.

The selected Self-Managed product requires a Red Hat OpenShift AI subscription and an eligible OpenShift platform entitlement. Open-source components do not grant the complete supported product entitlement.

OpenShift AI runs persistent operator-managed workloads on customer OpenShift clusters with storage, compute and optional accelerator dependencies.


### Category fit

- ai-tools: AI workbenches, pipelines, model serving and lifecycle tooling delivered on a customer-operated OpenShift platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 


### Cloud deployment evidence

- OpenShift AI Self-Managed on supported OpenShift public-cloud platforms (aws, azure, gcp, oci, ibm): https://access.redhat.com/articles/rhoai-supported-configs
  Red Hat's Self-Managed matrix explicitly lists OpenShift Container Platform on AWS, Azure, Google Cloud, IBM Cloud and Oracle Cloud. The selected OpenShift release, subscriptions, storage, accelerator and component restrictions apply; managed cloud-service add-ons are a separate offering.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- OpenShift AI supported configurations: https://access.redhat.com/articles/rhoai-supported-configs

- OpenShift AI Self-Managed 3.5 installation and subscription: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install

- RHSA-2026:95872: https://access.redhat.com/errata/RHSA-2026%3A95872

### Licensing sources

- https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install

### Infrastructure sources

- https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install


### 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. OperatorHub installation and required subscriptions do not establish a specific cloud Marketplace offer for the Self-Managed AI entitlement. Managed add-ons and generic OpenShift offers are separate. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Self-Managed AI and underlying OpenShift subscriptions need offer-specific confirmation before software charges are treated as eligible cloud commitment spend. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Single sign-on: Documented. OpenShift AI uses the identity provider configured for its OpenShift cluster. Configure cluster identity and AI user/admin groups; this does not establish a separate application SCIM endpoint. Scope: Self-managed OpenShift AI 3.5 identity through the cluster. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. AI authentication delegates to the OpenShift IdP. The reviewed installation guide does not establish a separate AI SCIM endpoint or the provisioning capabilities of the buyer’s chosen IdP. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Red Hat OpenShift AI 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.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Security controls: Documented. Installation requires cluster administrator access, a configured IdP and compatible subscriptions. Configure access groups and certificate trust for workbenches, models, pipelines and object storage. Current advisory review: RHSA-2026:95872 is a critical OpenShift AI 3.5.3 update covering nine CVEs. Apply OpenShift AI 3.5.3 or a later supported update following Red Hat's erratum. Scope: OpenShift AI cluster access prerequisites Red Hat OpenShift AI 3.5 packages identified in the erratum.. Source: https://access.redhat.com/errata/RHSA-2026%3A95872 (reviewed 2026-11-18). Supporting source: Certificate trust in disconnected deployments — https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed_in_a_disconnected_environment/working-with-certificates_certs. Supporting source: Prior security-controls source — https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install.

- Air-gapped operation: Documented. Red Hat supplies a separate disconnected installation guide using mirrored Operator/container content. Required model, notebook, accelerator and object-storage dependencies must also be staged for the selected components. Scope: Self-managed OpenShift AI disconnected installation. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed_in_a_disconnected_environment/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Install the supported OpenShift AI Operator on an entitled, compatible OpenShift cluster and enable the required components. Cluster creation, storage, accelerators and model assets remain separate deployment work. Scope: OpenShift AI Self-Managed 3.5 Operator installation. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Installing the Operator requires at least two workers with 8 CPU/32 GiB each; single-node OpenShift requires 32 CPU/128 GiB. Workloads, models, accelerators and storage need additional resources; these installation minima do not establish HA workload capacity. Scope: OpenShift AI 3.5 installation minima; platform/control-plane resources additional. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- License pricing: Documented. The selected Self-Managed product requires a Red Hat OpenShift AI subscription and an eligible OpenShift platform entitlement. Open-source components do not grant the complete supported product entitlement. Scope: Red Hat OpenShift AI Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Select OpenShift HA topology, enabled AI components, model size, GPU needs, concurrency, object storage and both subscription entitlements. Operator installation minima do not size inference/training. 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.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Red Hat OpenShift AI 3.5.3 was published as critical security advisory RHSA-2026:95872 on November 6, 2026 and covers nine CVEs. Scope: Red Hat OpenShift AI self-managed 3.5. Source: https://access.redhat.com/errata/RHSA-2026%3A95872 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Red Hat OpenShift AI 3.5.3 critical security update (security-advisory): RHSA-2026:95872 is a critical OpenShift AI 3.5.3 update covering nine CVEs. Scope: Red Hat OpenShift AI 3.5 packages identified in the erratum. Conditions: Installed components and package versions determine applicability. Action: Apply OpenShift AI 3.5.3 or a later supported update following Red Hat's erratum. Source: https://access.redhat.com/errata/RHSA-2026%3A95872; reviewed 2026-11-18.




## Red Hat OpenShift Container Platform

Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.

- Listing: https://launchinyourcloud.com/directory/openshift-container-platform/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat OpenShift subscription.
- Licensing model: commercial-only
- Installation: OpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba Cloud
- Architecture: Customer-operated control-plane and worker machines with integrated operators, networking, storage and cluster services
- Operations: Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.
- Product website: https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform
- 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-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.

The selected self-managed OpenShift Container Platform edition is delivered through a commercial Red Hat subscription with entitlement and support terms.

OpenShift Container Platform runs persistent control-plane and worker nodes plus integrated cluster operators and storage services in the customer cloud.


### Category fit

- backend-platforms: Provides a self-managed Kubernetes application platform with integrated operators, developer workflows, networking, registry and cluster services.

- devops: Provides platform engineering, build, deployment and operations workflows for applications across customer-managed clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index (checked 2026-11-15). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index (checked 2026-11-15). 


### Cloud deployment evidence

- Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud (aws, azure, gcp): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview
  Red Hat's current installation overview explicitly distinguishes self-managed OpenShift Container Platform and documents installer- and user-provisioned installation paths on AWS, Microsoft Azure and Google Cloud using customer accounts and credentials.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Self-managed OpenShift on IBM Cloud (ibm): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index
  Red Hat documents installer-provisioned deployment into customer IBM Cloud infrastructure, including account IAM/API keys, region selection, VPC networking and cluster administration.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Versions: 4.21.

- OpenShift on Alibaba Cloud — Technology Preview (alibaba): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index
  Red Hat documents Assisted Installer deployment using customer Alibaba Cloud OSS images, ECS machines, VPC and DNS. This 4.21 path is Technology Preview: outside production SLAs, potentially incomplete and not recommended by Red Hat for production.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Versions: 4.21 Technology Preview.


### Sources

- OpenShift Container Platform 4.21 installation overview: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview

- Red Hat self-managed OpenShift subscription guide: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide

- Self-managed OpenShift on IBM Cloud: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index

- OpenShift on Alibaba Cloud — Technology Preview: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index

### Licensing sources

- https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide

### Infrastructure sources

- https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview


### 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 4.20 Authentication Operator supports an external OIDC identity provider using authorization-code flow, discovery and mapped claims. This authenticates platform users; applications running on the cluster need their own identity integration. Review browser/CLI token workflows and selected provider compatibility. Scope: OpenShift 4.20 platform-user OIDC through the integrated OAuth service. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/observability/authentication_and_authorization/using-rbac (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. Red Hat documents installer-provisioned AWS infrastructure using the release-matched openshift-install tool, install configuration, pull secret and cloud credentials. Customer-managed networking and permissions require review. Use the entitled Red Hat release distribution; the upstream installer source alone is not the product entitlement. Scope: OpenShift Container Platform 4.20 AWS installer path. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure (reviewed 2026-11-20). Deployment artifact: https://github.com/openshift/installer. Artifact reference: Upstream installer source; obtain matching Red Hat release tooling and pull secret.

- Minimum footprint / sizing: Documented. The 4.20 AWS installation matrix gives bootstrap/control-plane minima of 4 vCPUs, 16 GB RAM and 100 GB disk, and compute nodes 2 vCPUs, 8 GB and 100 GB. A standard cluster uses multiple control-plane and worker machines; workload pods, operators, storage, bootstrap and HA capacity are additional. Scope: OpenShift 4.20 per-machine installation floors, not complete workload sizing. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure (reviewed 2026-11-20).

- License pricing: Documented. Self-managed subscriptions can use core-pairs or bare-metal nodes. On hyperscaler VMs, one core-pair covers four vCPUs; aggregate compute-node entitlement and support level must be sized. AI accelerators may require separate subscriptions. Obtain the applicable order and price. Scope: Red Hat self-managed OpenShift Container Platform subscription guide. Source: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## REDCap (Research Electronic Data Capture)

Institutionally licensed research data-capture and records software with AWS and Azure deployment assets.

- Listing: https://launchinyourcloud.com/directory/redcap/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself.
- Licensing model: commercial-only
- Installation: AWS CDK / CloudFormation or Azure deployment templates; separately supply licensed REDCap software
- Architecture: Licensed REDCap application, database, file storage and identity configuration in customer cloud resources.
- 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/aws-samples/redcap-on-aws
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

REDCap is not open source. Eligible nonprofit institutions can obtain a no-charge institutional licence through the consortium; licensing conditions still apply. Open infrastructure licences do not license REDCap, and deployment does not provide automatic clinical or regulatory validation. Update and rebuild the selected AWS sample container to the corrected pinned base; apply licensed REDCap application updates separately.

Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself.

Licensed REDCap application, database, file storage and identity configuration in customer cloud resources. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- clinical-regulatory-document-management: Institutionally licensed research data-capture and records software with AWS and Azure deployment assets.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/vanderbilt-redcap/redcap-azure (checked 2026-11-19). 


### Cloud deployment evidence

- AWS CDK (aws): https://github.com/aws-samples/redcap-on-aws
  Licensed REDCap application, database, file storage and identity configuration in customer cloud resources. REDCap is not open source. Eligible nonprofit institutions can obtain a no-charge institutional licence through the consortium; licensing conditions still apply. Open infrastructure licences do not license REDCap, and deployment does not provide automatic clinical or regulatory validation.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure PaaS (azure): https://github.com/vanderbilt-redcap/redcap-azure
  Licensed REDCap application, database, file storage and identity configuration in customer cloud resources. REDCap is not open source. Eligible nonprofit institutions can obtain a no-charge institutional licence through the consortium; licensing conditions still apply. Open infrastructure licences do not license REDCap, and deployment does not provide automatic clinical or regulatory validation.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS CDK: https://github.com/aws-samples/redcap-on-aws

- Azure PaaS: https://github.com/vanderbilt-redcap/redcap-azure

- AWS CFN: https://github.com/Vanderbilt-REDCap/redcap-aws-cloudformation

- Consortium: https://projectredcap.org/about/consortium/

- EULA Terms: https://projectredcap.org/join/termsofuse/

- AWS Releases: https://github.com/aws-samples/redcap-on-aws/releases

- REDCap AWS sample container runtime update: https://github.com/aws-samples/redcap-on-aws/releases/tag/v1.3.2

### Licensing sources

- https://projectredcap.org/about/consortium/

- https://projectredcap.org/join/termsofuse/

### Infrastructure sources

- https://github.com/aws-samples/redcap-on-aws

- https://github.com/vanderbilt-redcap/redcap-azure


### 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. Vanderbilt lists Shibboleth, OpenID and Google OAuth2 among REDCap authentication options, separately from LDAP and local-table login. Select and configure an entitled institutional release, IdP and user-rights policy. The AWS infrastructure sample does not automatically configure those application identity methods. Scope: REDCap institutional application authentication options; release/configuration and infrastructure packaging separate. Source: https://projectredcap.org/wp-content/uploads/2025/01/REDCapTechnicalOverview.pdf (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 AWS-maintained v1.3.2 sample supplies CDK/serverless deployment with an institution-supplied REDCap archive and application configuration. Obtain the REDCap consortium licence/package, review IAM/network/database/storage and supported runtime settings, and plan upgrades; sample code does not grant REDCap software rights. Scope: AWS sample v1.3.2 infrastructure automation; separately entitled REDCap application. Source: https://github.com/aws-samples/redcap-on-aws/blob/v1.3.2/README.md (reviewed 2026-11-21). Deployment artifact: https://github.com/aws-samples/redcap-on-aws/tree/v1.3.2. Artifact reference: v1.3.2.

- Minimum footprint / sizing: Documented. The v1.3.2 AWS sample defaults each application instance to 2 vCPU/4 GB memory and sets concurrency to ten based on a limited test, recommending workload monitoring/tuning. Database, storage, scheduled work, scaling/HA and uploaded data are separate; this is not a complete 100-user/1-TB capacity or cost estimate. Scope: AWS REDCap sample application-instance defaults and limited reference test. Source: https://github.com/aws-samples/redcap-on-aws/blob/v1.3.2/README.md (reviewed 2026-11-21).

- License pricing: Documented. Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself. Scope: REDCap (Research Electronic Data Capture); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://projectredcap.org/about/consortium/ (reviewed 2026-11-19).

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

- REDCap AWS sample container runtime update (security-advisory): The AWS sample v1.3.2 updates its PHP/Apache base image for CVE-2026-109618 and CVE-2026-109619. Scope: aws-samples/redcap-on-aws container base php:8.4.27-apache in infrastructure release v1.3.2; not a REDCap application release. Conditions: Applies to installations built from the affected sample container. Azure and separately assembled REDCap deployments need their own runtime checks. Action: Update and rebuild the selected AWS sample container to the corrected pinned base; apply licensed REDCap application updates separately. Source: https://github.com/aws-samples/redcap-on-aws/releases/tag/v1.3.2; reviewed 2026-11-19.




## Redis Software Self-Managed

Commercial Redis Enterprise software installed and operated in the customer's cloud or data center.

- Listing: https://launchinyourcloud.com/directory/redis-software-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Redis Software subscription.
- Licensing model: commercial-only
- Installation: Redis operator on EKS, AKS or GKE; Linux, container and AWS AMI options are also available
- Architecture: Customer-operated Redis Enterprise cluster and operator with persistent data and management services
- Operations: Customer manages cluster infrastructure, networking, persistence, backups, upgrades, monitoring and licensed capacity.
- Product website: https://redis.io/software/
- Source review: 2026-11-17; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers Redis Software and Redis Enterprise for Kubernetes, not Redis Cloud, Azure Managed Redis or the separately licensed Redis Open Source distribution. Confirm operator, Kubernetes and subscription compatibility for the selected release. Redis Software 8.2.6-52 fixes critical Brotli CVE-2026-111497, includes current Redis OSS security fixes, and resolves SAML SSO, S3 backup, Active-Active, certificate, and OCSP problems. Redis database 8.0 reaches end of life on December 1, 2026; migrate databases to a supported feature set before then.

This listing is for Redis Software, a subscription product governed by Redis commercial terms. It does not classify Redis Open Source.

Redis Enterprise runs persistent cluster nodes and an operator inside customer-managed Kubernetes or on customer VMs. It remains a stateful server deployment.


### Category fit

- databases-vector: Provides commercial in-memory data, search and vector capabilities in a customer-operated Redis Enterprise cluster.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/ (checked 2026-11-14). 


### Cloud deployment evidence

- Redis Software on EKS, AKS and GKE (aws, azure, gcp): https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/
  Redis lists and tests its current Kubernetes operator on Amazon EKS, Microsoft AKS and Google GKE. The customer operates the Kubernetes cluster and Redis Software deployment; Redis Cloud is separate.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- Redis deployment methods: https://redis.io/deployment/method/

- Redis Enterprise for Kubernetes: https://redis.io/docs/latest/operate/kubernetes/

- Supported Kubernetes distributions: https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/

- Redis Software agreement: https://redis.io/legal/software-agreement/

- Redis Software 8.2.6-52 security and lifecycle notes: https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-6-52/

- Redis database and cluster version lifecycle: https://redis.io/docs/latest/operate/rs/8.0/installing-upgrading/product-lifecycle/

### Licensing sources

- https://redis.io/legal/software-agreement/

- https://redis.io/deployment/method/

### Infrastructure sources

- https://redis.io/docs/latest/operate/kubernetes/

- https://redis.io/docs/latest/operate/kubernetes/deployment/


### 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. Redis Software supports IdP- and SP-initiated SAML 2.0 for the Cluster Manager UI with role mapping. This is administrative browser identity, not the Redis database client authentication protocol. Scope: Redis Software Cluster Manager UI; not Redis Cloud or Open Source. Source: https://redis.io/docs/latest/operate/rs/security/access-control/saml-sso/ (reviewed 2026-11-14).

- SCIM provisioning: Explicitly unsupported. The Software SAML guide explicitly says SCIM user provisioning is unavailable. It supports just-in-time user creation at first SSO login; JIT is not equivalent to SCIM provisioning/deprovisioning. Scope: Redis Software administrative users. Source: https://redis.io/docs/latest/operate/rs/security/access-control/saml-sso/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide delivers Redis Software as a vendor package and installation script for supported Linux hosts, followed by cluster/database configuration. Obtain the chosen compatible release and licence. This is a product installer path; operating-system provisioning, node placement and HA design remain separate. Scope: Official Redis Software Linux installation; not Redis Open Source packaging. Source: https://redis.io/docs/latest/operate/rs/installing-upgrading/install/install-on-linux/ (reviewed 2026-11-20). Deployment artifact: https://redis.io/docs/latest/operate/rs/installing-upgrading/install/install-on-linux/. Artifact reference: Select the supported Redis Software release for the target OS.

- Minimum footprint / sizing: Documented. The 7.8 production matrix requires at least three nodes, each with 2 CPU cores and 8 GB RAM; it recommends at least 8 cores/32 GB per node. Ephemeral and persistent storage depend on RAM and persistence/tiering modes. This is Redis Software guidance, not Redis Open Source sizing or capacity for a specified dataset. Scope: Redis Software 7.8 production node floor; workload/tiering sizing additional. Source: https://redis.io/docs/latest/operate/rs/7.8/installing-upgrading/install/plan-deployment/hardware-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. Redis Software uses a cluster licence controlling features and shard capacity; every cluster, including passive/cold DR, needs a separate licence. Trial mode lasts 30 days and permits four shards. Obtain commercial capacity/support pricing; Redis Open Source licensing does not cover this product. Scope: Commercial self-managed Redis Software cluster licensing; no public price quoted. Source: https://redis.io/docs/latest/operate/rs/clusters/configure/license-keys/ (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.

- Redis Software Brotli and dependency patch (security-advisory): Redis Software 8.2.6-52 patches critical Brotli CVE-2026-111497 through updated bundled components. Scope: Redis Software 8.2.6-52; not Redis Cloud or every independently installed Redis Open Source distribution. Conditions: The actual Redis Software image and affected bundled components determine exposure. Redis database and cluster version lifecycles are separate. Action: Apply a compatible Software/operator update; review SAML role mappings, tokens, backup behavior and module-upgrade limitations. Source: https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-6-52/; reviewed 2026-11-17.

- Redis database 8.0 support deadline (lifecycle): The bundled Redis database 8.0 STS line reaches end of life on December 1, 2026. Scope: Redis database 8.0 feature set inside Redis Software; this is not the Redis Software 8.0 cluster-version EOL date. Conditions: A database can lose support while its enclosing cluster version remains supported. Contract terms and the selected operator/cluster version need separate checks. Action: Move databases to a supported compatible database version before the deadline; plan the database upgrade separately from the cluster upgrade. Source: https://redis.io/docs/latest/operate/rs/8.0/installing-upgrading/product-lifecycle/; reviewed 2026-11-17.




## Redpanda BYOC

Managed Kafka-compatible streaming in your cloud account.

- Listing: https://launchinyourcloud.com/directory/redpanda/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial
- Licensing model: commercial-only
- Installation: Redpanda Cloud BYOC provisioning
- Architecture: Vendor-managed cluster in customer network
- Operations: Redpanda manages provisioning, monitoring and upgrades with the permissions you grant.
- Product website: https://www.redpanda.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

BYOC supports AWS and Google Cloud VPCs and Azure VNets. BYOVPC/BYOVNet lets the customer provision networking first. Review agent permissions and emergency support access. Redpanda Cloud's November update adds Load Factor dashboard metrics for BYOC deployments on version 26.2 or later. Treat the October BYOVNet, self-service scaling, and Azure tier announcements as separate earlier changes when planning upgrades.

This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.

BYOC uses a customer-cloud cluster and Kubernetes infrastructure. Redpanda’s separately hosted Serverless service is outside this listing.


### Category fit

- streaming: Managed Kafka-compatible streaming in your cloud account.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

Operating responsibility: Redpanda provisions, monitors and upgrades the cluster using delegated access to the customer cloud account. Customer-managed networking is a separate BYOVPC/BYOVNet option. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-20). Supporting source: BYOC managed control plane and customer data plane — https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/.


### Cloud deployment evidence

- Redpanda BYOC supported infrastructure (aws, azure, gcp): https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/
  Redpanda explicitly documents BYOC clusters in the customer AWS or Google Cloud VPC or Azure VNet, with a Redpanda-operated control plane. The architecture and provisioning requirements differ by provider; this is the BYOC offering, not Dedicated clusters in the vendor account.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- BYOC deployment options: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/

- BYOC cluster and Kubernetes architecture: https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/

- Redpanda Cloud what's new: https://docs.redpanda.com/cloud-data-platform/get-started/whats-new-cloud/

### Licensing sources

- https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/

### Infrastructure sources

- https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/


### 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: Edition-dependent. Redpanda documents an AWS Marketplace private-offer subscription workflow and links it to BYOC cluster creation. Confirm that the order is for the intended BYOC deployment, not a vendor-account cluster. Scope: Redpanda Cloud marketplace subscription and BYOC path; selected offer terms apply. Source: https://docs.redpanda.com/cloud-data-platform/billing/aws-commit/ (reviewed 2026-11-14).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Redpanda Cloud documents organisation user login through an OIDC-compliant identity provider with discovery. An organisation administrator configures and enables the connection, with optional enrolment and group-based permissions. The BYOC pricing page includes OIDC SSO in that service. Scope: Vendor-operated Cloud control-plane user SSO for a BYOC organisation; data-plane broker/client authentication is separate. Source: https://docs.redpanda.com/cloud-data-platform/security/cloud-authentication/ (reviewed 2026-11-21). Supporting source: BYOC service identity features — https://www.redpanda.com/pricing.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Redpanda documents a Cloud Terraform provider for networks, clusters and data-plane resources, with separate BYOVPC modules for AWS/GCP and a BYOVNet module for Azure. Select the BYOC cluster type, customer-managed resource configuration and throughput tier, pin provider/module versions and review replacement behavior. The provider automates the managed Cloud service, not installation of self-managed Community brokers. Scope: Redpanda Cloud BYOC control-plane automation and customer-cloud data plane; not self-managed Redpanda core Helm delivery. Source: https://docs.redpanda.com/cloud-data-platform/manage/terraform-provider/ (reviewed 2026-11-21). Deployment artifact: https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs. Artifact reference: Current Cloud provider documentation; pin the selected provider/module versions.

- Minimum footprint / sizing: Sources checked — unresolved. The BYOC tier reference maps throughput tiers to cloud machine types and directs buyers to a sizing calculator for broker count, machine type and RPU rate. Its connection examples are not a universal cluster minimum. A production configuration for 100 users/1 TB/HA still needs ingress/egress rate, partitions, retention, connections and recovery targets. Scope: Redpanda Cloud BYOC workload-based sizing; no complete reference-workload machine configuration verified. Source: https://docs.redpanda.com/cloud-data-platform/reference/tiers/byoc-tiers/ (reviewed 2026-11-21).

- License pricing: Documented. The vendor distinguishes Redpanda Cloud BYOC as a fully managed commercial service with an annual commitment and a sales-led trial/quote. Its customer-cloud infrastructure and agreed service charges require separate assessment; self-managed Community or Enterprise software terms are different offerings. Scope: Redpanda Cloud BYOC service pricing model; no Community licence or hosted Serverless price applied to BYOC. Source: https://www.redpanda.com/pricing (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## RegScale

Commercial self-hosted governance and policy platform with provider-specific container and Kubernetes guides.

- Listing: https://launchinyourcloud.com/directory/regscale/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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: Kubernetes manifests
- Architecture: RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE.
- 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://regscale.readme.io/docs/aws-ecs.md
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.

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

RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Commercial self-hosted governance and policy platform with provider-specific container and Kubernetes guides.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://regscale.readme.io/docs/aws-ecs.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://regscale.readme.io/docs/azure-aca.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://regscale.readme.io/docs/gcp-cloud-run.md (checked 2026-11-19). 


### Cloud deployment evidence

- AWS ECS (aws): https://regscale.readme.io/docs/aws-ecs.md
  RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure ACA (azure): https://regscale.readme.io/docs/azure-aca.md
  RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Cloud Run (gcp): https://regscale.readme.io/docs/gcp-cloud-run.md
  RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS ECS: https://regscale.readme.io/docs/aws-ecs.md

- Azure ACA: https://regscale.readme.io/docs/azure-aca.md

- GCP Cloud Run: https://regscale.readme.io/docs/gcp-cloud-run.md

- K8s Helm: https://regscale.readme.io/docs/kubernetes-deployment.md

- Policies Module: https://regscale.readme.io/docs/policies.md

- RegScale Licensing Docs: https://regscale.readme.io/docs/setup-general.md

- RegScale ESLA: https://regscale.com/enterprise-software-license-agreement/

- Helm Index YAML: https://regscale.github.io/helm/index.yaml

### Licensing sources

- https://regscale.readme.io/docs/setup-general.md

- https://regscale.com/enterprise-software-license-agreement/

### Infrastructure sources

- https://regscale.readme.io/docs/aws-ecs.md

- https://regscale.readme.io/docs/azure-aca.md

- https://regscale.readme.io/docs/gcp-cloud-run.md


### 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 OAuth2/OIDC or SAML2 user SSO, with only one active method per tenant and configured first-login provisioning. Set issuer/client or metadata, identity claims and role policy for the selected installation; orchestration-hub compatibility and service credentials are separate. Scope: Current RegScale tenant user federation and configuration. Source: https://regscale.readme.io/docs/setup-single-sign-on-sso (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 AWS guide supplies an ECS Fargate task definition and CLI workflow with ALB/TLS, EFS, external SQL Server and secrets; Kubernetes deployment is separately documented. Select compatible image/chart versions and licences. The example is configurable infrastructure guidance, not a complete turnkey HA stack. Scope: RegScale current vendor AWS ECS deployment reference. Source: https://regscale.readme.io/docs/aws-ecs (reviewed 2026-11-21). Deployment artifact: https://regscale.readme.io/docs/aws-ecs. Artifact reference: Current vendor guide reviewed on this date. Supporting source: Kubernetes deployment — https://regscale.readme.io/docs/kubernetes-deployment.

- Minimum footprint / sizing: Documented. The sizing guide separates evaluation (web 2 vCPU/4 GB, database 4 vCPU/16 GB) from recommended production (web 4 vCPU/8 GB, database 8 vCPU/32 GB). Its HA tier starts with two or more web nodes and separately sized database availability. Monitor actual imports, users, reporting, storage and backups rather than treating these as workload guarantees. Scope: Current RegScale component/tier baselines; evaluation, production and HA distinguished. Source: https://regscale.readme.io/docs/sizing-guide (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## ResourceSpace Self-Hosted

Open-source digital asset management deployed on your own infrastructure.

- Listing: https://launchinyourcloud.com/directory/resourcespace/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open source; paid hosting and support available separately
- Licensing model: open-source
- Installation: Official Docker Compose or source/LAMP installation
- Architecture: Customer-operated DAM application, database and asset storage
- Operations: Customer manages the application, database, asset storage, backups and upgrades.
- Product website: https://www.resourcespace.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The official download page explicitly names AWS, Azure and Google Cloud for self-installed Docker deployments. The installation guide provides the official repository and Compose instructions. Other provider support is not inferred from Docker portability.

ResourceSpace publishes its self-hosted code under a permissive BSD-style license allowing modification and redistribution, with attribution and derivative-name trademark conditions. Paid hosting/support is separate, not evidence of proprietary feature code; inspect the actual release license for exact terms.

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.


Cloud evidence scope: Documented provider-specific deployment

### Category fit

- digital-asset-management: Dedicated digital asset management for organizing, finding and distributing media. This entry covers self-installation, not vendor-hosted free or managed cloud plans. Validate production sizing and backup design.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.resourcespace.com/get?from_rs=true (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.resourcespace.com/get?from_rs=true (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.resourcespace.com/get?from_rs=true (checked 2026-11-12). 


### Cloud deployment evidence

- ResourceSpace self-installation cloud compatibility (aws, azure, gcp): https://www.resourcespace.com/get?from_rs=true
  The vendor explicitly identifies AWS, Azure and Google Cloud for self-installation, alongside its separate hosted service. The linked Docker/source installation instructions establish the customer-operated application path; select compatible dependencies and arrange support separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-installation and named cloud platforms: https://www.resourcespace.com/get?from_rs=true

- Official Docker installation steps: https://www.resourcespace.com/knowledge-base/systemadmin/install_docker

- Product and self-hosting FAQ: https://www.resourcespace.com/faq

- Licensing and edition terms: https://www.resourcespace.com/docs/ResourceSpace_License_Agreement.pdf

- Licensing and edition terms: https://www.resourcespace.com/terms

### Licensing sources

- https://www.resourcespace.com/docs/ResourceSpace_License_Agreement.pdf

- https://www.resourcespace.com/faq

- https://www.resourcespace.com/terms

### Infrastructure sources

- https://www.resourcespace.com/get?from_rs=true

- https://www.resourcespace.com/knowledge-base/systemadmin/install_docker


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. ResourceSpace publishes a SimpleSAMLphp-based plugin for SAML 2.0 identity-provider login. Enable the plugin and exchange provider metadata; group mapping, local-login fallback and share-access rules are configurable. Metadata-URL handling and migration steps depend on the ResourceSpace/plugin version. Scope: ResourceSpace self-hosted SAML plugin; an existing compatible IdP and administrator configuration are required. Source: https://www.resourcespace.com/knowledge-base/plugins/simplesaml (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide links this application/database deployment repository and requires replacing database credentials before building the stack. Scope: Official ResourceSpace Docker recipe. Source: https://github.com/resourcespace/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/resourcespace/docker. Artifact reference: repository default branch (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The official requirements specify its LAMP stack and preview-processing tools, but do not establish a quantitative whole-host CPU/RAM/storage floor for the intended DAM workload. PHP limits and hosted storage allowances are not production capacity for originals, previews, video jobs, database and replicas. Scope: Complete self-hosted ResourceSpace deployment; current version and selected preview/AI integrations affect sizing. Source: https://www.resourcespace.com/knowledge-base/systemadmin/general_requirements (reviewed 2026-11-20).

- License pricing: Documented. The vendor FAQ states that local installation has no software licence fee or per-user charge. Paid hosting, technical/customer support and services are separate. The hosted free-storage allowance does not establish a self-hosted infrastructure cost or include a support contract. Scope: ResourceSpace self-hosted software pricing; review the actual software licence and any hosting/support agreement separately. Source: https://www.resourcespace.com/faq (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Retool Self-Hosted, Self-Managed

Commercial single-tenant Retool deployment installed and operated on customer-managed Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/retool-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Enterprise subscription with custom annual pricing and a self-hosted license key.
- Licensing model: commercial-only
- Installation: Official Terraform blueprints for Amazon EKS, Azure AKS or Google GKE, or Helm into an existing supported Kubernetes cluster
- Architecture: Distributed Retool containers on Kubernetes with external PostgreSQL, object storage, ingress and optional Temporal services
- Operations: Customer manages Kubernetes, PostgreSQL, object storage, DNS, TLS, secrets, networking, backups, capacity, upgrades and the Retool license.
- Product website: https://retool.com/self-hosted
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-hosted, self-managed Retool, not Retool-managed hosting. Kubernetes with Helm is the supported production path for Retool 4.0 and later; Docker Compose is non-production only. EKS must use EC2-backed workers rather than Fargate for the agent sandbox. The standard deployment requires outbound access for license checks, authentication and usage reporting; Enterprise pricing separately offers air-gapped deployment, requiring the appropriate license and vendor-provided procedure. Workflows and Agents require Temporal, and Retool recommends its managed Temporal Cloud service unless the customer operates a compatible cluster.

Current pricing places self-hosted and air-gapped deployments in Enterprise with custom annual pricing. Product-specific subscription and license-key terms apply; cloud per-seat prices do not price this deployment.

Production deployments run persistent Retool services on customer EKS, AKS or GKE infrastructure with external database and object-storage dependencies.


### Category fit

- internal-tools: Provides a self-hosted low-code platform for building internal applications and operational interfaces.

- workflow-automation: Runs Retool Workflows and related automation services inside the customer-operated deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 


### Cloud deployment evidence

- Official Retool Terraform and Helm deployment paths (aws, azure, gcp): https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes
  Retool provides production Terraform blueprints for AWS, Azure and Google Cloud and explicitly targets Amazon EKS, Azure AKS and Google GKE. Customers may alternatively deploy with Helm into an existing supported cluster.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Self-hosted, self-managed Retool: https://docs.retool.com/self-hosted/self-managed

- Self-managed Retool quickstart: https://docs.retool.com/self-hosted/self-managed/quickstart

- Retool Kubernetes deployment tutorials: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes

- Deploy Retool on Kubernetes with Helm: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm

- Retool product-specific terms: https://docs.retool.com/legal/product-specific-terms

- Enterprise deployment options and pricing: https://retool.com/pricing

### Licensing sources

- https://docs.retool.com/legal/product-specific-terms

- https://retool.com/pricing

### Infrastructure sources

- https://docs.retool.com/self-hosted/self-managed/quickstart

- https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm


### Buyer diligence


Research coverage: 11/12 fields (92%); 10 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: Edition-dependent. Retool’s AWS Marketplace listing explicitly describes self-hosted and Retool-managed AWS environments, with private-contract procurement. AWS classifies delivery as a SaaS contract; confirm the self-managed Enterprise entitlement rather than assuming an AMI installer or included infrastructure. Retool also announces Google Cloud private-offer purchasing with the same deployment options; the exact offer and agreement must match the self-hosted subscription. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-cqgbgmrm63i4y (reviewed 2026-11-16). Supporting source: Google Cloud Marketplace procurement and commitment conditions — https://retool.com/blog/retool-google-cloud-marketplace-announcement. Offer prodview-cqgbgmrm63i4y: Retool; SaaS contract/private offer; select self-managed Enterprise entitlement; https://aws.amazon.com/marketplace/pp/prodview-cqgbgmrm63i4y.

- Cloud commitment eligibility: Edition-dependent. Retool states that eligible Google Cloud Marketplace purchases can draw down a Google Cloud commitment and that Marketplace procurement preserves deployment options. Purchases use a private offer; the amount credited depends on the buyer’s Google agreement and accepted offer. This is not a blanket credit promise for all purchases or providers. Scope: Google Cloud private-offer procurement; buyer agreement controls eligibility. Source: https://retool.com/blog/retool-google-cloud-marketplace-announcement (reviewed 2026-11-16).

- Single sign-on: Edition-dependent. Retool documents SAML and OIDC providers, including Entra ID and Okta, plus identity-provider group/role mapping. Apply the self-hosted instance configuration and subscription entitlements; Google Group sync is a separate integration. Scope: Retool organization SSO; protocol support does not establish every plan entitlement; current pricing includes this capability in Enterprise. Source: https://docs.retool.com/sso/quickstart (reviewed 2026-11-16). Supporting source: Enterprise entitlement matrix — https://retool.com/pricing.

- SCIM provisioning: Edition-dependent. SCIM provisioning is documented for self-hosted versions 2.32.1+, with bearer-token authentication and /api/scim/v2/* endpoints. The guide covers Okta and Entra ID; the identity provider must reach the instance through its firewall. Scope: Self-hosted technical configuration; selected subscription governs commercial entitlement; current pricing includes this capability in Enterprise. Source: https://docs.retool.com/sso/guides/scim-user-provisioning (reviewed 2026-11-16). Supporting source: Enterprise entitlement matrix — https://retool.com/pricing.

- Compliance attestations: Sources checked — unresolved. Retool’s legal security practices describe independent SOC 2/ISO audits and direct readers to its Trust Center. Those public practices alone do not establish report dates or coverage of the customer-operated self-managed environment. Scope: Vendor controls and audit availability; customer-environment scope/period needs the actual report. Source: https://docs.retool.com/legal/security (reviewed 2026-11-16).

- Security controls: Documented. The code-executor uses nsjail, which needs privileged container access. The documented fallback runs code without sandboxing if that access is unavailable. Review this specific container’s isolation separately from agent and JavaScript executors. Scope: Self-managed code-executor container; not an attestation for every Retool service. Source: https://docs.retool.com/self-hosted/self-managed/quickstart (reviewed 2026-11-16).

- Air-gapped operation: Edition-dependent. Retool’s current Enterprise pricing explicitly offers air-gapped deployments. The standard self-managed guide still requires outbound license/authentication/usage services, so obtain the separate air-gap license, artifacts and procedure from Retool rather than applying the standard online setup unchanged. Scope: Enterprise commercial air-gap option is confirmed; deployment-specific procedure and integration dependencies require account-team coordination. Source: https://retool.com/pricing (reviewed 2026-11-16). Supporting source: Standard deployment outbound requirements — https://docs.retool.com/self-hosted/self-managed/quickstart.

- Deployment artifact / IaC: Documented. Retool provides Terraform blueprints that provision EKS, AKS or GKE and deploy Helm. Kubernetes with Helm is the production path for 4.0 and later; Compose is for development and proofs of concept. AWS agent sandboxes require EC2-backed EKS workers rather than Fargate. Scope: Self-managed Retool 4.0+; select matching chart and application versions. Source: https://docs.retool.com/self-hosted/self-managed/quickstart (reviewed 2026-11-16). Deployment artifact: https://github.com/tryretool/terraform-retool-self-hosted-blueprints/tree/main. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The current Helm guide calls for at least 32 CPU cores and 64 GiB available across the workload-node pool. Agent sandbox pods scale with builder sessions; the external PostgreSQL database, storage and peak autoscaling capacity must also be planned. Scope: Current production Helm stack with app-builder/agent services; not the older Compose baseline. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm (reviewed 2026-11-16).

- License pricing: Documented. Current pricing places self-hosted and air-gapped deployment in Enterprise, with custom annual pricing. Its published cloud per-seat prices do not price a self-hosted Enterprise installation. The subscription and license-key terms govern use. Scope: Self-hosted Enterprise procurement; excludes cloud infrastructure and operating labor. Source: https://retool.com/pricing (reviewed 2026-11-16). Supporting source: Self-hosted legal terms — https://docs.retool.com/legal/product-specific-terms.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor release is 4.86.0, published 2026-11-11. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Retool documents quarterly stable releases and six months of support for each stable version. Scope: Self-hosted stable-channel release, separate from cloud/edge versions; source supplies a publication day, not a timestamp. Source: https://docs.retool.com/releases/stable/version/4.86 (reviewed 2026-11-16).







## Reveal Enterprise Private Deployment

Customer-operated review and e-discovery platform with redaction, audit and production workflows.

- Listing: https://launchinyourcloud.com/directory/reveal-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Reveal application services, Kubernetes/Helm and provider-specific database/object-storage services.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.revealdata.com/rpd
- 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 AWS and Azure customer-controlled deployments. Apply the exact 2026.6 compatibility matrix, including the Azure S3Proxy testing qualification. Optional AI, translation and transcription paths can involve AWS subscriptions or a Reveal-managed Bedrock service; private hosting does not make every feature disconnected.

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

Reveal application services, Kubernetes/Helm and provider-specific database/object-storage services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- freedom-of-information: Customer-operated review and e-discovery platform with redaction, audit and production workflows.

- document-management: Customer-operated review and e-discovery platform with redaction, audit and production workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.revealdata.com/rpd-2026-6/docs/system-overview (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix (checked 2026-11-19). 


### Cloud deployment evidence

- RPD System Overview (AWS EC2/EKS/S3) (aws): https://docs.revealdata.com/rpd-2026-6/docs/system-overview
  Reveal application services, Kubernetes/Helm and provider-specific database/object-storage services. The vendor documents AWS and Azure customer-controlled deployments. Apply the exact 2026.6 compatibility matrix, including the Azure S3Proxy testing qualification. Optional AI, translation and transcription paths can involve AWS subscriptions or a Reveal-managed Bedrock service; private hosting does not make every feature disconnected.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Compatibility Matrix (AWS/Azure) (azure): https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix
  Reveal application services, Kubernetes/Helm and provider-specific database/object-storage services. The vendor documents AWS and Azure customer-controlled deployments. Apply the exact 2026.6 compatibility matrix, including the Azure S3Proxy testing qualification. Optional AI, translation and transcription paths can involve AWS subscriptions or a Reveal-managed Bedrock service; private hosting does not make every feature disconnected.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- RPD System Overview (AWS EC2/EKS/S3): https://docs.revealdata.com/rpd-2026-6/docs/system-overview

- Compatibility Matrix (AWS/Azure): https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix

- Reveal Private Deployment: https://www.revealdata.com/rpd

- RPD FAQs (S3/KMS/IAM): https://docs.revealdata.com/rpd-2026-6/docs/reveal-private-deployment-faqs

- PDF Redaction Workflow: https://docs.revealdata.com/rpd-2026-6/docs/pdf-redaction-workflow-sequence-1

- DSAR/Records Workflow: https://docs.revealdata.com/rpd-2026-6/docs/dsar-data-subject-access-request-use-case

- Reveal MSA PDF (On-Premises & SaaS): https://assets.applytosupply.digitalmarketplace.service.gov.uk/g-cloud-15/documents/724143/788391829807931-terms-and-conditions-2026-01-09-1357.pdf

- Reveal SaaS Terms (MSA Precedence): https://www.revealdata.com/saas-terms-of-service

- RPD 2026.6 8.19 Release Notes (2026-08-19): https://docs.revealdata.com/rpd-2026-6/docs/2026-6-8-19-patch-release-notes-reveal

- RPD 2026.6 8.15 Redaction Fix (2026-08-15): https://docs.revealdata.com/rpd-2026-6/docs/2026-6-8-15-patch-release-notes-reveal

### Licensing sources

- https://assets.applytosupply.digitalmarketplace.service.gov.uk/g-cloud-15/documents/724143/788391829807931-terms-and-conditions-2026-01-09-1357.pdf

- https://www.revealdata.com/saas-terms-of-service

### Infrastructure sources

- https://docs.revealdata.com/rpd-2026-6/docs/system-overview

- https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The RPD manual documents SAML and OpenID Connect integration and coordination with Reveal Support. Its examples use Reveal-hosted authentication URLs; confirm the actual private-instance realm, identity-service location and metadata rather than assuming those example hosts or fully local authentication. Scope: Reveal Private Deployment 2026.6 manual; provider configuration, support activation and the instance authentication boundary must be established. Source: https://docs.revealdata.com/rpd-2026-6/docs/reveal-sso-documentation (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The public RPD overview and compatibility matrix describe Kubernetes, mixed Windows/Linux services and database roles, but do not identify a complete version-matched production Helm/image/installer bundle. Obtain the entitled release artifacts and component compatibility instructions for the selected private deployment. Scope: Reveal Private Deployment 2026.6 application artifacts; architecture and software compatibility do not identify the actual licensed installation bundle. Source: https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix (reviewed 2026-11-20). Supporting source: System and component overview — https://docs.revealdata.com/rpd-2026-6/docs/system-overview.

- Minimum footprint / sizing: Documented. Reveal publishes a reference profile for 50 concurrent users and 10 TB under management. It includes two SQL database roles at 16 CPUs/64 GB each, a separate PostgreSQL database, search nodes and additional processing/management/storage roles. Use the complete table; those example allocations are not universal minima or a 100-user HA benchmark. Scope: RPD 2026.6 reference architecture and workload; named users, concurrent users, data phases and all dependent roles must be sized separately. Source: https://docs.revealdata.com/rpd-2026-6/docs/system-overview (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Reveal Enterprise Private Deployment; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://assets.applytosupply.digitalmarketplace.service.gov.uk/g-cloud-15/documents/724143/788391829807931-terms-and-conditions-2026-01-09-1357.pdf (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAP Business One (BYOL)

Licensed ERP for financials, purchasing, inventory and customer operations.

- Listing: https://launchinyourcloud.com/directory/sap-business-one/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp, alibaba
- 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: Customer-managed SAP Business One application and a certified database on cloud VMs.
- 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://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.

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

Customer-managed SAP Business One application and a certified database on cloud VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Licensed ERP for financials, purchasing, inventory and customer operations.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide (checked 2026-11-19). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide (checked 2026-11-19). 


### Cloud deployment evidence

- Azure Docs (azure): https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Docs (gcp): https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Alibaba Docs (alibaba): https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure Docs: https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure

- GCP Docs: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide

- Alibaba Docs: https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide

- GCP SAP B1 BYOL Guide: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide

- SAP Help Portal: https://help.sap.com/docs/SAP_BUSINESS_ONE

- SAP B1 2026 News: https://news.sap.com/2026/11/sap-business-one-30-years-of-growing-together/

### Licensing sources

- https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide

- https://help.sap.com/docs/SAP_BUSINESS_ONE

### Infrastructure sources

- https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure

- https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide

- https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SAP Business One documents external OpenID Connect identity providers registered in the SLD control center, with provider users bound to company users before activation. This is the Business One IAM path, distinct from the separate Cloud Control Center product. Scope: SAP Business One 10.0 IAM documentation; verify the selected feature package, provider and client compatibility. Source: https://help.sap.com/docs/SAP_BUSINESS_ONE_IAM/548d6202b2b6491b824a488cfc447343/13c565324759468490589d60e6c75a92.html (reviewed 2026-11-20). Supporting source: Identity and authentication introduction — https://help.sap.com/docs/SAP_BUSINESS_ONE_IAM/548d6202b2b6491b824a488cfc447343/7f94c5836fad44e6a02322d39e229cc3.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Google Cloud guide provisions SAP HANA using its Terraform scale-up guide, then installs licensed SAP Business One using the SAP administrator guide. Infrastructure/HANA automation is not a complete Business One application installer; acquire and version-match SAP media and entitlements separately. Scope: Business One for SAP HANA on Google Cloud; not the SQL Server edition or an end-to-end HA template. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide (reviewed 2026-11-20). Supporting source: Planning and BYOL requirements — https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide.

- Minimum footprint / sizing: Sources checked — unresolved. The provider planning guide requires an SAP-certified HANA machine and workload-specific memory/storage sizing. Its 32-vCPU/834-GB disk performance example is not a universal Business One minimum, and the documented single-node architecture is not an HA design for the proposed workload. Scope: Business One 10.0 for SAP HANA on Google Cloud; CPU, memory, storage and redundancy require a selected certified configuration. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: SAP Business One (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAP Process Control (On-Premise)

Licensed SAP internal-control and policy lifecycle management application.

- Listing: https://launchinyourcloud.com/directory/sap-process-control/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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: SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs.
- 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.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.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 SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.

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

SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Licensed SAP internal-control and policy lifecycle management application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/netweaver-guides (checked 2026-11-19). 


### Cloud deployment evidence

- AWS SAP NetWeaver Guides (aws): https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html
  SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure SAP Planning Guide (azure): https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide
  SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP SAP NetWeaver Guides (gcp): https://docs.cloud.google.com/sap/docs/netweaver-guides
  SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS SAP NetWeaver Guides: https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html

- Azure SAP Planning Guide: https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide

- GCP SAP NetWeaver Guides: https://docs.cloud.google.com/sap/docs/netweaver-guides

- AWS Launch Wizard SAP: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html

- GCP Business Suite on HANA: https://docs.cloud.google.com/sap/docs/architectures/sap-business-suite-on-hana

- PC 12.0 SP27 Admin Guide PDF (2025-01-08): https://help.sap.com/doc/d83af7d22baa49829e464111338e9c12/12.0.27/en-US/loio60d658f576b6452eb0f943c04b354018_en.pdf

- PC 12.0 Master Guide PDF: https://help.sap.com/doc/3110c68ac50046cc8a035bfe348a9bc3/12.0.13/en-US/loio4570e559019f40a587bc3dce4fafbbbd_4570e559019f40a587bc3dce4fafbbbd_en.pdf

- SAP Process Control Course: https://learning.sap.com/courses/discovering-the-key-functionalities-of-sap-process-control

- SAP GRC for HANA 2026 PAM PDF: https://help.sap.com/doc/4d01ca92f5884240ab864b9ff08776a6/12.0.26/en-US/SAP%20GRC%20FOR%20HANA,%202026%20_PAM.pdf

- SAP On-Premise Variants: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

- SAP Security Notes (2026-11-10): https://support.sap.com/en/my-support/knowledge-base/security-notes-news.html

- SAP 2040 Maintenance Commitment: https://support.sap.com/en/release-upgrade-maintenance/maintenance-information/maintenance-strategy/s4hana-business-suite7.html

### Licensing sources

- https://help.sap.com/doc/4d01ca92f5884240ab864b9ff08776a6/12.0.26/en-US/SAP%20GRC%20FOR%20HANA,%202026%20_PAM.pdf

- https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Infrastructure sources

- https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html

- https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide

- https://docs.cloud.google.com/sap/docs/netweaver-guides


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed deployment and Process Control material does not establish the selected GRC portal/UI and its actual SSO configuration. NetWeaver or SAP workforce identity features alone do not confirm the complete customer-managed Process Control user login path. Scope: SAP Process Control selected-release user identity remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. AWS Launch Wizard automates supported SAP NetWeaver platform landscapes and customer-supplied installation media, including distributed and HA patterns. This provisions the underlying platform, not the Process Control application configuration. Verify GRC/NetWeaver/database compatibility, licences and application installation separately. Scope: SAP Process Control parent-platform infrastructure automation; GRC application delivery is separate. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21). Deployment artifact: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html. Artifact reference: Current AWS Launch Wizard SAP guide.

- Minimum footprint / sizing: Sources checked — unresolved. Provider deployment patterns require input sizing and do not establish GRC Process Control production capacity. Obtain supported application/database memory, concurrent control/test workflows, batch jobs, data growth and HA requirements for the selected release. Scope: SAP Process Control workload sizing remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- License pricing: Sources checked — unresolved. The master guide identifies the Process Control 12.0 add-on and separately licensed Risk Management and Access Control products, but does not establish the selected customer licence or pricing. The GRC for HANA 2026 roadmap is a different scope. Scope: Selected self-managed application or customer-cloud service; contract confirmation required. Source: https://help.sap.com/doc/3110c68ac50046cc8a035bfe348a9bc3/12.0.13/en-US/loio4570e559019f40a587bc3dce4fafbbbd_4570e559019f40a587bc3dce4fafbbbd_en.pdf (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAP S/4HANA EHS — Customer-Operated

Customer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.

- Listing: https://launchinyourcloud.com/directory/sap-s4hana-ehs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SAP S/4HANA on-premise licensing; verify EHS component entitlements
- Licensing model: commercial-only
- Installation: Install the licensed SAP S/4HANA on-premise edition and configure the selected EHS components using SAP implementation guides
- Architecture: SAP S/4HANA application stack with SAP HANA database and EHS Fiori applications
- Operations: Customer manages the application and database infrastructure, installation, upgrades, access, backups and EHS configuration; agree implementation and support arrangements.
- Product website: https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The on-premise edition is explicitly customer-installed and customer-operated. This entry covers its EHS components, not SAP-managed Cloud Private Edition or Public Edition. Check the selected release, component entitlements and implementation scope. Environmental reporting still requires configured requirements and reliable source data.

The listed on-premise edition uses SAP commercial software licensing. The official deployment comparison describes its perpetual-license model; the customer agreement defines the exact component rights.

Customer-operated SAP application and HANA database services run on provisioned infrastructure. This is the on-premise edition, separate from SAP-managed cloud services.


### Category fit

- energy-environmental-compliance: Environmental requirements, emissions calculations, compliance scenarios, deviations and reports for environmental authorities.

- incident-investigation-management: Safety incident and near-miss capture, investigations, root-cause classifications and follow-up actions. This is industrial EHS scope, rather than a general legal investigation platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp (checked 2026-11-12). 


### Cloud deployment evidence

- Customer-provided SAP S/4HANA deployment on AWS (aws): https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html
  AWS Launch Wizard provisions customer resources and can install customer-provided SAP S/4HANA software. Evidence covers the underlying S/4HANA platform; confirm EHS licensing, supported sizing, database and SAP release before deployment.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- SAP S/4HANA infrastructure deployment on Azure (azure): https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana
  Microsoft documents S/4HANA infrastructure in a customer Azure subscription. Evidence covers the platform hosting option; confirm EHS modules, SAP licensing, supported operating systems and software installation separately.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- SAP S/4HANA reference architecture on Google Cloud (gcp): https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp
  Google documents S/4HANA on SAP-certified Compute Engine infrastructure. This is platform hosting evidence; EHS functionality, licenses and supported SAP configurations still require confirmation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Customer-operated on-premise installation and operations: https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest

- Environment Management scope: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/1b3596cc5dd5428d887966a4193ddc29/6d08555321d77d77e10000000a441470.html

- Current incident-investigation configuration: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/f5d3e1005efd4e86acf9a65abf428082/96e81bbdc3c54a70b3b374b182bb87c0.html?locale=en-US&version=2025.000

- Commercial model and deployment responsibilities: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Licensing sources

- https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Infrastructure sources

- https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest


### 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. The reviewed EHS and deployment material does not establish the selected application UI, release and complete identity configuration. SAP platform authentication options require the actual Fiori/ABAP/GUI entry points and compatible identity components; do not infer a ready EHS federation setup from a generic SAP capability. Scope: Customer-operated S/4HANA EHS identity deployment remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. AWS Launch Wizard can provision SAP landscapes and install customer-provided supported S/4HANA software, including separate multi-instance/HA patterns. Supply licensed installation media and validate supported releases. This is underlying S/4HANA platform automation; EHS activation, business configuration and data migration remain separate. Scope: Provider-documented S/4HANA deployment supporting the EHS parent platform; not a packaged EHS solution. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21). Deployment artifact: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html. Artifact reference: Current AWS Launch Wizard supported SAP deployment guide.

- Minimum footprint / sizing: Sources checked — unresolved. Launch Wizard selects resources from supplied SAP requirements; it does not establish an EHS-specific capacity baseline. Obtain certified S/4HANA/HANA sizing for application/database memory, batch/analytics, data volume and HA rather than interpreting supported maximum memory as a minimum. Scope: S/4HANA EHS workload sizing remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- License pricing: Documented. SAP distinguishes customer-managed S/4HANA on-premise perpetual licensing from subscription-based Private Edition with SAP technical managed services. Do not substitute a cloud subscription for the customer-operated scope; EHS module rights and implementation pricing require the actual agreement. Scope: S/4HANA on-premise deployment model; not a module-specific EHS quote. Source: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5 (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAS Viya Platform

Commercial analytics and AI platform deployed into a customer-operated managed Kubernetes cluster.

- Listing: https://launchinyourcloud.com/directory/sas-viya-platform/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SAS Viya licensing; deployment assets and a JWT license are delivered for the customer's software order.
- Licensing model: commercial-only
- Installation: Provision EKS, AKS or GKE with SAS Terraform projects, then deploy Kubernetes manifests generated through Kustomize and SAS automation
- Architecture: Customer-operated EKS, AKS or GKE cluster running SAS Viya containers, CAS, PostgreSQL integrations and persistent storage.
- Operations: Customer manages Kubernetes, networking, ingress, storage, PostgreSQL, identity, sizing, backups, platform updates and licensed deployment assets.
- Product website: https://www.sas.com/en_us/software/viya.html
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

The public SAS infrastructure repositories are Apache-licensed deployment tooling; SAS Viya itself is commercial software and requires licensed order assets and a JWT license. Kubernetes and PostgreSQL are mandatory. SAS states that its infrastructure-as-code projects satisfy most, not all, deployment requirements. The viya4-deployment project can patch the same manifest but does not move an installation to a different cadence, version or software offering. SAS November bulletins cover compromised eMudhra certificates and critical Brotli CVE-2026-111497 across specified Viya branches. Use the vendor matrices to identify the exact affected component and fixed maintenance level; do not treat a generic Viya version as sufficient.

SAS Viya requires a commercial order, licensed deployment assets and a JWT license. Apache licenses on the public infrastructure repositories apply to tooling, not the Viya product distribution.

SAS Viya runs persistent container workloads on managed Kubernetes with CAS compute, shared storage and PostgreSQL. Terraform projects provision customer infrastructure but do not complete the application deployment.


### Category fit

- data-analytics: Enterprise data preparation, analytics, reporting and decisioning delivered by the customer-operated Viya platform.

- ai-tools: Model development, machine learning, model management and AI operationalization; exact products depend on the licensed order.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/sassoftware/viya4-iac-aws (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/sassoftware/viya4-iac-azure (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/sassoftware/viya4-iac-gcp (checked 2026-11-17). 


### Cloud deployment evidence

- SAS Viya infrastructure on AWS (aws): https://github.com/sassoftware/viya4-iac-aws
  Official SAS Terraform provisions customer AWS resources including EKS, storage and optional RDS, after which the customer deploys licensed Viya assets.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SAS Viya infrastructure on Azure (azure): https://github.com/sassoftware/viya4-iac-azure
  Official SAS Terraform provisions customer Azure resources including AKS, storage and optional PostgreSQL, after which the customer deploys licensed Viya assets.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SAS Viya infrastructure on Google Cloud (gcp): https://github.com/sassoftware/viya4-iac-gcp
  Official SAS Terraform provisions customer Google Cloud resources including GKE, storage and optional Cloud SQL, after which the customer deploys licensed Viya assets.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Introduction to SAS Viya Platform: https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en

- SAS Viya Platform system requirements: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en

- AWS infrastructure as code: https://github.com/sassoftware/viya4-iac-aws

- Azure infrastructure as code: https://github.com/sassoftware/viya4-iac-azure

- Google Cloud infrastructure as code: https://github.com/sassoftware/viya4-iac-gcp

- SAS Viya deployment automation: https://github.com/sassoftware/viya4-deployment

- How to buy SAS Viya: https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html

- SAS compromised eMudhra certificates bulletin: https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html

- SAS Brotli CVE-2026-111497 bulletin: https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html

### Licensing sources

- https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en

- https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html

### Infrastructure sources

- https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en

- https://github.com/sassoftware/viya4-deployment


### 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. SAS documents buying Viya through cloud marketplaces and specifically links Microsoft Marketplace. Select the matching packaged offering and delivery/entitlement terms; this is not proof every Marketplace offer matches a Terraform-based licensed deployment. Scope: Viya software procurement; offering selection required. Source: https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The purchasing page links packaged Viya offerings, but does not establish qualifying charges for this licensed platform deployment under the buyer cloud agreement. Workbench is separate. Scope: Reviewed public evidence for SAS Viya Platform; unresolved within this edition/deployment. Source: https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html (reviewed 2026-11-17).

- Single sign-on: Documented. Viya documents SAML and OIDC web SSO. Configure a compatible identity provider and matching certificates; this is distinct from user provisioning. Scope: Reviewed SAS Viya platform requirements; web authentication; reviewed 2025.10 requirements. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- SCIM provisioning: Documented. Viya supports SCIM 2.0, tested with Okta and Entra ID. Disable LDAP when using SCIM; SAML/OIDC, HTTPS, a public-CA certificate and inbound IdP access are required. Google Identity provisioning is not supported in this reviewed configuration. Scope: Viya SCIM requirements; selected identity configuration; reviewed 2025.10 requirements. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SAS Viya Platform 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://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- Security controls: Documented. The requirements separate service/user accounts, elevated deployment permissions, TLS/identity and database dependencies. Apply the selected platform security configuration; a reference to a security standard is not an independent deployment attestation. Current advisory review: SAS bulletins address compromised eMudhra certificates and critical Brotli CVE-2026-111497 in specified Viya components and branches. Apply the exact fixed maintenance level for each affected component and review certificate trust. Scope: Viya installation security prerequisites; reviewed 2025.10 requirements Affected and fixed maintenance levels vary by Viya component and branch; consult both vendor matrices.. Source: https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en. Supporting source: Brotli CVE-2026-111497 bulletin — https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html.

- Air-gapped operation: Edition-dependent. The reviewed 2025.10 guide documents air-gapped deployment using SAS Mirror Manager: download entitled content outside the isolated network, transfer it and populate an internal registry without contacting the SAS entitlement/container services. Match the order assets, cadence and component dependencies. Scope: SAS Viya 2025.10 air-gapped deployment procedure; confirm compatibility with the purchased cadence assets. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/dplyml0phy0dkr/content/dplyml0phy0dkr.pdf?locale=en (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. SAS publishes Terraform for AWS infrastructure and separate deployment automation for the licensed Viya manifests. Pin a compatible tooling revision and SAS order assets; the Apache-licensed automation does not license the application. Scope: SAS-owned AWS IaC repository. Source: https://github.com/sassoftware/viya4-iac-aws (reviewed 2026-11-17). Deployment artifact: https://github.com/sassoftware/viya4-iac-aws. Artifact reference: default branch (moving; select a compatible release). Supporting source: Viya deployment automation — https://github.com/sassoftware/viya4-deployment.

- Minimum footprint / sizing: Documented. Sizing depends on licensed workloads, CAS/compute roles, Kubernetes node pools, storage bandwidth and PostgreSQL. The requirements include provider-specific sizing; 100 users and 1 TB alone do not determine a supported HA cluster. Scope: SAS Viya platform and workload-specific sizing; reviewed 2025.10 requirements. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- License pricing: Documented. SAS Viya requires a commercial order, licensed deployment assets and a JWT license. Apache licenses on the public infrastructure repositories apply to tooling, not the Viya product distribution. Scope: SAS Viya Platform: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Choose the licensed Viya modules/cadence, CAS/compute pools, data-in-memory requirements, HA services and storage throughput. The order-specific topology and commercial licence price are not public. 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://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. SAS publishes monthly Stable releases and Long-Term Support releases about every six months, aggregating prior Stable changes. Obtain deployment assets for the purchased order and cadence; automation repository tags are not Viya application releases. Scope: Viya platform cadence policy; exact order/version assets remain separate. Source: https://documentation.sas.com/api/collections/itopscdc/v_066/docsets/itopscon/content/itopscon.pdf?locale=en (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- SAS Viya November 2026 certificate and Brotli bulletins (security-advisory): SAS bulletins address compromised eMudhra certificates and critical Brotli CVE-2026-111497 in specified Viya components and branches. Scope: Affected and fixed maintenance levels vary by Viya component and branch; consult both vendor matrices. Conditions: Bundled trust stores, certificates, and Brotli-using components determine exposure. Action: Apply the exact fixed maintenance level for each affected component and review certificate trust. Source: https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html; reviewed 2026-11-18. Supporting source: Brotli CVE-2026-111497 bulletin — https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html.




## ScyllaDB Enterprise Self-Managed

Self-managed distributed NoSQL database deployed on customer-controlled cloud virtual machines.

- Listing: https://launchinyourcloud.com/directory/scylladb-enterprise-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: ScyllaDB Source Available License Agreement for current Enterprise releases; eligibility and capacity limits apply unless covered by paid terms.
- Licensing model: source-available
- Installation: Official cloud image/AMI, with a documented AWS CloudFormation cluster example
- Architecture: Customer-operated ScyllaDB nodes with cloud networking and local or attached persistent storage
- Operations: Customer manages topology, networking, authentication, capacity, backups, monitoring, patching and upgrades.
- Product website: https://www.scylladb.com/product/scylla-enterprise/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current stable documentation covers ScyllaDB 2026.3 and labels each provider path self-managed, separately from ScyllaDB Cloud. The source-available license is not OSI open source; its free grant has eligibility and aggregate capacity limits, and commercial customers require paid terms.

Current ScyllaDB Enterprise is source-available under ScyllaDB's agreement, not an OSI-approved license. The agreement imposes eligibility, usage and commercial-customer restrictions.

The database runs directly on customer-controlled cloud compute instances; multi-node durability, storage layout and replication are customer-operated.


### Category fit

- databases-vector: Distributed NoSQL wide-column database for high-throughput, low-latency application data.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-azure.html (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html (checked 2026-11-19). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html (checked 2026-11-19). 


### Cloud deployment evidence

- Self-managed ScyllaDB 2026.3 on AWS (aws): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html
  Official instructions launch ScyllaDB AMIs into the customer's AWS VPC and distinguish this self-managed deployment from ScyllaDB Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on Google Cloud (gcp): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html
  Official instructions use the customer's active Google Cloud account and gcloud to launch ScyllaDB images and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on Azure (azure): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-azure.html
  Official instructions use the customer's Azure subscription and resource group to create a ScyllaDB VM and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on OCI (oci): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html
  Official instructions deploy the bring-your-own-license ScyllaDB Marketplace image into the customer's OCI tenancy, compartment, VCN and compute instance and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.


### Sources

- Install ScyllaDB 2026.3: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/

- ScyllaDB Enterprise self-managed product: https://www.scylladb.com/product/

- Supported ScyllaDB versions: https://docs.scylladb.com/stable/versioning/version-support.html

- ScyllaDB Source Available License Agreement: https://www.scylladb.com/scylladb-software-license-agreement/

- Buyer evidence: marketplace: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html

- Buyer evidence: commitments: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html

- Reviewed deployment artifact reference: https://s3.amazonaws.com/downloads.scylladb.com/downloads/scylla/aws/cloudformation/scylla_cluster_2026.3.6_x86_64.yaml

- Buyer evidence: footprint: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html

- Source-available licensing FAQ: https://www.scylladb.com/source-available-faq/

### Licensing sources

- https://www.scylladb.com/scylladb-software-license-agreement/

- https://www.scylladb.com/source-available-faq/

### Infrastructure sources

- https://docs.scylladb.com/manual/stable/getting-started/install-scylla/


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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. ScyllaDB documents a bring-your-own-license Marketplace image for self-managed Enterprise deployment in OCI. The other reviewed cloud paths use vendor images or instructions and do not establish equivalent Marketplace offers. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html (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: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (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: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- Security controls: Edition-dependent. The provider guides deploy customer-controlled database nodes and networking. The buyer must explicitly configure authentication, encryption, firewall rules, monitoring, backup and repair; image delivery alone is not a hardened cluster baseline. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- 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: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The AWS guide links a versioned x86 CloudFormation cluster example for 2026.3.6. It provisions EC2 networking and cluster resources and accepts a regional Scylla AMI. Review its public-address/SSH settings, initial credentials, instance count and licence limits; this sample is not a validated production HA or cost design. Scope: AWS x86 sample stack; ARM templates and other providers have separate images and configuration. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19). Deployment artifact: https://s3.amazonaws.com/downloads.scylladb.com/downloads/scylla/aws/cloudformation/scylla_cluster_2026.3.6_x86_64.yaml. Artifact reference: scylla_cluster_2026.3.6_x86_64.yaml; SHA-256 71c636562d0e5ea54633ba4c0f95a32a1db139726a46923c2372e6550cfb6c7c.

- Minimum footprint / sizing: Documented. The GCP image launch guide requires at least 2 vCPUs. This bootstrap requirement does not establish production node count, RAM, local SSD capacity, HA, replication, compaction or a 1-TB workload design; follow provider-specific sizing and licence limits separately. Scope: ScyllaDB 2026.3 GCP image launch minimum only; not a cluster-wide production footprint. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html (reviewed 2026-11-19).

- License pricing: Edition-dependent. The current source-available agreement provides a restricted free grant subject to eligibility and aggregate capacity limits; commercial customers and use beyond those terms require a paid agreement. Validate legal eligibility and capacity calculations. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://www.scylladb.com/scylladb-software-license-agreement/ (reviewed 2026-11-19). Supporting source: Source-available licensing FAQ — https://www.scylladb.com/source-available-faq/.

- 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: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The current stable self-managed installation documentation is labeled ScyllaDB 2026.3. Verify the exact patch and its support window before deploying provider images or performing an upgrade. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).







## SeedDMS

Self-hosted document repository with versions, approval workflows and access controls.

- Listing: https://launchinyourcloud.com/directory/seeddms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed SeedDMS 6.0 branch; separately licensed extensions require their own review.
- Licensing model: open-source
- Installation: VM image
- Architecture: SeedDMS 6 application, database and persistent documents in a cloudimg Azure VM.
- 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.microsoft.com/en-gb/product/cloudimg1647283583153.seeddms-ubuntu-24-04
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The third-party package and upstream SeedDMS release line have separate maintenance. Licence terms and bundled libraries must be checked for the selected package.

GNU GPL-2.0 for the reviewed SeedDMS 6.0 branch; separately licensed extensions require their own review.

SeedDMS 6 application, database and persistent documents in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted document repository with versions, approval workflows and access controls.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.seeddms-ubuntu-24-04
  SeedDMS 6 application, database and persistent documents in a cloudimg Azure VM. The third-party package and upstream SeedDMS release line have separate maintenance. Licence terms and bundled libraries must be checked for the selected package.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The project’s public discussion archive records maintainer Uwe Steinmann and community contributors diagnosing notification bugs and discussing patches and the Codeberg migration in July 2026. This is evidence of an active user/contributor community, rather than a production-support guarantee.

Reviewed 2026-11-19.

- SeedDMS maintainer and community technical discussion: https://sourceforge.net/p/seeddms/mailman/seeddms-discuss/

- SeedDMS project and user reports: https://sourceforge.net/projects/seeddms/

### Sources

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

- SeedDMS About: https://www.seeddms.org/

- Codeberg GPL-2.0 LICENSE: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-5.1.x/LICENSE

- SeedDMS Download (6.0.42): https://www.seeddms.org/download/

- SeedDMS Changelog: https://www.seeddms.org/changelog/

- SeedDMS RSS (2026-10): https://www.seeddms.org/index.xml

- Codeberg Repo (2026-11): https://codeberg.org/seeddms

- Selected edition licence text: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/LICENSE

### Licensing sources

- https://www.seeddms.org/

- https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-5.1.x/LICENSE

- https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The official download page points to externally maintained OpenID Connect and ForwardAuth extensions and directs support to their developers. This establishes possible extension paths, but not core-native federation, current 6.0 compatibility or a supported marketplace-image configuration. Confirm those details before relying on SSO. Scope: Third-party extension pointers; selected-release federation support unresolved. Source: https://www.seeddms.org/download/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project publishes a 6.0 source branch with Composer/Phing packaging instructions and links installable distributions from its official download page. This is a PHP application distribution, not a public cloud provisioning template. Keep repository data and configuration outside the public web root and select a supported package. Scope: Upstream 6.0 application build/distribution. Source: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/README.md (reviewed 2026-11-20). Deployment artifact: https://www.seeddms.org/download/. Artifact reference: 6.0 release line; choose the versioned distribution. Supporting source: Official download options — https://www.seeddms.org/download/.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed official 6.0 source/build and distribution pages do not establish a validated CPU/RAM minimum or HA topology. Size the PHP application, database, document storage and extraction/preview processes together; a PHP package download is not production sizing. Scope: Upstream 6.0 distribution; numeric production sizing unresolved. Source: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/README.md (reviewed 2026-11-20). Supporting source: Distribution and extension scope — https://www.seeddms.org/download/.

- License pricing: Documented. GNU GPL-2.0 for the reviewed SeedDMS 6.0 branch; separately licensed extensions require their own review. Scope: SeedDMS; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SharePoint Server Subscription Edition

Commercial collaboration, content and document management server farm deployed on customer-operated Microsoft Azure infrastructure.

- Listing: https://launchinyourcloud.com/directory/sharepoint-server-subscription-edition/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Server/CAL licensing; Subscription Edition requires active Software Assurance or a subscription license.
- Licensing model: commercial-only
- Installation: Install Microsoft media on Windows Server Azure virtual machines, then configure the farm with the configuration wizard or PowerShell
- Architecture: Customer-operated Windows Server farm with Active Directory and SQL Server or Azure SQL Managed Instance.
- Operations: Customer manages Windows and SharePoint servers, identity, SQL, load balancing, certificates, search, storage, backups, patching and availability.
- Product website: https://learn.microsoft.com/en-us/sharepoint/sharepoint-server
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers SharePoint Server Subscription Edition, not SharePoint Online or Microsoft 365. It is a manually installed farm rather than an Azure-managed SaaS or one-click service. Azure SQL Database other than Managed Instance and SQL Server Express are unsupported for SharePoint databases. Windows Server, SQL Server and supporting Azure resources have separate licensing and costs; enterprise functionality can require additive Enterprise CALs. Monthly Public Update builds are supported for one year. The November 10, 2026 update brings SharePoint Server Subscription Edition to build 16.0.20326.20278 and fixes multiple RCE, elevation, disclosure, spoofing, and bypass CVEs. Workflow Manager requires KB5002799; SharePoint 2010 workflows and InfoPath Forms Services are removed July 13, 2027, after InfoPath support ended July 14, 2026.

SharePoint Server uses commercial Server/CAL terms. Subscription Edition entitlement requires active Software Assurance or subscription licensing; Windows Server, SQL Server and additive Enterprise CAL entitlements are separate where applicable.

SharePoint Server Subscription Edition runs on Windows Server virtual machines with persistent database, identity and supporting services. Production generally uses a multi-server farm.


### Category fit

- document-management: Document libraries, metadata, content types, versioning, workflows, governance and retention on a customer-operated farm.

- collaboration: Sites, shared content and team collaboration capabilities delivered by the self-managed product.

- content-management: Authoring, publishing and managing intranet and site content in a self-managed farm.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-farm-in-azure (checked 2026-11-17). 


### Cloud deployment evidence

- SharePoint Server Subscription Edition farms on Azure IaaS (azure): https://learn.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-farm-in-azure
  Microsoft documents development/test, disaster-recovery and production SharePoint Server farms on Azure virtual machines, and the page applies to Subscription Edition. This is customer-operated IaaS, not SharePoint Online.
  Source type: provider-guide; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Designing a SharePoint Server farm in Azure: https://learn.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-farm-in-azure

- Deploy SharePoint Server with Azure SQL Managed Instance: https://learn.microsoft.com/en-us/sharepoint/administration/deploy-azure-sql-managed-instance-with-sharepoint-servers

- SharePoint Server in Microsoft Azure: https://learn.microsoft.com/en-us/sharepoint/administration/sharepoint-server-in-microsoft-azure

- Subscription Edition installation overview: https://learn.microsoft.com/en-us/sharepoint/install/install-overview-spserver-se

- SharePoint Server licensing guidance: https://www.microsoft.com/licensing/guidance/SharePoint-Server

- SharePoint Server Product Terms: https://www.microsoft.com/licensing/terms/productoffering/SharePointServer/MPSA

- Document management in SharePoint Server: https://learn.microsoft.com/en-us/sharepoint/governance/document-management-in-sharepoint-server

- SharePoint Server servicing policy: https://learn.microsoft.com/en-us/sharepoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-server-se

- SharePoint Server Subscription Edition November 2026 update KB5002945: https://support.microsoft.com/en-us/servicing/office/hotfix/sharepoint/5002945

### Licensing sources

- https://www.microsoft.com/licensing/guidance/SharePoint-Server

- https://www.microsoft.com/licensing/terms/productoffering/SharePointServer/MPSA

### Infrastructure sources

- https://learn.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-farm-in-azure

- https://learn.microsoft.com/en-us/sharepoint/install/install-overview-spserver-se


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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 licensed Server/farm installation is documented, but a current first-party Marketplace offer delivering Subscription Edition was not established. Microsoft 365 offers are a different product. Scope: Reviewed public evidence for SharePoint Server Subscription Edition; unresolved within this edition/deployment. Source: https://www.microsoft.com/licensing/guidance/SharePoint-Server (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Server licences/CALs and separately billed Azure resources do not establish that SharePoint software spend counts toward a cloud commitment. Scope: Reviewed public evidence for SharePoint Server Subscription Edition; unresolved within this edition/deployment. Source: https://www.microsoft.com/licensing/guidance/SharePoint-Server (reviewed 2026-11-17).

- Single sign-on: Documented. Subscription Edition supports OIDC 1.0 through a trusted identity-token issuer. Microsoft documents an Entra ID setup; Windows and claims-based authentication alternatives have different configuration requirements. Scope: SharePoint Server Subscription Edition, not SharePoint Online. Source: https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/oidc-1-0-authentication (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The Server OIDC guide establishes federation, not a SCIM service. SharePoint Online/Entra provisioning evidence cannot be transferred to Subscription Edition. Scope: Reviewed public evidence for SharePoint Server Subscription Edition; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/oidc-1-0-authentication (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SharePoint Server Subscription Edition 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://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/set-up-oidc-auth-in-sharepoint-server-with-msaad (reviewed 2026-11-17).

- Security controls: Documented. Configure the trusted OIDC issuer and farm properties for the selected server update level. Identity-provider access, certificates and SharePoint authorization remain separate customer responsibilities. Current advisory review: Build 16.0.20326.20278 fixes multiple remote-code-execution, elevation, information-disclosure, spoofing, and security-bypass CVEs. Apply KB5002945 with its prerequisites and plan migration from SharePoint 2010 workflows and InfoPath Forms Services before July 13, 2027. Scope: Subscription Edition identity trust and certificates SharePoint Server Subscription Edition November 10, 2026 update KB5002945.. Source: https://support.microsoft.com/en-us/servicing/office/hotfix/sharepoint/5002945 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/set-up-oidc-auth-in-sharepoint-server-with-msaad.

- Air-gapped operation: Sources checked — unresolved. The Server installation overview does not establish a complete isolated prerequisite, activation, identity and monthly-update workflow. Azure deployment alone is not evidence of isolation. Scope: Reviewed public evidence for SharePoint Server Subscription Edition; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/sharepoint/install/install-overview-spserver-se (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The vendor documents installation media, prerequisite installation and farm configuration with supported Windows/SQL components. Azure deployment is customer-managed IaaS; the evidence is not a one-click Marketplace farm. Scope: Subscription Edition installation workflow. Source: https://learn.microsoft.com/en-us/sharepoint/install/install-overview-spserver-se (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Microsoft publishes separate minimum CPU, memory and disk requirements for development, evaluation and production farm roles. Database hosts and additional farm roles must be sized separately; a development single-server example does not establish HA capacity. Scope: Subscription Edition role/topology sizing matrix. Source: https://learn.microsoft.com/en-us/sharepoint/install/hardware-and-topology-requirements-for-sharepoint-server-subscription-editon (reviewed 2026-11-17).

- License pricing: Documented. SharePoint Server uses commercial Server/CAL terms. Subscription Edition entitlement requires active Software Assurance or subscription licensing; Windows Server, SQL Server and additive Enterprise CAL entitlements are separate where applicable. Scope: SharePoint Server Subscription Edition: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.microsoft.com/licensing/guidance/SharePoint-Server (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Only Azure deployment is confirmed here. Obtain the farm-role topology, Server/CAL/Windows/SQL licences and Azure region; no AWS farm support is inferred. 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://learn.microsoft.com/en-us/sharepoint/install/hardware-and-topology-requirements-for-sharepoint-server-subscription-editon (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The November 10, 2026 update is build 16.0.20326.20278 and includes security fixes. Workflow Manager requires KB5002799, and SharePoint 2010 workflows plus InfoPath Forms Services are scheduled for removal July 13, 2027. Scope: SharePoint Server Subscription Edition. Source: https://support.microsoft.com/en-us/servicing/office/hotfix/sharepoint/5002945 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- SharePoint Server Subscription Edition November 2026 security update (security-advisory): Build 16.0.20326.20278 fixes multiple remote-code-execution, elevation, information-disclosure, spoofing, and security-bypass CVEs. Scope: SharePoint Server Subscription Edition November 10, 2026 update KB5002945. Conditions: Installed components and the individual CVE prerequisites determine applicability. Workflow Manager requires KB5002799. Action: Apply KB5002945 with its prerequisites and plan migration from SharePoint 2010 workflows and InfoPath Forms Services before July 13, 2027. Source: https://support.microsoft.com/en-us/servicing/office/hotfix/sharepoint/5002945; reviewed 2026-11-18.




## Siemens Teamcenter (Quality & Document Control)

Commercial product-lifecycle platform with controlled technical documents and quality-management options.

- Listing: https://launchinyourcloud.com/directory/siemens-teamcenter/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: Customer Azure Teamcenter client, web, enterprise and resource tiers with supported database/storage services.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Microsoft documents the complete Azure application architecture, including multi-zone storage choices. Generic quality and technical-document features do not establish a ready-made clinical-regulatory or medical-device validation solution.

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

Customer Azure Teamcenter client, web, enterprise and resource tiers with supported database/storage services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial product-lifecycle platform with controlled technical documents and quality-management options.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline (checked 2026-11-19). 


### Cloud deployment evidence

- Azure Baseline (azure): https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline
  Customer Azure Teamcenter client, web, enterprise and resource tiers with supported database/storage services. Microsoft documents the complete Azure application architecture, including multi-zone storage choices. Generic quality and technical-document features do not establish a ready-made clinical-regulatory or medical-device validation solution.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure Baseline: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline

- Azure NetApp: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-plm-netapp-files

- Quality & Compliance: https://plm.sw.siemens.com/en-US/teamcenter/solutions/quality-compliance-management/

- Document Mgmt: https://plm.sw.siemens.com/en-US/teamcenter/solutions/document-management/

- Siemens Software Terms: https://www.siemens.com/en-us/company/customer-partner-terms/sw-terms/

- Teamcenter Blog: https://blogs.sw.siemens.com/teamcenter/

### Licensing sources

- https://www.siemens.com/en-us/company/customer-partner-terms/sw-terms/

### Infrastructure sources

- https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline


### 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: Documented. Microsoft's customer-managed Teamcenter architecture documents application SSO through Microsoft Entra ID using SAML and Teamcenter Security Services. This is a configured Teamcenter integration, not merely Azure control-plane IAM. Validate the selected Teamcenter/TCSS release and identity topology. Scope: Teamcenter application and Active Workspace/rich-client architecture on Azure; provider-documented integration, not a vendor support entitlement. Source: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The provider architecture explains Teamcenter infrastructure and discusses infrastructure automation, but does not identify a complete public Teamcenter application installer or end-to-end version-matched IaC bundle. Licensed Teamcenter/TCSS components and their installation sequence still require the appropriate Siemens release media and guidance. Scope: Teamcenter customer-managed Azure application deployment artifacts; ARM/storage automation alone is not the product installer. Source: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline (reviewed 2026-11-20).

- Minimum footprint / sizing: Sources checked — unresolved. The provider guidance separates web, enterprise, database, file-management and visualization roles and recommends application sizing with an Azure architect. It does not establish a quantitative whole-stack floor for the selected Teamcenter/quality/document-control workload. Size compute, database and file I/O together. Scope: Teamcenter PLM on Azure; architecture, storage throughput and VM-family recommendations are not a validated 100-user HA sizing profile. Source: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-plm-netapp-files (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Siemens Teamcenter (Quality & Document Control); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.siemens.com/en-us/company/customer-partner-terms/sw-terms/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SigNoz Self-Hosted

OpenTelemetry-based application observability platform for traces, metrics and logs.

- Listing: https://launchinyourcloud.com/directory/signoz/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Expat for core code; ee/ enterprise code has its own separate license.
- Licensing model: open-source
- Installation: Use the supported Foundry workflow to generate and run the Docker Compose stack; the older bundled install script/deploy files are deprecated.
- Architecture: Customer-operated observability services, OpenTelemetry collection and persistent analytical storage
- Operations: Customer manages collectors, storage capacity, retention, authentication, backups, alert API and operator migrations, and platform upgrades.
- Product website: https://signoz.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

The reviewed guide is explicitly for self-hosted Community without a license. Commercial features require their stated terms. Instrumentation can capture sensitive payloads, so configure capture and retention according to the data being monitored. SigNoz v0.150.0 automatically migrates stored alert rules to v2alpha1 but removes the v1 rule APIs and GET /api/v2/rules. Update API scripts, move Terraform configurations from signoz_alert to signoz_rule, use SigNoz Operator v0.0.5 or newer, and back up the metastore before upgrading. The release also begins dual-ingesting log bodies into native JSON storage; plan additional collector, ClickHouse, and log-disk capacity before rollout.

MIT Expat for core code; ee/ enterprise code has its own separate license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated observability services, OpenTelemetry collection and persistent analytical storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. From v0.150.0, log bodies are dual-ingested during migration. The vendor recommends 25% OpenTelemetry Collector CPU and memory headroom, 15% ClickHouse CPU headroom, and log-disk growth approximately equal to the existing body column.


### Category fit

- observability: Application observability over OpenTelemetry traces, metrics and logs; applications must be instrumented and collection configured.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://signoz.io/docs/install/kubernetes/aws/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://signoz.io/docs/install/kubernetes/aks/ (checked 2026-11-12). 

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


### Cloud deployment evidence

- SigNoz self-hosting on Amazon EKS (aws): https://signoz.io/docs/install/kubernetes/aws/
  Official self-hosting instructions install SigNoz and its storage components on Amazon EKS; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- SigNoz self-hosting on Azure Kubernetes Service (azure): https://signoz.io/docs/install/kubernetes/aks/
  Official self-hosting instructions install SigNoz and its storage components on Azure Kubernetes Service; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- SigNoz self-hosting on Google Kubernetes Engine (gcp): https://signoz.io/docs/install/kubernetes/gcp/
  Official self-hosting instructions install SigNoz and its storage components on Google Kubernetes Engine; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The active release stream records recent maintenance and multiple named contributors and first-time contributions across releases.

Reviewed 2026-11-10.

- Maintenance and community contributor credits: https://github.com/SigNoz/signoz/releases

- Public upstream project: https://github.com/SigNoz/signoz

### Sources

- Official installation and runtime: https://signoz.io/docs/install/docker/

- Upstream project and capabilities: https://github.com/SigNoz/signoz

- Current upstream license: https://raw.githubusercontent.com/SigNoz/signoz/develop/LICENSE

- SigNoz v0.150.0 breaking changes: https://github.com/SigNoz/signoz/releases/tag/v0.150.0

- SigNoz v0.150.0 alert-rule upgrade guide: https://signoz.io/docs/operate/migration/upgrade-0-150/

- SigNoz JSON log migration capacity guidance: https://signoz.io/guides/json-logs-migration/

### Licensing sources

- https://raw.githubusercontent.com/SigNoz/signoz/develop/LICENSE

### Infrastructure sources

- https://signoz.io/docs/install/docker/

- https://signoz.io/docs/operate/migration/upgrade-0-150/

- https://signoz.io/guides/json-logs-migration/


### 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 and OIDC require Enterprise Self-Hosted. Google Workspace OAuth2 is also documented for Community Edition. Login-time account creation is distinct from automated deprovisioning. Scope: Self-hosted SigNoz edition-specific protocols. Source: https://signoz.io/docs/manage/administrator-guide/sso/overview/ (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 supported Docker workflow uses Foundry to generate/manage the Compose deployment. The older install.sh and bundled deploy files are deprecated from v0.130.0; do not use them as the current installation artifact. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://signoz.io/docs/install/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The supported Foundry/Docker installation requires at least 4 GB allocated to Docker for its local stack. Production ingestion rate, ClickHouse/Keeper topology, retention and replicas can raise capacity substantially; this is an installation baseline, not a 1 TB HA telemetry sizing guarantee. Scope: Current supported Docker installation requirements; application, storage and collector roles require workload sizing. Source: https://signoz.io/docs/install/docker/ (reviewed 2026-11-20).

- License pricing: Documented. The v0.150.0 licence applies MIT terms to the core and explicitly excludes ee/ and cmd/enterprise/, which have separate Enterprise terms. Community source rights do not grant paid SAML/OIDC features or commercial support. Self-hosted licence, ingestion/storage infrastructure and SigNoz Cloud charges are separate. Scope: Published Community/Enterprise source boundary; not a hosted usage-price quote. Source: https://github.com/SigNoz/signoz/blob/v0.150.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v0.150.0, 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 SigNoz/signoz release record; commercial editions and deployment packages may differ. Source: https://github.com/SigNoz/signoz/releases/tag/v0.150.0 (reviewed 2026-11-14).







## SimpleRisk (with Vendor Risk Management Extra)

Self-hosted SimpleRisk with the separately licensed Vendor Risk Management Extra.

- Listing: https://launchinyourcloud.com/directory/simplerisk-vrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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: SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension.
- 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.simplerisk.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 listed supplier workflow requires the commercial Extra; the core project's open-source licence does not include it. An AWS image is a deployment path, not a guarantee that software spend counts toward a buyer's commitment.

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

SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- vendor-supplier-document-management: Self-hosted SimpleRisk with the separately licensed Vendor Risk Management Extra.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.simplerisk.com/kb/01-04-installing-on-cloud (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.simplerisk.com/kb/01-04-installing-on-cloud (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.simplerisk.com/kb/01-04-installing-on-cloud (checked 2026-11-19). 


### Cloud deployment evidence

- Cloud Install KB (AWS AMI) (aws, azure, gcp): https://support.simplerisk.com/kb/01-04-installing-on-cloud
  SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension. The listed supplier workflow requires the commercial Extra; the core project's open-source licence does not include it. An AWS image is a deployment path, not a guarantee that software spend counts toward a buyer's commitment.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Cloud Install KB (AWS AMI): https://support.simplerisk.com/kb/01-04-installing-on-cloud

- VRM Extra: https://www.simplerisk.com/extras/vendor-risk-management

- Pricing & Editions: https://www.simplerisk.com/pricing

- SimpleRisk 20261105-001 Release: https://www.simplerisk.com/product-releases/whats-new-simplerisk-20261105-001-release

- GitHub Releases: https://github.com/simplerisk/code/releases

### Licensing sources

- https://www.simplerisk.com/pricing

### Infrastructure sources

- https://support.simplerisk.com/kb/01-04-installing-on-cloud


### 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 Custom Authentication Extra adds SAML with provider metadata, trusted domain and mapped user type, alongside LDAP/AD. Licence/enable that Extra separately from Vendor Risk Management, configure the IdP and user lifecycle, and retain recovery access; base local login does not include the same identity integration. Scope: SimpleRisk SAML via separately enabled Custom Authentication Extra. Source: https://support.simplerisk.com/kb/custom-authentication-extra-installation-and-administration-guide (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 vendor documents Linux/cloud and Docker installation, with configuration, persistence and separately activated Extras. Select compatible base application/DB and licensed VRM/authentication components, then configure HTTPS, backups and updates; installing the base does not activate all Extras. Scope: SimpleRisk upstream Docker installation plus separately licensed Extras. Source: https://support.simplerisk.com/kb/01-03-installing-via-docker (reviewed 2026-11-21). Deployment artifact: https://support.simplerisk.com/kb/01-03-installing-via-docker. Artifact reference: Current vendor Docker installation guide.

- Minimum footprint / sizing: Documented. The system guide suggests small deployments at 1–2 vCPU/2 GB RAM/20 GB disk and mid-size deployments at 2–4 vCPU/4–8 GB/50–100 GB. Large programs separate database and web tiers with 4+ vCPU/8+ GB per tier. These workload examples require tuning for frameworks, imports, evidence, audit growth and HA. Scope: SimpleRisk current deployment-size starting points; not a fixed VRM/HA minimum. Source: https://support.simplerisk.com/kb/01-01-system-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: SimpleRisk (with Vendor Risk Management Extra); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.simplerisk.com/pricing (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Sitecore Experience Platform (XP)

Licensed Sitecore Experience Platform content and digital-experience application.

- Listing: https://launchinyourcloud.com/directory/sitecore-xp/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: Azure ARM deployment templates and separately licensed Sitecore packages
- Architecture: Sitecore Azure application topology, databases, search and licensed platform components.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The XP product and XM-only topology are separate. ARM template release 9.0.7 is a deployment-tool version, not Sitecore XP 10.5 or a licence for the application.

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

Sitecore Azure application topology, databases, search and licensed platform components. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Licensed Sitecore Experience Platform content and digital-experience application.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates (checked 2026-11-19). 


### Cloud deployment evidence

- Sitecore Azure Templates (azure): https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates
  Sitecore Azure application topology, databases, search and licensed platform components. The XP product and XM-only topology are separate. ARM template release 9.0.7 is a deployment-tool version, not Sitecore XP 10.5 or a licence for the application.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Sitecore Azure Templates: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates

- Sitecore 10.5 Azure Docs: https://doc.sitecore.com/xp/en/developers/105/sitecore-experience-manager/sitecore-on-azure.html

- Sitecore MSTC: https://www.sitecore.com/legal/master-subscription-terms-conditions

- Agreement Overview: https://www.sitecore.com/legal/agreement-overview

- ARM Templates 2026-08: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates/commits/master

### Licensing sources

- https://www.sitecore.com/legal/master-subscription-terms-conditions

- https://www.sitecore.com/legal/agreement-overview

### Infrastructure sources

- https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The versioned Sitecore Identity guide documents using Identity Server as a federation gateway to external providers such as Microsoft Entra/Azure AD. Configure the selected XP/Identity versions and client login surface; this does not establish universal SSO for every public application or module. Scope: Sitecore XP 10.4 Experience Manager Identity gateway; separately hosted modules may differ. Source: https://doc.sitecore.com/xp/en/developers/104/sitecore-experience-manager/use-the-sitecore-identity-server-as-a-federation-gateway.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 Sitecore Azure Quickstart repository supplies ARM templates with a version/product compatibility table. Select the matching XP topology and licensed deployment packages; the template repository license does not grant a Sitecore application license or certify a newer unsupported combination. Scope: Official Azure App Service ARM deployment templates; version/topology-specific. Source: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates (reviewed 2026-11-20). Deployment artifact: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates. Artifact reference: master (moving repository); select a template folder from the compatibility matrix.

- Minimum footprint / sizing: Sources checked — unresolved. The Azure deployment repository provides versioned templates and topology choices, but the reviewed material does not establish a single supported production CPU/RAM/storage floor for the selected XP/SQL/search/Identity combination. Obtain a matching role/SKU design and validate it against the workload and HA target. Scope: Version-specific XP cloud topology; quantitative production sizing remains open. Source: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates (reviewed 2026-11-20). Supporting source: Versioned Identity component configuration — https://doc.sitecore.com/xp/en/developers/104/sitecore-experience-manager/use-the-sitecore-identity-server-as-a-federation-gateway.html.

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Sitecore Experience Platform (XP); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.sitecore.com/legal/master-subscription-terms-conditions (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Snowplow CDI Private Managed Cloud

Vendor-managed behavioural event pipeline running in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/snowplow-private-managed-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial Private Managed Cloud plan with quote-based pricing.
- Licensing model: commercial-only
- Installation: Provide a dedicated AWS account, Azure subscription, or Google Cloud project and grant the permissions in the provider guide.
- Architecture: Pipeline VM or Kubernetes resources run in the customer's cloud and load events to the customer's warehouse or lake. Snowplow hosts the management console and APIs.
- Operations: Snowplow provisions, monitors, patches, and upgrades the pipeline. The customer supplies the cloud environment, access permissions, and data destination.
- Product website: https://snowplow.io/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-21; infrastructure review: 2026-11-21

### Scope and qualifications

Snowplow requires dedicated subnets and remote operational access. Certain restricted environments, including AWS GovCloud and Azure Government, are outside the documented support scope. Agree how to preserve schema and configuration records and revoke Snowplow's access at offboarding.

Commercial Private Managed Cloud plan with quote-based pricing.

Pipeline VM or Kubernetes resources run in the customer's cloud and load events to the customer's warehouse or lake. Snowplow hosts the management console and APIs.


### Category fit

- data-analytics: Collects, validates, enriches, and delivers behavioural event data to the customer's data warehouse or lake.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/ (checked 2026-11-21). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-azure/ (checked 2026-11-21). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-gcp/ (checked 2026-11-21). 

Operating responsibility: Snowplow operates, monitors and upgrades the pipeline in the customer's dedicated cloud environment. Snowplow hosts the management Console and APIs outside that data plane; the customer supplies the cloud account, permissions and warehouse or lake. Source: https://docs.snowplow.io/docs/get-started/deployment-options/ (checked 2026-11-21). Supporting source: Operational access and deployment restrictions — https://docs.snowplow.io/restrictive-access-models/.


### Cloud deployment evidence

- Snowplow Private Managed Cloud on AWS (aws): https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/
  Snowplow uses delegated cross-account access to install and operate the pipeline in the customer's selected AWS region.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Snowplow Private Managed Cloud on Azure (azure): https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-azure/
  The Azure guide uses an application service principal and role scoped to the customer's subscription.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Snowplow Private Managed Cloud on Google Cloud (gcp): https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-gcp/
  The customer enables billing and grants installation and maintenance roles in its Google Cloud project.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Deployment options and control-plane boundary: https://docs.snowplow.io/docs/get-started/deployment-options/

- Infrastructure and access requirements: https://docs.snowplow.io/restrictive-access-models/

- Private Managed Cloud pricing: https://snowplow.io/pricing

- Customer account boundaries and operation: https://support.snowplow.io/articles/4431218364-learn-about-snowplow-bdp

- Snowplow Private Managed Cloud on AWS: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/

- Snowplow Private Managed Cloud on Azure: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-azure/

- Snowplow Private Managed Cloud on Google Cloud: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-gcp/

### Licensing sources

- https://snowplow.io/pricing

### Infrastructure sources

- https://docs.snowplow.io/restrictive-access-models/


### 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: Documented. Snowplow Console administrators can configure SSO using SAML or OpenID Connect. The PMC deployment uses the vendor-hosted Console and APIs; pricing lists SSO and user permissions on every plan. This does not establish SSO at event collectors, destination systems or the customer's cloud console. Scope: Vendor-hosted Snowplow Console identity for CDI Private Managed Cloud.. Source: https://docs.snowplow.io/docs/account-management/managing-users/ (reviewed 2026-11-21). Supporting source: PMC control-plane boundary — https://docs.snowplow.io/docs/get-started/deployment-options/. Supporting source: Plan features including SSO — https://snowplow.io/pricing.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Explicitly unsupported. PMC deployment and monitoring require Snowplow's direct public-internet access to the customer environment. The vendor explicitly excludes architectures that prohibit that access, even when customer-managed VPN or SSO gates would otherwise provide access. This managed model does not support a fully disconnected environment. Scope: Snowplow CDI PMC operational connectivity; IP allowlisting is supported, full disconnection is not.. Source: https://docs.snowplow.io/restrictive-access-models/ (reviewed 2026-11-21).

- Deployment artifact / IaC: Sources checked — unresolved. Snowplow documents a proprietary IaC platform for PMC. Its AWS setup guide links a public CloudFormation template for the SnowplowAdmin IAM role and describes a separate deployment role; that access bootstrap does not expose the complete managed pipeline installer. Obtain the release-specific deployment configuration, full permissions and rollback/export procedure from Snowplow. Self-Hosted Terraform modules describe a different operating model. Scope: Complete CDI PMC runtime artifact unresolved; AWS IAM-role bootstrap is documented separately.. Source: https://docs.snowplow.io/restrictive-access-models/ (reviewed 2026-11-21). Supporting source: AWS IAM role and CloudFormation access bootstrap — https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/.

- Minimum footprint / sizing: Sources checked — unresolved. The managed-cloud setup guides specify account access and dedicated networking, not a complete quantitative production CPU/RAM/storage baseline. Snowplow scales and operates the pipeline; obtain sizing against events per month, peak event rate, enrichment workloads, destinations, retention and HA/recovery objectives. Customer-console user count and warehouse data size do not establish event-pipeline capacity. Scope: CDI Private Managed Cloud production sizing unresolved; separate self-hosted examples are not a PMC guarantee.. Source: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/ (reviewed 2026-11-21). Supporting source: Dedicated-subnet and operational constraints — https://docs.snowplow.io/restrictive-access-models/.

- License pricing: Documented. Private Managed Cloud is a commercial, custom-quote deployment inside the customer's AWS, Google Cloud or Azure account. The quote depends on events per month, deployment location and destinations. Confirm infrastructure, vendor service and support charges in the contract; the free hosted trial and production Self-Hosted license are separate options. Scope: CDI Private Managed Cloud quote-based commercial terms; no numeric public PMC rate established.. Source: https://snowplow.io/pricing (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Solix Application Retirement — Customer-Managed

Archive retired applications while retaining searchable access to historical business information.

- Listing: https://launchinyourcloud.com/directory/solix-application-retirement/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci, ibm
- Operating model: Customer-operated
- Infrastructure IDs: unspecified
- License: Commercial Enterprise Edition
- Licensing model: commercial-only
- Installation: Vendor-assisted customer-managed enterprise deployment; confirm supported package/topology
- Architecture: Customer-managed archival platform and data storage
- Operations: Customer-managed deployment is available; agree implementation, support, upgrades and infrastructure ownership with Solix.
- Product website: https://www.solix.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Solix documents application retirement and separately describes customer-managed and self-managed on-premises/private/public-cloud options. This entry excludes fully managed SOLIXCloud SaaS. Public installation commands and specific customer-account hyperscaler deployment paths were not verified.

This entry covers the licensed Enterprise Edition customer-managed application retirement option. Self-management and public-cloud deployment do not imply open-source rights.

Customer-hosted installation is documented, but the reviewed public material does not specify enough runtime detail to classify it. Confirm the supported server or container topology with the vendor.


### Category fit

- legacy-system-archive-access: Dedicated application retirement and historical-data archival access using the customer-managed enterprise option. Vendor-assisted enterprise installation; no public installer was verified. Confirm package, deployment topology and responsibility split.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). Source: https://www.solix.com/documents/case-studies/how-a-clean-energy-utility-saved-millions-with-solixcloud.pdf (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 


### Cloud deployment evidence

- Solix private deployment and enterprise archiving platform disclosure (aws, azure, gcp, oci, ibm): https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf
  The parent company's 2024-25 annual report, printed page 46/PDF page 48, describes CDP Private on an organization's existing cloud instances with in-house application management. Its Enterprise Archiving architecture includes Application Retirement above named AWS, Azure, Google Cloud, Oracle Cloud and IBM Cloud infrastructure, and states that the bundle is offered privately as well as as SaaS. This is a platform compatibility disclosure, not a release-specific installation guide; confirm the current private package, topology, licenses and operating agreement.
  Source type: corporate-disclosure; reviewed: 2026-11-12; vendor support: not-assessed.

- Solix Application Retirement customer case on a Google Cloud private tenant (gcp): https://www.solix.com/documents/case-studies/how-a-clean-energy-utility-saved-millions-with-solixcloud.pdf
  The vendor case documents Application Retirement on a Google Cloud private tenant, delivered collaboratively with Kyndryl. It corroborates a real private deployment; it does not by itself establish customer account ownership or customer operations. Use the separate CDP Private disclosure for the customer-operated option and agree the exact contract and support boundaries.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Application retirement functionality: https://www.solix.com/products/application-retirement-solution/

- Explicit customer-managed deployment option: https://www.solix.com/solixcloud/

- Enterprise Edition deployment options: https://www.solix.com/products/enterprise-edition/

- Official self-managed private/public-cloud deployment statement: https://www.solix.com/documents/datasheets/solix-cloud-data-management-for-sap.pdf

### Licensing sources

- https://www.solix.com/products/enterprise-edition/

- https://www.solix.com/solixcloud/

### Infrastructure sources

- https://www.solix.com/products/application-retirement-solution/


### Buyer diligence


Research coverage: 5/12 fields (42%); 1 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed product and Enterprise Edition pages describe governance and deployment options but do not establish the customer-managed retirement application identity integration, provider protocol or account mapping. A hosted-service SSO statement cannot settle the selected customer-hosted edition. Scope: Solix customer-managed application retirement SSO remains unconfirmed. Source: https://www.solix.com/products/application-retirement-solution/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The product page mentions SOC 2 and ISO 27001 alongside SolixCloud options. It does not establish an assessed scope for the customer-managed Application Retirement installation. Scope: Customer-managed application versus vendor cloud scope unresolved. Source: https://www.solix.com/products/application-retirement-solution/ (reviewed 2026-11-14).

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Solix advertises implementation services and multiple deployment options, but the reviewed public material does not expose a release-specific installer, chart or infrastructure artifact for customer-managed retirement. Obtain the supported delivery package and deployment procedure. Scope: Customer-managed Solix installation artifact remains unconfirmed. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed enterprise/product material does not establish numeric customer-managed CPU/RAM/storage or HA requirements. Size ingestion, source formats, indexed archive volume, retrieval concurrency and retention separately from the vendor-operated cloud service. Scope: Customer-managed application retirement sizing remains unconfirmed. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- License pricing: Documented. Solix describes Enterprise Edition as a consumption-based commercial bundle including preservation products and application retirement, with on-premises, hybrid and cloud options. Obtain the applicable customer-managed order, consumption metric, support and non-production/DR rights; no SOLIXCloud SaaS rate is substituted for that agreement. Scope: Current Enterprise Edition commercial model; negotiated customer-managed entitlement and price remain order-specific. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SonarQube Server Data Center Edition

Commercial high-availability SonarQube Server edition with Google Cloud deployment, Azure Kubernetes instructions and documented AWS architecture guidance.

- Listing: https://launchinyourcloud.com/directory/sonarqube-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: gcp, azure, aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Data Center Edition license.
- Licensing model: commercial-only
- Installation: Google Cloud Marketplace on GKE or DCE Helm chart; documented AKS deployment and AWS architecture adaptation
- Architecture: Clustered application and search nodes with load balancing, persistent volumes and an external production database
- Operations: Customer manages the Kubernetes cluster, namespaces, database, persistent volumes, secrets, TLS, identity, load balancing, backups, autoscaling, upgrades and the SonarQube license.
- Product website: https://www.sonarsource.com/products/sonarqube/server/
- Source review: 2026-11-18; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers self-managed Data Center Edition. Google Cloud has a Marketplace path; Azure has a concrete AKS deployment example, while the AWS architecture requires adaptation. For 2026.1, use an external production database, compatible Helm values and an appropriate storage class on AKS; the documentation warns about Azure Fileshare permissions. Confirm chart and package versions independently. CVE-2026-114938 is reported to allow unauthenticated RCE in affected OpenJDK 17.0.6+ runtimes, including Java 21 and 25, on x86-64 CPUs with AVX-512 VBMI. Until Sonar publishes patched builds, set -XX:-UseBASE64Intrinsics for Web, Compute Engine, and Search; ARM is unaffected, and Sonar reported no evidence of exploitation.

SonarQube Server Data Center Edition is a paid, per-instance commercial edition priced by licensed lines of code.

Data Center Edition runs clustered application and search services on customer Kubernetes infrastructure with persistent storage and an external production database.


### Category fit

- devops: Provides high-availability self-managed code-quality and security analysis integrated with source-control and CI workflows.

### Deployment boundaries


- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks (checked 2026-11-15). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example (checked 2026-11-15). 


### Cloud deployment evidence

- SonarQube Data Center Edition on GKE (gcp): https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp
  Sonar documents deploying Data Center Edition through Google Cloud Marketplace into an existing customer GKE cluster, using either Click to Deploy or the advanced command-line path.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- SonarQube DCE deployment on Azure Kubernetes Service (azure): https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks
  Sonar provides a Data Center Edition deployment procedure for primary and replica AKS clusters using its Helm chart, an external PostgreSQL writer endpoint and Azure ingress. This is an active-cold standby example; cluster sizing must be assessed separately.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Edition: Data Center Edition. Versions: 2026.1.

- SonarQube DCE cloud architecture and AWS chart guidance (aws): https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example
  Sonar explicitly says its DCE Kubernetes disaster-recovery architecture can be adapted to AWS with modifications. The upstream DCE Helm chart separately documents AWS ingress migration settings. This is an architecture adaptation path, not an AWS one-click package or a support commitment.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Edition: Data Center Edition. Versions: 2026.1 architecture; select a compatible Helm chart.


### Sources

- SonarQube Data Center Edition on Google Cloud: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp

- SonarQube Server plans and licensing: https://www.sonarsource.com/plans-and-pricing/sonarqube/

- SonarQube DCE deployment on Azure Kubernetes Service: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks

- SonarQube DCE cloud architecture and AWS chart guidance: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example

- Upstream SonarQube DCE Helm chart and AWS ingress settings: https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube-dce/README.md

- DCE Kubernetes prerequisites and AKS storage limitation: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/before-you-start

- SonarQube Java4Shell workaround advisory: https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330

### Licensing sources

- https://www.sonarsource.com/plans-and-pricing/sonarqube/

### Infrastructure sources

- https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp

- https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks

- https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example


### 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. SonarQube Server 2026.5 documents SP-initiated SAML 2.0 federation and optional SCIM provisioning with configured identity providers. This applies to the licensed Server deployment; verify the chosen Data Center licence and identity-provider mapping. Scope: SonarQube Server 2026.5 SAML; selected Data Center entitlement requires review. Source: https://docs.sonarsource.com/sonarqube-server/instance-administration/authentication/saml/overview (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Sonar reports that CVE-2026-114938 may permit unauthenticated RCE in affected OpenJDK runtimes on x86-64 AVX-512 VBMI systems. Apply -XX:-UseBASE64Intrinsics to Web, Compute Engine, and Search as documented, and move to a patched Sonar build when the vendor names one. Scope: Potentially affects supported SonarQube Server 2026.5, 2026.1 LTA, 2025.4 LTA, Community Build, and older versions when the affected Java and CPU conditions are present. ARM is unaffected.. Source: https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream sonarqube-dce Helm chart installs Data Center Edition and requires an external database. It explicitly excludes Community, Developer and Enterprise Editions. Pin and validate the chart/application versions instead of assuming a moving chart matches the versioned cloud guide. Scope: SonarSource sonarqube-dce chart README on moving master branch. Source: https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube-dce/README.md (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. Current Data Center requirements call for at least two application nodes and three search nodes, plus a separate database and load balancer. The validated example uses 4-vCPU/16-GB application nodes and 8-vCPU/32-GB search nodes. Code/issue volume, storage, database and optional agentic features require additional sizing. Scope: Current five-node Data Center topology and vendor validation example. Source: https://docs.sonarsource.com/sonarqube-server/server-installation/data-center-edition/installation-requirements.md (reviewed 2026-11-20).

- License pricing: Documented. Self-hosted editions are priced per instance per year by lines of code; Data Center is the commercial clustered edition. Obtain the required LOC tier and support quote. Optional agentic features require separate subscriptions; the Community licence and Cloud price do not cover Data Center. Scope: Commercial Data Center edition; LOC-based annual model. Source: https://www.sonarsource.com/plans-and-pricing/sonarqube/ (reviewed 2026-11-20). Supporting source: Optional feature subscriptions — https://docs.sonarsource.com/sonarqube-server/server-installation/data-center-edition/installation-requirements.md.

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

- SonarQube Java4Shell workaround (security-advisory): Sonar reports that CVE-2026-114938 may permit unauthenticated RCE in affected OpenJDK runtimes on x86-64 AVX-512 VBMI systems. Scope: Potentially affects supported SonarQube Server 2026.5, 2026.1 LTA, 2025.4 LTA, Community Build, and older versions when the affected Java and CPU conditions are present. ARM is unaffected. Conditions: OpenJDK 17.0.6 or later, including Java 21 and 25, on x86-64 with AVX-512 VBMI. Sonar reported no known exploitation when publishing the notice. Action: Apply -XX:-UseBASE64Intrinsics to Web, Compute Engine, and Search as documented, and move to a patched Sonar build when the vendor names one. Source: https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330; reviewed 2026-11-18.




## Sonatype Nexus Repository Pro Self-Hosted

Commercial self-hosted artifact repository with supported high-availability deployment across customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/nexus-repository-pro-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Nexus Repository Pro license required for high availability and other Pro capabilities.
- Licensing model: commercial-only
- Installation: Official Helm chart for resilient or high-availability Kubernetes deployments, or supported standalone and Docker installation paths
- Architecture: Standalone node or active-active Nexus Repository Pro cluster with persistent storage, external PostgreSQL, load balancing and cloud blob storage
- Operations: Customer manages compute or Kubernetes, PostgreSQL, blob and node storage, ingress and load balancing, TLS, secrets, backups, monitoring, upgrades and license persistence.
- Product website: https://www.sonatype.com/products/sonatype-nexus-repository
- Source review: 2026-11-19; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Nexus Repository Pro self-hosted deployments, not Nexus Repository Cloud or the unlicensed Community Edition. High availability requires Pro, an external PostgreSQL database and customer expertise in Kubernetes, Helm and cloud infrastructure. Sonatype states that its support expertise is strongest on AWS even though Azure and Google Cloud infrastructure are supported. Container deployments must persist both nexus-data and Java preferences so license state survives restarts. Nexus Repository 3.98.0 fixes seven November advisories covering Rut Auth privilege escalation, disabled or locked SSO users regaining access, exposed signing material, SQL injection in the optional reindex task, stored XSS, and group-member authorization bypass. After upgrading, remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove existing group members that group editors are not allowed to read; the upgrade does not clean these up. Review affected sign-ins and tasks, and rotate potentially exposed signing keys or passphrases. Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport.

A Sonatype license file unlocks Nexus Repository Pro capabilities; unlicensed self-hosted instances operate as Community Edition, while the selected high-availability deployment requires Pro.

Nexus Repository Pro runs on persistent VM or Kubernetes capacity with durable node storage, blob storage and, for resilient or HA deployments, an external PostgreSQL database.


### Category fit

- devops: Provides a self-managed repository for packages, containers and other build artifacts used by software-delivery pipelines.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html (checked 2026-11-16). Source: https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html (checked 2026-11-16). 


### Cloud deployment evidence

- Supported Nexus Repository Pro high-availability infrastructure (aws, azure, gcp): https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html
  Sonatype explicitly lists AWS, Azure and Google Cloud as supported providers for Nexus Repository Pro HA and names EKS, AKS and GKE together with provider-specific databases, storage and blob services.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Edition: Nexus Repository Pro.

- Nexus Repository Pro deployment on Google Cloud (gcp): https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html
  Sonatype provides a concrete Google Cloud deployment path for Nexus Repository Pro using its resiliency and high-availability Helm chart, GKE ingress, persistent storage and license management.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Edition: Nexus Repository Pro.


### Sources

- Install self-hosted Nexus Repository: https://help.sonatype.com/en/install-nexus-repository.html

- Nexus Repository high-availability requirements: https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html

- Deploy Nexus Repository to Google Cloud: https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html

- Nexus Repository license management: https://help.sonatype.com/en/license-management.html

- Nexus Repository CVE-2026-113373 advisory: https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04

- Nexus Repository Rut Auth cleanup after upgrade: https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04

- Nexus Repository existing group-member cleanup after upgrade: https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04

- Nexus Repository 3.90.7 release notes: https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html

- Nexus Repository 3.88.2 release notes: https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html

- Sonatype Java4Shell FAQ: https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products

- Nexus Repository 3.98.2 Java4Shell mitigation and publication date: https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html

### Licensing sources

- https://help.sonatype.com/en/license-management.html

- https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html

### Infrastructure sources

- https://help.sonatype.com/en/install-nexus-repository.html

- https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html


### Buyer diligence


Research coverage: 9/12 fields (75%); 8 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: Edition-dependent. Sonatype publishes an AWS Marketplace offer explicitly named Nexus Repository Pro (Self-Hosted). It is a contract/license procurement listing classified as SaaS, not a vendor-run Repository Cloud deployment or an infrastructure installer. Confirm usage, renewal and support terms. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-444trrzad4z56 (reviewed 2026-11-16). Offer prodview-444trrzad4z56: Sonatype; Self-hosted license contract; AWS delivery classification SaaS; https://aws.amazon.com/marketplace/pp/prodview-444trrzad4z56.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Licensed self-hosted Nexus Repository supports SAML 2.0 browser SSO, including IdP group attributes for authorization. SAML authenticates the UI; repository clients use other supported credentials such as user tokens. Scope: Nexus Repository Pro self-hosted UI; not Community or a repository-content SAML protocol. Source: https://help.sonatype.com/en/saml.html (reviewed 2026-11-16).

- SCIM provisioning: Explicitly unsupported. Sonatype explicitly states that direct SCIM is unsupported. SSO does not automatically synchronize user lifecycle or group changes; manual management or custom API integrations are required. Scope: Nexus Repository direct SCIM integration. Source: https://help.sonatype.com/en/authentication.html (reviewed 2026-11-16). Supporting source: Separate SAML-user management REST API — https://help.sonatype.com/en/security-management-api.html.

- Compliance attestations: Not researched.

- Security controls: Documented. The policy requires base usage telemetry and administrator acknowledgment starting in 3.97.0. Pro has a stated 45-day telemetry-delivery grace period; customers requiring disconnected operation need entitlement-specific support review. This is an egress requirement, not a security attestation. Current advisory review: Seven November advisories cover privilege escalation, SSO account reactivation, exposed signing credentials, SQL injection, stored XSS, and repository-member authorization bypass. Upgrade to 3.98.0 or later. The upgrade retains existing Rut Auth capabilities and repository-group memberships: remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove group members that group editors are not allowed to read. Review disabled or locked SSO users' sign-ins and affected reindex tasks; rotate potentially exposed signing keys and passphrases. Current review: Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport. Scope: Nexus Repository maintenance lines explicitly covered by the November 19 release notes. Source: https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04. Supporting source: Prior security-controls source — https://help.sonatype.com/en/nexus-repository-telemetry.html. Supporting source: CVE-2026-113374 — https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04. Supporting source: CVE-2026-113372 — https://support.sonatype.com/hc/en-us/articles/56612283547539-CVE-2026-113372-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-YUM-Repository-Signing-Key-2026-11-04. Supporting source: CVE-2026-113371 — https://support.sonatype.com/hc/en-us/articles/56609541356051-CVE-2026-113371-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-Repository-Signing-Passphrase-2026-11-04. Supporting source: CVE-2026-113370 — https://support.sonatype.com/hc/en-us/articles/56603207226131-CVE-2026-113370-Nexus-Repository-3-SQL-Injection-in-Reindex-Search-by-Pattern-Task-2026-11-04. Supporting source: CVE-2026-113369 — https://support.sonatype.com/hc/en-us/articles/56597339691027-CVE-2026-113369-Nexus-Repository-3-Stored-Cross-Site-Scripting-in-OCI-Attestations-Tab-2026-11-04. Supporting source: CVE-2026-113368 — https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04. Supporting source: 3.90.7 release notes — https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html. Supporting source: 3.88.2 release notes — https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html. Supporting source: 3.98.2 current-line Java4Shell mitigation — https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html.

- Air-gapped operation: Sources checked — unresolved. The current telemetry policy requires base usage reporting and directs commercially entitled customers needing disconnected operation to Sonatype Support. It does not publish an unconditional Pro exemption or a complete disconnected procedure; obtain entitlement-specific terms before relying on air-gapped operation. Scope: Current self-hosted Pro telemetry policy, including 3.97+ onboarding; not Community or SAGE. Source: https://help.sonatype.com/en/nexus-repository-telemetry.html (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. Sonatype publishes the nxrm-ha Helm chart for resilient and high-availability deployments. Pro HA requires an external PostgreSQL database and persistent storage; choose a supported chart, application and database combination. Scope: Nexus Repository Pro HA; not the standalone Community Edition topology. Source: https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html (reviewed 2026-11-16). Deployment artifact: https://github.com/sonatype/nxrm3-ha-repository/tree/main/nxrm-ha. Artifact reference: main (moving branch). Supporting source: HA requirements — https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html.

- Minimum footprint / sizing: Documented. The current cloud-native XS profile recommends one node with 4 vCPU and 16 GiB RAM for its stated 100 requests/second workload. Larger profiles increase node count and resources; Pro HA additionally needs a load balancer, shared blob storage and external PostgreSQL. Scope: Per-node example for the documented workload; not an HA total or performance guarantee. Source: https://help.sonatype.com/en/sonatype-nexus-repository-system-requirements.html (reviewed 2026-11-16). Supporting source: HA infrastructure requirements — https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html.

- License pricing: Documented. A Sonatype license file unlocks Nexus Repository Pro capabilities; unlicensed self-hosted instances operate as Community Edition, while the selected high-availability deployment requires Pro. Scope: Sonatype Nexus Repository Pro Self-Hosted: software license terms; infrastructure and operating costs are separate. Source: https://help.sonatype.com/en/license-management.html (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Nexus Repository 3.98.2 was released November 18, 2026 and includes Java4Shell mitigation for CVE-2026-114938. This is the reviewed 3.98-line snapshot; 3.90.7 and 3.88.2 are separate maintenance backports. Check commercial-edition, runtime, Helm and HA compatibility before upgrading. Scope: Self-hosted Nexus Repository release; commercial edition and HA compatibility still govern use; source supplies a publication day, not a timestamp. Source: https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html (reviewed 2026-11-19). Supporting source: 3.90.7 maintenance-line mitigation — https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html. Supporting source: 3.88.2 maintenance-line mitigation — https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html. Supporting source: Sonatype Java4Shell product and maintained-branch guidance — https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products.




### Security and lifecycle reviews

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

- Nexus Repository 3.98.0 security update (security-advisory): Seven November advisories cover privilege escalation, SSO account reactivation, exposed signing credentials, SQL injection, stored XSS, and repository-member authorization bypass. Scope: Affected ranges vary from 3.0.0 through 3.97.x to narrower 3.86–3.97, 3.90–3.97, 3.93–3.97, and 3.94–3.97 ranges. All are fixed in 3.98.0. Conditions: Rut Auth, SSO, YUM or repository signing, the optional reindex task, OCI attestations, and repository groups determine applicability. Action: Upgrade to 3.98.0 or later. The upgrade retains existing Rut Auth capabilities and repository-group memberships: remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove group members that group editors are not allowed to read. Review disabled or locked SSO users' sign-ins and affected reindex tasks; rotate potentially exposed signing keys and passphrases. Source: https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04; reviewed 2026-11-18. Supporting source: CVE-2026-113374 — https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04. Supporting source: CVE-2026-113372 — https://support.sonatype.com/hc/en-us/articles/56612283547539-CVE-2026-113372-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-YUM-Repository-Signing-Key-2026-11-04. Supporting source: CVE-2026-113371 — https://support.sonatype.com/hc/en-us/articles/56609541356051-CVE-2026-113371-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-Repository-Signing-Passphrase-2026-11-04. Supporting source: CVE-2026-113370 — https://support.sonatype.com/hc/en-us/articles/56603207226131-CVE-2026-113370-Nexus-Repository-3-SQL-Injection-in-Reindex-Search-by-Pattern-Task-2026-11-04. Supporting source: CVE-2026-113369 — https://support.sonatype.com/hc/en-us/articles/56597339691027-CVE-2026-113369-Nexus-Repository-3-Stored-Cross-Site-Scripting-in-OCI-Attestations-Tab-2026-11-04. Supporting source: CVE-2026-113368 — https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04.

- Nexus Repository Java4Shell fixes for current and maintained branches (security-advisory): Nexus Repository 3.98.2 includes Java4Shell mitigation; 3.90.7 and 3.88.2 are separate older-line backports, not substitutes for the current 3.98-line fix. Scope: Self-hosted Nexus Repository: 3.98.2 on the 3.98 line. The FAQ also lists 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the linked November 19 notes identify 3.90.7 and 3.88.2. Conditions: Installed branch, bundled JDK, CPU and process restart determine applicability. Action: Upgrade the installed supported branch to its fixed release, including 3.98.2 or later on 3.98. Restart and verify affected processes. If an immediate upgrade is unavailable, follow Sonatype’s temporary JVM mitigation and runtime-compatibility guidance. Do not downgrade to match an older maintenance backport. Source: https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products; reviewed 2026-11-19. Supporting source: 3.90.7 release notes — https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html. Supporting source: 3.88.2 release notes — https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html. Supporting source: 3.98.2 current-line fix, released November 18, 2026 — https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html.




## Spacelift Self-Hosted

Commercial infrastructure-as-code automation platform deployed to customer AWS, Azure or Google Cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/spacelift-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Spacelift Self-Hosted Enterprise subscription and license token required.
- Licensing model: commercial-only
- Installation: Official Terraform/OpenTofu reference architectures and Helm charts for EKS/ECS, AKS or GKE
- Architecture: Customer-operated Spacelift backend, gateway, workers and data services on cloud compute or Kubernetes.
- Operations: Customer manages compute or Kubernetes, database and object storage, networking, secrets, workers, backups, scaling, upgrades and licensing.
- Product website: https://spacelift.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 entry covers Spacelift Self-Hosted, not the Spacelift SaaS service. New features can reach SaaS before self-hosted releases; match the deployment artifacts and architecture to the licensed version.

Self-hosting is a commercial Enterprise capability governed by Spacelift subscription and license terms.

Spacelift Self-Hosted runs persistent backend and worker services with database and object-storage dependencies.


### Category fit

- devops: Provides self-hosted infrastructure-as-code runs, policy, state, integrations and private workers.

- workflow-automation: Orchestrates governed infrastructure workflows, approvals and automated runs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 


### Cloud deployment evidence

- Spacelift in customer AWS, Azure or GCP infrastructure (aws, azure, gcp): https://docs.spacelift.io/self-hosted
  Spacelift explicitly documents a customer-maintained self-hosted product for AWS, Azure and GCP and links provider-specific reference architectures.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Spacelift Self-Hosted: https://docs.spacelift.io/self-hosted

- Deploy Spacelift to EKS: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-eks

- Deploy Spacelift to AKS: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-aks

- Deploy Spacelift to GKE: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-gke

- Spacelift pricing: https://spacelift.io/pricing

### Licensing sources

- https://docs.spacelift.io/self-hosted/latest/legal/terms

- https://spacelift.io/pricing

### Infrastructure sources

- https://docs.spacelift.io/self-hosted


### 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: Sources checked — unresolved. Spacelift documents public AWS contracts and a sales-assisted private-offer route. Its pricing FAQ says plans are available through AWS, but the reviewed public offer/registration describes SaaS. A private worker is not a self-hosted backend. Obtain an order/private offer that explicitly entitles Enterprise Self-Hosted, its package and support scope before applying Marketplace availability to this listing. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/product/billing/aws-marketplace (reviewed 2026-11-18). Supporting source: Plan, Self-Hosted and Marketplace FAQ statements — https://spacelift.io/pricing. Supporting source: Backend versus SaaS/private-worker boundary — https://docs.spacelift.io/self-hosted.

- Cloud commitment eligibility: Sources checked — unresolved. Spacelift’s pricing FAQ says it qualifies as a SaaS partner for AWS PPA commitments. That statement does not identify a Self-Hosted private-offer entitlement or its eligible billed dimensions. Confirm the selected Enterprise Self-Hosted order and buyer agreement; private-worker SaaS procurement is a separate boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://spacelift.io/pricing (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. Supporting source: Public versus sales-assisted private procurement — https://docs.spacelift.io/product/billing/aws-marketplace.

- Single sign-on: Documented. The self-hosted documentation supports SAML 2.0 or OIDC SSO and describes the transition from managed-IdP bootstrap to SSO administration. Login policies are not evaluated for the bootstrap/SSO admin, so protect and govern those accounts explicitly. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/ (reviewed 2026-11-18).

- SCIM provisioning: Documented. The self-hosted SCIM 2.0 integration provisions users/groups with OAuth client credentials and requires configured SSO. Provisioning does not grant roles by itself; the corresponding group claims must also be sent during login. The self-hosted change log confirms availability from v6.1.0. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/scim (reviewed 2026-11-18). Supporting source: Self-hosted v6.1.0 release boundary — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog.

- Compliance attestations: Sources checked — unresolved. Spacelift’s Trust Center says it uses ISO 27001 internally but is not ISO 27001 certified, and instead maintains SOC 2 Type II assurance. The self-hosted security guide also claims SOC 2. Obtain the current report period, system boundary and customer controls before applying that claim to a customer-operated backend; a SaaS/private-worker assessment alone would not settle this boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://trust.spacelift.io/faq (reviewed 2026-11-18). Supporting source: Self-hosted security statement and customer patch responsibilities — https://docs.spacelift.io/self-hosted/latest/product/security.

- Security controls: Documented. Spacelift documents security boundaries for code/state/secrets and integrations. Self-hosting adds customer-managed encryption keys, backend database/object storage and private workers. SSO/SCIM configuration and worker permissions remain distinct from cloud-target authorization. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/product/security (reviewed 2026-11-18). Supporting source: Customer backend dependencies — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements. Supporting source: SSO administrator behavior — https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/.

- Air-gapped operation: Documented. The vendor documents isolated deployment, local VCS, cached IaC providers/CLI binaries, custom runner images and manual usage/licence handling. EC2 launchers require customer-staged artifacts. Repeat this preparation for upgrades and ensure IdP/cloud targets are reachable within the selected boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/air-gapped (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The self-hosted Helm chart is versioned v7.2.0 and now tracks the application release. Provider-specific Terraform/OpenTofu modules provision backing infrastructure separately. Pin chart, images, modules and worker artifacts as a compatible set; do not confuse old 0.x chart versions with application versions. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0 (reviewed 2026-11-18). Deployment artifact: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0. Artifact reference: Spacelift self-hosted Helm chart v7.2.0. Supporting source: EKS reference deployment — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-eks.

- Minimum footprint / sizing: Documented. The reference architecture requires PostgreSQL 14+, object storage, container orchestration, encryption keys and separate application/worker connectivity. This establishes component dependencies, not a fixed CPU/RAM minimum. Concurrent runs and worker jobs drive capacity independently of user count. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements (reviewed 2026-11-18).

- License pricing: Documented. Self-Hosted is a commercial Enterprise purchase requiring a quote and licence. Public SaaS plan/worker prices do not price this deployment. Confirm backend, private workers, feature entitlement, usage reporting and renewal terms. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://spacelift.io/pricing (reviewed 2026-11-18). Supporting source: Isolated deployment licence/usage handling — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/air-gapped.

- Operating cost estimate: Sources checked — unresolved. Specify parallel runs, worker instance sizes and run duration, state/artifact/log retention, HA backend/DB, optional messaging transport, source-control/IdP dependencies and Enterprise pricing. One hundred users do not determine worker concurrency or the cloud resources those jobs manage. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-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. Spacelift self-hosted chart v7.2.0 was published November 11, 2026 and aligns with the application release. Review the self-hosted changelog and upgrade path. The DinD worker chart reaches EOL February 1, 2027; v7 is also the last major with CloudFormation installation support. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0 (reviewed 2026-11-18). Supporting source: Self-hosted changes and deprecations — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog.




### Security and lifecycle reviews

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

- Spacelift DinD worker Helm chart support ends February 2027 (lifecycle): The Docker-in-Docker worker chart reaches end of life February 1, 2027. Existing charts remain available/runnable, but receive no new versions, fixes or support. Scope: DinD worker Helm chart only; Docker workers on EC2 and the main self-hosted service are not retired by this notice. Conditions: Only installations using the DinD chart require this worker migration. CloudFormation has a separate version-based boundary: v7 is its last supported major. Action: Migrate DinD pools to operator-managed Kubernetes workers. Separately move CloudFormation installations to Terraform/OpenTofu while on v7 before considering v8. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog; reviewed 2026-11-18.

- Spacelift self-hosted component CA trust update (security-advisory): The v7.1.0 changelog updates shipped Go components/images to reject compromised eMudhra intermediate certificate chains and names CVE-2026-111943. Scope: Self-hosted components, launchers/workers and shipped Docker images covered by the vendor’s v7.1.0 security entry; IaC binaries used by stacks are separate. Conditions: TLS trust depends on component/binary version and connection path. The vendor also identifies fixed OpenTofu versions; updating the backend alone does not replace every stack binary. Action: Use a self-hosted release containing the fix, refresh affected worker/launcher images and upgrade stack OpenTofu versions according to the changelog. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog; reviewed 2026-11-18.




## Splunk Enterprise

Customer-managed platform for ingesting, indexing, searching and visualizing machine data.

- Listing: https://launchinyourcloud.com/directory/splunk-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions.
- Licensing model: commercial-only
- Installation: Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies.
- Architecture: Standalone or distributed customer-operated search heads, indexers and management components, with local storage or optional SmartStore object storage
- Operations: Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.
- Product website: https://www.splunk.com/en_us/products/splunk-enterprise.html
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers customer-managed Splunk Enterprise, not Splunk Cloud Platform. Splunk documents customer-managed BYOL architectures on AWS, Azure and Google Cloud. Current installation documentation limits supported container deployments to standalone and single-server topologies, so distributed production deployments should follow supported package-based validated architectures. Confirm supported operating systems, instance types, object-store throughput, cache sizing and clustering requirements. Splunk advance notice SVD-2026-1101 says forthcoming November disclosures are fixed in Enterprise 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 and strongly recommends those or later releases. Final CVE-specific disclosures were not live during this review; 10.6.0 Universal Forwarder users should move to 10.6.1 or later.

Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition.

Splunk Enterprise runs persistent standalone or distributed search, indexing and management services on customer-managed hosts. SmartStore can move indexed data to customer object storage, but the search and indexing tiers remain long-running server workloads.


### Category fit

- observability: Ingests, indexes and searches machine data for operational monitoring, troubleshooting, dashboards and alerting.

- data-analytics: Provides search, dashboards, reports and statistical analysis over indexed machine-generated data.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 


### Cloud deployment evidence

- Splunk Enterprise reference hardware for AWS, Azure and Google Cloud (aws, azure, gcp): https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware
  Splunk explicitly states that Splunk Enterprise can be deployed on Amazon Web Services, Microsoft Azure and Google Cloud Platform, including named government, local and distributed variants. Customers must still select supported host specifications and size each deployment for its workload.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Customer-managed Splunk Enterprise BYOL architecture (aws, azure, gcp): https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform
  Splunk describes customer-managed cloud deployments as BYOL on AWS, Google Cloud or Azure and provides provider-specific SmartStore architecture guidance. This evidence concerns customer-operated Splunk Enterprise, not Splunk Cloud Platform; validate instance, network, object-store and cache requirements for the selected topology.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Splunk Enterprise installation overview: https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview

- Splunk Enterprise reference hardware: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware

- Customer-managed BYOL SmartStore architectures: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform

- Splunk Enterprise license types: https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses

- Splunk November 2026 advance notice: https://advisory.splunk.com/advisories/SVD-2026-1101

- Splunk Enterprise 10.6 release notes: https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6

### Licensing sources

- https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses

- https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.6/install-a-splunk-enterprise-license/install-a-license

### Infrastructure sources

- https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview

- https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware

- https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform


### Buyer diligence


Research coverage: 10/12 fields (83%); 10 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. Splunk publishes an AWS AMI with a 60-day Enterprise trial. Continued paid software use requires an external license; the AMI is not a paid Enterprise subscription or proof of software-spend commitment credit. Verify its packaged version separately from upstream releases. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-l6oos72bsyaks (reviewed 2026-11-16). Offer prodview-l6oos72bsyaks: Splunk; EC2 AMI with trial; commercial license purchased outside Marketplace; https://aws.amazon.com/marketplace/pp/prodview-l6oos72bsyaks.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Enterprise 10.6 documents SAML 2.0 SSO, supported IdP connectivity, role/realName/mail attributes and administrator change_authentication capability. Encrypted assertions can be decrypted when configured; this does not establish SCIM provisioning. Scope: Customer-managed Splunk Enterprise 10.6 SAML configuration. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-single-sign-on-with-saml (reviewed 2026-11-16).

- SCIM provisioning: Documented. Enterprise 10.6 documents SCIM-based deletion of SAML users with a compatible Okta integration. Its release notes identify Entra ID de-provisioning as controlled availability. These sources establish scoped de-provisioning, not unrestricted SCIM user creation, updates or group synchronization. Scope: Splunk Enterprise 10.6 SAML user-removal workflow; identity-provider and availability conditions apply. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-sso-with-okta-as-your-identity-provider (reviewed 2026-11-16). Supporting source: 10.6 controlled-availability Entra ID feature — https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6.

- Compliance attestations: Documented. Splunk’s 10.6 guide identifies OpenSSL FIPS Provider certificate 4985 for FIPS 140-3. NIST lists that module as active, with sunset 2030-03-10 and approved-mode conditions. This is a cryptographic-module validation; deployment OS, mode, TLS and app prerequisites remain essential and it is not a blanket Splunk deployment attestation. Scope: Splunk 10.6 documented module plus NIST validation status checked 2026-11-16. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/establish-and-maintain-compliance-with-fips-and-common-criteria-in-splunk-enterprise/secure-splunk-enterprise-with-fips (reviewed 2026-11-16). Supporting source: NIST CMVP certificate 4985 — https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4985.

- Security controls: Documented. FIPS mode requires a supported x86-64 OS running in FIPS mode, TLS 1.2+ between nodes and compatible apps. The guide lists the older FIPS 140-2 certificate as expired in September 2026; select the supported 140-3 path and validate the full configuration. Scope: Enterprise 10.6 FIPS configuration prerequisites; not automatic security or regulatory compliance. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/establish-and-maintain-compliance-with-fips-and-common-criteria-in-splunk-enterprise/secure-splunk-enterprise-with-fips (reviewed 2026-11-16).

- Air-gapped operation: Documented. Splunk explicitly offers Enterprise for private-cloud/on-premises deployment, including air-gapped environments. This establishes the vendor’s deployment option; the selected apps, license delivery, updates, trust material and data integrations still need a disconnected operating procedure. Scope: Commercial Splunk Enterprise deployment option; not Splunk Cloud or every add-on. Source: https://www.splunk.com/en_us/products/pricing.html (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. Splunk supplies operating-system-specific Enterprise installers. Select the required platform/version and verify the published checksum. The installation guide limits Docker to supported standalone and single-server uses; a download is not a complete distributed infrastructure template. Scope: Splunk Enterprise 10.6 installation guidance; topology and platform determine the artifact. Source: https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview (reviewed 2026-11-16). Supporting source: Enterprise packages and checksums — https://www.splunk.com/en_us/download/splunk-enterprise.html.

- Minimum footprint / sizing: Documented. The Enterprise 10.6 single-instance reference specifies 12 physical cores or 24 vCPU at 2 GHz+, 12 GB RAM and a 1 Gb NIC. Storage, search concurrency, ingest volume and distributed roles require separate sizing. Scope: S1 single-instance production reference; not a multi-tier total or operating-cost estimate. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (reviewed 2026-11-16).

- License pricing: Documented. Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition. Scope: Splunk Enterprise: software license terms; infrastructure and operating costs are separate. Source: https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.6/install-a-splunk-enterprise-license/install-a-license.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Splunk Enterprise 10.6.1 was released October 16, 2026. The release page warns against Universal Forwarder 10.6.0, while SVD-2026-1101 names 10.6.1 and maintained parallel branches as forthcoming November fix targets. Scope: Splunk Enterprise 10.6 release line; advance notice is not a final CVE matrix. Source: https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6 (reviewed 2026-11-18). Supporting source: November 2026 advance notice — https://advisory.splunk.com/advisories/SVD-2026-1101.







## Squidex

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

- Listing: https://launchinyourcloud.com/directory/squidex/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, render, heroku, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Squidex application, database and asset storage using provider-specific instructions.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://squidex.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

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

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

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

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

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

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


### Community and maintenance

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

Reviewed 2026-11-19.

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

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

### Sources

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

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

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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

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

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

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

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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







## Starburst Enterprise

Commercial distributed SQL and analytics platform deployed by Helm into customer-operated Kubernetes.

- Listing: https://launchinyourcloud.com/directory/starburst-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Starburst Enterprise license and entitled registry access required.
- Licensing model: commercial-only
- Installation: Authenticated Starburst Enterprise Helm charts on EKS, AKS or GKE
- Architecture: Coordinator, worker and supporting services on Kubernetes with external service database and data-source connections.
- Operations: Customer manages Kubernetes, dedicated node capacity, storage, networking, service database, catalogs, secrets, backups and upgrades.
- Product website: https://www.starburst.io/platform/starburst-enterprise/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Starburst Enterprise, not Starburst Galaxy or the upstream Trino project. Production Kubernetes deployment requires entitled images and charts, a Starburst license, dedicated adequately sized nodes and an external service database. The older AWS CloudFormation path is deprecated and is not presented as the current installation method. Starburst's November advisory fixes critical Brotli CVE-2026-111497 in 482-e.6, 480-e.13, 479-e.20, and 477-e.24. Upgrade the installed maintained branch to its fixed or later patch.

Starburst Enterprise requires a commercial license and access to authenticated container and Helm registries. The open-source Trino project is separate.

Starburst Enterprise runs persistent coordinator, worker and supporting containers on Kubernetes and requires an external service database plus production capacity planning.


### Category fit

- data-analytics: Distributed SQL query, federation and governed analytics across cloud data stores and lakehouse systems.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.starburst.io/latest/k8s/requirements.html (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.starburst.io/latest/k8s/requirements.html (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.starburst.io/latest/k8s/requirements.html (checked 2026-11-17). 


### Cloud deployment evidence

- Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE (aws, azure, gcp): https://docs.starburst.io/latest/k8s/requirements.html
  Starburst documents its Enterprise Helm deployment on customer Kubernetes and explicitly supports Amazon EKS, Azure AKS and Google GKE with provider-specific ecosystem guidance. Customers operate the cluster and data services.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Starburst Enterprise on Kubernetes: https://docs.starburst.io/latest/k8s.html

- Kubernetes requirements: https://docs.starburst.io/latest/k8s/requirements.html

- AWS ecosystem and deployment: https://docs.starburst.io/latest/ecosystems/aws/

- Microsoft Azure ecosystem: https://docs.starburst.io/latest/ecosystems/microsoft/

- Google Cloud ecosystem: https://docs.starburst.io/latest/ecosystems/google/

- Starburst security advisories: https://docs.starburst.io/security/advisories.html

### Licensing sources

- https://docs.starburst.io/latest/k8s.html

### Infrastructure sources

- https://docs.starburst.io/latest/k8s.html

- https://docs.starburst.io/latest/k8s/requirements.html


### 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. SEP documents AWS EKS Marketplace deployment and Google Cloud Marketplace subscriptions. The Google Click to Deploy path is recommended only for small proofs of concept; prefer the documented command-line customization path. Scope: Starburst Enterprise Marketplace, not Galaxy SaaS. Source: https://docs.starburst.io/latest/ecosystems/aws/marketplace/ (reviewed 2026-11-17). Supporting source: Google Cloud Marketplace limits and support — https://docs.starburst.io/latest/ecosystems/google/gcp-marketplace.html.

- Cloud commitment eligibility: Sources checked — unresolved. SEP Marketplace deployment is documented, but the reviewed procurement guides do not establish qualifying fees and contract-specific commitment treatment. Galaxy claims were excluded. Scope: Reviewed public evidence for Starburst Enterprise; unresolved within this edition/deployment. Source: https://docs.starburst.io/latest/ecosystems/aws/marketplace/ (reviewed 2026-11-17).

- Single sign-on: Documented. SEP supports SAML 2.0 SSO configured on the coordinator. TLS is required; authentication is separate from the access-control rules that grant data permissions. Scope: Starburst Enterprise, not Galaxy or upstream Trino. Source: https://docs.starburst.io/latest/security/saml.html (reviewed 2026-11-17).

- SCIM provisioning: Documented. SEP documents SCIM user/group synchronization with its internal group provider and a configured secret token. Configure a supported external provider and network reachability; authorization to data remains separate. Scope: SEP self-managed SCIM configuration. Source: https://docs.starburst.io/latest/security/scim-provisioning.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Starburst Enterprise 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.starburst.io/latest/security/authentication-types.html (reviewed 2026-11-17).

- Security controls: Documented. Authentication requires TLS/HTTPS and a shared secret. Apply the selected authenticator plus access-control system and restrict coordinator exposure; provisioning identities does not grant unrestricted data access. Current advisory review: Starburst documents fixed builds for critical Brotli CVE-2026-111497. Upgrade the installed maintained branch to its fixed or later patch. Scope: Starburst Enterprise authentication requirements Fixed in 482-e.6, 480-e.13, 479-e.20, and 477-e.24; branch-specific affected ranges follow the vendor advisory.. Source: https://docs.starburst.io/security/advisories.html (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.starburst.io/latest/security/authentication-types.html.

- Air-gapped operation: Sources checked — unresolved. SEP requires entitled images/charts and a licence. The reviewed Kubernetes requirements do not establish complete isolated licence renewal, connector dependencies and upgrades. Scope: Reviewed public evidence for Starburst Enterprise; unresolved within this edition/deployment. Source: https://docs.starburst.io/latest/k8s/requirements.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. SEP supplies licensed Helm charts and images in its Harbor registry. Obtain customer credentials and configure the coordinator, workers and backend database; the legacy AWS CloudFormation path is deprecated. Scope: Supported Kubernetes SEP installation. Source: https://docs.starburst.io/latest/k8s/requirements.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The Kubernetes guide specifies identical dedicated nodes with 16–64 cores and 64–256 GB RAM, one coordinator/worker per node, plus an externally managed service database. This is substantially more than a small general-purpose app cluster. Scope: SEP Kubernetes node requirements; workload and HA counts still need design. Source: https://docs.starburst.io/latest/k8s/requirements.html (reviewed 2026-11-17).

- License pricing: Documented. Starburst Enterprise requires a commercial license and access to authenticated container and Helm registries. The open-source Trino project is separate. Scope: Starburst Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.starburst.io/latest/k8s.html (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm coordinator failover, worker concurrency, backend database, data-source storage and licensed cores. The documented dedicated-node minimum does not by itself establish the required HA query architecture. 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.starburst.io/latest/k8s/requirements.html (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The version policy distinguishes LTS and STS. The reviewed table lists 482-e.x LTS through 2027-08-31 and 483-e STS from October 2026 until the next release; select a supported line and review breaking changes. Scope: SEP support policy and month-level release table; not a patch timestamp. Source: https://docs.starburst.io/latest/versions.html (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Starburst Enterprise Brotli security update (security-advisory): Starburst documents fixed builds for critical Brotli CVE-2026-111497. Scope: Fixed in 482-e.6, 480-e.13, 479-e.20, and 477-e.24; branch-specific affected ranges follow the vendor advisory. Conditions: Exposure depends on the bundled Brotli decoder and reachable processing paths. Action: Upgrade the installed maintained branch to its fixed or later patch. Source: https://docs.starburst.io/security/advisories.html; reviewed 2026-11-18.




## Strapi Self-Hosted

Headless CMS for managing structured content and delivering it through APIs.

- Listing: https://launchinyourcloud.com/directory/strapi/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core; commercial Growth/Enterprise features and terms differ
- Licensing model: open-source
- Installation: Node.js production deployment with a supported SQL database; container/Kubernetes options
- Architecture: Customer-operated Node.js CMS, admin panel and database
- Operations: Customer operates application servers, database, media storage, backups and upgrades.
- Product website: https://strapi.io/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosted Strapi, not Strapi Cloud. Review workflows, audit logs and other editorial controls are plan-dependent. Confirm supported database/runtime versions and storage requirements for the selected release. Strapi 5.62.0, released November 12, 2026, includes a security patch whose detailed disclosure was delayed to allow operators time to upgrade. It also changes invalid boolean-filter handling, so self-hosted operators should review compatibility and upgrade promptly. Strapi v5.63.0 changes filter behavior: invalid or previously dropped conditions now return errors or no results, arrays are limited to 100 items, null semantics change, locale permissions are not automatically restored, and AI jobs require rolling-upgrade care. Test existing queries, permissions, and mixed-version nodes before rollout.

The broad self-hosted listing includes the MIT core and separately licensed Enterprise feature code under ee/ directories; paid hosting alone is not the reason for this classification.

Classified for the documented long-running Node.js application/server deployment with a database; headless APIs do not imply a function-based or static-only deployment.


### Category fit

- content-management: Headless content management with content modeling, editorial administration and APIs; paid governance features depend on plan.

### Deployment boundaries


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

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

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://strapi.io/hosting (checked 2026-11-12). 


### Cloud deployment evidence

- Strapi self-hosting compatibility (aws, azure, gcp): https://strapi.io/hosting
  The vendor explicitly identifies AWS, Azure and Google Cloud for self-hosted Strapi. This is its Node.js application in customer infrastructure, not Strapi Cloud; production database, backups and updates remain customer responsibilities.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted deployment requirements: https://docs.strapi.io/cms/deployment

- Project functionality and core license: https://github.com/strapi/strapi

- Licensing and edition terms: https://github.com/strapi/strapi/blob/develop/packages/core/content-manager/LICENSE

- Strapi 5.62.0 security release: https://github.com/strapi/strapi/releases/tag/v5.62.0

- Strapi v5.63.0 release: https://github.com/strapi/strapi/releases/tag/v5.63.0

### Licensing sources

- https://github.com/strapi/strapi/blob/develop/packages/core/content-manager/LICENSE

- https://docs.strapi.io/cms/deployment

### Infrastructure sources

- https://docs.strapi.io/cms/deployment


### 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 self-hosted pricing page offers SSO as a paid Growth add-on and includes it in Enterprise. The listed identity options include SAML 2.0 and OAuth2 providers; Community does not gain those entitlements. Scope: CMS self-hosted admin-user authentication; paid-plan/add-on scope. Source: https://strapi.io/pricing-self-hosted (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 Strapi 5 Docker guide supplies development/production Dockerfile and Compose examples for building your own application image. Strapi explicitly does not publish an official container image; do not label a third-party image as upstream-supported. Scope: Upstream courtesy examples for a custom Strapi 5 project. Source: https://docs.strapi.io/cms/installation/docker (reviewed 2026-11-20). Deployment artifact: https://docs.strapi.io/cms/installation/docker. Artifact reference: Current Strapi 5 Dockerfile/Compose examples; pin project dependencies and base images.

- Minimum footprint / sizing: Documented. The deployment guide lists a minimum of 1 CPU core, 2 GB RAM and 8 GB disk, with 2+ cores, 4 GB+ and 32 GB+ recommended. Database and workload sizing remain separate. Scope: Strapi deployment-guide baseline; not an end-to-end infrastructure bill. Source: https://docs.strapi.io/cms/deployment (reviewed 2026-11-14).

- License pricing: Documented. Community is free under MIT. Growth is listed at $45/month including three admin users, with additional users at $15/month. SSO is a separate priced add-on; Enterprise is quoted. Hosting is separate. Scope: Self-hosted CMS software plans; not Strapi Cloud hosting. Source: https://strapi.io/pricing-self-hosted (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Strapi v5.63.0 was published November 18, 2026. It changes invalid-filter, array-limit, null, locale-permission, and AI-job behavior; test queries and rolling upgrades before rollout. Scope: Upstream Strapi 5 release. Source: https://github.com/strapi/strapi/releases/tag/v5.63.0 (reviewed 2026-11-18).







## Strategy Enterprise in Your Cloud

Vendor-managed enterprise analytics and AI platform deployed as a dedicated single-tenant environment in the customer's public-cloud account.

- Listing: https://launchinyourcloud.com/directory/strategy-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, stackit
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial Strategy Enterprise subscription; customer-cloud deployment is not available with the Standard plan.
- Licensing model: commercial-only
- Installation: Vendor-assisted, fully managed deployment into the customer's licensed AWS, Azure Google Cloud or STACKIT environment
- Architecture: Dedicated containerized Strategy services in a customer-licensed VPC or VNet, administered and maintained by Strategy.
- Operations: Strategy administers and maintains the platform; the customer supplies the cloud environment, data sources, identity, network approvals and shared governance responsibilities.
- Product website: https://software.strategy.com/pricing
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers the Strategy Enterprise customer-cloud option, not Strategy Standard in the vendor's managed environment. Strategy describes the service as fully managed despite its deployment in a customer-licensed AWS, Azure Google Cloud or STACKIT environment, so it is classified as BYOC rather than fully customer-operated. Confirm contract-specific account ownership, cloud-resource billing, service availability, support boundaries and cloud-commitment eligibility before procurement.

The customer-cloud option is a commercial Strategy Enterprise service. Strategy Standard is vendor-hosted and does not include deployment into the customer's cloud; exact entitlements and cloud-credit treatment follow the Enterprise contract.

Strategy describes a dedicated single-tenant, containerized environment using cloud virtual networks and provider infrastructure in the customer's licensed cloud, with Strategy operating the platform.


### Category fit

- data-analytics: Enterprise business intelligence, dashboards, reporting, embedded analytics and governed data exploration in a dedicated environment.

- ai-tools: Enterprise includes customizable AI agents and AI-assisted analysis capabilities; exact features and model integrations follow the contracted platform.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (checked 2026-11-17). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (checked 2026-11-17). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (checked 2026-11-17). 

- stackit: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://software.strategy.com/pricing (checked 2026-11-17). 

Operating responsibility: Strategy Enterprise is fully managed in the customer's selected cloud environment. The customer administers the analytics solution while Strategy maintains platform infrastructure and application upgrades. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (checked 2026-11-20). Supporting source: Enterprise customer-cloud eligibility, including STACKIT — https://software.strategy.com/pricing.


### Cloud deployment evidence

- Strategy Enterprise in customer-licensed AWS, Azure or Google Cloud (aws, azure, gcp): https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise
  Strategy documents a dedicated single-tenant deployment in a customer-licensed AWS, Azure or GCP environment and states that its cloud team administers and maintains the service on the customer's behalf. The pricing page separately limits own-cloud deployment to Enterprise.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Strategy Enterprise customer-cloud deployment on STACKIT (stackit): https://software.strategy.com/pricing
  The current pricing FAQ explicitly lists STACKIT alongside AWS, Azure and Google Cloud for Enterprise deployment in the customer cloud environment. Standard is vendor-hosted; contract-specific regions, account access, support and commitment eligibility remain procurement checks.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Strategy plans, customer-cloud option and named providers: https://software.strategy.com/pricing

- Strategy Managed Cloud Enterprise security and operating model: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise

- Strategy on AWS and customer-licensed cloud environments: https://software.strategy.com/ecosystems/aws

- Strategy product licensing list: https://software.strategy.com/company/product-listing

- Strategy for regulated industries and customer-cloud custody: https://software.strategy.com/ecosystems/regulated-industries

### Licensing sources

- https://software.strategy.com/pricing

- https://software.strategy.com/company/product-listing

### Infrastructure sources

- https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise

- https://software.strategy.com/pricing


### Buyer diligence


Research coverage: 12/12 fields (100%); 4 documented, 8 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 Enterprise FAQ permits customer-cloud deployment and conditional commitment usage, but does not identify the offer/delivery terms for each provider. Confirm the managed Enterprise order. Scope: Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment. Source: https://software.strategy.com/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Edition-dependent. The Enterprise pricing FAQ states usage can count toward cloud commitments/credits for the supported customer-cloud deployment. Confirm the provider agreement, offer and eligible charges; Standard is a different deployment tier. Scope: Enterprise customer-cloud procurement statement, conditional eligibility. Source: https://software.strategy.com/pricing (reviewed 2026-11-17).

- Single sign-on: Sources checked — unresolved. Strategy Library documents SAML/OIDC interaction with SCIM, but the reviewed guide does not establish the managed Enterprise package, IdP configuration and contractual entitlement for this listing. Scope: Strategy One identity features versus purchased Enterprise service. Source: https://www2.strategy.com/producthelp/Current/WorkstationWeb/en-us/Content/config_lib_server_scim.htm (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Strategy One Library documents SCIM 2.0 from September 2025, but the reviewed material does not establish which Library release, enablement and entitlement are supplied in the purchased managed Enterprise environment. Confirm these before treating it as included. Scope: Strategy One feature evidence; managed Enterprise delivery/entitlement unconfirmed. Source: https://www2.strategy.com/producthelp/Current/Workstation/en-us/Content/config_lib_server_scim.htm (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The Enterprise security page names SOC 2, ISO 27001 and other frameworks, but the actual report/certificate scope, audit period and applicability to the purchased customer-account deployment were not available in the reviewed page. Scope: Enterprise marketing claims versus scoped current attestation. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Security controls: Documented. The Enterprise architecture describes a dedicated, single-tenant customer-account boundary with vendor administration and VPC configuration. Review the operational access and responsibility split in the contract. Scope: Enterprise account/network boundary; certification scope reviewed separately. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. Customer-account/VPC custody and dedicated vendor management do not establish no-internet operation, offline licensing or isolated vendor administration. Scope: Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Enterprise is vendor-managed in the customer cloud account. Obtain the approved provisioning/access design and region/topology with the Enterprise order; a public self-service Terraform/Helm artifact is not established. Scope: Vendor-operated Enterprise deployment, not Standard hosted service. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Minimum footprint / sizing: Sources checked — unresolved. The managed Enterprise page does not publish a complete HA bill of materials for 100 users/1 TB. Obtain the service topology, regional availability, capacity and responsibility split in the quote. Scope: Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- License pricing: Documented. The customer-cloud option is a commercial Strategy Enterprise service. Strategy Standard is vendor-hosted and does not include deployment into the customer's cloud; exact entitlements and cloud-credit treatment follow the Enterprise contract. Scope: Strategy Enterprise in Your Cloud: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://software.strategy.com/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Obtain the managed Enterprise HA deployment/region bill of materials, user roles, service fees, data-processing profile and cloud-resource billing boundary from the vendor. 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://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. Strategy One Library feature dates do not establish the release installed or upgrade cadence in the contracted Enterprise managed service. Obtain its maintenance and version policy. Scope: Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment. Source: https://www2.strategy.com/producthelp/Current/Workstation/en-us/Content/config_lib_server_scim.htm (reviewed 2026-11-17).







## SuperPlane Enterprise Self-Hosted

Enterprise software-factory and agent-workflow platform installed with Terraform and Helm in a customer cloud account.

- Listing: https://launchinyourcloud.com/directory/superplane-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SuperPlane Enterprise license required for the documented Kubernetes deployment.
- Licensing model: commercial-only
- Installation: Vendor Terraform modules provision EKS, AKS or GKE, managed data services and the SuperPlane Helm release
- Architecture: Customer-operated Kubernetes cluster, managed PostgreSQL and object storage, Fleet Manager and runner virtual machines.
- Operations: Customer manages the cloud account, cluster, database, object storage, runner images and VMs, DNS, TLS, backups, upgrades and connected model or tool credentials.
- Product website: https://superplane.com/
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry scopes only the Enterprise Kubernetes deployment on AWS, Azure and Google Cloud. The Apache-2.0 community engine and single-VM Compose installation are separate. Google Cloud public runner images are not yet published and must be built with Packer. Connected source-control, model and workflow services can move code or data outside the cluster according to their own configuration and terms.

The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements.

Terraform provisions persistent Kubernetes application services, managed PostgreSQL and object storage, while Fleet Manager creates runner virtual machines.


### Category fit

- devops: Coordinates coding agents, source control, CI, review and verified software-delivery work.

- workflow-automation: Defines durable automation lines, approvals, checks and repair loops for recurring engineering work.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.superplane.com/self-hosting/overview/ (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.superplane.com/self-hosting/overview/ (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.superplane.com/self-hosting/overview/ (checked 2026-11-17). 


### Cloud deployment evidence

- SuperPlane Enterprise on EKS, AKS and GKE (aws, azure, gcp): https://docs.superplane.com/self-hosting/overview/
  SuperPlane documents Terraform-created EKS, AKS and GKE clusters with managed PostgreSQL, object storage and Helm releases in the customer's account. Enterprise licensing is required; Google Cloud runner images must currently be built by the operator with Packer.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Self-hosted editions and provider architectures: https://docs.superplane.com/self-hosting/overview/

- Provider-specific Enterprise installation: https://docs.superplane.com/self-hosting/install/

- SuperPlane pricing and Enterprise self-hosting: https://superplane.com/pricing/

- Upstream Apache-2.0 project: https://github.com/superplanehq/superplane

### Licensing sources

- https://docs.superplane.com/self-hosting/overview/

- https://superplane.com/pricing/

### Infrastructure sources

- https://docs.superplane.com/self-hosting/overview/

- https://docs.superplane.com/self-hosting/install/


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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. Enterprise installation and direct commercial terms are documented; a current cloud Marketplace offer for this Kubernetes edition was not established. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Enterprise custom terms do not establish an eligible Marketplace offer, qualifying fees or cloud-commitment treatment. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. The plan comparison includes SSO in Enterprise together with Enterprise self-hosting. Confirm the required IdP protocol and configuration with the vendor; these entitlements do not apply to the separate community VM edition. Scope: Enterprise self-hosting plan. Source: https://superplane.com/pricing/ (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Enterprise includes automated user provisioning, but the pricing table does not name SCIM or document its endpoint, operations and identity-provider limitations. Scope: Enterprise automated provisioning; protocol not established. Source: https://superplane.com/pricing/ (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SuperPlane Enterprise Self-Hosted 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.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Security controls: Documented. The provider installation separates infrastructure provisioning, application secrets and runner management. Protect Terraform state, generated credentials and license material; configure TLS/DNS and restrict the provider permissions used by the installer. Scope: Enterprise Kubernetes provider installation. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. The standard installer downloads charts, images and provider tooling and configures public DNS/certificates. A supported offline licensing, dependency-transfer and upgrade workflow was not established in this guide. Scope: Enterprise installation; no inference from running in a private VPC. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Provider-specific Terraform creates the managed Kubernetes, PostgreSQL and storage dependencies; Helm installs the application and Fleet Manager controls runners. GCP requires building runner images with Packer rather than using the published AWS/Azure images. Scope: Enterprise installer and provider dependencies; community VM is a different path. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The Enterprise guide requires managed Kubernetes, PostgreSQL, object storage and separately provisioned runners. Runner defaults and example machine types are component settings, not a measured minimum for the complete Enterprise service. Scope: Enterprise topology requirements; size the cluster and runners separately. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- License pricing: Documented. The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements. Scope: SuperPlane Enterprise Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Price EKS, RDS HA PostgreSQL, storage and runner pools after the Enterprise bill of materials and active-runner concurrency are confirmed. Hosted sandbox/model charges do not price this deployment. 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.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. The installer names component/chart revisions, while the latest GitHub release is Fleet Manager v0.1.7. Neither alone establishes the current Enterprise application bundle and supported upgrade compatibility. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).







## SUSE Multi-Linux Manager 5.2

Open-source Linux infrastructure management and automation platform deployed as a customer-operated container or cloud virtual machine.

- Listing: https://launchinyourcloud.com/directory/suse-multi-linux-manager/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source product based on Uyuni with component open-source licenses; SUSE subscriptions, support, images and trademarks use separate commercial terms.
- Licensing model: open-source
- Installation: SUSE Multi-Linux Manager 5.2 container with mgradm on SL Micro 6.2 or SLES 15 SP7, or a SUSE-provided cloud VM image
- Architecture: Customer-operated management server container with persistent repositories, database data, proxy services and managed-system connections.
- Operations: Customer manages the cloud VM, private networking, DNS, storage, server and proxy containers, repository synchronization, backups, upgrades and registered systems.
- Product website: https://www.suse.com/products/multi-linux-manager/
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

SUSE documents public-cloud installation tested on Amazon EC2, Google Compute Engine and Microsoft Azure. Keep the server on a restricted private network with working forward-confirmed reverse DNS and external persistent disks for repositories and database data. AWS supports PAYG and BYOS; Azure supports BYOS, while the public guide's GCP path is a tested customer-operated installation rather than a confirmed marketplace billing offer. Public-cloud proxies are BYOS-only.

SUSE describes Multi-Linux Manager as an open-source infrastructure-management solution based on Uyuni and publishes corresponding GPL source. SUSE-provided images, updates, support, host entitlements and trademarks remain governed by the selected subscription and commercial terms.

The supported 5.2 deployment runs persistent server and proxy containers on customer virtual machines with large durable repository and database volumes.


### Category fit

- devops: Automates Linux provisioning, patching, configuration, monitoring, inventory and compliance operations across managed systems.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html (checked 2026-11-17). Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html (checked 2026-11-17). Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html (checked 2026-11-17). 


### Cloud deployment evidence

- SUSE Multi-Linux Manager public-cloud installation on EC2, Azure and GCE (aws, azure, gcp): https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html
  SUSE states that its public-cloud requirements and procedures were tested on Amazon EC2, Microsoft Azure and Google Compute Engine. The customer operates the instance, DNS, private networking and durable storage; billing and image availability differ by provider.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SUSE Multi-Linux Manager BYOS and PAYG public-cloud models (aws, azure): https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html
  The public-cloud guide documents BYOS on AWS and Azure and PAYG on AWS. This evidence qualifies procurement models; it does not extend PAYG availability to Azure or Google Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- SUSE Multi-Linux Manager 5.2 documentation: https://documentation.suse.com/multi-linux-manager/5.2/

- Public-cloud requirements for EC2, GCE and Azure: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html

- Public Cloud Guide and subscription models: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html

- SUSE Multi-Linux Manager 5.2 container deployment: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html

- SUSE Multi-Linux Manager 5.2 release notes: https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html

- Product and subscription overview: https://www.suse.com/products/multi-linux-manager/

### Licensing sources

- https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html

- https://www.suse.com/products/multi-linux-manager/

### Infrastructure sources

- https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html

- https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html


### 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: Edition-dependent. The public-cloud guide documents AWS BYOS/PAYG and Azure BYOS routes. Google Cloud is tested but a corresponding Marketplace offer is not established by the guide; proxies are BYOS only. Scope: Product-specific public-cloud delivery variants. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. AWS PAYG and BYOS variants have different entitlement/billing terms. The public-cloud guide does not establish qualifying charges under a buyer commitment agreement. Scope: Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html (reviewed 2026-11-17).

- Single sign-on: Documented. Multi-Linux Manager supports SAML 2 SSO with signed/encrypted assertions and SP metadata. The corresponding Manager user must exist before enabling SSO; selecting an IdP and its support remain customer responsibilities. Scope: SUSE Multi-Linux Manager 5.2 server authentication. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The SAML guide requires the Manager user to exist before enabling SSO. It does not establish a SCIM endpoint or automatic lifecycle provisioning. Scope: Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SUSE Multi-Linux Manager 5.2 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://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html (reviewed 2026-11-17).

- Security controls: Documented. The SSO workflow requires mapping the IdP uid to an existing Manager user and protecting signing/encryption material. SSO does not automatically provision accounts or grant other SUSE products the same identity support. Scope: Manager identity trust; not SCIM or a certification. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. The reviewed 5.2 administration PDF identifies itself as Beta 1 and describes disconnected repository synchronization. It does not settle the supported GA installation, subscription renewal, container updates and client-content transfer workflow. Scope: Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment. Source: https://documentation.suse.com/multi-linux-manager/5.2/pdf/en/suse_multi_linux_manager_administration_guide.pdf (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The 5.2 server workflow deploys containers using mgradm on the supported host OS, with persistent volumes and separately prepared repository/database storage. Select the matching BYOS/PAYG cloud image and entitlements. Scope: Multi-Linux Manager container deployment. Source: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Size the server and proxy for managed clients and mirrored repositories, not human users. PostgreSQL must be local; remote PostgreSQL and NFS database storage are unsupported. Separate persistent repository/database devices and supported filesystems are recommended. Scope: 5.2 storage and database requirements; not an approved active-active HA design. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/installation-and-upgrade/hardware-requirements.html (reviewed 2026-11-17).

- License pricing: Documented. SUSE describes Multi-Linux Manager as an open-source infrastructure-management solution based on Uyuni and publishes corresponding GPL source. SUSE-provided images, updates, support, host entitlements and trademarks remain governed by the selected subscription and commercial terms. Scope: SUSE Multi-Linux Manager 5.2: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Specify managed clients, OS repositories/proxies, subscription units and a supported HA/recovery design. The guide requires local PostgreSQL, so substituting RDS Multi-AZ is not established. 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://documentation.suse.com/multi-linux-manager/5.2/en/docs/installation-and-upgrade/hardware-requirements.html (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The reviewed 5.2 Server notes include 5.2.1 updates, PostgreSQL 18, platform changes and security fixes. Kubernetes deployment remains a Technology Preview; the notes document host/feature support separately from container and proxy versions. Scope: 5.2 Server release notes; document revision time is not a software release timestamp. Source: https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html (reviewed 2026-11-17).







## SUSE Observability Self-Hosted

Commercial observability platform installed by Helm into a dedicated customer Kubernetes cluster.

- Listing: https://launchinyourcloud.com/directory/suse-observability-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SUSE Observability self-hosted subscription and license key required.
- Licensing model: commercial-only
- Installation: SUSE Observability server Helm chart on EKS, AKS, GKE or Alibaba ACK, with provider-specific storage configuration
- Architecture: Persistent observability services, ingestion and storage components on a dedicated customer Kubernetes cluster.
- Operations: Customer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.
- Product website: https://www.suse.com/products/observability/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers the self-hosted server product, not SUSE Cloud Observability SaaS. Installation requires a license key, compatible Helm and Kubernetes versions, persistent storage and dedicated sizing. High-availability and non-high-availability profiles are not interchangeable after installation, so choose the production topology before deployment. SUSE Observability 2.13.0 includes authentication, disk, and backup fixes and requires the documented sequential upgrade path. Version 2.10 reached end of support on November 12, 2026; move through supported intermediate releases as required.

The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering.

SUSE Observability runs persistent stateful services on a dedicated Kubernetes cluster with durable storage and substantial capacity requirements.


### Category fit

- observability: Collects, correlates and visualizes Kubernetes topology, metrics, events and related operational signals in a customer-operated deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html (checked 2026-11-17). 


### Cloud deployment evidence

- SUSE Observability on EKS, AKS and GKE (aws, azure, gcp): https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html
  The server-installation guide explicitly covers the Observability server on EKS, AKS and GKE and supplies the Helm installation. The customer operates the dedicated server cluster, default storage class, persistent volumes and ingress; monitored-cluster agent integrations are separate.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SUSE Observability server installation on Alibaba ACK (alibaba): https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html
  The server guide supplies ACK-specific Helm values for stateful backend PVCs, each at least 20 GiB. This is server deployment evidence, distinct from monitoring an ACK cluster with an agent. Apply the selected HA sizing profile and provider storage requirements.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Install SUSE Observability self-hosted: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html

- Kubernetes quick start and named-cloud integrations: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/k8s-quick-start-guide.html

- SUSE subscription terms: https://www.suse.com/products/subscription_terms.pdf

- Alibaba ACK server Helm installation and PVC minimums: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html

- SUSE Observability 2.13.0 release notes: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/release-notes/v2.13.0.html

- SUSE product lifecycle: https://www.suse.com/lifecycle/

### Licensing sources

- https://www.suse.com/products/subscription_terms.pdf

- https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html

### Infrastructure sources

- https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html


### 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 server guide supplies a licensed Helm repository, not a cloud-provider billing offer. A current Marketplace offer for this self-hosted server was not established. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/installing-suse-obs.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The self-hosted SUSE subscription and Helm installation do not establish an eligible offer or contract-specific cloud commitment treatment. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://www.suse.com/products/subscription_terms.pdf (reviewed 2026-11-17).

- Single sign-on: Documented. The server supports OIDC, including Rancher and Keycloak configurations, or LDAP as the selected authentication mechanism. Only one mechanism is configured at a time; map external groups to the intended server roles. Scope: SUSE Observability server authentication. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The server supports selected OIDC/LDAP authentication and role mappings, but a SCIM provisioning endpoint and lifecycle operations were not established. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SUSE Observability Self-Hosted 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://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Security controls: Documented. The default shared administrator password is explicitly not production-ready. Configure an external identity method, limit administrator roles and review RBAC before production use. Scope: Server identity and role hardening; not monitored-cluster agent settings. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Air-gapped operation: Documented. SUSE supplies an air-gapped server installation workflow: download the charts/images, transfer them to the isolated network, load a private registry and apply the licensed Helm configuration. Configure registry credentials and preserve the chosen sizing profile. Scope: Licensed self-hosted Observability server, not agents only. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/k8s-suse-rancher-prime-air-gapped.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The server installer uses the SUSE Observability Helm repository, licence key and a selected sizing profile. It provisions the Observability backend on EKS/AKS/GKE; agent installation is a separate workflow. Scope: Self-hosted server Helm installation. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/installing-suse-obs.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The smallest HA profile (150-ha) requests 49.8 CPU and 130.7 GiB RAM across at least three workers, with 2,595 GiB default storage. It is based on observed default-node capacity, not users; spare rolling-update capacity is additional. Scope: Observability 150-ha resource requests, not CPU limits or physical-node counts. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/requirements.html (reviewed 2026-11-17).

- License pricing: Documented. The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering. Scope: SUSE Observability Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.suse.com/products/subscription_terms.pdf (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 3,656.44/month. Three 32-vCPU/128-GiB workers price the minimum 150-ha profile, plus its 2,595 GiB default PVC request and 150 GB boot allowance. For this illustration each requested GiB is budgeted as one EBS billing GB. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Smallest documented HA profile, not a conversion from 100 users/1 TB into monitored-node capacity. It exceeds a 1 TB storage allowance before boot volumes. 96 vCPU/384 GiB fleet leaves nominal CPU/memory capacity after one worker loss; scheduling, AZ/storage failover and rolling updates still need validation.. 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-17). Supporting source: Product topology/sizing basis — https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/requirements.html. Supporting source: Current AWS documentation: 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: EKS standard versus extended support pricing — https://aws.amazon.com/eks/pricing/.

- Release snapshot / cadence: Documented. The self-hosted Helm chart v2.13.0 release notes are dated November 12, 2026. They list SUSE Observability 2.13.0, Values helper chart 1.4.13 (deprecated since 2.8.0), Agent 1.7.64 and CLI 3.9.0. Component versions are separate; apply every version-specific upgrade step from the installed version through 2.13.0, including the changed scheduling precedence. Scope: Dated SUSE Observability self-hosted Helm release snapshot; the deprecated Values helper chart is not a universal installation requirement. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/release-notes/v2.13.0.html (reviewed 2026-11-18).







## SUSE Security (NeuVector)

Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.

- Listing: https://launchinyourcloud.com/directory/suse-security-neuvector/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.
- Licensing model: open-source
- Installation: SUSE Security Helm chart or manifests on public-cloud Kubernetes
- Architecture: Manager, controller and scanner services plus an enforcer DaemonSet inside the customer Kubernetes cluster.
- Operations: Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
- Product website: https://www.suse.com/products/security/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.

NeuVector is Apache-2.0 licensed. SUSE subscriptions can add entitled delivery, integrations and support.

SUSE Security runs controller, scanner and enforcement workloads on customer Kubernetes nodes.


### Category fit

- devops: Adds runtime security, vulnerability scanning and policy enforcement to customer Kubernetes delivery environments.

- observability: Provides workload, network and security-event visibility for Kubernetes clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 


### Cloud deployment evidence

- SUSE Security on six named public-cloud Kubernetes services (aws, azure, gcp, ibm, alibaba, oci): https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html
  SUSE explicitly names AWS EKS, Azure AKS, Google Cloud, IBM Cloud Kubernetes, Alibaba Cloud and Oracle Cloud and links full Kubernetes/Helm application deployment. Confirm tested platform versions and privileges. GKE Autopilot requires allowlists; AWS ECS is no longer supported in the requirements guide.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

NeuVector publishes contribution/governance instructions and maintained public application and Helm releases. This is sustained upstream participation rather than a star-count threshold; commercial SUSE support remains a separately purchased entitlement.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/blob/main/CONTRIBUTING.md

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/releases/tag/v5.6.4

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4

### Sources

- Deploy SUSE Security on public-cloud Kubernetes: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html

- Deploy SUSE Security with Helm: https://documentation.suse.com/cloudnative/security/latest/en/helm.html

- SUSE Security support matrix: https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/

- NeuVector Apache 2.0 license: https://github.com/neuvector/neuvector/blob/main/LICENSE

### Licensing sources

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

### Infrastructure sources

- https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html


### 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. SUSE’s security guide routes AWS procurement through its multi-product Rancher/SUSE subscription offer. The current offer is a private-offer commercial contract labelled SaaS delivery; it is not a standalone upstream OSS AMI or proof of included NeuVector support. Confirm the Security entitlement in the order. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html (reviewed 2026-11-18). Supporting source: Actual SUSE Cloud Marketplace Program offer — https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw. Offer prodview-b6es6ar6n4siw: SUSE; SaaS-labelled multi-product private-offer subscription; https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw.

- Cloud commitment eligibility: Sources checked — unresolved. The multi-product private-offer route does not settle the buyer’s commitment eligibility or whether SUSE Security is included in the selected contract. Confirm exact entitlement, billable dimensions and cloud agreement. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw (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. The v5.6 guide documents SAML 2.0 SSO, including Okta and group-to-role mapping. Signed assertions are required; encrypted assertions are not supported by this documented configuration. Set a deliberate default role rather than assuming group import grants appropriate access. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. SAML group-to-role mapping does not establish a SCIM server or provisioning/deprovisioning operations. Confirm a current endpoint and user-removal behavior for the selected OSS or subscription-delivered edition. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- Compliance attestations: Documented. LRQA certificate 10726335 covers SUSE’s ISO/IEC 27001:2022 ISMS and ISO/IEC 27701:2019 PIMS; schedule page 28 explicitly includes NeuVector, LLC. Issued November 4, 2025, it expires November 3, 2028. This is organisational information/privacy management assurance, not certification of a customer’s NeuVector cluster, protected workloads, configuration or operations. Scope: SUSE organisational management systems including the scheduled NeuVector entity; not a customer-deployment attestation. Source: https://www.suse.com/support/security/certifications/SUSE-ISO-27001-ISO-27701.pdf (reviewed 2026-11-18). Supporting source: Official SUSE certificate index — https://www.suse.com/support/security/certifications/isoiec-certification/.

- Security controls: Documented. NeuVector documents SAML role mapping and signed-assertion requirements. Enforcers run on cluster nodes and controllers coordinate security policy, so deployment needs the documented privileged access and network visibility. Scope cluster roles and protect console/controller access. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18). Supporting source: Runtime and component requirements — https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html. Supporting source: Cloud network and topology requirements — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- Air-gapped operation: Documented. The air-gap guide mirrors charts and images using Skopeo/zstd, transfers them and deploys from an internal registry. Its example versions are older than the current 5.6 line; resolve matching current application/chart/scanner versions and arrange offline vulnerability-database updates. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/airgap.html (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. NeuVector maintains a Helm chart for manager/controller/enforcer/scanner deployment. The reviewed chart release is v2.11.4, separate from application v5.6.4. Pin image tags and check values/privileges; air-gap documentation’s historical chart example is not a current version pin. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/latest/en/helm.html (reviewed 2026-11-18). Deployment artifact: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4. Artifact reference: NeuVector Helm chart v2.11.4.

- Minimum footprint / sizing: Documented. The requirements recommend three controllers for HA, an enforcer on each worker and separate scanner/manager resources. Controller minimum is 1 CPU/2 GB; an enforcer needs 1+ CPU/1 GB and a scanner 1 CPU/2 GB before workload growth. The public-cloud guide warns against multiple managers behind a load balancer because of session state, while requirements suggest manager redundancy; resolve that design before claiming full HA. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Manager scaling caveat and cloud topology — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- License pricing: Documented. Upstream NeuVector is Apache 2.0 licensed. SUSE subscription-delivered images, support and Rancher Prime integrations may require commercial entitlements. The multi-product AWS order is distinct from the free upstream code licence. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/blob/main/LICENSE (reviewed 2026-11-18). Supporting source: SUSE commercial procurement path — https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html.

- Operating cost estimate: Sources checked — unresolved. Size by protected Kubernetes node count, network throughput, container/image scan volume, registry retention and HA controller/scanner design, not directory users. Include per-node enforcers, scan capacity, persistent configuration and any SUSE support subscription. The manager redundancy conflict also needs resolution. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (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. NeuVector v5.6.4 was published October 27, 2026; chart v2.11.4 is a separate release. When upgrading from before v5.6.0, SUSE requires restarting/redeploying existing scanner pods for critical CVE severity handling. Maintenance releases on older branches are not a newer major-line snapshot. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/releases/tag/v5.6.4 (reviewed 2026-11-18). Supporting source: 5.6.4 upgrade and scanner requirements — https://documentation.suse.com/cloudnative/security/5.6/en/5x.html. Supporting source: Separate chart release — https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4.




### Security and lifecycle reviews

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

- NeuVector scanner restart required for critical-severity results (security-advisory): SUSE requires existing scanner pods to restart or redeploy when upgrading from before 5.6.0 to 5.6.4 or later, so cached capabilities recognize critical CVE severity. Scope: Upgrades from pre-5.6.0 controllers with existing scanner pods; not a claim of a new exploitable vulnerability in every NeuVector installation. Conditions: Older scanners cache the controller capability response. SUSE also calls for current scanner/CVE database content for PHP vulnerability checks. Action: Follow the 5.6.4 scanner restart and database-update instructions, including the transfer process in isolated environments. Source: https://documentation.suse.com/cloudnative/security/5.6/en/5x.html; reviewed 2026-11-18.




## SYSPRO Customer-Managed

Customer-managed ERP with sales-contract pricing and stock-item controls.

- Listing: https://launchinyourcloud.com/directory/syspro/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: Licensed SYSPRO Installer and application packages on Azure Windows servers
- Architecture: Windows application services and Azure SQL Managed Instance or SQL Server on an Azure VM.
- 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://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure server deployment is separate from vendor-operated Syspro Cloud ERP. The vendor's 2026 licensing notice moves customers to named-user subscriptions on regional expiry dates. Confirm the actual contract and current installer before using older SQL Managed Instance recipes; contract-compliance functions do not establish environmental or regulatory certification. The October 2026 module guide describes active customer contracts, allowed stock items and agreed prices in sales orders, quotes and returns; it does not establish legal drafting or a full contract-lifecycle suite.

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

Windows application services and Azure SQL Managed Instance or SQL Server on an Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-managed ERP with sales, financial and inventory functions.

- contract-management: Contract Compliance Management checks customer contract stock items, dates and prices during sales-order and related transactions; this is a commercial sales-control module, rather than a legal contract-lifecycle suite.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm (checked 2026-11-19). 


### Cloud deployment evidence

- Azure SQL Managed Instance (azure): https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm
  Windows application services and Azure SQL Managed Instance or SQL Server on an Azure VM. The Azure server deployment is separate from vendor-operated Syspro Cloud ERP. The vendor's 2026 licensing notice moves customers to named-user subscriptions on regional expiry dates. Confirm the actual contract and current installer before using older SQL Managed Instance recipes; contract-compliance functions do not establish environmental or regulatory certification.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure SQL Managed Instance: https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm

- Azure SQL MI Guide PDF: https://help.syspro.com/syspro-8-2019-r1/resources/pdfs/syspro-8-sql-managed-instance-reference-guide.pdf

- Contract Compliance Guide PDF (Oct 2026): https://help.syspro.com/syspro-8-2026-r2/resources/pdfs/2026-release/topics/contract-compliance-management.pdf

- SYSPRO Legal & Terms: https://trust.syspro.com/legal/

- Subscription Licensing Notice: https://www.syspro.com/formal-notice-change-to-syspro-licensing/

- Syspro Installer EULA: https://help.syspro.com/syspro-8-installer/i-installation/sys-8-install-installer/sys-8-install-installer.htm

- Updating to 2026 R2 PDF: https://help.syspro.com/syspro-8-2025/resources/pdfs/2026-release/technical/sys-8-updating-to-2026-r2.pdf

### Licensing sources

- https://trust.syspro.com/legal/

- https://www.syspro.com/formal-notice-change-to-syspro-licensing/

- https://help.syspro.com/syspro-8-installer/i-installation/sys-8-install-installer/sys-8-install-installer.htm

### Infrastructure sources

- https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SYSPRO documents identity-provider integration with Google, Microsoft and LinkedIn for both Desktop and Web UI (Avanti). Windows/Active Directory SSO is a distinct Desktop path and does not apply to Avanti. Configure the relevant identity-provider and operator settings for the installed release. Scope: SYSPRO 8 2025 identity-provider integration; Desktop and Web UI credentials are configured separately. Source: https://help.syspro.com/syspro-8-2025/g_programs/imp/impssi/impssi.htm (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 SYSPRO Installer installs SYSPRO 8 components and hotfixes using SYSPRO Online Profile credentials and licence-controlled downloads. It manages deployment groups spanning servers, services and clients; it is a vendor installer, not a public cloud IaC template. Scope: SYSPRO 8 installer and entitled software availability; select compatible application and installer releases. Source: https://help.syspro.com/syspro-8-2025/i-installation/sys-8-install-installer/sys-8-install-installer.htm (reviewed 2026-11-20).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed installer documentation identifies a deployment group containing application servers, services and clients, but does not establish a quantitative CPU/RAM/storage floor for the selected ERP modules and database. A release- and workload-specific sizing design is still needed. Scope: Complete customer-managed SYSPRO deployment, including SQL and optional services; not installer-only prerequisites. Source: https://help.syspro.com/syspro-8-2025/i-installation/sys-8-install-installer/sys-8-install-installer.htm (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Tableau Server

Commercial analytics and business-intelligence server installed and operated on customer cloud virtual machines.

- Listing: https://launchinyourcloud.com/directory/tableau-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Tableau Server product-key licensing with user-, core- or subscription-based entitlements.
- Licensing model: commercial-only
- Installation: Native server installer on customer virtual machines; optional AWS CloudFormation, Azure Resource Manager or marketplace BYOL paths
- Architecture: Customer-operated Tableau Server on cloud virtual machines in a single-node or distributed topology.
- Operations: Customer manages the virtual machines, operating system, Tableau services, identity, networking, storage, backups, upgrades and availability.
- Product website: https://www.tableau.com/products/server
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

Tableau's provider-specific public-cloud guides are archived and no longer updated, although Tableau states that these deployments remain supported. Native virtual-machine self-deployment is the consistently documented production-ready path; marketplace and Quick Start options are convenience paths and should not be treated as the preferred production architecture. Tableau recommends Tableau Cloud where it meets the customer's requirements.

Tableau Server requires a commercial product key and the applicable user-, core- or subscription-based entitlement. Tableau Cloud is a separate hosted offering.

The production self-managed path installs Tableau Server on persistent cloud virtual machines; distributed deployments use multiple nodes and external cloud services.


### Category fit

- data-analytics: Enterprise analytics, governed data exploration, dashboards and business-intelligence publishing on a customer-operated server.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm (checked 2026-11-17). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm (checked 2026-11-17). 


### Cloud deployment evidence

- Tableau Server on Amazon Web Services (aws): https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm
  Tableau documents customer-managed EC2 installation as the production-ready AWS path. The provider guide is archived, but Tableau states the deployment remains supported.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Tableau Server on Microsoft Azure (azure): https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm
  Tableau documents customer-managed Azure VM installation as the production-ready path. The provider guide is archived, but Tableau states the deployment remains supported.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Tableau Server on Google Cloud (gcp): https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm
  Tableau documents production-ready self-deployment on customer Google Compute Engine virtual machines with BYOL operation. The provider guide is archived.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Tableau Server on Alibaba Cloud (alibaba): https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm
  Tableau documents production-ready self-deployment on customer Alibaba Elastic Compute Service virtual machines with BYOL operation. The provider guide is archived.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Tableau Server public-cloud overview: https://help.tableau.com/current/server-linux/en-us/ts_tableau_server_cloud_overview.htm

- Tableau Server administrator overview: https://help.tableau.com/current/server/en-us/admin.htm

- AWS deployment options: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm

- Azure deployment options: https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm

- Google Cloud deployment options: https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm

- Alibaba Cloud deployment options: https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm

- AWS prerequisites and licensing: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm

### Licensing sources

- https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm

### Infrastructure sources

- https://help.tableau.com/current/server-linux/en-us/ts_tableau_server_cloud_overview.htm

- https://help.tableau.com/current/server/en-us/admin.htm


### 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. Archived AWS/Azure deployment guides identify Marketplace paths with production-readiness warnings. A current production-ready offer and entitlement were not confirmed. Scope: Reviewed public evidence for Tableau Server; unresolved within this edition/deployment. Source: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The reviewed Server deployment/licensing material does not establish a qualifying software Marketplace offer and buyer commitment treatment. Scope: Reviewed public evidence for Tableau Server; unresolved within this edition/deployment. Source: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm (reviewed 2026-11-17).

- Single sign-on: Documented. The Server SCIM guide explicitly supports site-specific SAML, TSM authentication and identity pools with version qualifications. Configure the chosen Server identity method and network reachability separately from provisioning. Scope: Server identity methods applicable to SCIM. Source: https://help.tableau.com/current/server/en-us/scim_config_online.htm (reviewed 2026-11-17).

- SCIM provisioning: Documented. Server supports site-level SCIM from 2025.3. Site-specific SAML works from 2025.3.0; TSM-configured authentication and identity pools require 2025.3.1+. Entra/Okta may need an on-premises provisioning connector through the server firewall. Scope: Tableau Server SCIM; not Tableau Cloud-only documentation. Source: https://help.tableau.com/current/server/en-us/scim_config_online.htm (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Tableau Server 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://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Security controls: Documented. The offline activation guide distinguishes product keys and ATR workflows. Protect transferred activation files and configure server identity and permissions separately; disconnected activation does not confer a security attestation. Scope: Server offline activation and licence handling. Source: https://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. Offline Server activation is documented, but this alone does not establish isolation for every connector, extension, update and identity dependency. Confirm the selected full deployment and licence workflow. Scope: Offline activation versus complete air-gapped operation. Source: https://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Vendor cloud guides describe installing Server on customer VMs. Archived AWS/Azure Quick Start and Marketplace routes carry production-readiness warnings; use a supported self-deployment design and installation media. Scope: Customer-managed Server; archived automation warnings retained. Source: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The production single-node recommendation is 8 physical cores/16 vCPU, 128 GB RAM for 2022.3+ and at least 50 GB disk. Multi-node/HA design needs Tableau guidance; extracts, refresh scratch space and backups add storage. Scope: Production single-node recommendation, not the complete HA design. Source: https://help.tableau.com/current/server/en-us/server_hardware_min.htm (reviewed 2026-11-17).

- License pricing: Documented. Tableau Server requires a commercial product key and the applicable user-, core- or subscription-based entitlement. Tableau Cloud is a separate hosted offering. Scope: Tableau Server: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Obtain the supported multi-node/HA design, user-role licence mix, extract/refresh workload, repository/file-store sizing and any Windows licences. Single-node production recommendations do not price an HA farm. 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://help.tableau.com/current/server/en-us/server_hardware_min.htm (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Tableau Server 2026.3 was released 2026-10-23. The release page warns Windows Server 2016/Windows 10 users to review installation issue W-24614917 before upgrading; this is Server, not Tableau Cloud/Desktop. Scope: Tableau Server vendor release record. Source: https://www.tableau.com/support/releases/server/2026.3 (reviewed 2026-11-17).







## Teleport Enterprise Self-Hosted

Commercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.

- Listing: https://launchinyourcloud.com/directory/teleport-enterprise-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Teleport Enterprise Self-Hosted subscription and license file required.
- Licensing model: commercial-only
- Installation: Teleport Helm charts on EKS, AKS or GKE; official Terraform deployment paths are also documented
- Architecture: Customer-operated Teleport Auth and Proxy services with provider databases, object storage, DNS and load balancing.
- Operations: Customer manages Kubernetes or VMs, backend state, storage, DNS, TLS, upgrades, capacity, backups and the Enterprise license.
- Product website: https://goteleport.com/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers Enterprise Self-Hosted, not Teleport Enterprise Cloud. Community licensing and feature availability differ; confirm the purchased edition and current upgrade compatibility.

The selected Enterprise Self-Hosted edition requires a commercial subscription and license file.

Teleport runs persistent authentication and proxy services with provider-backed state and network dependencies.


### Category fit

- identity-access-management: Provides identity-aware access to servers, Kubernetes, databases and applications through customer-operated authentication and proxy services.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://goteleport.com/docs/installation/self-hosted/helm-deployments/aws/ (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://goteleport.com/docs/installation/self-hosted/helm-deployments/azure/ (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://goteleport.com/docs/installation/self-hosted/helm-deployments/gcp/ (checked 2026-11-18). 


### Cloud deployment evidence

- Teleport Enterprise on AWS EKS (aws): https://goteleport.com/docs/installation/self-hosted/helm-deployments/aws/
  Teleport documents a full HA Auth and Proxy deployment on customer EKS with AWS backing services.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Teleport Enterprise on Azure AKS (azure): https://goteleport.com/docs/installation/self-hosted/helm-deployments/azure/
  Teleport documents a full HA deployment on customer AKS.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Teleport Enterprise on Google GKE (gcp): https://goteleport.com/docs/installation/self-hosted/helm-deployments/gcp/
  Teleport documents a full HA deployment on customer GKE.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Self-hosting Teleport: https://goteleport.com/docs/installation/self-hosted/

- Teleport deployment guides: https://goteleport.com/docs/installation/self-hosted/deployments/

- Teleport on AWS EKS: https://goteleport.com/docs/installation/self-hosted/helm-deployments/aws/

- Teleport on Azure AKS: https://goteleport.com/docs/installation/self-hosted/helm-deployments/azure/

- Teleport on Google GKE: https://goteleport.com/docs/installation/self-hosted/helm-deployments/gcp/

### Licensing sources

- https://goteleport.com/docs/installation/self-hosted/

- https://goteleport.com/docs/feature-matrix/

### Infrastructure sources

- https://goteleport.com/docs/installation/self-hosted/deployments/


### 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: Sources checked — unresolved. Teleport’s Marketplace announcement describes cloud or self-hosted deployment, but the linked current AWS offer prodview-fnmgbsyr3kwko prices its dimension as Cloud only and excludes support. It does not establish self-hosted licence terms. Obtain a self-hosted order/private-offer identifier, entitlement and support terms rather than transferring the public Cloud price to this deployment. Scope: Current linked public AWS offer versus separately negotiated Enterprise Self-Hosted entitlement. Source: https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko (reviewed 2026-11-18). Supporting source: Broader vendor Marketplace announcement — https://goteleport.com/about/newsroom/press-releases/teleport-infrastructure-identity-platform-in-aws-marketplace-ai-agents-tools/.

- Cloud commitment eligibility: Sources checked — unresolved. The linked AWS public offer prices Cloud only; it does not establish eligible spend for Enterprise Self-Hosted. Confirm a self-hosted private offer, its billed entitlement/support dimensions and the buyer’s applicable AWS commitment terms. Do not transfer the public Cloud offer’s procurement or credits to a self-hosted order. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko (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: Edition-dependent. The feature matrix assigns SAML and OIDC SSO to Enterprise Self-Hosted. Configure the IdP connector, roles and login policy; the Community GitHub-login option is a separate edition boundary. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/feature-matrix/ (reviewed 2026-11-18).

- SCIM provisioning: Edition-dependent. Teleport Enterprise Identity Governance documents SCIM 2.0 for users/groups with SAML SSO, OAuth client credentials and matching Access Lists. It requires v17.6.1 or v18.0.3+; the IdP pushes changes into Teleport, not the reverse. Confirm the Identity Governance entitlement and tested deactivation/session-lock behavior. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/identity-governance/integrations/scim/ (reviewed 2026-11-18).

- Compliance attestations: Edition-dependent. Teleport’s v18.11.10 documentation identifies BoringCrypto fips-20220613, CMVP 4735, in Enterprise FIPS builds from 17.7.3/18.0.0. NIST lists the FIPS 140-3 Level 1 module as active, with a July 22, 2029 sunset and approved-mode/tested-configuration conditions. This validates the cryptographic module, not Teleport as a whole, every OS/CPU combination or a customer’s FedRAMP authorisation. Scope: Enterprise FIPS-build cryptographic-module boundary; operating environment and approved-mode conditions still require assessment. Source: https://github.com/gravitational/teleport/blob/v18.11.10/docs/pages/zero-trust-access/compliance-frameworks/fedramp.mdx (reviewed 2026-11-18). Supporting source: NIST module status, caveats and tested configurations — https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4735.

- Security controls: Documented. The chart separates Auth/Proxy services and configures TLS, backing storage and Enterprise licence secrets. Avoid treating standalone local storage as HA. Authentication, roles, short-lived certificates, audit/session storage and backup protection need an explicit deployment policy. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/reference/helm-reference/teleport-cluster/ (reviewed 2026-11-18). Supporting source: HA scaling and service separation — https://goteleport.com/docs/reference/deployment/scaling/. Supporting source: Identity governance provisioning controls — https://goteleport.com/docs/identity-governance/integrations/scim/.

- Air-gapped operation: Edition-dependent. Teleport explicitly supports fully air-gapped clusters, including privately reachable Auth and Proxy services. Enterprise uses a local licence file. Automatic licence updates require api.teleport.sh, but the cluster continues without that access while its local licence remains valid. Transfer renewed licences and release artifacts deliberately, and provide internal IdP, DNS, certificates, audit/storage backends and client access. Scope: Fully self-hosted Teleport Enterprise with a valid local licence and internally reachable dependencies. Source: https://goteleport.com/docs/reference/deployment/networking/ (reviewed 2026-11-18). Supporting source: Offline licence behavior and expiry boundary — https://goteleport.com/docs/installation/self-hosted/license/. Supporting source: Vendor statement of air-gapped self-hosting — https://goteleport.com/use-cases/data-centers/.

- Deployment artifact / IaC: Documented. The upstream teleport-cluster Helm chart configures Enterprise images using enterprise: true and a customer licence secret. The reviewed chart source is pinned to v18.11.10. Follow the separate EKS/AKS/GKE backend and network configuration guides. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/reference/helm-reference/teleport-cluster/ (reviewed 2026-11-18). Deployment artifact: https://github.com/gravitational/teleport/tree/v18.11.10/examples/chart/teleport-cluster. Artifact reference: Teleport v18.11.10 chart source.

- Minimum footprint / sizing: Documented. Teleport publishes an illustrative HA configuration for up to 10,000 SSH nodes: two Proxy instances at 4 vCPU/8 GB and two Auth at 8 vCPU/16 GB, with appropriate external storage. It is a scale example, not the minimum for 100 users. Kubernetes API request rate, sessions, registered clusters and recording volume require measurement. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/reference/deployment/scaling/ (reviewed 2026-11-18).

- License pricing: Documented. The June 16, 2026 Enterprise guide bills Monthly Active Users and Teleport Protected Resources, with Standard/Premium feature bundles; Priority Support is included for self-hosted deployments. It publishes metric definitions, not numeric rates. Request a self-hosted quote with protected resources, machine identities and entitlements; public Cloud Marketplace prices are not self-hosted rates. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/api/files/teleport-pricing-guide.pdf (reviewed 2026-11-18). Supporting source: Public offer explicitly prices Cloud only — https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko.

- Operating cost estimate: Sources checked — unresolved. The current pricing guide defines MAUs and hourly/monthly averaged Protected Resources but gives no rates. One hundred internal users is at most a user assumption, not a resource or machine-identity count; 1 TB is not a session-recording retention model. Supply MAUs, protected resources/bots, recording volume/retention, auth/proxy/backend HA design and a self-hosted licence quote before completing the AWS us-east-1 budget. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://goteleport.com/api/files/teleport-pricing-guide.pdf (reviewed 2026-11-18). Supporting source: Self-hosted topology and backend sizing — https://goteleport.com/docs/reference/deployment/scaling/. 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. Teleport v18.11.10 was published November 16, 2026. Match Enterprise images, cluster chart, clients and Terraform provider to the supported upgrade path. Community repository publication does not itself establish the buyer’s commercial support term. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://github.com/gravitational/teleport/releases/tag/v18.11.10 (reviewed 2026-11-18). Supporting source: Teleport application change log — https://goteleport.com/docs/changelog/.







## Terraform Enterprise

Commercial self-hosted Terraform collaboration and infrastructure-automation platform.

- Listing: https://launchinyourcloud.com/directory/terraform-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Terraform Enterprise license required.
- Licensing model: commercial-only
- Installation: Official HashiCorp Terraform modules for EC2, EKS, Azure VMs, AKS, GCE or GKE; Kubernetes or OpenShift workflow on IBM Cloud
- Architecture: Containerized Terraform Enterprise application with customer-managed runtime, data storage and worker capacity
- Operations: Customer manages compute or Kubernetes, PostgreSQL and object storage, cache, networking, TLS, identity, worker images, backups, scaling, upgrades and licensing.
- Product website: https://developer.hashicorp.com/terraform/enterprise
- 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 Terraform Enterprise, the self-hosted distribution, not HCP Terraform. Match the selected runtime to the current compatibility matrix and review the module's IAM, managed-identity, database, object-storage and network requirements before applying it.

Terraform Enterprise is a commercial self-hosted product and requires a valid license file or license server configuration.

Terraform Enterprise runs as persistent containers on VM or Kubernetes runtimes with durable database and object-storage dependencies.


### Category fit

- devops: Provides self-hosted infrastructure-as-code runs, workspaces, policy controls, private registry and team workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (checked 2026-11-15). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (checked 2026-11-15). 


### Cloud deployment evidence

- Official Terraform Enterprise modules and provider guidance (aws, azure, gcp): https://developer.hashicorp.com/terraform/enterprise/deploy
  HashiCorp lists official Terraform Enterprise modules for AWS EC2 and EKS, Azure VMs and AKS, and Google GCE and GKE, together with provider-specific deployment guidance for customer environments.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Terraform Enterprise on IBM Cloud (ibm): https://developer.hashicorp.com/terraform/enterprise/deploy
  HashiCorp explicitly directs IBM Cloud Kubernetes Service users to its Kubernetes deployment workflow, and Red Hat OpenShift users to its OpenShift workflow. It also links the IBM Cloud deployable architecture. This is separate from the EC2, Azure and Google Cloud validated modules.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Terraform Enterprise deployment overview and cloud modules: https://developer.hashicorp.com/terraform/enterprise/deploy

- Terraform Enterprise license configuration: https://developer.hashicorp.com/terraform/enterprise/deploy/configuration/license

### Licensing sources

- https://developer.hashicorp.com/terraform/enterprise/deploy/configuration/license

### Infrastructure sources

- https://developer.hashicorp.com/terraform/enterprise/deploy


### 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 validates SAML 2.0 integration and requires connectivity to the identity provider metadata endpoint at login. Configure the Enterprise identity integration and recovery access; an air-gapped deployment needs a reachable internal IdP. Scope: Terraform Enterprise SAML login and metadata connectivity. Source: https://developer.hashicorp.com/validated-designs/terraform/installation-guide/air-gapped-configuration (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. HashiCorp links official deployment modules for AWS EC2/EKS, Azure VM/AKS and Google Cloud GCE/GKE. Select a supported Enterprise version, runtime and storage arrangement before using the appropriate module. A module is not a software license. Scope: Terraform Enterprise flexible deployment overview and HashiCorp Validated Designs. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The validated design gives per-node application baseline 4 vCPUs/32 GB/1 TB, PostgreSQL 4 cores/32 GB/2 TB, and Redis 4 cores/16 GB/500 GB. It notes larger initial application nodes are common. Execution concurrency, per-run memory, availability and object storage require separate sizing. Scope: Vendor validated-design baseline; execution workers and HA topology additional. Source: https://developer.hashicorp.com/validated-designs/terraform/installation-guide/detailed-design (reviewed 2026-11-20).

- License pricing: Documented. HashiCorp identifies Terraform Enterprise as closed-source commercial software. It requires Enterprise entitlement; Terraform CLI source-available terms do not license the Enterprise service. The reviewed product documentation does not establish a numeric price; obtain a current licence/support quote. Scope: Terraform Enterprise commercial licensing; CLI and HCP pricing excluded. Source: https://developer.hashicorp.com/terraform/docs/glossary (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## TheHive Self-Hosted

Self-hosted security incident-response case management for investigations and analyst collaboration.

- Listing: https://launchinyourcloud.com/directory/thehive/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial plans; verify current Community Edition limitations and terms
- Licensing model: commercial-only
- Installation: Docker Compose, packages or Kubernetes installation.
- Architecture: Customer-operated incident-response application and supporting data services
- Operations: Customer manages infrastructure, backup and version upgrades; optional vendor support depends on the plan.
- Product website: https://strangebee.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 covers self-hosted TheHive. Its investigation scope is cybersecurity, so it is an adjacent alternative to broader business-incident workflows. Current licensing and Community use restrictions should be checked before procurement. AWS and Azure offer documented vendor v5 images; the evidence notes identify the applicable release and maintenance policy.

The current listed TheHive product uses vendor license plans and activation. Community is a restricted free non-commercial edition, not the historical open-source release; free availability is not an open-source license grant. This label concerns proprietary licensing, not whether every plan has a fee.

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.


Deployment qualification: Official current TheHive6 documentation publishes Docker Compose installation instructions and operational requirements. Suitable portable self-hosting, without inferring cloud-account support from vendor-managed cloud marketing. The provider-specific evidence separately covers the vendor v5 AWS image; it does not extend v6 container portability into a cloud-image claim.

### Category fit

- incident-investigation-management: Dedicated cybersecurity incident-response and investigation case platform. Relevant to security cases, tasks and observables; not a general HR, regulatory-complaint or physical-safety investigation product.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.strangebee.com/resources/iaas/aws/thehive/ (checked 2026-11-12). Source: https://aws.amazon.com/marketplace/pp/prodview-gcjij3iscupae (checked 2026-11-12). Source: https://docs.strangebee.com/thehive/installation/release-and-maintenance-policy/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.strangebee.com/thehive/installation/release-and-maintenance-policy/ (checked 2026-11-12). Source: https://docs.strangebee.com/resources/iaas/azure/thehive/ (checked 2026-11-12). 


### Cloud deployment evidence

- StrangeBee official TheHive v5 AMI deployment instructions (aws): https://docs.strangebee.com/resources/iaas/aws/thehive/
  StrangeBee documents the TheHive v5 AMI, EC2 launch, dedicated EBS volumes, initialization and restoration in the customer VPC. This badge covers that version-specific cloud distribution, not a verified TheHive v6 image. Select a maintained release and its current patch, confirm license entitlement, and provide the documented HTTPS reverse proxy or load balancer.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Official TheHive AWS image release and customer licensing scope (aws): https://aws.amazon.com/marketplace/pp/prodview-gcjij3iscupae
  The StrangeBee listing identifies an EC2 AMI, a v5.6.1 image and separately obtained vendor licenses. Infrastructure is launched through the customer AWS account. The displayed image is not proof of the newest patch or of v6 availability; follow the vendor maintenance policy and confirm the image/version before use.
  Source type: marketplace-offer; reviewed: 2026-11-12; vendor support: not-assessed.

- TheHive maintained releases and patch policy (aws, azure): https://docs.strangebee.com/thehive/installation/release-and-maintenance-policy/
  The vendor still maintains the 5.6, 5.7 and 5.8 series as of this review and requires the latest patch within a maintained series. This release policy qualifies the v5 image path; it does not establish a separate provider deployment or certify the displayed marketplace image as fully patched.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- StrangeBee TheHive v5 Azure image deployment (azure): https://docs.strangebee.com/resources/iaas/azure/thehive/
  StrangeBee documents launching its TheHive v5 Azure VM image, attaching the required data disks and initializing or restoring the application, with a Terraform option. This is the same maintained v5 distribution scope as the AWS image path; select a maintained series and current patch, with the required license and HTTPS configuration. It does not establish a v6 image.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker deployment guide: https://docs.strangebee.com/thehive/installation/docker/

- Product and self-hosting overview: https://strangebee.com/thehive-community-edition/

- Current plan and license options: https://strangebee.com/thehive-pricing/

- Licensing and edition terms: https://docs.strangebee.com/thehive/installation/licenses/about-licenses/

- StrangeBee TheHive v5 Azure image deployment: https://docs.strangebee.com/resources/iaas/azure/thehive/

### Licensing sources

- https://docs.strangebee.com/thehive/installation/licenses/about-licenses/

- https://strangebee.com/thehive-community-edition/

### Infrastructure sources

- https://docs.strangebee.com/thehive/installation/docker/

- https://strangebee.com/thehive-community-edition/


### 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. StrangeBee sells an official AWS AMI; the reviewed offer packages TheHive 5.6.1 with Cassandra 4 and Elasticsearch 7. The software license is purchased outside AWS Marketplace, and infrastructure charges are separate. Do not substitute TheHive 6 requirements for this image. Scope: Vendor-published TheHive v5 AMI; not a current-upstream-version or commitment-credit claim. Source: https://aws.amazon.com/marketplace/pp/prodview-gcjij3iscupae (reviewed 2026-11-14). Offer prodview-gcjij3iscupae: StrangeBee; AMI; external software license; package v5.6.1-1; https://aws.amazon.com/marketplace/pp/prodview-gcjij3iscupae.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The current authentication guide requires a paid plan for non-local providers and Platinum or ONE for Active Directory, OAuth2, OpenID and SAML. Configure the selected provider and account lifecycle explicitly; Community/local login does not grant the paid federation options. Scope: Current TheHive user federation; paid Platinum/ONE entitlement. Source: https://docs.strangebee.com/thehive/administration/authentication/configure-authentication/ (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. StrangeBee publishes Docker Compose production profiles in its deployment repository. These are single-server deployments with supporting services; demo and clustered installations follow separate guides. Scope: TheHive 6 On-prem production Compose profiles. Source: https://docs.strangebee.com/thehive/installation/docker/ (reviewed 2026-11-14). Deployment artifact: https://github.com/StrangeBeeCorp/docker. Artifact reference: repository default branch (moving; select the matching profile/release).

- Minimum footprint / sizing: Documented. Current Docker deployment guidance distinguishes testing at 4 vCPU/8 GB RAM from standard production at 4 vCPU/16 GB and higher-performance production at 8 vCPU/32 GB. Package guidance separately allocates resources to TheHive, Cassandra and Elasticsearch. These profiles need workload/storage and cluster validation rather than representing every release or HA topology. Scope: Current TheHive 6 documentation profiles; not a version-5 or reference-workload capacity guarantee. Source: https://docs.strangebee.com/thehive/installation/system-requirements/ (reviewed 2026-11-21).

- License pricing: Documented. The vendor offers annual paid subscriptions with plan-specific authentication/support features and a separate Community licence with limits. Obtain the selected self-hosted plan, users/organisations, renewal and support terms; SaaS hosting and infrastructure are separate considerations. Scope: Current commercial self-hosted plans versus Community licensing. Source: https://strangebee.com/thehive-pricing/ (reviewed 2026-11-21). Supporting source: Licence framework — https://docs.strangebee.com/thehive/installation/licenses/about-licenses/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## ThingsBoard Self-Hosted

Source-available IoT device, telemetry and dashboard platform.

- Listing: https://launchinyourcloud.com/directory/thingsboard/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.
- Licensing model: source-available
- Installation: Kubernetes manifests
- Architecture: ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths.
- 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://thingsboard.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.

Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.

ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Source-available IoT device, telemetry and dashboard platform.

- observability: Source-available IoT device, telemetry and dashboard platform.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://thingsboard.io/docs/installation/azure/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://thingsboard.io/docs/installation/gcp/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS (aws): https://thingsboard.io/docs/installation/aws/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure (azure): https://thingsboard.io/docs/installation/azure/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP (gcp): https://thingsboard.io/docs/installation/gcp/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS: https://thingsboard.io/docs/installation/aws/

- Azure: https://thingsboard.io/docs/installation/azure/

- GCP: https://thingsboard.io/docs/installation/gcp/

- v4.4 Unification: https://thingsboard.io/docs/pe/installation/upgrade-from-ce/

- Smart Energy: https://thingsboard.io/use-cases/smart-energy/

- BUSL-1.1: https://github.com/thingsboard/thingsboard/blob/master/LICENSE

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

### Licensing sources

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

### Infrastructure sources

- https://thingsboard.io/docs/installation/aws/

- https://thingsboard.io/docs/installation/azure/

- https://thingsboard.io/docs/installation/gcp/


### 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 ThingsBoard guide configures OAuth2/OIDC clients and domain-specific callbacks for Web UI or mobile login, including Keycloak, Okta, Azure and social providers. Configure issuer/JWKS, trusted claims, tenant/customer mapping and account-creation policy. Device transport credentials and API tokens are separate; the selected release licence still applies. Scope: Current self-hosted ThingsBoard user login and identity mapping, distinct from device authentication. Source: https://thingsboard.io/docs/user-guide/oauth-2-support/ (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 a versioned application package, Java and database, then initializes the schema and starts the service. AWS guidance separates single-VM, EKS monolith and microservice topologies. Select matching application/manifests and dependencies, replace sample secrets, and configure TLS, persistence, mail and licence activation. Scope: Official native package installation; AWS reference topologies and provider images have separate versions. Source: https://thingsboard.io/docs/user-guide/install/ubuntu/ (reviewed 2026-11-20). Deployment artifact: https://github.com/thingsboard/thingsboard/releases/tag/v4.4.0.2. Artifact reference: v4.4.0.2 application package release; match provider image/manifests separately. Supporting source: Official AWS deployment choices — https://thingsboard.io/docs/installation/aws/.

- Minimum footprint / sizing: Documented. The Ubuntu guide distinguishes a 1-core/4 GB/20 GB proof of concept from small production at 2 cores/8 GB/50 GB SSD and a larger starting tier at 4+ cores/16+ GB/100+ GB SSD. Queue/database choices add resources; the heap example is not total host capacity. Device/message rate, retention and HA require separate sizing. Scope: Current single-host tier recommendations; not a 1 TB microservice/HA sizing guarantee. Source: https://thingsboard.io/docs/user-guide/install/ubuntu/ (reviewed 2026-11-20).

- License pricing: Edition-dependent. Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions. Scope: ThingsBoard Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/thingsboard/thingsboard/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## TiDB Community Self-Hosted

Open-source distributed SQL database with customer-operated cloud Kubernetes guides and a separately packaged third-party AWS VM option.

- Listing: https://launchinyourcloud.com/directory/tidb-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, azure, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: TiDB Operator and versioned Kubernetes resources on EKS/GKE/AKS; the Alibaba ACK Terraform recipe has older development/test version constraints; optional Techlatest AWS single-VM bundle is separately packaged and does not supply the Operator HA topology
- Architecture: TiDB, PD and TiKV services on customer Kubernetes node pools with persistent storage, or a separately reviewed third-party single-VM bundle; optional analytics and monitoring depend on the deployment.
- Operations: Customer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.
- Product website: https://www.pingcap.com/tidb/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers TiDB Community, not TiDB Cloud. AKS has a complete current guide even though the deployment FAQ omits it; that difference does not negate the documented path. The ACK guide is an older development/test recipe, while the current FAQ still names ACK. Match operator/database versions and validate production permissions, storage and HA before use. An alternative Techlatest AWS image packages TiDB OSS with Grafana/Prometheus on one VM. Package 1.0.2 does not identify the database components’ versions and is not an HA cluster or PingCAP support entitlement. Do not transfer Operator sizing, offline procedures or the upstream v8.5.8 snapshot to this image.

The TiDB repository is Apache-2.0 licensed. Managed TiDB Cloud services have separate terms.

TiDB runs persistent database/storage services on customer Kubernetes node pools, or as a separately packaged single-VM OSS bundle. The seller VM is not the Operator-based production HA topology.


### Category fit

- databases-vector: Provides a distributed SQL database with horizontally scaled storage and query services.

- data-analytics: Supports scalable transactional and analytical SQL workloads on a customer-operated cluster.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/ (checked 2026-11-18). Source: https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/ (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/ (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/ (checked 2026-11-18). 


### Cloud deployment evidence

- TiDB on Amazon EKS (aws): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/
  PingCAP documents customer EKS node pools, storage and TiDB Operator deployment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB on Google Kubernetes Engine (gcp): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/
  PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB Community on Azure AKS (azure): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/
  PingCAP provides a full AKS deployment guide with customer node pools, PD/TiKV/TiDB and monitoring manifests. A deployment guide establishes a documented path, not a commercial support contract.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB on Alibaba Cloud ACK (alibaba): https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/
  PingCAP’s v1.4 guide deploys a full cluster into customer ACK using Terraform and TiDB Operator and is scoped to development/testing. The current deployment FAQ still names ACK; old Terraform/image examples need a current-version production review.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed. Versions: TiDB Operator guide v1.4.

- Techlatest TiDB OSS single-VM bundle in customer EC2 (aws): https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html
  The seller guide subscribes to exact AWS offer prodview-ddl3tqewcoko4 and launches into the customer region/VPC/EC2 account. TiDB and its monitoring interfaces run on the VM. This is a separately packaged single-node option, not the Kubernetes HA path; package 1.0.2 leaves embedded database versions unreported. Restrict SSH/RDP and set the documented initial credentials.
  Source type: third-party-package; reviewed: 2026-11-18; vendor support: not-assessed. Edition: Repackaged open-source TiDB bundle. Versions: Seller package 1.0.2; embedded database versions unreported.


### Community and maintenance

PingCAP maintains the Apache-licensed database and operator with public contribution activity and supported LTS releases. Its named customer case-study catalog demonstrates adoption, while TiDB Cloud stories are kept separate from Community cloud evidence.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/pingcap/tidb/releases/tag/v8.5.8

- Official maintenance and adoption evidence: https://www.pingcap.com/case-studies/

- Official maintenance and adoption evidence: https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

### Sources

- TiDB Operator overview: https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

- Deploy TiDB on AWS EKS: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/

- Deploy TiDB on Google Cloud GKE: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/

- TiDB Apache 2.0 license: https://github.com/pingcap/tidb/blob/master/LICENSE

- TiDB Community on Azure AKS: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/

- TiDB on Alibaba Cloud ACK: https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/

- Current TiDB deployment FAQ: https://docs.pingcap.com/tidb/stable/deploy-and-maintain-faq/

- Exact third-party TiDB OSS AWS image: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4

- Seller customer-account VM deployment: https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html

### Licensing sources

- https://github.com/pingcap/tidb/blob/master/LICENSE

### Infrastructure sources

- https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

- https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html


### 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. Techlatest.net publishes TiDB with Grafana/Prometheus as AWS AMI prodview-ddl3tqewcoko4: a repackaged open-source single-VM bundle, package 1.0.2 on CentOS Stream 9. The reviewed t2.large option charges USD 0.13/hour for seller support plus AWS resources. This is an alternative to the Operator-based Kubernetes path, not that HA topology. The seller does not name embedded TiDB/TiKV/PD versions; inspect and pin them before production rather than inheriting the upstream release snapshot. Scope: Optional third-party TiDB Community VM delivery in the customer AWS account; independent from Operator/Kubernetes topology, package versions and support. Source: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4 (reviewed 2026-11-18). Supporting source: Seller single-VM installation and initial credentials — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html. Supporting source: TiDB Community upstream licence — https://github.com/pingcap/tidb/blob/master/LICENSE. Offer prodview-ddl3tqewcoko4: Techlatest.net; Amazon Machine Image (AMI), x86; single-VM bundle; package Seller package 1.0.2; embedded database versions unreported; https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Cloud commitment eligibility: Sources checked — unresolved. The upstream Community Apache licence has no subscription charge. The alternative Techlatest VM has a separately billed seller-support charge on AWS Marketplace, but its exact commitment eligibility is not established by the offer. Confirm the selected offer/contract and buyer’s AWS agreement; neither the free licence nor TiDB Cloud SaaS terms settle that transaction. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4 (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. Supporting source: Community licence — https://github.com/pingcap/tidb/blob/master/LICENSE.

- Single sign-on: Documented. TiDB Self-Managed v8.5 documents OIDC SSO for the TiDB Dashboard web UI, with Okta, Auth0 and self-hosted Casdoor examples. Dashboard encrypts/stores a SQL account password to complete an impersonated SQL sign-in after OIDC authentication. SQL password rotation requires reauthorization; disabling SSO erases the stored password. This establishes Dashboard sign-in only. A selected SQL client’s federated login and SCIM lifecycle require separate confirmation. Scope: TiDB Community/Self-Managed v8.5 Dashboard web UI, including its documented Kubernetes deployment; SQL-client SSO and the versions inside the third-party VM are assessed separately. Source: https://docs.pingcap.com/tidb/stable/dashboard-session-sso/ (reviewed 2026-11-18). Supporting source: Dashboard access on customer-operated Kubernetes — https://docs.pingcap.com/tidb-in-kubernetes/stable/access-dashboard/. Supporting source: Least-privileged Dashboard SQL users — https://docs.pingcap.com/tidb/stable/dashboard-user/. Supporting source: Protect Dashboard and privileged PD interfaces — https://docs.pingcap.com/tidb/stable/dashboard-ops-security/. Supporting source: Separate SQL JWT/LDAP authentication boundary — https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/.

- SCIM provisioning: Sources checked — unresolved. JWT and LDAP authentication do not establish SCIM user/group management or automatic SQL-account deprovisioning. A current Community endpoint and supported operations were not confirmed; review provisioning and token revocation separately. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. PingCAP’s Trust Hub advertises ISO and SOC assurances and requests certificate/report access. Its specific ISO announcement identifies TiDB Cloud, a managed service, rather than this customer-operated Community cluster. A current certificate/report covering the relevant Community development/support boundary and buyer controls was not established; do not inherit TiDB Cloud attestations. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://www.pingcap.com/trust-hub/compliance/ (reviewed 2026-11-18). Supporting source: Explicit TiDB Cloud ISO certification boundary — https://www.pingcap.com/press-release/announcing-iso-27001-certification-for-tidb-cloud/.

- Security controls: Documented. PingCAP documents certificates and TLS between components, plus client TLS and privileged-user/network controls. JWT SQL authentication requires trusted issuer/JWKS configuration and client TLS because the client sends the token through a clear-password plugin. Database token/LDAP authentication alone does not establish SSO or SCIM. Techlatest’s VM guide starts TiDB root with a blank password and Grafana with admin/admin; set new credentials and restrict SSH/RDP before use. Its component patch levels remain unconfirmed. Optional Dashboard OIDC SSO stores an encrypted SQL password for impersonation; use the documented least-privileged account and network/TLS controls, and reauthorize after SQL password rotation. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://docs.pingcap.com/tidb/stable/enable-tls-between-components/ (reviewed 2026-11-18). Supporting source: Self-managed security configuration — https://docs.pingcap.com/tidb/stable/best-practices-for-security-configuration/. Supporting source: SQL authentication and JWT TLS requirements — https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/. Supporting source: Seller-specific initial credential requirements — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html. Supporting source: Dashboard OIDC credential-handling boundary — https://docs.pingcap.com/tidb/stable/dashboard-session-sso/. Supporting source: Least-privileged Dashboard SQL users — https://docs.pingcap.com/tidb/stable/dashboard-user/.

- Air-gapped operation: Documented. The Kubernetes guide explicitly describes transferring container images to a server without external network access and loading them locally. Include operator, PD/TiKV/TiDB, optional TiFlash/TiCDC, monitoring and initialization images; its v8.5.7 example is not a complete current-version image lockfile. Scope: Operator-based Kubernetes offline procedure only; the third-party VM’s offline lifecycle is not established. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-general-kubernetes/ (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The AKS guide provides a versioned TiDB custom-resource manifest from TiDB Operator v1.6.6, together with separate monitoring/dashboard manifests. The operator version and TiDB image versions are independent; review requests, storage classes and all example defaults. The optional seller VM has a separate AMI/image inventory; do not treat the Operator manifest as its installation artifact. Scope: Operator v1.6.6 Kubernetes manifest; the third-party VM is a separate delivery. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/ (reviewed 2026-11-18). Deployment artifact: https://raw.githubusercontent.com/pingcap/tidb-operator/v1.6.6/examples/aks/tidb-cluster.yaml. Artifact reference: TiDB Operator v1.6.6 AKS example. Supporting source: Separate single-VM deployment artifact — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html.

- Minimum footprint / sizing: Documented. The v8.5 production hardware baseline lists two TiDB nodes at 16 cores/48 GB each, three PD at 8 cores/16 GB, and three TiKV at 16 cores/64 GB, plus SSD and network requirements. Optional analytics/changefeed/monitoring add components. These are component recommendations, not exact pod requests or a benchmark for 100 users. The seller’s t2.large VM example is not this production multi-node baseline. Scope: Upstream v8.5 production component recommendations; not the third-party VM’s capacity or HA guarantee. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-requirements/ (reviewed 2026-11-18). Supporting source: Different single-VM baseline — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html.

- License pricing: Documented. TiDB Community is Apache 2.0 licensed. PingCAP support and TiDB Cloud are separate commercial purchases. Review the licences of optional monitoring tools and other bundled components. The alternative Techlatest AMI bills USD 0.13/hour for seller support on its reviewed t2.large option, with AWS resources separate. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://github.com/pingcap/tidb/blob/master/LICENSE (reviewed 2026-11-18). Supporting source: Separately transacted seller bundle pricing — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Operating cost estimate: Sources checked — unresolved. Define SQL QPS, transaction mix, concurrency, indexes, TiKV replication, usable versus raw 1 TB, compaction headroom, TiFlash/TiCDC needs, monitoring and recovery targets. Price EKS and stateful nodes/storage across failure domains after benchmarking; the user count alone does not size this distributed database. The seller’s single-VM bundle does not provide the requested HA architecture. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-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/. Supporting source: Single-VM price/topology is a different cost scope — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Release snapshot / cadence: Documented. TiDB v8.5.8 was published August 27, 2026 and is the reviewed v8.5 LTS snapshot. Its notes include PD endpoint and TiKV dependency security fixes. The later v7.5.8 publication belongs to an older branch. Match Operator, TiKV, PD and optional component versions rather than treating the chart version as the database version. Techlatest’s AMI package 1.0.2 does not disclose its embedded database versions, so this upstream snapshot must not be inherited by that VM. Scope: Upstream TiDB v8.5 LTS snapshot; not a confirmed version for the third-party AWS image. Source: https://github.com/pingcap/tidb/releases/tag/v8.5.8 (reviewed 2026-11-18). Supporting source: Component fixes in v8.5.8 — https://docs.pingcap.com/tidb/stable/release-8.5.8. Supporting source: Separate seller package/version boundary — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.




### Security and lifecycle reviews

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

- TiDB v8.5.8 PD endpoint and component security review (security-advisory): The release fixes potential SSRF/upstream response exposure in PD metric endpoints, GlobalConfig namespace access and dependency vulnerabilities in TiKV/DM. Scope: The v8.5.8 component release notes; a complete affected-version range and a universal exposure claim are not established. Conditions: Exposure depends on component versions, PD endpoint accessibility and configured dependencies. Community, Cloud and unrelated LTS branches must not be treated as identical deployments. Action: Review the fixed PD/TiKV/optional component versions, restrict management endpoints and follow the matching LTS upgrade procedure. Source: https://docs.pingcap.com/tidb/stable/release-8.5.8; reviewed 2026-11-18.




## Timesketch

Open-source collaborative forensic timeline analysis application.

- Listing: https://launchinyourcloud.com/directory/timesketch/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: gcp, azure
- 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: Helm / Kubernetes operator; Kubernetes manifests; VM image
- Architecture: Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack.
- 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/google/timesketch
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.

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

Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Open-source collaborative forensic timeline analysis application.

### Deployment boundaries


- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://google.github.io/osdfir-infrastructure/docs/getting-started.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://secureanycloud.com/stacks/timesketch/ (checked 2026-11-19). 


### Cloud deployment evidence

- OSDFIR Getting Started (gcp): https://google.github.io/osdfir-infrastructure/docs/getting-started.html
  Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- SecureAnyCloud Azure (azure): https://secureanycloud.com/stacks/timesketch/
  Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes berggren, kiddinn, jaegeral, 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/google/timesketch/graphs/contributors

- Upstream project: https://github.com/google/timesketch

### Sources

- OSDFIR Getting Started: https://google.github.io/osdfir-infrastructure/docs/getting-started.html

- SecureAnyCloud Azure: https://secureanycloud.com/stacks/timesketch/

- OSDFIR Timesketch: https://google.github.io/osdfir-infrastructure/charts/timesketch/

- Apache-2.0: https://github.com/google/timesketch/blob/master/LICENSE

- Releases: https://github.com/google/timesketch/releases

### Licensing sources

- https://github.com/google/timesketch/blob/master/LICENSE

### Infrastructure sources

- https://google.github.io/osdfir-infrastructure/docs/getting-started.html

- https://secureanycloud.com/stacks/timesketch/


### 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 versioned configuration supports trusted web-server REMOTE_USER SSO and separately Google OIDC/Cloud IAP options, with actual token/authentication implementation. Configure the selected mode, trusted proxy boundary, identity claims and group policy; these mechanisms are not interchangeable and must not trust spoofed headers. Scope: Timesketch 20261014 configured user SSO/OIDC/IAP paths. Source: https://github.com/google/timesketch/blob/20261014/data/timesketch.conf (reviewed 2026-11-21). Supporting source: Google token validation — https://github.com/google/timesketch/blob/20261014/timesketch/lib/google_auth.py. Supporting source: Application authentication views — https://github.com/google/timesketch/blob/20261014/timesketch/views/auth.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Google maintains OSDFIR Helm charts with Timesketch values and production installation guidance. Select compatible chart/application/OpenSearch versions, expose ingress deliberately and configure secrets, persistent storage and backups. Local Minikube instructions and default port-forward access are not production deployment. Scope: Maintainer Timesketch Kubernetes/Helm deployment; chart and application versions separate. Source: https://google.github.io/osdfir-infrastructure/charts/timesketch/ (reviewed 2026-11-21). Deployment artifact: https://google.github.io/osdfir-infrastructure/charts/timesketch/. Artifact reference: Current OSDFIR Timesketch chart guide reviewed on this date.

- Minimum footprint / sizing: Documented. The upstream scaling guide gives at least 8 GB RAM for its described Ubuntu environment and stresses fast local storage and OpenSearch sizing/shard limits. This is an entry baseline, not capacity for arbitrary timelines/events or an HA cluster; separately size indexes, imports, workers, replicas and backups. Scope: Timesketch published entry baseline and search-scaling guidance. Source: https://timesketch.org/guides/admin/scaling-and-limits/ (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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







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




## Tyk Self-Managed

Commercial self-managed API management platform with documented AWS, Azure and Google Cloud deployments.

- Listing: https://launchinyourcloud.com/directory/tyk-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Tyk Self-Managed license required for the full platform; Gateway and Pump are available without that license.
- Licensing model: commercial-only
- Installation: Docker, Helm, Linux packages or Ansible on customer cloud infrastructure
- Architecture: Tyk Gateway, Dashboard, Pump and Developer Portal services with Redis and MongoDB or supported SQL data stores
- Operations: Customer manages hosts or Kubernetes, data stores, networking, TLS, identities, secrets, monitoring, backups, scaling, upgrades and the Tyk license.
- Product website: https://tyk.io/self-managed/
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers the full Tyk Self-Managed platform, not Tyk Cloud or the standalone OSS Gateway. The Dashboard and other full-platform components require a commercial license, and Kubernetes installation requires a multi-node license. Provider tutorials are starter deployments rather than production sizing or high-availability guarantees.

The selected full Tyk Self-Managed platform requires a commercial license. Tyk Gateway and Pump are separately available as open-source components, but they do not constitute the complete listed platform.

Tyk Self-Managed runs persistent gateway, management, analytics, portal and database services on customer virtual machines or Kubernetes.


### Category fit

- backend-platforms: Provides a self-managed API gateway, management dashboard, analytics, developer portal and lifecycle controls for application APIs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://tyk.io/deploying-on-aws/ (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://tyk.io/deploying-on-azure/ (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://tyk.io/deploying-on-gcp/ (checked 2026-11-16). 


### Cloud deployment evidence

- Tyk Self-Managed on AWS (aws): https://tyk.io/deploying-on-aws/
  Tyk documents creating an Amazon EC2 instance in the customer's AWS account and deploying the licensed Tyk Self-Managed platform with Docker.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Tyk Self-Managed on Microsoft Azure (azure): https://tyk.io/deploying-on-azure/
  Tyk documents creating an Azure virtual machine and installing the Tyk Self-Managed stack with Docker in the customer's Azure environment.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Tyk Self-Managed on Google Cloud (gcp): https://tyk.io/deploying-on-gcp/
  Tyk documents deploying its licensed Self-Managed platform on customer Google Cloud infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Install Tyk Self-Managed: https://tyk.io/docs/5.7/tyk-self-managed/

- Deploy Tyk on AWS: https://tyk.io/deploying-on-aws/

- Deploy Tyk on Azure: https://tyk.io/deploying-on-azure/

- Deploy Tyk on Google Cloud: https://tyk.io/deploying-on-gcp/

- Tyk Self-Managed product and pricing model: https://tyk.io/self-managed/

### Licensing sources

- https://tyk.io/docs/5.7/tyk-self-managed/

- https://tyk.io/self-managed/

### Infrastructure sources

- https://tyk.io/docs/5.7/tyk-self-managed/

- https://tyk.io/self-managed/


### Buyer diligence


Research coverage: 8/12 fields (67%); 8 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: Edition-dependent. The vendor AWS offer explicitly covers Cloud, Hybrid and Self-Managed. Its delivery classification is a SaaS contract and its public dimensions price Tyk Cloud; request terms that specifically license the self-managed deployment rather than treating it as an application AMI. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-pboluroscnqro (reviewed 2026-11-16). Offer prodview-pboluroscnqro: Tyk Technologies Ltd; SaaS contract listing covering multiple deployment modes; self-managed terms require confirmation; https://aws.amazon.com/marketplace/pp/prodview-pboluroscnqro.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Tyk documents Dashboard SAML login through its internal Identity Broker with Okta, and an OIDC integration with AWS Cognito. Configure the identity profile and user mapping for the licensed Dashboard; API-consumer authentication is a separate concern. Scope: Commercial self-managed Dashboard with internal TIB. Source: https://support.tyk.io/hc/en-gb/articles/8568981329564-SSO-access-using-internal-TIB-SAML-OKTA (reviewed 2026-11-16). Supporting source: Dashboard OIDC with Cognito — https://support.tyk.io/hc/en-gb/articles/21540673255836--Setting-Up-SSO-with-AWS-Cognito-as-IdP-for-Tyk-Dashboard.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The self-managed guide documents database-backed Dashboard audit-log storage from v5.7 onward. Operators must configure it, size the database and set retention/archive policies; example log sizes are workload assumptions, not a default retention guarantee or an attestation. Scope: Dashboard 5.7+ audit-log configuration and storage responsibilities. Source: https://tyk.io/docs/5.7/tyk-self-managed/ (reviewed 2026-11-16).

- Air-gapped operation: Documented. Tyk documents mirroring all chart images, packaging the Helm chart and installing from private registries; Linux deployments can use local package mirrors. Include optional-component images and arrange the correct commercial licenses and compatible versions. Scope: Documented self-managed offline installation workflow; selected integrations and license terms still require deployment-specific review. Source: https://tyk.io/docs/api-management/air-gapped-deployment (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. Tyk publishes the tyk-stack Helm chart and a trial-ready installation wrapper. Use the current tyk-charts repository; the former tyk-helm-chart repository is archived and deprecated. Select compatible chart/component versions, configure the required Dashboard license and production databases, and review trial defaults before production. Scope: Full self-managed platform; not the standalone open-source gateway. Source: https://tyk.io/docs/tyk-self-managed/install/kubernetes (reviewed 2026-11-16). Deployment artifact: https://github.com/TykTechnologies/tyk-charts/tree/main/tyk-stack. Artifact reference: main (moving branch; select compatible chart release). Supporting source: Archived chart repository and replacement notice — https://github.com/TykTechnologies/tyk-helm-chart.

- Minimum footprint / sizing: Documented. The current Kubernetes tutorial requires at least 4 GB RAM available to the cluster, but explicitly deploys a trial-ready configuration. Production sizing must include Gateway traffic, Redis, PostgreSQL and optional components; 4 GB is not a production capacity guarantee. Scope: Self-managed Kubernetes tutorial prerequisites, not a universal production minimum. Source: https://tyk.io/docs/tyk-self-managed/install/kubernetes (reviewed 2026-11-16).

- License pricing: Documented. The selected full Tyk Self-Managed platform requires a commercial license. Tyk Gateway and Pump are separately available as open-source components, but they do not constitute the complete listed platform. Scope: Tyk Self-Managed: software license terms; infrastructure and operating costs are separate. Source: https://tyk.io/docs/5.7/tyk-self-managed/ (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://tyk.io/self-managed/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor policy lists 5.13 as its current LTS line. Gateway/Dashboard LTS receives 12 months of full support with eight-week patches, then 12 months of critical maintenance. Other components and non-LTS releases have separate compatibility and lifecycle rules. Scope: Published Gateway/Dashboard LTS policy as reviewed; not a single version or support guarantee for the entire platform. Source: https://tyk.io/docs/developer-support/release-types/long-term-support (reviewed 2026-11-16).







## UiPath Automation Suite

Self-hosted enterprise automation platform installed on customer-managed Amazon EKS or Azure AKS.

- Listing: https://launchinyourcloud.com/directory/uipath-automation-suite/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: hybrid
- License: Commercial UiPath Unified Pricing or Flex plans and applicable product SKUs
- Licensing model: commercial-only
- Installation: uipathctl on customer-managed Amazon EKS or Azure AKS
- Architecture: Kubernetes application platform with customer-managed cluster, SQL database, object, block and file storage, cache and secrets infrastructure
- Operations: Customer provisions, patches and operates the cloud infrastructure; UiPath supplies and supports Automation Suite and its upgrade tooling.
- Product website: https://www.uipath.com/product/automation-suite
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Automation Suite contains UiPath server products supported by that release, not every Automation Cloud service. The selected 2.2510 EKS/AKS documentation covers online and offline customer-managed infrastructure; verify the licensed product set and supported component versions.

Automation Suite requires commercial UiPath licenses and applicable product SKUs; this entry does not represent a free or open-source edition.

Automation Suite runs on customer-managed Kubernetes compute and depends on customer-managed or cloud-managed SQL, storage, cache, secrets and networking services.


### Category fit

- workflow-automation: Self-hosted enterprise automation products and shared platform services on a customer-managed Kubernetes environment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios (checked 2026-11-19). 


### Cloud deployment evidence

- UiPath Automation Suite on customer-managed Amazon EKS (aws): https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios
  UiPath documents production architectures for Automation Suite on customer-managed Amazon EKS, including required database, storage, cache, networking and secrets services.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2.2510 documentation.

- UiPath Automation Suite on customer-managed Azure AKS (azure): https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios
  UiPath documents production architectures for Automation Suite on customer-managed Azure AKS, including required database, storage, cache, networking and secrets services.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2.2510 documentation.


### Sources

- Automation Suite overview for EKS and AKS: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/automation-suite-overview

- Customer-managed Automation Suite infrastructure: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/automation-suite-stack

- Automation Suite deployment scenarios: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios

- Install Automation Suite: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/installing-automation-suite

- Automation Suite licensing: https://docs.uipath.com/automation-suite/automation-suite/2.2510/admin-guide/about-licensing

- Buyer evidence: iac: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/downloading-the-installation-packages

- Reviewed deployment artifact reference: https://download.uipath.com/automation-suite/2.2510.2/as-cmk-2.2510.2.tar.gz

- Vendor checksum manifest: https://download.uipath.com/automation-suite/2.2510.2/as-cmk-2.2510.2-sha256sum.txt

### Licensing sources

- https://docs.uipath.com/automation-suite/automation-suite/2.2510/admin-guide/about-licensing

- https://docs.uipath.com/automation-suite/automation-suite/2.2510/admin-guide/flex-licensing-plan-framework

### Infrastructure sources

- https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/automation-suite-stack

- https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios (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: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/automation-suite-overview (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/automation-suite-overview (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: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/automation-suite-overview (reviewed 2026-11-19).

- Security controls: Edition-dependent. The responsibility and deployment guides define customer ownership of cluster hardening, networking, secrets, certificates, database and storage, and include private and offline production topologies. Product authorization and audit configuration remain part of the buyer's implementation. Scope: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/automation-suite-stack (reviewed 2026-11-19).

- Air-gapped operation: Edition-dependent. UiPath documents offline Automation Suite deployment scenarios for customer-managed EKS and AKS. Stage the exact product bundles, container images, uipathctl release, operating-system packages and license workflow required by version 2.2510. Scope: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The EKS/AKS download matrix publishes as-cmk-2.2510.2.tar.gz and its SHA-256 manifest. Pair the bundle with the matching uipathctl and required online/offline images. This customer-managed Kubernetes bundle is distinct from Linux-only patch downloads and individually licensed products; the archive itself was not installed or fully downloaded in this review. Scope: Published Automation Suite 2.2510.2 customer-managed EKS/AKS bundle reference and checksum. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/downloading-the-installation-packages (reviewed 2026-11-19). Deployment artifact: https://download.uipath.com/automation-suite/2.2510.2/as-cmk-2.2510.2.tar.gz. Artifact reference: as-cmk-2.2510.2.tar.gz; SHA-256 e0d3ba1eaf5b5e35c2ce3b4e467799c20db97df1e91818f4262969a050dde1e6. Supporting source: Vendor checksum manifest — https://download.uipath.com/automation-suite/2.2510.2/as-cmk-2.2510.2-sha256sum.txt.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed sources describe the deployment components but do not provide one complete production sizing model for the buyer's users, data volume, traffic, retention and availability target. Size every application and managed-service dependency. Scope: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios (reviewed 2026-11-19).

- License pricing: Edition-dependent. Commercial UiPath Unified Pricing or Flex plans and applicable product SKUs Infrastructure, support and operating labor are separate unless the order states otherwise. Scope: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/admin-guide/about-licensing (reviewed 2026-11-19).

- 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: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/deployment-scenarios (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The reviewed customer-managed EKS/AKS documentation is versioned 2.2510. Treat this as a documentation snapshot, not proof that every bundled server product has the same version or support window; record the installed bundle and follow its upgrade matrix. Scope: UiPath Automation Suite: selected customer-operated edition. Source: https://docs.uipath.com/automation-suite/automation-suite/2.2510/installation-guide-eks-aks/automation-suite-overview (reviewed 2026-11-19).







## Umbraco CMS Self-Hosted

MIT-licensed .NET CMS with documented customer-managed Azure and AWS hosting options.

- Listing: https://launchinyourcloud.com/directory/umbraco-cms-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT-licensed Umbraco CMS core; Umbraco Cloud, Deploy, Forms and other products have separate commercial terms.
- Licensing model: open-source
- Installation: Umbraco.Cms NuGet package and customer-managed hosting, including Azure Web Apps and AWS; provision a supported database and media storage; optional cloudimg Azure VM package has its own version, database and patch constraints
- Architecture: ASP.NET Core CMS application with a supported customer-controlled database and persistent media; Azure App Service is one documented hosting configuration.
- Operations: Customer manages application releases, database, media, settings and secrets, backups, scaling, domains, TLS and packages.
- Product website: https://umbraco.com/products/umbraco-cms/
- 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 self-hosted Umbraco CMS, not Umbraco Cloud or Heartcore. CMS 18 is STS and 17 is LTS; 13 reaches EOL December 14, 2026. Match the major version, .NET/database requirements, shared media and load-balanced deployment; commercial add-ons have separate terms. A separate cloudimg Azure VM guide packages CMS 17.5.3 with embedded SQLite. It is a single-instance option, not HA or Umbraco Cloud. Verify the actual installed build against GHSA-348f-9mg8-rhv4; affected builds require a branch-appropriate upgrade and Members-index rebuild. GHSA-5pr6-xx84-wp49 separately affects Umbraco CMS 13.0.0–13.16.4 when the Delivery API is enabled and protected or excluded content is referenced through content pickers. Upgrade to 13.16.5 or later. Versions 12 and 14–15 are end of life and require migration; CMS 17 and 18 are not affected by this specific issue.

Umbraco CMS core is MIT-licensed. Umbraco Cloud and optional commercial products are separate.

Umbraco runs as a persistent application backed by a relational database and media storage; Azure App Service abstracts servers but does not remove stateful application dependencies.


### Category fit

- content-management: Provides open-source web content authoring, publishing, templating and extensible CMS capabilities.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps (checked 2026-11-18). Source: https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/ (checked 2026-11-18). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umbraco.com/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/hosting-with-umbraco-cloud-cloud-vs.-self-hosted (checked 2026-11-18). 


### Cloud deployment evidence

- Umbraco CMS on Azure Web Apps (azure): https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps
  Umbraco documents configuration and operation of the self-hosted CMS on Azure App Service in the customer's environment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Umbraco customer-managed AWS hosting (aws): https://docs.umbraco.com/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/hosting-with-umbraco-cloud-cloud-vs.-self-hosted
  Umbraco’s hosting comparison explicitly names AWS and Azure as self-hosted infrastructure managed by the customer. The CMS, database and commercial add-on lifecycle remain customer responsibilities.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- cloudimg Umbraco CMS VM in a customer Azure subscription (azure): https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/
  The seller documents a complete MIT CMS deployment into the selected customer subscription/VNet, using image URN cloudimg1647283583153:umbraco-ubuntu-24-04:default:latest, nginx, .NET 10, embedded SQLite and a data disk. Its 17.5.3 guide version needs the documented security/upgrade review; it is not a clustered/HA database or an HQ-supported package.
  Source type: third-party-package; reviewed: 2026-11-18; vendor support: not-assessed. Versions: Guide application 17.5.3; verify actual image and patched build.


### Community and maintenance

The public CMS repository publishes fixes across current/LTS branches and Umbraco maintains a named implementation case-study catalog. Cloud/Heartcore case studies are not used as customer-cloud proof; the separate hosting comparison establishes the listed deployment boundary.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/umbraco/Umbraco-CMS/releases/tag/release-18.3.2

- Official maintenance and adoption evidence: https://umbraco.com/case-studies-testimonials/

- Official maintenance and adoption evidence: https://docs.umbraco.com/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/hosting-with-umbraco-cloud-cloud-vs.-self-hosted

### Sources

- Hosting an Umbraco infrastructure: https://docs.umbraco.com/getting-started/hosting-an-umbraco-infrastructure

- Configure Umbraco CMS for Azure Web Apps: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps

- Umbraco Cloud versus self-hosted: https://docs.umbraco.com/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/hosting-with-umbraco-cloud-cloud-vs.-self-hosted

- Umbraco CMS source-code license: https://umbraco.com/products/umbraco-cms/source-code-license/

- cloudimg self-hosted Umbraco Azure VM guide: https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/

- Provider exact Azure offer metadata: https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en

- Umbraco November 17, 2026 security advisory: https://umbraco.com/blog/security-advisory-security-patches-for-umbraco-cms-umbraco-workflow-umbraco-commerce-umbraco-engage-and-umbraco-mcp-server-sdk-now-available/

- GHSA-5pr6-xx84-wp49: https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-5pr6-xx84-wp49

### Licensing sources

- https://umbraco.com/products/umbraco-cms/source-code-license/

### Infrastructure sources

- https://docs.umbraco.com/umbraco-cms/13.latest/fundamentals/setup/server-setup/azure-web-apps

- https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/


### 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. cloudimg publishes Azure VM offer cloudimg1647283583153.umbraco-ubuntu-24-04, default plan. Its guide/catalog package MIT-licensed CMS 17.5.3 on .NET 10, nginx and embedded SQLite with per-VM administrator credentials. It excludes Umbraco Cloud and paid add-ons. The guide’s version is within GHSA-348f’s affected 17.x range: verify the installed build, upgrade to the maintained patched branch and rebuild the Members index where affected. The seller’s 17.8.0 AWS guide is closed to new subscriptions. Scope: Third-party self-hosted Azure VM, default plan; not Umbraco Cloud, an HQ support commitment or an HA/clustered SQLite design. Source: https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/ (reviewed 2026-11-18). Supporting source: Current seller product and offer link — https://www.cloudimg.co.uk/products/umbraco-on-ubuntu-24-04-lts-azure/. Supporting source: Provider public offer/version/availability metadata — https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en. Supporting source: Official version-specific fix and index rebuild — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4. Supporting source: Newer-looking AWS guide is retired for new subscribers — https://www.cloudimg.co.uk/guides/umbraco-17-8-0-on-ubuntu-24-04-aws/. Offer cloudimg1647283583153.umbraco-ubuntu-24-04: cloudimg; Azure virtual-machine image; default plan; package Guide application 17.5.3; moving latest image; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.umbraco-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. Microsoft’s public catalog marks the reviewed cloudimg Umbraco CMS Azure VM offer as ineligible for MACC. Its software packaging/support charge therefore does not supply MACC-eligible software spend through this public offer. Recheck the current offer at procurement. Azure infrastructure, other providers, commercial add-ons and separately negotiated offers need their own eligibility and agreement review. Scope: MACC eligibility of public cloudimg offer cloudimg1647283583153.umbraco-ubuntu-24-04, default plan, US catalog checked; other procurement paths are outside this finding. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-18). Supporting source: Microsoft definition of the catalog eligibility field — https://raw.githubusercontent.com/Azure/azure-rest-api-specs/00f083f4efcbfe54730b7af700a50327232c199a/specification/marketplacecatalog/data-plane/Marketplace/stable/2021-10-01/marketplacecatalog.json. Supporting source: Microsoft MACC purchasing and infrastructure boundaries — https://learn.microsoft.com/en-us/marketplace/azure-consumption-commitment-benefit.

- Single sign-on: Documented. The CMS supports external OAuth/OIDC login providers for backoffice users and frontend members through ASP.NET Core Identity. Configure each provider and optional auto-linking explicitly. A community Azure SSO package is not an Umbraco HQ support commitment. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://docs.umbraco.com/umbraco-cms/reference/security/external-login-providers (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. miniOrange documents an outbound Umbraco SCIM Client: existing Backoffice Users/Members provision into a destination SCIM server. Its FAQ explicitly says it does not create Umbraco users from an IdP. The setup guide names Trial package 18.0.1, but its public NuGet version URL returned 404. Confirm the current production package/feed, CMS compatibility and licence; an inbound Umbraco provisioning requirement remains unanswered. Scope: Third-party outbound connector documentation; current deliverable and inbound provisioning are not confirmed. Source: https://plugins.miniorange.com/umbraco-scim-user-provisioning (reviewed 2026-11-18). Supporting source: Named trial package and outbound setup — https://plugins.miniorange.com/umbraco-scim-user-provisioning-setup-guide.

- Compliance attestations: Documented. Sensiba certificate 202601-189 identifies Umbraco A/S’s ISO/IEC 27001:2022 ISMS for CMS platform development/provisioning processes. It was issued January 21, 2026 and expires January 21, 2029. The certificate expressly excludes certifying products, processes or services; it does not certify a customer’s self-hosted website, plugins, database or operations. Scope: Organisational ISO 27001 management-system assurance covering CMS development/provisioning; not product or customer-deployment certification. Source: https://umbraco.com/media/vj0c1qi5/umbraco-iso-27001-certificate-jan-2026-93.pdf (reviewed 2026-11-18). Supporting source: Official certificate announcement and organisation scope — https://umbraco.com/blog/iso-27001/. Supporting source: Compliance boundaries and SOC position — https://umbraco.com/trust-center/compliance-faq/.

- Security controls: Documented. Backoffice and member authentication have separate external-login configuration and optional account auto-linking. Review provider ownership, callback URLs and linking rules. Supported major versions have different security-maintenance windows; external authentication does not remove patch obligations. A seller’s hardened OS/first-boot credentials do not establish that its older CMS package contains the member-index fix; verify the app build and required index rebuild. Current review: GHSA-5pr6-xx84-wp49 affects CMS 13.0.0–13.16.4 when the Delivery API is enabled and protected or excluded content is referenced through content pickers; upgrade to 13.16.5 or later. CMS 12 and 14–15 are end of life, while 17 and 18 are not affected by this specific issue. GHSA-348f-9mg8-rhv4 separately requires affected 17/18 sites to rebuild the Members index after upgrading. Scope: Umbraco CMS branch-specific November 17 fixes; commercial add-ons have separate advisories. Source: https://umbraco.com/blog/security-advisory-security-patches-for-umbraco-cms-umbraco-workflow-umbraco-commerce-umbraco-engage-and-umbraco-mcp-server-sdk-now-available/ (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://docs.umbraco.com/umbraco-cms/reference/security/external-login-providers. Supporting source: CMS support lifecycle — https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/. Supporting source: Older packaged application and local safeguards — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/. Supporting source: Official patch and index remediation — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4. Supporting source: CMS 13 Delivery API advisory — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-5pr6-xx84-wp49.

- Air-gapped operation: Sources checked — unresolved. The official telemetry material documents Minimal, Basic and Detailed reporting levels, while health checks can be disabled/configured individually. Those controls are not a complete disconnected CMS lifecycle. Confirm NuGet/.NET artifact transfer, news/telemetry and update requests, local identity/mail/media, and any add-on activation; the self-contained Azure SQLite image alone does not establish air-gapped operation. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://docs.umbraco.com/sustainability-best-practices/telemetry/telemetry (reviewed 2026-11-18). Supporting source: Current CMS health-check controls — https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/configuration/healthchecks. Supporting source: VM component boundary, not an offline guarantee — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/.

- Deployment artifact / IaC: Documented. The CMS is distributed as the Umbraco.Cms NuGet package; 18.3.2 is a versioned package. Azure Web Apps has a separate vendor configuration guide. Database provisioning, deployment automation and load-balanced content/media handling remain part of the customer design. cloudimg separately documents the moving Azure image URN cloudimg1647283583153:umbraco-ubuntu-24-04:default:latest; resolve its version before deployment. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/requirements (reviewed 2026-11-18). Deployment artifact: https://www.nuget.org/packages/Umbraco.Cms/18.3.2. Artifact reference: Umbraco.Cms 18.3.2. Supporting source: Current Azure Web Apps configuration — https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps. Supporting source: Separate VM artifact and deployment instructions — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/.

- Minimum footprint / sizing: Documented. The current CMS requirements name .NET 10, supported hosting runtimes, SQLite or SQL Server 2016+ with the required case-insensitive collation, and WebSocket/SignalR support. They do not provide a universal CPU/RAM minimum or a 100-user HA bill of materials. Check requirements again for older LTS majors. The cloudimg SQLite appliance suggests Standard_B2s (2 vCPU/4 GiB); this is a single-instance package baseline, not clustered HA sizing. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/requirements (reviewed 2026-11-18). Supporting source: Single-instance Azure appliance requirements — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/.

- License pricing: Documented. Umbraco CMS core is MIT licensed. Commercial Forms, Deploy, support and Umbraco Cloud hosting have separate terms; none is automatically included with a self-hosted core installation. The cloudimg Azure default plan charges USD 0.04/vCPU-hour for packaging/support (USD 0.08/hour at two vCPUs), plus Azure infrastructure; this is not an Umbraco HQ subscription. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://umbraco.com/products/umbraco-cms/source-code-license/ (reviewed 2026-11-18). Supporting source: Exact Azure plan and per-core meters — https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.

- Operating cost estimate: Sources checked — unresolved. Define editor versus public traffic, content/media split, database and Windows/Linux choice, shared media, cache, HA topology, backups and commercial add-ons. One hundred editors and 1 TB do not size the CMS’s public request workload or SQL licensing. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/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. The CMS release release-18.3.2 was published November 17, 2026. GHSA-348f-9mg8-rhv4 requires affected sites to upgrade and rebuild the Members index; patch installation alone leaves existing indexed values. Version 18 is STS, 17 is LTS, and 13 reaches EOL December 14, 2026; 19.0.0-rc1 is a prerelease. The reviewed cloudimg Azure package instead documents 17.5.3, which falls within the advisory’s affected 17.x range; confirm the installed build and upgrade/rebuild where affected. CMS 13.16.5 fixes GHSA-5pr6-xx84-wp49 on the maintained 13.x line; this does not replace the current release-18.3.2 primary snapshot. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://github.com/umbraco/Umbraco-CMS/releases/tag/release-18.3.2 (reviewed 2026-11-19). Supporting source: Official lifecycle dates — https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/. Supporting source: Sensitive member data advisory and index rebuild — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4. Supporting source: Provider packaged-version boundary — https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en. Supporting source: CMS 13 Delivery API advisory — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-5pr6-xx84-wp49.




### Security and lifecycle reviews

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

- Umbraco sensitive member data requires upgrade and index rebuild (security-advisory): GHSA-348f-9mg8-rhv4 describes sensitive member property values exposed through the Examine members index to some authenticated backoffice users or custom index queries. Scope: The vendor identifies introduction in 17.4.0 and fixes in 17.8.2/18.3.2. The default members index in 17.0–17.3 is excluded. Read the advisory’s branch-specific range rather than applying this to every CMS major. cloudimg’s current Azure guide/plan documents CMS 17.5.3 within the affected 17.x range; resolve the actual image and installed build, including any documented backport, before assessing an instance. Conditions: Member types must have sensitive properties. The described backoffice path requires Settings and Members access without Sensitive data group membership; custom code returning all indexed fields can also expose values. Action: Install the patched version for the maintained branch and rebuild the Members index. Until upgrade, restrict the named group access and review custom code that returns indexed fields. Source: https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4; reviewed 2026-11-18. Supporting source: Seller Azure image and application version — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/. Supporting source: Provider current offer/plan metadata — https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.

- Umbraco 13 LTS reaches end of life in December 2026 (lifecycle): Umbraco 13 is in security-only maintenance and reaches end of life December 14, 2026. Other CMS majors have different windows. Scope: Umbraco CMS 13 deployments, including older Azure recipes; this is not an end-of-life announcement for the current CMS product. Conditions: The installed major version determines support. Version 17 is LTS and 18 is STS; neither inherits version 13’s date. Action: Inventory the installed major and plugins, and plan a tested migration to a maintained major before the applicable deadline. Source: https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/; reviewed 2026-11-18.

- Umbraco CMS 13 protected-content Delivery API fix (security-advisory): GHSA-5pr6-xx84-wp49 fixes protected or excluded content disclosure through the Delivery API and content pickers. Scope: Umbraco CMS 13.0.0–13.16.4; fixed in 13.16.5. CMS 12 and 14–15 are end of life; CMS 17 and 18 are not affected by this specific issue. Conditions: The Delivery API must be enabled and protected or excluded content referenced through a Content Picker or Multi-Node Tree Picker. Action: Upgrade maintained CMS 13 to 13.16.5 or later; migrate end-of-life branches. Source: https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-5pr6-xx84-wp49; reviewed 2026-11-19. Supporting source: Vendor security summary — https://umbraco.com/blog/security-advisory-security-patches-for-umbraco-cms-umbraco-workflow-umbraco-commerce-umbraco-engage-and-umbraco-mcp-server-sdk-now-available/.




## Vault Enterprise Self-Managed

Commercial self-managed secrets and identity security platform deployed as a customer-operated high-availability cluster.

- Listing: https://launchinyourcloud.com/directory/vault-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Vault Enterprise license required.
- Licensing model: commercial-only
- Installation: Official HashiCorp Validated Design Terraform modules for AWS EC2, Azure VMs or Google GCE
- Architecture: High-availability Vault Enterprise VM cluster with integrated storage, load balancing, TLS and cloud key-management dependencies
- Operations: Customer manages VPC or VNet infrastructure, VMs, load balancers, storage, cloud KMS or Key Vault, TLS, initialization and unseal controls, audit logs, backups, replication, upgrades and licensing.
- Product website: https://developer.hashicorp.com/vault
- 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 Vault Enterprise self-managed, not HCP Vault Dedicated or the separately licensed Community edition. Protect recovery and root credentials, design unseal and disaster-recovery procedures, and review the Terraform modules' requested permissions before deployment.

The selected Vault Enterprise edition requires a commercial license and supports license autoloading or explicit license configuration.

The validated design deploys a persistent high-availability Vault Enterprise VM cluster with integrated storage and provider key-management services.


### Category fit

- identity-access-management: Provides centrally governed secrets, encryption, authentication methods, dynamic credentials and identity-based access policies.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 


### Cloud deployment evidence

- Vault Enterprise inside a customer cloud account (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform
  HashiCorp provides official validated-design modules for AWS EC2, Azure VMs and Google GCE and states that the modules deploy a complete Vault Enterprise environment inside the customer's own cloud account.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Deploy Vault Enterprise with official Terraform modules: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform

- Vault Enterprise license keys: https://developer.hashicorp.com/vault/docs/license

- Vault editions: https://developer.hashicorp.com/vault/tutorials/get-started/available-editions

### Licensing sources

- https://developer.hashicorp.com/vault/docs/license

- https://developer.hashicorp.com/vault/tutorials/get-started/available-editions

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform


### 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. Vault documents OIDC browser login from the UI and CLI, using configured identity providers, callback URLs, roles and claim-bound policies. OIDC authentication is distinct from Kubernetes/JWT machine login and from downstream applications consuming secrets. Configure authorization and the selected Enterprise feature entitlements separately. Scope: Self-managed Vault user authentication via the JWT/OIDC auth method. Source: https://developer.hashicorp.com/vault/docs/auth/jwt (reviewed 2026-11-20). Supporting source: Identity-provider configuration examples — https://developer.hashicorp.com/vault/docs/auth/jwt/oidc-providers.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. HashiCorp publishes validated Terraform modules for Vault Enterprise on AWS EC2, Azure VMs and Google Cloud. Provider-specific networking, encryption keys, TLS material and a valid Enterprise license are prerequisites. These modules do not include an Enterprise entitlement. Scope: Vault Enterprise VM installation, HashiCorp Validated Designs. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The integrated-storage reference recommends 2–4 cores, 8–16 GB RAM and 100+ GB SSD at 3,000+ IOPS per small-cluster server; larger workloads have higher tiers. Its resilient topology uses five nodes across three zones. Audit-log I/O, replication and secret/request rates need separate sizing; these figures are not a complete 1 TB HA design. Scope: Official Vault integrated-storage per-server and cluster reference; not an application-data storage estimate. Source: https://developer.hashicorp.com/vault/tutorials/day-one-raft/raft-reference-architecture (reviewed 2026-11-20).

- License pricing: Documented. Vault Enterprise requires a commercial licence key governing feature access and use dates. The current policy distinguishes expiration from termination: release date and termination conditions affect restart, unseal and security-upgrade eligibility. Obtain the applicable self-managed quote, feature/replication entitlements and term; HCP Vault Dedicated uses a separate commercial model. Scope: Current Vault Enterprise self-managed licence-key policy; no public numeric quote established. Source: https://developer.hashicorp.com/vault/docs/license (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## VIDIZMO Digital Evidence Management

Commercial digital-evidence and redaction platform with customer-account AWS and Azure deployments.

- Listing: https://launchinyourcloud.com/directory/vidizmo-dems/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: AWS Marketplace CloudFormation/VM deployment or documented Azure deployment
- Architecture: Customer application VMs, SQL database, object storage and deployment templates.
- 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.microsoft.com/en-us/product/vidizmo.az-ama-vidizmo-dems
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This profile covers the documented Digital Evidence Management system and its licensed redaction workflows. A standalone Redactor entitlement is not inferred from a DEMS Marketplace offer. Review optional AI services, activation and managed-service terms separately from the customer-operated application.

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

Customer application VMs, SQL database, object storage and deployment templates. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Commercial digital-evidence and redaction platform with customer-account AWS and Azure deployments.

- freedom-of-information: Commercial digital-evidence and redaction platform with customer-account AWS and Azure deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20setup%20VIDIZMO%20Digital%20Evidence%20Management%20Virtual%20Machine%20on%20Azure%20Marketplace/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Cloud Guide (aws): https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/
  Customer application VMs, SQL database, object storage and deployment templates. This profile covers the documented Digital Evidence Management system and its licensed redaction workflows. A standalone Redactor entitlement is not inferred from a DEMS Marketplace offer. Review optional AI services, activation and managed-service terms separately from the customer-operated application.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure VM Setup (azure): https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20setup%20VIDIZMO%20Digital%20Evidence%20Management%20Virtual%20Machine%20on%20Azure%20Marketplace/
  Customer application VMs, SQL database, object storage and deployment templates. This profile covers the documented Digital Evidence Management system and its licensed redaction workflows. A standalone Redactor entitlement is not inferred from a DEMS Marketplace offer. Review optional AI services, activation and managed-service terms separately from the customer-operated application.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Cloud Guide: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/

- Azure VM Setup: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20setup%20VIDIZMO%20Digital%20Evidence%20Management%20Virtual%20Machine%20on%20Azure%20Marketplace/

- Azure Marketplace DEMS: https://marketplace.microsoft.com/en-us/product/vidizmo.az-ama-vidizmo-dems

- AWS Marketplace Guide: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20purchase%20VIDIZMO%20App%20on%20AWS%20Marketplace/

- FOIA Redaction: https://redactor.ai/use-cases/foia-public-records-redaction-software

- VIDIZMO SSA (BYOC): https://vidizmo.ai/subscription-service-agreement

- License Activation: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Installation%20and%20Configuration/VIDIZMO%20License%20Activation/

- Release Notes 12.3.368: https://help.vidizmo.ai/docs/Release%20Notes/Version%2012.3/Release%20Notes%2012.3.368/

- Press Releases RSS: https://vidizmo.ai/press-releases/rss.xml

### Licensing sources

- https://vidizmo.ai/subscription-service-agreement

- https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Installation%20and%20Configuration/VIDIZMO%20License%20Activation/

### Infrastructure sources

- https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/

- https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20setup%20VIDIZMO%20Digital%20Evidence%20Management%20Virtual%20Machine%20on%20Azure%20Marketplace/


### 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 official Microsoft catalog identifies this customer-subscription AzureApplication offer from VIDIZMO LLC. The publisher package and upstream application have separate maintenance. Scope: VIDIZMO Digital Evidence Management selected Azure public offer. Source: https://catalogapi.azure.com/offers/vidizmo.az-ama-vidizmo-dems?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer vidizmo.az-ama-vidizmo-dems: VIDIZMO LLC; Azure application; https://marketplace.microsoft.com/en-us/product/vidizmo.az-ama-vidizmo-dems.

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

- Single sign-on: Documented. The vendor provides a portal SAML-P setup with Microsoft Entra/Azure and an application IdP, metadata/certificate and callback configuration. Configure the selected DEMS portal, users and entitlement; mailbox OAuth, host login and vendor workforce authentication are separate identity surfaces. Scope: VIDIZMO portal-user SAML-P deployment configuration. Source: https://help.vidizmo.ai/docs/Integration%20and%20Customization/SAML-P/How%20to%20Setup%20SAMLP%20SSO%20using%20Azure/ (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 AWS deployment guide describes application infrastructure and Marketplace delivery with separately configured application/database/processing services. Supply the appropriate VIDIZMO licence and release, configure network/storage and activation, and validate the chosen topology rather than treating one VM as the full production system. Scope: Vendor VIDIZMO AWS deployment procedure; DEMS licence and service configuration required. Source: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/ (reviewed 2026-11-21). Deployment artifact: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/. Artifact reference: Current vendor AWS deployment guide.

- Minimum footprint / sizing: Documented. The prerequisite guide separates server roles: database minimum 8 cores/32 GB RAM with 150-GB OS and 256-GB data disks; application minimum 4 cores/16 GB with 150-GB OS and 100-GB data disks. Encoding, AI, broker/cache and storage roles are additional. These per-role minimums do not size a complete HA video/evidence workload. Scope: Current VIDIZMO role-specific minimums; full-system and workload capacity separate. Source: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Installation%20and%20Configuration/Prerequisites%20for%20VIDIZMO%20Application/ (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: VIDIZMO Digital Evidence Management; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://vidizmo.ai/subscription-service-agreement (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## vLLM Self-Hosted

Self-hosted model inference and serving engine with OpenAI-compatible APIs.

- Listing: https://launchinyourcloud.com/directory/vllm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 2.0 for vLLM; model weights and supporting dependencies have independent licenses and access conditions.
- Licensing model: open-source
- Installation: Official vLLM Docker image or supported Python installation; choose a compatible hardware/backend configuration.
- Architecture: Customer-operated model-serving process, model weights and inference hardware
- Operations: Customer manages model acquisition, hardware capacity, endpoint protection, availability, upgrades and model/runtime compatibility.
- Product website: https://vllm.ai/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers the inference server, not a hosted model service. It can run supported model weights on customer infrastructure, but those weights may need external downloads or access approval and are not licensed by vLLM. Review default usage telemetry and optional outbound integrations; hosting inference does not automatically create an air-gapped system. vLLM v0.34.0 removes Model Runner V1; configurations setting VLLM_USE_V2_MODEL_RUNNER=0 now fail at startup. It changes the default block size from 16 to 64, enables extensible KV cache by default with gpu_memory_utilization defaulting to 1.0, drops ROCm 7.2 wheels and images in favor of ROCm 10.0, requires huggingface_hub 2.0.0 or later, and removes QuTLASS/fp_quant and Marlin W4A8 support. Review the upstream breaking-change table and test model, quantization, memory, and accelerator compatibility before rollout.

The reviewed inference runtime is Apache-2.0 licensed. Its license does not grant rights to the model weights served by that runtime; check model and dependency terms separately.

vLLM is a running inference-server workload. Hardware support and capacity depend on the model and selected backend; the documented container paths include accelerator-specific images, and CPU support is separately documented. In v0.34.0, the KV-cache allocator sizes from free memory after warmup and defaults to gpu_memory_utilization=1.0; revalidate GPU headroom, and set 0.9 or disable extensible cache to retain prior sizing. ROCm 10.0 replaces 7.2 for published images and wheels.


### Category fit

- ai-inference-gateways: Model inference engine and OpenAI-compatible serving API for compatible model weights. Distinct from an API gateway that forwards calls to proprietary hosted models.

- ai-tools: Self-hosted model inference and serving engine with OpenAI-compatible APIs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/aws.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/azure.html (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/gcp.html (checked 2026-11-12). 


### Cloud deployment evidence

- vLLM Production Stack deployment on Amazon EKS (aws): https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/aws.html
  The project publishes Amazon EKS provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- vLLM Production Stack deployment on Azure Kubernetes Service (azure): https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/azure.html
  The project publishes Azure Kubernetes Service provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- vLLM Production Stack deployment on Google Kubernetes Engine (gcp): https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/gcp.html
  The project publishes Google Kubernetes Engine provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official Docker serving images: https://docs.vllm.ai/en/latest/deployment/docker/

- Online serving: https://docs.vllm.ai/en/latest/serving/online_serving/

- Usage statistics and opt-out: https://docs.vllm.ai/en/latest/usage/usage_stats/

- Apache 2.0 license: https://github.com/vllm-project/vllm/blob/main/LICENSE

- vLLM v0.34.0 breaking upgrade notes: https://github.com/vllm-project/vllm/releases/tag/v0.34.0

### Licensing sources

- https://github.com/vllm-project/vllm/blob/main/LICENSE

### Infrastructure sources

- https://docs.vllm.ai/en/latest/deployment/docker/

- https://github.com/vllm-project/vllm/releases/tag/v0.34.0


### 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 security guide documents API-key protection for specified HTTP path prefixes and warns that other sensitive endpoints remain unprotected. It does not establish a native SAML/OIDC user sign-on workflow. Use a reviewed gateway/network design; an API bearer key alone is not corporate SSO or complete endpoint protection. Scope: Upstream inference-server auth surface; federated user integration unresolved. Source: https://docs.vllm.ai/en/latest/usage/security/ (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 stable deployment guide links the official vllm/vllm-openai image for a CUDA-backed OpenAI-compatible server. Select a release/architecture tag and compatible GPU drivers; model memory, credentials and optional dependencies need separate review. Scope: Stable upstream CUDA image path; not the latest developer-preview guide or a GPU sizing guarantee. Source: https://docs.vllm.ai/en/stable/deployment/docker/ (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/vllm/vllm-openai. Artifact reference: select a stable version and architecture tag; latest is moving.

- Minimum footprint / sizing: Sources checked — unresolved. The stable memory guide sizes serving around model weights, precision/quantization, tensor parallelism, context length, batch size and cache. A supported accelerator alone does not establish sufficient memory. Select the exact model and target throughput/latency, then benchmark VRAM/RAM and HA replica requirements. Scope: Model-specific inference sizing; no universal numeric footprint established. Source: https://docs.vllm.ai/en/stable/configuration/conserving_memory/ (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. 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/vllm-project/vllm/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







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




## YugabyteDB Anywhere

Commercial self-managed database-as-a-service control plane for YugabyteDB clusters.

- Listing: https://launchinyourcloud.com/directory/yugabytedb-anywhere/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial installed-software license; YugabyteDB core components have separate source licenses.
- Licensing model: commercial-only
- Installation: Installer or Helm deployment, followed by customer-cloud provider configuration
- Architecture: Customer-operated management control plane and distributed database universe nodes
- Operations: Customer operates YugabyteDB Anywhere and its database nodes while the software automates provisioning, scaling, backups and upgrades.
- Product website: https://www.yugabyte.com/yugabytedb-anywhere/
- 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 YugabyteDB Anywhere, not the managed YugabyteDB Aeon service or a manual deployment of only the open-source database. Cloud provider configurations require customer credentials, network access and supported machine images.

YugabyteDB Anywhere is commercial installed software. The open-source YugabyteDB database and evaluation packages have separate terms and do not replace the production YBA entitlement.

YugabyteDB Anywhere and the database universe run as persistent control-plane and database-server workloads on VMs or Kubernetes.


### Category fit

- databases-vector: Provides a self-managed control plane for deploying and operating distributed YugabyteDB database clusters across customer cloud infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/aws/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/azure/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/gcp/ (checked 2026-11-14). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/oci/ (checked 2026-11-14). 


### Cloud deployment evidence

- YugabyteDB Anywhere AWS provider (aws): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/aws/
  Yugabyte documents customer AWS credentials, regions, networks and VM provisioning for YBA-managed database universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere Azure provider (azure): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/azure/
  Yugabyte documents customer Azure subscription credentials, resource groups, networks and VM provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere Google Cloud provider (gcp): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/gcp/
  Yugabyte documents customer GCP service accounts, projects, regions and instance provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere OCI provider (oci): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/oci/
  Yugabyte documents customer OCI credentials, regions, availability domains and VM provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- YugabyteDB Anywhere overview: https://docs.yugabyte.com/stable/yugabyte-platform/

- Provider configurations: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/

- Deployment planning: https://docs.yugabyte.com/stable/yugabyte-platform/create-deployments/create-universes-overview/

- Installed software license terms: https://www.yugabyte.com/legal/installed-software-terms/

### Licensing sources

- https://www.yugabyte.com/legal/installed-software-terms/

- https://docs.yugabyte.com/stable/faq/general/

### Infrastructure sources

- https://docs.yugabyte.com/stable/yugabyte-platform/

- https://docs.yugabyte.com/stable/yugabyte-platform/prepare/


### 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. YugabyteDB Anywhere documents OIDC authentication for its management console with IdP/client configuration and user/role mapping. This is management-platform SSO, distinct from database-user OIDC and from the vendor-operated Aeon service. Scope: YugabyteDB Anywhere administrator console; database identities separate. Source: https://docs.yugabyte.com/stable/yugabyte-platform/administer-yugabyte-platform/oidc-authentication/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Documented. YBA documents manual database-release upload for air-gapped instances and additional software prerequisites for offline database nodes. Prepare dependencies and the management/data-plane network; this is not the default connected installation. Scope: Documented YBA offline release-management path. Source: https://docs.yugabyte.com/stable/yugabyte-platform/manage-deployments/ybdb-releases/ (reviewed 2026-11-14). Supporting source: Offline database-node prerequisites — https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-nodes-software/.

- Deployment artifact / IaC: Documented. The vendor YBA Installer deploys and manages YugabyteDB Anywhere using a downloaded release, YAML configuration and installer lifecycle commands. Provision the management host and permissions separately from database universe nodes; pin a supported release and configure storage, TLS and backups. Scope: YugabyteDB Anywhere management-platform installer, not the whole managed database estate. Source: https://docs.yugabyte.com/stable/yugabyte-platform/install-yugabyte-platform/install-software/installer/ (reviewed 2026-11-21). Deployment artifact: https://docs.yugabyte.com/stable/yugabyte-platform/install-yugabyte-platform/install-software/installer/. Artifact reference: Current stable vendor YBA Installer documentation.

- Minimum footprint / sizing: Documented. The YBA management-server VM requires 4 cores, 8 GB RAM and 215 GB disk on x86 Linux. Database universes run on separate nodes and need separate sizing; these figures are not a complete database footprint. Scope: YugabyteDB Anywhere management VM only; a license file is required. Source: https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-yba/ (reviewed 2026-11-14).

- License pricing: Documented. The installed-software terms explicitly include YugabyteDB Anywhere and license executable use under an Order Form with capacity metrics such as vCPU/CPU cores. Monitor contracted usage and review support, increases and renewal terms; the open-source database core licence is a different entitlement. Scope: April 2026 installed-software commercial terms for YugabyteDB Anywhere. Source: https://www.yugabyte.com/legal/installed-software-terms/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## ZenphotoCMS

Self-hosted gallery and media content management application.

- Listing: https://launchinyourcloud.com/directory/zenphoto/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL version 2 or later for the reviewed upstream v1.6.8 core; bundled components, optional extensions and commercial packaging have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Zenphoto application, database and media files on an Azure VM.
- 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.zenphoto.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-21; infrastructure review: 2026-11-19

### Scope and qualifications

The cloudimg package and upstream 1.6 release line are separate. Optional themes and plugins can change both licensing and security requirements.

GPL version 2 or later for the reviewed upstream v1.6.8 core; bundled components, optional extensions and commercial packaging have separate terms.

Zenphoto application, database and media files on an Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted gallery and media content management application.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.zenphoto-ubuntu-24-04
  Zenphoto application, database and media files on an Azure VM. The cloudimg package and upstream 1.6 release line are separate. Optional themes and plugins can change both licensing and security requirements.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes sbillard, acrylian, fretzl, 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/zenphoto/zenphoto/graphs/contributors

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

### Sources

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

- GPL-2.0 LICENSE: https://raw.githubusercontent.com/zenphoto/zenphoto/master/LICENSE

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

### Licensing sources

- https://github.com/zenphoto/zenphoto/blob/v1.6.8/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The v1.6.8 external-authorization base class is deprecated, returns no authenticated user and states it will be removed. That extension hook alone does not establish a working SAML/OIDC integration. No maintained, version-matched gallery-user federation path was confirmed in the reviewed upstream material. Scope: Zenphoto v1.6.8 upstream gallery authentication; VM/hosting credentials are a different identity surface. Source: https://github.com/zenphoto/zenphoto/blob/v1.6.8/zp-core/classes/class-external_auth.php (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. Zenphoto documents a manual release upload and browser setup/upgrade process using a supported PHP server, database and writable gallery folders. Select a matching release and configure credentials, filesystem permissions, TLS and backups. The upstream installer is separate from any third-party marketplace VM image. Scope: Upstream self-hosted Zenphoto manual installer; not a turnkey cloud or HA template. Source: https://www.zenphoto.org/news/installation-and-upgrading/ (reviewed 2026-11-21). Deployment artifact: https://www.zenphoto.org/news/installation-and-upgrading/. Artifact reference: Current official installation and upgrading guide reviewed on this date. Supporting source: Versioned source release — https://github.com/zenphoto/zenphoto/tree/v1.6.8.

- Minimum footprint / sizing: Sources checked — unresolved. The requirements page gives approximately 55 MB for application code plus photos/cache and lists PHP/image-processing/database dependencies, but provides no complete numeric production CPU/RAM baseline. Code size does not size image processing, concurrent users, original assets, backups or HA. Scope: Upstream Zenphoto requirements; third-party VM/image hardware is not a verified application minimum. Source: https://www.zenphoto.org/news/requirements/ (reviewed 2026-11-21).

- License pricing: Documented. The v1.6.8 licence explicitly grants GPL version 2 or later. Bundled components, optional extensions, paid marketplace packaging and infrastructure require separate review. Scope: Versioned ZenphotoCMS core licence; marketplace image charges and support rights are separate. Source: https://github.com/zenphoto/zenphoto/blob/v1.6.8/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

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







## ZenTao Project Management (Open Source)

Self-hosted project, development, testing and issue management application.

- Listing: https://launchinyourcloud.com/directory/zentao/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Dual-licensed under ZPL 1.2 or GNU AGPL-3.0, at the user’s choice.
- Licensing model: open-source
- Installation: VM image
- Architecture: ZenTao application and database in a cloudimg Azure VM.
- 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-5jziwpvx4puq4
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The AWS route pairs Websoft9 platform installation with its explicit ZenTao application installer. The Azure route is cloudimg's separate VM. Package/platform versions do not establish an upstream ZenTao version; AGPL-3.0 and ZPL are alternative upstream licences.

Dual-licensed under ZPL 1.2 or GNU AGPL-3.0, at the user’s choice.

ZenTao application and database in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted project, development, testing and issue management application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.websoft9.com/en/docs/zentao/ (checked 2026-11-19). 

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


### Cloud deployment evidence

- Zentao | Websoft9 (aws): https://support.websoft9.com/en/docs/zentao/
  ZenTao application and database in a cloudimg Azure VM. The AWS route pairs Websoft9 platform installation with its explicit ZenTao application installer. The Azure route is cloudimg's separate VM. Package/platform versions do not establish an upstream ZenTao version; AGPL-3.0 and ZPL are alternative upstream licences.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.zentao-ubuntu-24-04
  ZenTao application and database in a cloudimg Azure VM. The AWS route pairs Websoft9 platform installation with its explicit ZenTao application installer. The Azure route is cloudimg's separate VM. Package/platform versions do not establish an upstream ZenTao version; AGPL-3.0 and ZPL are alternative upstream licences.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes catouse, liumengyi-luna, liyangLyon, 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/easysoft/zentaopms/graphs/contributors

- Upstream project: https://github.com/easysoft/zentaopms

### Sources

- Zentao | Websoft9: https://support.websoft9.com/en/docs/zentao/

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

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

- ZPL-1.2/AGPL-3.0 COPYING: https://github.com/easysoft/zentaopms/blob/main/COPYING

- Releases v22.7: https://github.com/easysoft/zentaopms/releases

- AWS | Websoft9: https://support.websoft9.com/en/docs/install-aws/

### Licensing sources

- https://github.com/easysoft/zentaopms/blob/main/COPYING

### Infrastructure sources

- https://support.websoft9.com/en/docs/zentao/

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


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The linked AWS offer delivers the Websoft9 platform. Its separate installer can deploy ZenTao, but a distinct transactable ZenTao software offer was not established. Scope: Websoft9 platform AMI versus the ZenTao application. Source: https://aws.amazon.com/marketplace/pp/prodview-5jziwpvx4puq4 (reviewed 2026-11-19).

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

- Single sign-on: Documented. The reviewed 22.6 source implements a ZDOO/Ranzhi SSO callback, validates the configured shared-key response, maps or binds the external account and creates the ZenTao user session. The settings explicitly target ZDOO. This confirms that specific integration, not general SAML/OIDC or current support for third-party federation plugins. Scope: Versioned source-code evidence for built-in ZDOO/Ranzhi user SSO only; broader IdP compatibility and vendor support are not established. Source: https://github.com/easysoft/zentaopms/blob/zentaopms_22.6_20260917/module/sso/zen.php (reviewed 2026-11-20). Supporting source: SSO route and configured callback — https://github.com/easysoft/zentaopms/blob/zentaopms_22.6_20260917/module/sso/control.php. Supporting source: ZDOO endpoint and shared-key settings — https://github.com/easysoft/zentaopms/blob/zentaopms_22.6_20260917/module/sso/lang/en.php.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes the easysoft/zentao container repository with installation, external-database and Compose instructions. Its description warns of the post-18.6 image-layout change to /data. Many examples still name older app/database versions; choose a verified compatible release, persistence layout and secrets before deploying. Websoft9 has separate packaged-install instructions. Scope: Vendor container artifact and third-party packaging are distinct; old samples do not establish current component support. Source: https://hub.docker.com/r/easysoft/zentao (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/easysoft/zentao/tags. Artifact reference: moving image repository; select a verified release tag, not latest or an old documentation example. Supporting source: Packager-specific console installation — https://support.websoft9.com/en/docs/zentao/.

- Minimum footprint / sizing: Sources checked — unresolved. The official container description documents persistent storage and a configurable per-PHP-process memory limit, but no complete production CPU/RAM/storage baseline was confirmed. That process limit and older single-container examples do not size current ZenTao, database, attachments, backups and HA replicas. Scope: Deployment configuration established; quantitative production and HA workload sizing remains unconfirmed. Source: https://hub.docker.com/r/easysoft/zentao (reviewed 2026-11-20).

- License pricing: Documented. Dual-licensed under ZPL 1.2 or GNU AGPL-3.0, at the user’s choice. Scope: ZenTao Project Management (Open Source); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/easysoft/zentaopms/blob/main/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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






