Software on Google Cloud
Software with a documented deployment path in a customer environment on Google Cloud.
148 listings, including 148 from other publishers. Search and filter Google Cloud listings →
Read this page as JSON or Markdown.
Each listing needs its own deployment evidence. A cloud badge identifies a documented option, not a certification or an exclusive list of compatible providers. FormKiQ listings carry a Directory Publisher disclosure.
Customer-account guidance
- Account boundary
- Google Cloud project
- Network
- VPC network
- Identity & access
- IAM policies and service accounts
- Deployment tooling
- Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-10. Check region, service availability, backup destinations and support access for your deployment.
Deployment and procurement checks
- Private offers
- Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture. Provider source ↗ · Reviewed 2026-11-14
- External workload access
- Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles. Provider source ↗ · Reviewed 2026-11-14
- Regulated environments
- Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Browse by category
37 categories on Google Cloud. Counts show matching listings; a listing can appear in more than one category.
Business operations10 categories
- Case management3 listings
- Claims management2 listings
- Contract management2 listings
- Correspondence management2 listings
- Customer support3 listings
- ERP & CRM1 listing
- Financial application management1 listing
- HR & employee records management2 listings
- Project management3 listings
- Vendor & supplier document management3 listings
Governance & industries6 categories
Content & collaboration4 categories
Data & analytics5 categories
Developer platforms & operations8 categories
AI tools & infrastructure4 categories
No categories match your search.
Documented software
Deployment evidence and qualifications
Commercial business communications and PBX platform installed into the customer's public-cloud account.
- 3CX in the customer's Google Cloud account ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
3CX documents provisioning the PBX in a customer Google Cloud account.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the cloud instance, networking and firewall, DNS/FQDN, backups, upgrades, monitoring, trunks, endpoints and licensing.
Scope: 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.
License: Proprietary annual 3CX system license; edition and simultaneous-call entitlements vary.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- 3CX in the customer's Google Cloud account ↗
Deployment evidence and qualifications
Self-hosted workflow automation platform with integrations, triggers, actions and worker execution.
- Google Cloud VM deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents running the Activepieces application container on a Google Cloud VM or instance group. Its example uses SQLite and in-memory Redis; confirm compatibility with the selected release and follow current production database, queue and security requirements.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages application configuration, secrets, integrations, backups and upgrades. AWS and Google Cloud paths require customer-managed infrastructure; Railway operates the underlying platform within the customer project.
Scope: This entry covers self-hosted Activepieces, not Activepieces Cloud. The AWS template can provision RDS PostgreSQL, Redis, load balancing and Route 53 integration. The Google Cloud guide uses a VM/container example with SQLite and in-memory Redis; confirm release compatibility and use the current production database and queue requirements. Railway deploys into a customer project on platform-managed infrastructure. Enterprise features require a separate license.
License: MIT-licensed Community Edition core; enterprise and cloud feature directories use commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Google Cloud VM deployment ↗
Deployment evidence and qualifications
Self-managed data movement and ELT platform with customer-operated connectors and job execution.
- Airbyte self-managed deployment on named cloud providers ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or VM capacity, the metadata database, object storage, secrets, connector images, network access, backups and upgrades.
Scope: 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.
License: Elastic License 2.0 for the Airbyte platform; connector and component licenses vary. Enterprise and Cloud offerings use separate commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Airbyte self-managed deployment on named cloud providers ↗
Deployment evidence and qualifications
Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.
- Aiven custom cloud on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
The customer sets up a Google Cloud custom cloud in its project before provisioning Kafka.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Aiven manages provisioning and maintenance. The customer provides the cloud account, network configuration, IAM, quotas, and backup storage access.
Scope: 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.
License: Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately.
Cloud evidence reviewed 2026-11-21. Read the full listing and sources →
- Aiven custom cloud on Google Cloud ↗
Deployment evidence and qualifications
Self-hosted application for document-grounded AI chat, retrieval and agents.
- AnythingLLM Docker installation overview ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project explicitly names AWS, Google Cloud and Railway for self-hosting the Docker edition, paired with its Docker installation workflow. This is an upstream hosting compatibility statement. Model endpoints, embeddings and external vector stores are separately configured and can have different data boundaries.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages users, documents, persistent storage, model access, integration secrets, backups and upgrades.
Scope: The Docker edition supports multi-user operation and differs from the desktop application. Local inference is an option; configured external LLMs, embeddings, vector stores and agent tools can send data outside the account. AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Optional MCP identity forwarding creates a new outbound identity path; keep the server and extension on compatible 1.20+ versions.
License: MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- AnythingLLM Docker installation overview ↗
Deployment evidence and qualifications
Column-oriented analytics database for interactive queries over streaming and historical event data.
- Apache Druid cloud deployment FAQ ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cluster sizing, ingestion, metadata and deep storage, access controls, backups and upgrades.
Scope: 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.
License: Apache License 2.0 for upstream Apache Druid.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Apache Druid cloud deployment FAQ ↗
Deployment evidence and qualifications
Distributed event streaming platform for durable publication, storage and consumption of event streams.
- Apache Kafka deployment on GKE using Strimzi ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Google documents creating customer GKE infrastructure and deploying Apache Kafka through the Strimzi operator. This is upstream Kafka operated in the customer project, not Confluent Cloud. The published tutorial includes version-specific ZooKeeper/KRaft assumptions; verify current Kafka and Strimzi compatibility and production security.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages broker capacity, replication, retention, authentication, authorization, monitoring and upgrades.
Scope: The single-node quickstart is an evaluation starting point. Commercial Kafka distributions, hosted services and independently licensed connectors are outside this upstream listing.
License: Apache License 2.0 for upstream Apache Kafka.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Apache Kafka deployment on GKE using Strimzi ↗
Deployment evidence and qualifications
Commercial contract lifecycle application installed into a licensed, self-managed Appian platform.
- Appian on K8s ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Appian on K8s ↗
Deployment evidence and qualifications
Build internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.
- Appsmith provider-specific installation index ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages deployment, persistent databases, backups, networking and upgrades; confirm edition-specific vendor connectivity.
Scope: 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.
License: Apache-2.0 Community core; commercial edition and plan-dependent features
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Appsmith provider-specific installation index ↗
Deployment evidence and qualifications
Self-hosted backend services for authentication, databases, storage, functions and messaging.
- Appwrite self-hosting on google-cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer configures the environment and handles software updates, scaling, security and backups.
Scope: 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.
License: BSD-3-Clause core; enterprise services and feature terms should be confirmed separately
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Appwrite self-hosting on google-cloud ↗
Deployment evidence and qualifications
AI observability and evaluation server for traces, datasets and application experiments.
- Phoenix self-hosting deployment options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.
Scope: 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.
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.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Phoenix self-hosting deployment options ↗
Deployment evidence and qualifications
Self-hosted no-code database for organizing, relating and collaborating on business data.
- Baserow Docker image compatibility with Google Cloud Run ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide explicitly designs the all-in-one application image for simple container services such as Google Cloud Run. Use external PostgreSQL, Redis and durable file storage for a stateless runtime; this is an application-hosting compatibility statement, not evidence based only on a Google storage adapter.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the application, database and storage, applies updates and configures backups.
Scope: Self-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.
License: MIT-licensed core with paid premium features and subscription terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Baserow Docker image compatibility with Google Cloud Run ↗
Deployment evidence and qualifications
Self-hosted conferencing and virtual classroom platform.
- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 ↗
Deployment evidence and qualifications
Commercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
- Bitbucket Data Center on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or hosts, Git and shared storage, Mesh where used, database, search, networking, TLS, identity, backups, monitoring and upgrades.
Scope: 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.
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.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Bitbucket Data Center on EKS, AKS or GKE ↗
Deployment evidence and qualifications
Commercial self-managed process orchestration and workflow automation platform.
- Camunda 8 Self-Managed on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
Camunda documents its Self-Managed Helm deployment and Google Cloud-specific GKE configuration.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, supported databases or search services, storage, ingress, identity, backups, scaling and upgrades.
Scope: 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.
License: Commercial Enterprise license required for production; unlicensed use is limited to non-production conditions.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- Camunda 8 Self-Managed on Google GKE ↗
Deployment evidence and qualifications
Self-hosted customer-support inbox combining live chat, email and messaging conversations.
- Chatwoot self-hosted deployment on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains the server, database, storage, updates and channel integrations; support differs by plan.
Scope: 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.
License: MIT Community Edition; proprietary enterprise features and paid self-hosted plans
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Chatwoot self-hosted deployment on Google Cloud ↗
Deployment evidence and qualifications
Commercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
- CircleCI Server on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16 · Version: 4.10. Vendor support commitment: not assessed; confirm the selected release and contract.
CircleCI documents preparing a customer GCP project, VPC, GKE cluster, Cloud Storage and workload identity before installing CircleCI Server. The guide states that GKE Autopilot is unsupported.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, networking, object storage, databases, secrets, TLS, execution capacity, backups, upgrades and the CircleCI Server license.
Scope: This entry covers CircleCI Server, not CircleCI Cloud or cloud-connected self-hosted runners. EKS and GKE are the tested cloud environments; CircleCI labels Azure and DigitalOcean as untested. GKE Autopilot is unsupported. CircleCI Server currently supports GitHub Enterprise Cloud and GitHub Enterprise Server as version-control providers.
License: Commercial CircleCI Server license required.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- CircleCI Server on Google GKE ↗
Deployment evidence and qualifications
Managed analytical database with its data plane in your cloud account.
- ClickHouse BYOC customer account support ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: ClickHouse operates the BYOC service; the customer owns the cloud environment.
Scope: 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.
License: Commercial
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- ClickHouse BYOC customer account support ↗
Deployment evidence and qualifications
Open-source cloud-usage, energy and carbon-estimation application.
- GCP App Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. The named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: The named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP App Engine ↗
Deployment evidence and qualifications
Enterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
- CloudBees CI installation on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer provisions and operates Kubernetes, storage, networking, ingress, DNS, certificates and upgrades; CloudBees supports the licensed application within documented boundaries.
Scope: 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.
License: Commercial CloudBees CI license required.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- CloudBees CI installation on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Cloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.
- Cloudera workloads in customer AWS, Azure and Google Cloud environments ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Cloudera operates the service control plane; the customer owns cloud resources, credentials, data governance, network integration, workload sizing and shared operational responsibilities.
Scope: 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.
License: Commercial Cloudera subscription with cloud infrastructure charges paid separately.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Cloudera workloads in customer AWS, Azure and Google Cloud environments ↗
Deployment evidence and qualifications
Vendor-managed CockroachDB service deployed into the customer's AWS, Azure or Google Cloud account.
- CockroachDB BYOC customer-cloud support ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Cockroach Labs manages database provisioning, upgrades, backups, monitoring and incidents; the customer owns the cloud account, network and billing boundary.
Scope: 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.
License: Commercial CockroachDB BYOC service.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- CockroachDB BYOC customer-cloud support ↗
Deployment evidence and qualifications
Commercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
- Confluence Data Center on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16 · Version: 11.0; use the current compatibility matrix for other releases. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, Synchrony, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
Scope: 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.
License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Confluence Data Center on EKS, AKS or GKE ↗
Deployment evidence and qualifications
Self-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.
- Confluent for Kubernetes guidance for EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: A commercial Confluent subscription is required for Confluent Platform components deployed with CFK; component licenses otherwise vary.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Confluent for Kubernetes guidance for EKS, AKS and GKE ↗
Deployment evidence and qualifications
Self-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
- Coroot on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor explicitly names GKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: The customer manages the operator, image versions, privileged node-agent permissions, storage capacity, telemetry retention, backup and recovery, and access to the UI.
Scope: 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.
License: Apache License 2.0 for Coroot Community Edition. Enterprise Edition has separate subscription terms.
Cloud evidence reviewed 2026-11-20. Read the full listing and sources →
- Coroot on Google GKE ↗
Deployment evidence and qualifications
Self-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.
- Couchbase Server Enterprise on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Enterprise Edition · Version: Server 7.2 through 8.0 in the reviewed compatibility matrix. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, storage, networking, security, backups and upgrade policy; the Operator automates database lifecycle operations.
Scope: 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.
License: Commercial subscription for Couchbase Server Enterprise Edition; Community Edition is separately licensed.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Couchbase Server Enterprise on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Commercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.
- GCP Deploy ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP Deploy ↗
Deployment evidence and qualifications
Data and AI platform with classic compute in your cloud environment.
- Databricks classic compute architecture ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: The vendor manages the control plane. Your team configures classic compute, cloud resources and policies.
Scope: 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.
License: Commercial
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Databricks classic compute architecture ↗
Deployment evidence and qualifications
Datadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
- Datadog BYOC Logs on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
Vendor guide installs the engine in the customer's Google Cloud project with GKE, Cloud Storage, PostgreSQL and Workload Identity.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial Datadog software and service. Confirm BYOC Logs activation and commercial terms with the account team.
Cloud evidence reviewed 2026-11-20. Read the full listing and sources →
- Datadog BYOC Logs on Google GKE ↗
Deployment evidence and qualifications
Open-source data catalog and metadata platform for discovery, lineage and governance.
- DataHub on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
The official guide deploys DataHub to a customer GKE cluster with Helm and provider-managed dependency options.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, stateful dependencies, networking, secrets, backups, scaling, ingestion, and upgrades, including search-backend compatibility and per-version breaking-change actions.
Scope: 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.
License: Apache License 2.0.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- DataHub on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Commercial Dataiku DSS deployment managed through Fleet Manager inside a customer AWS, Azure or Google Cloud tenant.
- Dataiku DSS Cloud Stacks on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cloud accounts, Fleet Manager, IAM identities, networking, VM and Kubernetes capacity, storage, TLS, backups, upgrades and license configuration.
Scope: 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.
License: Commercial Dataiku license or license token required for the full Cloud Stacks capabilities.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Dataiku DSS Cloud Stacks on Google Cloud ↗
Deployment evidence and qualifications
Commercial rules and workflow platform with provider-specific container deployments.
- GCP Deploy ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP Deploy ↗
Deployment evidence and qualifications
Self-hosted discussion and community platform for workplace collaboration and customer support communities.
- Discourse supported cloud server installation ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The official cloud installation guide explicitly names DigitalOcean, AWS EC2, Google Cloud, Linode/Akamai, Vultr and Hetzner as supported hosts, then provides a complete server installation workflow. This is provider compatibility for the customer-operated Discourse application, not its separate hosted SaaS; configure the supported OS, DNS, email, HTTPS and recovery.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains the Linux host, Docker deployment, backups, updates and configured messaging services; choose an actively supported release channel.
Scope: This entry covers self-hosted Discourse. The official cloud installation guide explicitly lists AWS EC2 and Google Cloud as supported Docker hosts; customers provision the Linux server, rather than using a bundled cloud-specific infrastructure template. The installer offers an external Discourse ID login option when SMTP is skipped. Review authentication, email and other integrations for outbound data flows. Supported-series updates published November 10, 2026 include 2026.10.1 and 2026.7.5 ESR; the 2026.10.1 changelog records 38 security fixes. Self-hosted operators should upgrade on their selected supported release channel.
License: GPL-2.0 core; review extensions separately
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Discourse supported cloud server installation ↗
Deployment evidence and qualifications
Self-hosted document forms and electronic-signature workflows with API and webhook integration.
- Vendor Google Cloud Run deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Vendor Google Cloud Run deployment ↗
Deployment evidence and qualifications
Vendor-operated content platform deployed into a customer cloud account.
- Cloud Anywhere Quickstart ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Vendor operates the Cloud Anywhere application through its management plane and scoped customer-cloud access; agree support access, logs, egress and exit procedures.
Scope: 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.
License: Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloud Anywhere Quickstart ↗
Deployment evidence and qualifications
Self-managed distributed SQL and lakehouse analytics platform for customer-controlled data sources.
- Dremio self-managed editions on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Dremio-tested EKS, AKS and GKE environments ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or container capacity, storage, security, scaling, upgrades, backups and integration with data sources.
Scope: 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.
License: Apache License 2.0 for Dremio Community; Dremio Enterprise uses separate commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Dremio self-managed editions on AWS, Azure and Google Cloud ↗
Deployment evidence and qualifications
Commercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- Elastic Cloud Enterprise on public cloud hosts ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.
Scope: 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.
License: Commercial Elastic Cloud Enterprise license required after the trial.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Elastic Cloud Enterprise on public cloud hosts ↗
Elastic Cloud on Kubernetes
Databases & vector · Observability · Data & analytics · AI tools & infrastructure
Deployment evidence and qualifications
Elastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- Elastic Cloud on Kubernetes on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.
Scope: 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.
License: Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Elastic Cloud on Kubernetes on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Managed data capture, transformation, and delivery with a dedicated data plane in the customer's cloud account.
- Estuary BYOC on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
The guide asks for project-level Editor access for Estuary's controller principal.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial BYOC under an annual Enterprise agreement with custom pricing.
Cloud evidence reviewed 2026-11-21. Read the full listing and sources →
- Estuary BYOC on Google Cloud ↗
Deployment evidence and qualifications
Open-source business operations platform for people, projects, time and financial records.
- GCP Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP Guide ↗
Deployment evidence and qualifications
Feature management platform for targeted rollouts and remotely configured application behavior.
- Flagsmith self-hosted platform architecture ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages flag API availability, SDK endpoints, database, permissions, secrets, backups and upgrades.
Scope: 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.
License: BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Flagsmith self-hosted platform architecture ↗
Deployment evidence and qualifications
Proprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.
- FusionAuth on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
FusionAuth documents the full application on customer GKE and Google Cloud database resources.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: FusionAuth Customer License Agreement; Community and paid plans are proprietary, with feature and support limits by plan.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- FusionAuth on Google GKE ↗
Deployment evidence and qualifications
Customer-operated GitHub software-development platform deployed as a licensed virtual appliance.
- GitHub Enterprise Server on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
GitHub documents deploying its appliance image to a supported Compute Engine VM with persistent disks in the customer's project.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer provisions infrastructure and manages networking, storage, backups, upgrades, monitoring and high availability.
Scope: 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.
License: Commercial GitHub Enterprise license required.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- GitHub Enterprise Server on Google Cloud ↗
Deployment evidence and qualifications
Source control and CI/CD on infrastructure you operate.
- GitLab Self-Managed cloud installation guides ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Your team operates, upgrades and backs up the installation.
Scope: 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.
License: Free and paid tiers
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- GitLab Self-Managed cloud installation guides ↗
Deployment evidence and qualifications
Open-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
- Gravitee APIM self-hosted deployment on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16 · Version: 4.10. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or hosts, databases, search, networking, ingress, TLS, identity, secrets, monitoring, backups, scaling, upgrades and any Enterprise license.
Scope: 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.
License: Apache License 2.0 Community Edition; Enterprise Edition requires a commercial license.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Gravitee APIM self-hosted deployment on EKS, AKS or GKE ↗
Deployment evidence and qualifications
Commercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.
- Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages controllers, workers, PostgreSQL, KMS, PKI, networking, identity integrations, backups, upgrades and availability.
Scope: 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.
License: Commercial Boundary Enterprise license required; HCP Boundary is a separate hosted service.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud ↗
Deployment evidence and qualifications
Commercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
- Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.
Scope: 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.
License: Commercial Consul Enterprise license required for the selected validated design.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud ↗
Deployment evidence and qualifications
Commercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.
- Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.
Scope: 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.
License: Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud ↗
Deployment evidence and qualifications
GraphQL API engine that exposes connected databases through permission-aware application APIs.
- Hasura GraphQL Engine on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages engine and metadata storage, database access, admin secrets, authorization, TLS, and coordinated engine/database upgrades.
Scope: 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.
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.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Hasura GraphQL Engine on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Commercial web content and digital asset management platform deployed by Helm to customer-operated Kubernetes.
- HCL Digital Experience on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
HCL's current support matrix explicitly lists Google GKE as a tested and supported full-container platform.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, storage, databases and integrations, ingress, certificates, capacity, backups, upgrades and version compatibility.
Scope: 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.
License: Commercial HCL Digital Experience Cloud Native subscription measured by user sessions and associated production processing capacity.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- HCL Digital Experience on Google GKE ↗
Hyland OnBase On-Premise
Document management · Records management · Contract management · Financial application management · Case management · Correspondence management · Vendor & supplier document management · HR & employee records management · Policy & procedure management · Claims management · Workflow automation
Deployment evidence and qualifications
Customer-hosted enterprise content and case platform for document-heavy business processes.
- Hyland partner statement on customer-managed OnBase cloud deployments ↗
Partner evidence · Reviewed 2026-11-12 · Version: OnBase 18+ in partner statement; confirm current release. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Hyland identification of Reveille as an authorized integration partner ↗
Partner relationship · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.
Scope: 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.
License: Commercial OnBase licenses and separately scoped modules
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Hyland partner statement on customer-managed OnBase cloud deployments ↗
Deployment evidence and qualifications
Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.
- Helm Chart (AWS/GCP) ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Helm Chart (AWS/GCP) ↗
Deployment evidence and qualifications
Customer-managed enterprise reporting and analytics deployed by Helm to a Kubernetes cluster in the customer's cloud.
- Cognos Certified Containers on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
IBM documents the certified Cognos containers on Amazon EKS, Microsoft AKS and Google GKE. Non-OpenShift support is narrower than the OpenShift delivery model.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, databases, authentication, storage, ingress, capacity, backups and upgrades; IBM support scope varies by platform.
Scope: 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.
License: Commercial, separately licensed Cognos Analytics Certified Containers entitlement.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Cognos Certified Containers on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Licensed self-managed planning, budgeting and multidimensional analytics cartridge.
- Application deployment guidance ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Application deployment guidance ↗
Deployment evidence and qualifications
Self-hosted secrets-management platform with application and machine-identity access workflows.
- Vendor GKE installation in the customer Google Cloud project ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Provisions GKE, Cloud SQL and Memorystore and installs the application Helm release in the operator project. Review supported chart/image versions, VPC access, TLS, key backup and database migrations. This is an application deployment, distinct from connecting Infisical to Google secrets APIs.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer owns the AWS account, Google project or Vultr instance and manages application identity, encryption keys, database recovery and upgrades. Providers operate selected managed infrastructure services.
Scope: Review used upstream 0.167.10. Vendor AWS/GCP examples contain older version placeholders; pin a current compatible image/chart and use the complete installation steps, not the abbreviated infrastructure snippets alone. Preserve encryption keys independently of database backups. Configure telemetry, mail and external secret/infrastructure connections for the intended boundary. Infisical Cloud and agent-only integrations are separate. Infisical v0.167.13 tightens delegated OAuth-token authorization: scope-narrowed tokens no longer pass role-only administration checks, approval/rejection/bypass operations are denied, and workspace listing checks organization permission. Previously accepted delegated-token calls may return 403; retest automation with least-privilege scopes.
License: MIT core outside enterprise directories; enterprise features and third-party components have separate terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Vendor GKE installation in the customer Google Cloud project ↗
Deployment evidence and qualifications
Customer-hosted project and issue management application from JetBrains.
- YouTrack Server Kubernetes deployment on named cloud services ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Docker/server resources, persistent data, backups, TLS/network configuration and upgrades.
Scope: 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.
License: Proprietary YouTrack Server subscription; a limited free-user tier is available
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- YouTrack Server Kubernetes deployment on named cloud services ↗
Deployment evidence and qualifications
Universal artifact repository installed on Kubernetes clusters or servers you operate.
- Artifactory Helm installation on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the cluster or servers, database, filestore, backups, upgrades and availability configuration.
Scope: 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.
License: Open-source Artifactory OSS; commercial Pro X, Enterprise X and Enterprise+ editions.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Artifactory Helm installation on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Commercial self-managed IT service management platform deployed on customer-operated infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
- Jira Service Management Data Center on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, email, Marketplace apps, backups, monitoring and upgrades.
Scope: 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.
License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Jira Service Management Data Center on EKS, AKS or GKE ↗
Deployment evidence and qualifications
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.
- Jira Data Center on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
Scope: 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.
License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Jira Data Center on EKS, AKS or GKE ↗
Deployment evidence and qualifications
Self-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.
- Kestra on Google GKE with Cloud SQL and Cloud Storage ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages server and worker capacity, PostgreSQL, object storage, plugins, credentials, network access, backups and upgrades.
Scope: 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.
License: Apache License 2.0 for the open-source Kestra platform; commercial Enterprise features and support are separate.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Kestra on Google GKE with Cloud SQL and Cloud Storage ↗
Deployment evidence and qualifications
Commercial workflow collaboration and automation platform launched from AWS, Azure or Google Cloud Marketplace VM images.
- KNIME Business Hub on Google Cloud Marketplace ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
KNIME documents launching Business Hub through Google Cloud Marketplace using a Google Compute VM image in the customer's project.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the cloud account, virtual machine, networking, DNS, TLS, identity, storage, backups, capacity, upgrades and Business Hub license.
Scope: 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.
License: Commercial KNIME Business Hub license or Marketplace software subscription required.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- KNIME Business Hub on Google Cloud Marketplace ↗
Deployment evidence and qualifications
Open-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
- Kong Gateway supported public-cloud deployment platforms ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Apache License 2.0 for the open-source core; Enterprise features use separate commercial licensing.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Kong Gateway supported public-cloud deployment platforms ↗
Deployment evidence and qualifications
Visual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.
- Langflow Kubernetes deployment architecture ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the application, database, access controls, installed components, backups and version upgrades.
Scope: 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.
License: MIT for the upstream project; connected models, providers and bundles have their own terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Langflow Kubernetes deployment architecture ↗
Deployment evidence and qualifications
Self-hosted LLM observability, evaluations and prompt-management platform.
- Langfuse customer cloud deployment on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
Scope: 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.
License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Langfuse customer cloud deployment on Google Cloud ↗
Deployment evidence and qualifications
Commercial digital experience, content management and digital asset platform deployed into customer cloud infrastructure with Liferay's Cloud Native Experience toolkit.
- Liferay DXP Cloud Native Experience GCP Ready ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Google Cloud environment, including GKE and managed data services.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the cloud account, GitOps repository, Kubernetes platform, secrets, domains, certificates, capacity, backups, upgrades and application customizations.
Scope: 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.
License: Commercial Liferay DXP subscription; Cloud Native Experience provider-ready capabilities require Enterprise Subscription entitlement.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Liferay DXP Cloud Native Experience GCP Ready ↗
Deployment evidence and qualifications
Self-hosted AI API gateway providing model routing, access controls and usage tracking.
- LiteLLM production deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: MIT outside the enterprise directory; enterprise code and features have separate license terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- LiteLLM production deployment ↗
Deployment evidence and qualifications
Customer-hosted commercial document platform for controlled business files and supplier documentation.
- LogicalDOC private-cloud deployment options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages application, database, document storage, backups and upgrades; agree support scope and required commercial capabilities.
Scope: 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.
License: Commercial edition under LogicalDOC EULA; separate Community Edition exists
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- LogicalDOC private-cloud deployment options ↗
Deployment evidence and qualifications
Customer-operated document vault and information-governance platform with metadata-driven workflows.
- M-Files self-managed cloud deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains server infrastructure, vault backups and upgrades; review server requirements and the contracted support and licensing connections.
Scope: 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.
License: Commercial subscription software; on-premises and support entitlements follow the order
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- M-Files self-managed cloud deployment ↗
Deployment evidence and qualifications
Self-hosted web analytics with visitor, campaign and website reporting on customer servers.
- Matomo named-cloud compatibility FAQ ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages hosting, upgrades, security, backups, tracking configuration and scheduled report processing.
Scope: 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.
License: GPLv3-or-later core; premium plugins use separate commercial EULA and subscription terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Matomo named-cloud compatibility FAQ ↗
Deployment evidence and qualifications
Self-hosted team messaging and collaborative operational workflows on customer infrastructure.
- Mattermost self-hosted provider architecture and sizing ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains the deployment, database, storage, upgrades and availability; subscriptions govern supported enterprise capabilities.
Scope: 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.
License: MIT Team Edition; commercial Enterprise offerings and separately licensed components; inspect the selected edition
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Mattermost self-hosted provider architecture and sizing ↗
Deployment evidence and qualifications
Open-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
- Production-validated Medplum deployment on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The official Terraform and Helm workflow deploys Medplum into the customer's Google Cloud project with GKE, Cloud SQL, Redis, storage and frontend resources.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.
Scope: 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.
License: Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Production-validated Medplum deployment on Google Cloud ↗
Deployment evidence and qualifications
Self-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.
- Meilisearch Community Edition on Google Compute Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents a production-oriented installation on a customer Google Compute Engine VM with billing enabled, including the official binary installer, dedicated service account, persistent data directory, systemd service and firewall configuration. The customer operates the VM and search service.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the VM, operating system, network rules, master key, TLS, persistent indexes, backups, monitoring, capacity and version upgrades.
Scope: The reviewed provider guides deploy a customer-operated server rather than a managed Meilisearch service. Meilisearch Cloud is the vendor-recommended production option, but the Community Edition is explicitly available for independent hosting. Community Edition does not include Enterprise-only sharding, so the documented VM paths do not establish a highly available or horizontally sharded topology. Configured remote embedders or LLM providers can receive indexed or query content; user-provided vectors and customer-selected local endpoints can produce a different data boundary. Meilisearch 1.56.1 and 1.55.1 were security maintenance releases; current 1.57.0 includes those fixes. Affected deployments should move to 1.57.0 or an appropriate later supported patch and review the vendor's branch guidance.
License: MIT License for Community Edition. Enterprise Edition uses a BUSL license, cannot be freely used in production and requires a commercial agreement for production self-hosting.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Meilisearch Community Edition on Google Compute Engine ↗
Deployment evidence and qualifications
Commercial low-code application runtime operated in customer Kubernetes infrastructure.
- Supported Clouds ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Supported Clouds ↗
Deployment evidence and qualifications
Business intelligence and dashboards on your infrastructure.
- Metabase production hosting compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Your team manages hosting, upgrades and the application database.
Scope: 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.
License: Open-source and commercial options
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Metabase production hosting compatibility ↗
Deployment evidence and qualifications
Vector database for similarity search and retrieval over embedding collections.
- Milvus deployment on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.
Scope: 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.
License: Apache License 2.0 for upstream Milvus.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Milvus deployment on Google Kubernetes Engine ↗
MLflow Tracking Server Self-Hosted
AI observability & LLMOps · AI tools & infrastructure · Observability
Deployment evidence and qualifications
Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.
- Self-hosted MLflow deployment on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.
Scope: 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.
License: Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Self-hosted MLflow deployment on Google Cloud ↗
Deployment evidence and qualifications
Automate integrations and business processes with a customer-hosted workflow editor and runtime.
- n8n deployment on Google Cloud Run ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
Scope: 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.
License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- n8n deployment on Google Cloud Run ↗
Deployment evidence and qualifications
Self-managed graph database available in open-source Community and commercial Enterprise editions.
- Neo4j Helm deployments on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages compute, storage, networking, security, backups, monitoring, capacity and upgrades.
Scope: 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.
License: GPLv3 Community Edition; Enterprise Edition uses a commercial Neo4j license.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- Neo4j Helm deployments on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Open-source zero-trust networking control plane self-hosted on a customer cloud VM.
- NetBird self-hosted control plane on a cloud VM ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Community Edition. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.
Scope: 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.
License: Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- NetBird self-hosted control plane on a cloud VM ↗
Deployment evidence and qualifications
Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.
- NocoDB community cloud installation methods ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
Scope: The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.
License: Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- NocoDB community cloud installation methods ↗
Deployment evidence and qualifications
Commercial enterprise AI software suite deployed on customer cloud GPU instances or managed Kubernetes clusters.
- NVIDIA AI Enterprise on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial NVIDIA AI Enterprise subscription, consumption or perpetual license; most customer-cloud paths require BYOL.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- NVIDIA AI Enterprise on AWS, Azure and Google Cloud ↗
Deployment evidence and qualifications
Deployment automation and runbook platform installed on servers or Kubernetes infrastructure you operate.
- Octopus Server in customer Kubernetes clusters with AKS and GKE guidance ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the server or cluster, SQL database, persistent storage, backups, security, upgrades and availability configuration.
Scope: 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.
License: Proprietary Free tier or annual Professional and Enterprise licenses.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Octopus Server in customer Kubernetes clusters with AKS and GKE guidance ↗
Deployment evidence and qualifications
Self-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.
- Onyx on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
Onyx documents Compute Engine and production GKE deployment paths in the customer's Google Cloud project.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages application services, databases, search, object storage, connectors, model credentials, backups, scaling and upgrades.
Scope: 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.
License: MIT Community Edition; Business and Enterprise features use separate commercial terms.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- Onyx on Google Cloud ↗
Deployment evidence and qualifications
Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.
- Open WebUI deployment on Google Cloud Run ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer runs application storage, authentication, provider configuration, updates and backups.
Scope: 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.
License: Open WebUI license based on BSD-style terms with additional branding restrictions and defined exceptions; enterprise terms may be required for rebranding.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Open WebUI deployment on Google Cloud Run ↗
Deployment evidence and qualifications
Open-source civil registration software for birth, death and related registration workflows.
- GCP GKE Terraform ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP GKE Terraform ↗
Deployment evidence and qualifications
Self-hosted health-financing software supporting health-insurance claim submission, review and reimbursement.
- openIMIS production server deployment on named VPS providers ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Scheme operator and implementation partner host, configure and maintain the installation.
Scope: 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.
License: Open-source; official distribution licensed under AGPL v3
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- openIMIS production server deployment on named VPS providers ↗
Deployment evidence and qualifications
Open-source metadata catalog and data-governance platform deployed with customer-operated services.
- OpenMetadata on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
The official guide deploys OpenMetadata with Helm on GKE. It explicitly notes that GKE Autopilot is incompatible with the documented Elasticsearch configuration.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, database, search, ingestion orchestration, secrets, backups, scaling and upgrades.
Scope: 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.
License: Apache License 2.0.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- OpenMetadata on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Self-hosted observability platform for ingesting, searching and analyzing logs, metrics and traces.
- OpenObserve Enterprise on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: The customer runs the cluster, configures storage credentials and ingestion endpoints, sizes components, manages backups and retention, and applies chart and application upgrades.
Scope: 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.
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.
Cloud evidence reviewed 2026-11-20. Read the full listing and sources →
- OpenObserve Enterprise on Google GKE ↗
Deployment evidence and qualifications
Self-hosted business VPN and network-access server deployed in the customer's cloud account.
- Access Server Google Cloud Marketplace deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The official guide deploys the self-hosted Access Server instance into the customer's selected Google Cloud project and VPC.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages compute, routing, network exposure, identity integration, certificates, upgrades, backups and availability.
Scope: 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.
License: Commercial subscription, fixed and cloud-marketplace licenses; unlicensed mode is limited to two connections.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Access Server Google Cloud Marketplace deployment ↗
Deployment evidence and qualifications
Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.
- # Paramify configuration
#
# Example install:
# helm registry login registry.paramify.com --username paramify@mycompan ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- # Paramify configuration
#
# Example install:
# helm registry login registry.paramify.com --username paramify@mycompan ↗
Deployment evidence and qualifications
Node.js application backend for data APIs, users, permissions and server-side application logic.
- Parse Server cloud hosting options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.
Scope: 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.
License: Apache License 2.0 for upstream Parse Server.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Parse Server cloud hosting options ↗
Deployment evidence and qualifications
Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.
- GKE Runbook ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GKE Runbook ↗
Deployment evidence and qualifications
Commercial centralized version-control server deployed from Perforce's cloud quickstarts into customer infrastructure.
- P4 Server on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Perforce documents deployment into the customer's selected Google Cloud project.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages VM and OS security, depot and metadata storage, accounts, firewall, backups, logs, upgrades, capacity and any replication or edge topology.
Scope: 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.
License: Proprietary P4 license; free within the published small-team limits, with commercial licensing and support above them.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- P4 Server on Google Cloud ↗
Philter by Philterd (Self-Hosted / Cloud Marketplace)
Freedom of information & public access · Document management
Deployment evidence and qualifications
Open-source API that identifies and redacts sensitive information in text and PDFs.
- Philter: Open Source, Self-Hosted PII & PHI Redaction API ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Philter: Open Source, Self-Hosted PII & PHI Redaction API ↗
Deployment evidence and qualifications
Self-hosted workflow server and Python framework for resilient task and data pipelines.
- Prefect deployment through Northflank BYOC ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.
Scope: 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.
License: Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Prefect deployment through Northflank BYOC ↗
Deployment evidence and qualifications
Enterprise infrastructure-delivery control plane deployed and operated in the customer's cloud account.
- Pulumi Cloud Self-Hosted on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Pulumi Enterprise Self-Hosted. Vendor support commitment: not assessed; confirm the selected release and contract.
The official deployment option installs the full self-hosted Pulumi Cloud service on customer Google GKE and supporting Google Cloud resources.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates backups, uptime, infrastructure and upgrades; Pulumi supplies the licensed application and deployment tooling.
Scope: 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.
License: Commercial Pulumi Enterprise subscription with the Self-Hosted deployment option
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Pulumi Cloud Self-Hosted on Google GKE ↗
Deployment evidence and qualifications
Self-hosted vector database for semantic retrieval and AI application data.
- Self-operated Qdrant cluster on Google Kubernetes Engine ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Google documents provisioning a regional GKE cluster and installing Qdrant with Helm and persistent disks. The customer operates the database cluster; this is separate from Qdrant Cloud and its separately offered Hybrid Cloud service.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages persistence, backups, access controls, upgrades and any distributed-cluster operations.
Scope: The local quickstart is an installation starting point, not a secured production configuration. Applications can supply their own vectors or use separately configured embedding models. External embedding APIs and hosted inference can receive source data even when the database is self-hosted; local FastEmbed is a documented alternative. This entry excludes Qdrant Cloud hosting. Qdrant 1.20.1, released November 13, 2026, prevents collection-scoped JWTs from viewing snapshot telemetry for collections they cannot access; operators using scoped JWTs should upgrade.
License: Apache 2.0 for the upstream database; managed cloud offerings and support have separate commercial terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Self-operated Qdrant cluster on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Commercial client-managed analytics platform installed on customer cloud Windows virtual machines.
- Qlik Sense Enterprise on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
Qlik documents preparing Google Compute Engine Windows instances and installing Qlik Sense Enterprise on Windows.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Windows hosts, networking, certificates, identity, repository database, shared storage, load balancing, backups, scaling, upgrades and license activation.
Scope: 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.
License: Commercial Qlik Sense Enterprise license.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Qlik Sense Enterprise on Google Cloud ↗
Deployment evidence and qualifications
Apache-licensed time-series database installed on customer virtual machines in AWS, Azure or Google Cloud.
- QuestDB on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
QuestDB documents deployment to customer Compute Engine with separate durable storage.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages VM and OS, data disks, networking, authentication, backups, monitoring, upgrades and capacity.
Scope: 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.
License: QuestDB Open Source is Apache License 2.0; QuestDB Enterprise is separately proprietary.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- QuestDB on Google Cloud ↗
Deployment evidence and qualifications
Document processing and retrieval platform for building RAG and agentic knowledge applications.
- Techlatest RAGFlow VM deployment in a customer Google Cloud project ↗
Third party package · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
Scope: 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.
License: Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Techlatest RAGFlow VM deployment in a customer Google Cloud project ↗
Deployment evidence and qualifications
Open-source Kubernetes management platform deployed into a customer-operated cluster.
- Rancher Manager on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide installs Rancher into a GKE Standard cluster. GKE Autopilot is explicitly unsupported for the Rancher server.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the management cluster, ingress, certificates, backups, upgrades, downstream-cluster credentials and availability.
Scope: 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.
License: Apache License 2.0; commercial SUSE subscriptions and support are separate.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- Rancher Manager on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Enterprise IT automation platform installed and managed by the customer in a public-cloud environment.
- Self-managed Ansible Automation Platform in named public clouds ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the platform, execution capacity, infrastructure, secrets, backups and upgrades; Red Hat supplies subscribed software updates and support.
Scope: 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.
License: Commercial Red Hat Ansible Automation Platform subscription required.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Self-managed Ansible Automation Platform in named public clouds ↗
Deployment evidence and qualifications
Commercial AI and machine-learning platform installed as an Operator on a customer-operated Red Hat OpenShift cluster.
- OpenShift AI Self-Managed on supported OpenShift public-cloud platforms ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the OpenShift cluster, storage, accelerators, identity, networking, model data, backups and upgrades within Red Hat's supported configuration matrix.
Scope: 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.
License: Commercial Red Hat OpenShift AI Self-Managed subscription; an eligible OpenShift subscription is also required.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- OpenShift AI Self-Managed on supported OpenShift public-cloud platforms ↗
Deployment evidence and qualifications
Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
- Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.
Scope: 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.
License: Commercial Red Hat OpenShift subscription.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud ↗
Deployment evidence and qualifications
Commercial Redis Enterprise software installed and operated in the customer's cloud or data center.
- Redis Software on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cluster infrastructure, networking, persistence, backups, upgrades, monitoring and licensed capacity.
Scope: 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.
License: Commercial Redis Software subscription.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- Redis Software on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Managed Kafka-compatible streaming in your cloud account.
- Redpanda BYOC supported infrastructure ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Redpanda manages provisioning, monitoring and upgrades with the permissions you grant.
Scope: 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.
License: Commercial
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Redpanda BYOC supported infrastructure ↗
Deployment evidence and qualifications
Commercial self-hosted governance and policy platform with provider-specific container and Kubernetes guides.
- GCP Cloud Run ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP Cloud Run ↗
Deployment evidence and qualifications
Open-source digital asset management deployed on your own infrastructure.
- ResourceSpace self-installation cloud compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the application, database, asset storage, backups and upgrades.
Scope: 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.
License: Open source; paid hosting and support available separately
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- ResourceSpace self-installation cloud compatibility ↗
Deployment evidence and qualifications
Commercial single-tenant Retool deployment installed and operated on customer-managed Kubernetes infrastructure.
- Official Retool Terraform and Helm deployment paths ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, PostgreSQL, object storage, DNS, TLS, secrets, networking, backups, capacity, upgrades and the Retool license.
Scope: 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.
License: Commercial Enterprise subscription with custom annual pricing and a self-hosted license key.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Official Retool Terraform and Helm deployment paths ↗
Deployment evidence and qualifications
Licensed ERP for financials, purchasing, inventory and customer operations.
- GCP Docs ↗
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP Docs ↗
Deployment evidence and qualifications
Licensed SAP internal-control and policy lifecycle management application.
- GCP SAP NetWeaver Guides ↗
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP SAP NetWeaver Guides ↗
SAP S/4HANA EHS — Customer-Operated
Energy & environmental compliance · Incident & investigation management
Deployment evidence and qualifications
Customer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.
- SAP S/4HANA reference architecture on Google Cloud ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the application and database infrastructure, installation, upgrades, access, backups and EHS configuration; agree implementation and support arrangements.
Scope: 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.
License: Commercial SAP S/4HANA on-premise licensing; verify EHS component entitlements
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- SAP S/4HANA reference architecture on Google Cloud ↗
Deployment evidence and qualifications
Commercial analytics and AI platform deployed into a customer-operated managed Kubernetes cluster.
- SAS Viya infrastructure on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Official SAS Terraform provisions customer Google Cloud resources including GKE, storage and optional Cloud SQL, after which the customer deploys licensed Viya assets.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, networking, ingress, storage, PostgreSQL, identity, sizing, backups, platform updates and licensed deployment assets.
Scope: 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.
License: Commercial SAS Viya licensing; deployment assets and a JWT license are delivered for the customer's software order.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- SAS Viya infrastructure on Google Cloud ↗
Deployment evidence and qualifications
Self-managed distributed NoSQL database deployed on customer-controlled cloud virtual machines.
- Self-managed ScyllaDB 2026.3 on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Version: 2026.3 documentation. Vendor support commitment: not assessed; confirm the selected release and contract.
Official instructions use the customer's active Google Cloud account and gcloud to launch ScyllaDB images and call the deployment self-managed.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages topology, networking, authentication, capacity, backups, monitoring, patching and upgrades.
Scope: 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.
License: ScyllaDB Source Available License Agreement for current Enterprise releases; eligibility and capacity limits apply unless covered by paid terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Self-managed ScyllaDB 2026.3 on Google Cloud ↗
Deployment evidence and qualifications
Model-serving framework for running supported language and multimodal models on customer-controlled compute.
- SGLang compatibility with GKE Inference Gateway ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Google explicitly supports SGLang as an alternative model server in its customer-operated multi-cluster GKE inference architecture. The worked manifests use vLLM; SGLang requires its own deployment, serving port, metric mapping and compatible Endpoint Picker image. Review GPU/model requirements, licenses and resource availability.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages accelerator capacity, model artifacts, runtime compatibility, endpoint access, including isolation of debug and dumper routes, monitoring, and upgrades.
Scope: Model downloads may require external registries and gated-model credentials. Pin compatible model/runtime/image versions and review model-specific permissions. Generic container instructions do not establish deployment badges for every hyperscaler. CVE-2026-111391 rates SGLang 0.5.10 through 0.5.22 critical (CVSS v4.0 9.2) for Python code execution through the debug dumper filter. The upstream report demonstrates the shared-API path with DUMPER_SERVER_PORT=reuse: an ordinary API-key holder can reach it when no separate admin API key is configured; access can be anonymous when no API key is configured. With an admin API key configured, that key is required. Exploitation also requires access to the dumper configuration and a subsequent model execution that reaches a dumper hook. Upstream issue #44188 remains open, and the v0.5.23 tag still contains the eval-based filter path even though that tag is outside the CVE record's enumerated affected range. Do not enable or expose the debug dumper endpoint; restrict it at the network layer and verify an upstream fix before treating a later version as remediated.
License: Apache License 2.0 for upstream SGLang. Model weights and hardware/runtime dependencies have their own licenses.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- SGLang compatibility with GKE Inference Gateway ↗
Deployment evidence and qualifications
OpenTelemetry-based application observability platform for traces, metrics and logs.
- SigNoz self-hosting on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Official self-hosting instructions install SigNoz and its storage components on Google Kubernetes Engine; this is not the vendor-hosted SigNoz Cloud service.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages collectors, storage capacity, retention, authentication, backups, alert API and operator migrations, and platform upgrades.
Scope: 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.
License: MIT Expat for core code; ee/ enterprise code has its own separate license.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- SigNoz self-hosting on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Self-hosted SimpleRisk with the separately licensed Vendor Risk Management Extra.
- Cloud Install KB (AWS AMI) ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Cloud Install KB (AWS AMI) ↗
Deployment evidence and qualifications
Vendor-managed behavioural event pipeline running in the customer's cloud account.
- Snowplow Private Managed Cloud on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
The customer enables billing and grants installation and maintenance roles in its Google Cloud project.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Snowplow provisions, monitors, patches, and upgrades the pipeline. The customer supplies the cloud environment, access permissions, and data destination.
Scope: 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.
License: Commercial Private Managed Cloud plan with quote-based pricing.
Cloud evidence reviewed 2026-11-21. Read the full listing and sources →
- Snowplow Private Managed Cloud on Google Cloud ↗
Deployment evidence and qualifications
Archive retired applications while retaining searchable access to historical business information.
- Solix private deployment and enterprise archiving platform disclosure ↗
Corporate disclosure · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Solix Application Retirement customer case on a Google Cloud private tenant ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer-managed deployment is available; agree implementation, support, upgrades and infrastructure ownership with Solix.
Scope: 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.
License: Commercial Enterprise Edition
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Solix private deployment and enterprise archiving platform disclosure ↗
Deployment evidence and qualifications
Commercial high-availability SonarQube Server edition with Google Cloud deployment, Azure Kubernetes instructions and documented AWS architecture guidance.
- SonarQube Data Center Edition on GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the Kubernetes cluster, namespaces, database, persistent volumes, secrets, TLS, identity, load balancing, backups, autoscaling, upgrades and the SonarQube license.
Scope: 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.
License: Commercial Data Center Edition license.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- SonarQube Data Center Edition on GKE ↗
Deployment evidence and qualifications
Commercial self-hosted artifact repository with supported high-availability deployment across customer cloud infrastructure.
- Supported Nexus Repository Pro high-availability infrastructure ↗
Vendor / upstream documentation · Reviewed 2026-11-16 · Scope: Nexus Repository Pro. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Nexus Repository Pro deployment on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-16 · Scope: Nexus Repository Pro. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages compute or Kubernetes, PostgreSQL, blob and node storage, ingress and load balancing, TLS, secrets, backups, monitoring, upgrades and license persistence.
Scope: 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.
License: Commercial Nexus Repository Pro license required for high availability and other Pro capabilities.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Supported Nexus Repository Pro high-availability infrastructure ↗
Deployment evidence and qualifications
Commercial infrastructure-as-code automation platform deployed to customer AWS, Azure or Google Cloud infrastructure.
- Spacelift in customer AWS, Azure or GCP infrastructure ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Spacelift explicitly documents a customer-maintained self-hosted product for AWS, Azure and GCP and links provider-specific reference architectures.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages compute or Kubernetes, database and object storage, networking, secrets, workers, backups, scaling, upgrades and licensing.
Scope: 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.
License: Commercial Spacelift Self-Hosted Enterprise subscription and license token required.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- Spacelift in customer AWS, Azure or GCP infrastructure ↗
Deployment evidence and qualifications
Customer-managed platform for ingesting, indexing, searching and visualizing machine data.
- Splunk Enterprise reference hardware for AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Customer-managed Splunk Enterprise BYOL architecture ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.
Scope: 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.
License: Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Splunk Enterprise reference hardware for AWS, Azure and Google Cloud ↗
Deployment evidence and qualifications
Self-hosted headless CMS with structured content, APIs and assets.
- GCP Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP Guide ↗
Deployment evidence and qualifications
Commercial distributed SQL and analytics platform deployed by Helm into customer-operated Kubernetes.
- Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, dedicated node capacity, storage, networking, service database, catalogs, secrets, backups and upgrades.
Scope: 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.
License: Commercial Starburst Enterprise license and entitled registry access required.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Open-source distributed analytical database deployed through the StarRocks Kubernetes Operator.
- StarRocks Operator on EKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
StarRocks documents creating an Amazon EKS or Google GKE cluster, installing its Kubernetes Operator and deploying a StarRocks cluster through customer-applied custom resources.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, StarRocks custom resources, storage, networking, credentials, scaling, backups, monitoring and upgrades.
Scope: This entry covers the open-source StarRocks deployment, not a vendor-hosted service. Size front-end, back-end and compute nodes for the selected shared-nothing or shared-data topology, and validate object-storage, persistent-volume and upgrade compatibility. StarRocks 4.1.7 escapes lookup_string arguments, runs its internal query as the caller, encodes web-console output, validates proc_profile input, restricts diagnostic endpoints to administrators, masks credentials, and updates security dependencies. Upstream does not publish a CVE, severity, or universal affected range for these fixes.
License: Apache License 2.0
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- StarRocks Operator on EKS or GKE ↗
Deployment evidence and qualifications
Headless CMS for managing structured content and delivering it through APIs.
- Strapi self-hosting compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates application servers, database, media storage, backups and upgrades.
Scope: 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.
License: MIT core; commercial Growth/Enterprise features and terms differ
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Strapi self-hosting compatibility ↗
Deployment evidence and qualifications
Vendor-managed enterprise analytics and AI platform deployed as a dedicated single-tenant environment in the customer's public-cloud account.
- Strategy Enterprise in customer-licensed AWS, Azure or Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Strategy administers and maintains the platform; the customer supplies the cloud environment, data sources, identity, network approvals and shared governance responsibilities.
Scope: 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.
License: Commercial Strategy Enterprise subscription; customer-cloud deployment is not available with the Standard plan.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Strategy Enterprise in customer-licensed AWS, Azure or Google Cloud ↗
Deployment evidence and qualifications
Open-source registries and verifiable-credential building blocks with named-cloud deployments.
- GCP Terraform ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP Terraform ↗
Deployment evidence and qualifications
Enterprise software-factory and agent-workflow platform installed with Terraform and Helm in a customer cloud account.
- SuperPlane Enterprise on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the cloud account, cluster, database, object storage, runner images and VMs, DNS, TLS, backups, upgrades and connected model or tool credentials.
Scope: 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.
License: Commercial SuperPlane Enterprise license required for the documented Kubernetes deployment.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- SuperPlane Enterprise on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Open-source Linux infrastructure management and automation platform deployed as a customer-operated container or cloud virtual machine.
- SUSE Multi-Linux Manager public-cloud installation on EC2, Azure and GCE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the cloud VM, private networking, DNS, storage, server and proxy containers, repository synchronization, backups, upgrades and registered systems.
Scope: 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.
License: Open-source product based on Uyuni with component open-source licenses; SUSE subscriptions, support, images and trademarks use separate commercial terms.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- SUSE Multi-Linux Manager public-cloud installation on EC2, Azure and GCE ↗
Deployment evidence and qualifications
Commercial observability platform installed by Helm into a dedicated customer Kubernetes cluster.
- SUSE Observability on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.
Scope: 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.
License: Commercial SUSE Observability self-hosted subscription and license key required.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- SUSE Observability on EKS, AKS and GKE ↗
Deployment evidence and qualifications
Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.
- SUSE Security on six named public-cloud Kubernetes services ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
Scope: 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.
License: Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- SUSE Security on six named public-cloud Kubernetes services ↗
Deployment evidence and qualifications
Commercial analytics and business-intelligence server installed and operated on customer cloud virtual machines.
- Tableau Server on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Tableau documents production-ready self-deployment on customer Google Compute Engine virtual machines with BYOL operation. The provider guide is archived.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the virtual machines, operating system, Tableau services, identity, networking, storage, backups, upgrades and availability.
Scope: 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.
License: Commercial Tableau Server product-key licensing with user-, core- or subscription-based entitlements.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Tableau Server on Google Cloud ↗
Deployment evidence and qualifications
Commercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.
- Teleport Enterprise on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Teleport documents a full HA deployment on customer GKE.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes or VMs, backend state, storage, DNS, TLS, upgrades, capacity, backups and the Enterprise license.
Scope: This entry covers Enterprise Self-Hosted, not Teleport Enterprise Cloud. Community licensing and feature availability differ; confirm the purchased edition and current upgrade compatibility.
License: Commercial Teleport Enterprise Self-Hosted subscription and license file required.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- Teleport Enterprise on Google GKE ↗
Deployment evidence and qualifications
Commercial self-hosted Terraform collaboration and infrastructure-automation platform.
- Official Terraform Enterprise modules and provider guidance ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages compute or Kubernetes, PostgreSQL and object storage, cache, networking, TLS, identity, worker images, backups, scaling, upgrades and licensing.
Scope: 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.
License: Commercial Terraform Enterprise license required.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Official Terraform Enterprise modules and provider guidance ↗
Deployment evidence and qualifications
Source-available IoT device, telemetry and dashboard platform.
- GCP ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- GCP ↗
Deployment evidence and qualifications
Open-source distributed SQL database with customer-operated cloud Kubernetes guides and a separately packaged third-party AWS VM option.
- TiDB on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Apache License 2.0.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- TiDB on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Open-source collaborative forensic timeline analysis application.
- OSDFIR Getting Started ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- OSDFIR Getting Started ↗
Deployment evidence and qualifications
Build internal tools and business applications with a customer-hosted app builder.
- ToolJet application deployment on cloud VMs ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates application, database, credentials, backups and upgrades; vendor license activation applies to paid features.
Scope: 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.
License: AGPL-3.0 open-source foundation; commercial self-hosted editions/plans
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- ToolJet application deployment on cloud VMs ↗
Deployment evidence and qualifications
Commercial self-managed API management platform with documented AWS, Azure and Google Cloud deployments.
- Tyk Self-Managed on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
Tyk documents deploying its licensed Self-Managed platform on customer Google Cloud infrastructure.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages hosts or Kubernetes, data stores, networking, TLS, identities, secrets, monitoring, backups, scaling, upgrades and the Tyk license.
Scope: 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.
License: Commercial Tyk Self-Managed license required for the full platform; Gateway and Pump are available without that license.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- Tyk Self-Managed on Google Cloud ↗
Deployment evidence and qualifications
Commercial self-managed secrets and identity security platform deployed as a customer-operated high-availability cluster.
- Vault Enterprise inside a customer cloud account ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial Vault Enterprise license required.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Vault Enterprise inside a customer cloud account ↗
Deployment evidence and qualifications
Self-hosted model inference and serving engine with OpenAI-compatible APIs.
- vLLM Production Stack deployment on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages model acquisition, hardware capacity, endpoint protection, availability, upgrades and model/runtime compatibility.
Scope: 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.
License: Apache 2.0 for vLLM; model weights and supporting dependencies have independent licenses and access conditions.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- vLLM Production Stack deployment on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Self-hosted vector-search database for retrieval and AI applications.
- Deploy self-hosted Weaviate on Google Kubernetes Engine ↗
Provider guide · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
Google documents provisioning a private GKE Standard or Autopilot cluster in the customer’s project with Terraform and installing Weaviate with Helm. The customer operates the database.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages authentication, storage, backup, scaling, configuration and upgrades.
Scope: The Docker defaults include anonymous access and default telemetry; production installations must configure the intended controls. Pre-vectorized data can be searched without an external vectorizer, but enabled embedding, reranking or generation integrations may call external providers. Telemetry is enabled by default and has a documented opt-out; the entire current codebase must not be described as uniformly BSD-licensed. Weaviate v1.39.17 fixes a v1.39 runtime-reindex restart bug in which writes arriving before reindex resumed could be absent from the new property index, or an incomplete index could be swapped in after partial files disappeared. Operators remaining on v1.39 should update and verify filter/search results; the primary reviewed release remains the newer v1.40.5 line.
License: BSD-3-Clause core outside the wl directory; wl code and associated enterprise features require a separate enterprise license/key.
Cloud evidence reviewed 2026-11-21. Read the full listing and sources →
- Deploy self-hosted Weaviate on Google Kubernetes Engine ↗
Deployment evidence and qualifications
Run scripts and workflows with customer-operated execution workers and an app builder.
- Windmill upstream self-hosting provider compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
Scope: 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.
License: AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Windmill upstream self-hosting provider compatibility ↗
Deployment evidence and qualifications
Open-source content management system with documented customer-account deployments across major clouds and application-provider images.
- WordPress on Google Cloud ↗
Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Google documents customer deployments of WordPress on Google Cloud, including a Compute Engine path. Provider packaging and support scope must be reviewed.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages WordPress core, themes and plugins, application security, identities, content, database, media, backups, scaling and upgrades.
Scope: 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.
License: GPLv2 or later; themes, plugins and provider packaging may have separate terms.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- WordPress on Google Cloud ↗
Deployment evidence and qualifications
Commercial self-managed database-as-a-service control plane for YugabyteDB clusters.
- YugabyteDB Anywhere Google Cloud provider ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
Yugabyte documents customer GCP service accounts, projects, regions and instance provisioning for YBA-managed universes.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates YugabyteDB Anywhere and its database nodes while the software automates provisioning, scaling, backups and upgrades.
Scope: 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.
License: Commercial installed-software license; YugabyteDB core components have separate source licenses.
Cloud evidence reviewed 2026-11-14. Read the full listing and sources →
- YugabyteDB Anywhere Google Cloud provider ↗
Deployment evidence and qualifications
Open-source monitoring platform deployed from official Zabbix cloud images into customer accounts.
- Zabbix Server on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Zabbix documents deployment from Google Cloud Marketplace into the customer's project.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages VM, database, storage, agents, networking, TLS, retention, backups, upgrades and monitoring capacity.
Scope: 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.
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.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- Zabbix Server on Google Cloud ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings