Observability on Google Cloud

Operational dashboards, application traces, monitoring and alerting.

14 documented options on Google Cloud. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Cloud Carbon FootprintGoogle CloudCustomer-operated
Servers / containers
Open Source / Open Core

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

Application platform deploymentCustomer 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 and evidence

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.

  • GCP App Engine — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

Coroot Community EditionAWS, Azure, Google Cloud, Oracle CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for Coroot Community Edition. Enterprise Edition has separate subscription terms.

Install the Coroot Operator and Community Edition Helm chart on the customer's Kubernetes cluster.The customer manages the operator, image versions, privileged node-agent permissions, storage capacity, telemetry retention, backup and recovery, and access to the UI.
Scope and evidence

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.

  • Coroot on Amazon EKS — The vendor explicitly names EKS as a supported Kubernetes environment. Use the linked Community Helm instructions to deploy the operator, server and agents. The vendor specifies basic support for Fargate.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Coroot on Azure AKS — The vendor explicitly names AKS among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster, subject to privileges and Linux requirements.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Coroot on Google GKE — The vendor explicitly names GKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Coroot on Oracle OKE — The vendor explicitly names OKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-20

Datadog BYOC LogsAWS, Azure, Google CloudCustomer-operated · vendor control plane
Servers / containers
Commercial Only

Commercial Datadog software and service. Confirm BYOC Logs activation and commercial terms with the account team.

Install the BYOC Logs engine and Observability Pipelines Worker with Helm. An operator-managed installation is documented on Amazon EKS.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 and evidence

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.

  • Datadog BYOC Logs on Amazon EKS — Vendor guide installs the engine in the customer's EKS cluster using S3 and PostgreSQL. Helm and the EKS-specific Datadog Operator are documented.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Datadog BYOC Logs on Azure AKS — Vendor guide installs the engine into the customer's AKS cluster with Azure Blob Storage and PostgreSQL Flexible Server.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Datadog BYOC Logs on Google GKE — Vendor guide installs the engine in the customer's Google Cloud project with GKE, Cloud Storage, PostgreSQL and Workload Identity.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-20

Elastic Cloud EnterpriseAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Elastic Cloud Enterprise license required after the trial.

Official ECE installation script on prepared AWS, Azure or Google Cloud Linux hostsCustomer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.
Scope and evidence

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.

  • Elastic Cloud Enterprise on public cloud hosts — 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.

    Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-15

Elastic Cloud on KubernetesAWS, Azure, Google CloudCustomer-operated
Servers / containers
Source Available

Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support.

Official ECK Helm chart or Kubernetes manifests on EKS, AKS or GKECustomer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.
Scope and evidence

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.

  • Elastic Cloud on Kubernetes on EKS, AKS and GKE — 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.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-17

Langfuse Self-HostedAWS, Azure, Google Cloud, Railway, RenderCustomer-operated
Servers / containers
Open Source / Open Core

MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.

Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.Customer operates the deployment, persistence, access policies, retention, backups and scaling.
Scope and evidence

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.

  • Langfuse customer cloud deployment on AWS — The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Langfuse customer cloud deployment on Azure — The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Langfuse customer cloud deployment on Google Cloud — 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.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Langfuse v3 community Railway deployment — The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Langfuse v4 community Render Blueprint — The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

MLflow Tracking Server Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.

Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment.Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.
Scope and evidence

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.

  • Self-hosted MLflow deployment on AWS — The project documents deployment of the MLflow server, metadata database and artifact storage on AWS. This does not refer to a managed MLflow edition or to model serving alone.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Self-hosted MLflow deployment on Azure — The project documents deployment of the MLflow server, metadata database and artifact storage on Azure. This does not refer to a managed MLflow edition or to model serving alone.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Self-hosted MLflow deployment on Google Cloud — 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.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

OpenObserve Enterprise Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Enterprise End User License Agreement. The vendor publishes a free tier through 50 GB/day of ingestion, with a license required above that threshold.

Install the Enterprise Helm chart and CloudNativePG operator, then configure the cluster, object storage and application settings for the selected provider.The customer runs the cluster, configures storage credentials and ingestion endpoints, sizes components, manages backups and retention, and applies chart and application upgrades.
Scope and evidence

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.

  • OpenObserve Enterprise on Amazon EKS — The vendor walkthrough deploys the Enterprise application to the customer's EKS cluster, with S3 for telemetry and IAM permissions for storage access. The linked cluster sample pins Kubernetes 1.30; verify AWS availability and application compatibility and update that example version before use.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

  • OpenObserve Enterprise on Azure AKS — The vendor walkthrough deploys the Enterprise application to the customer's AKS cluster, with Azure Blob Storage, CloudNativePG and clustered NATS.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

  • OpenObserve Enterprise on Google GKE — The vendor walkthrough deploys the Enterprise application to a Standard GKE cluster in the customer's Google Cloud project. The documented Cloud Storage configuration uses S3 interoperability and HMAC credentials.

    Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-20

SigNoz Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

MIT Expat for core code; ee/ enterprise code has its own separate license.

Use the supported Foundry workflow to generate and run the Docker Compose stack; the older bundled install script/deploy files are deprecated.Customer manages collectors, storage capacity, retention, authentication, backups, alert API and operator migrations, and platform upgrades.
Scope and evidence

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.

  • SigNoz self-hosting on Amazon EKS — Official self-hosting instructions install SigNoz and its storage components on Amazon EKS; this is not the vendor-hosted SigNoz Cloud service.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • SigNoz self-hosting on Azure Kubernetes Service — Official self-hosting instructions install SigNoz and its storage components on Azure Kubernetes Service; this is not the vendor-hosted SigNoz Cloud service.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • SigNoz self-hosting on Google Kubernetes Engine — Official self-hosting instructions install SigNoz and its storage components on Google Kubernetes Engine; this is not the vendor-hosted SigNoz Cloud service.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Splunk EnterpriseAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions.

Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies.Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.
Scope and evidence

This entry covers customer-managed Splunk Enterprise, not Splunk Cloud Platform. Splunk documents customer-managed BYOL architectures on AWS, Azure and Google Cloud. Current installation documentation limits supported container deployments to standalone and single-server topologies, so distributed production deployments should follow supported package-based validated architectures. Confirm supported operating systems, instance types, object-store throughput, cache sizing and clustering requirements. Splunk advance notice SVD-2026-1101 says forthcoming November disclosures are fixed in Enterprise 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 and strongly recommends those or later releases. Final CVE-specific disclosures were not live during this review; 10.6.0 Universal Forwarder users should move to 10.6.1 or later.

  • Splunk Enterprise reference hardware for AWS, Azure and Google Cloud — 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.

    Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Customer-managed Splunk Enterprise BYOL architecture — 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.

    Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-16

SUSE Observability Self-HostedAWS, Azure, Google Cloud, Alibaba CloudCustomer-operated
Servers / containers
Commercial Only

Commercial SUSE Observability self-hosted subscription and license key required.

SUSE Observability server Helm chart on EKS, AKS, GKE or Alibaba ACK, with provider-specific storage configurationCustomer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.
Scope and evidence

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.

  • SUSE Observability on EKS, AKS and GKE — 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.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

  • SUSE Observability server installation on Alibaba ACK — The server guide supplies ACK-specific Helm values for stateful backend PVCs, each at least 20 GiB. This is server deployment evidence, distinct from monitoring an ACK cluster with an agent. Apply the selected HA sizing profile and provider storage requirements.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-17

SUSE Security (NeuVector)AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud, Oracle CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.

SUSE Security Helm chart or manifests on public-cloud KubernetesCustomer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
Scope and evidence

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.

  • SUSE Security on six named public-cloud Kubernetes services — 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.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

ThingsBoard Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Source Available

Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.

Kubernetes manifestsCustomer 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 and evidence

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.

  • AWS — ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Azure — ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • GCP — ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

Zabbix ServerAWS, Azure, Google Cloud, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

AGPLv3 for Zabbix 7.0+; older releases such as the reviewed DigitalOcean 6.x packages use GPLv2. Provider images/support can be separately charged.

Official Zabbix VM images from AWS, Azure, Google Cloud or DigitalOcean marketplacesCustomer manages VM, database, storage, agents, networking, TLS, retention, backups, upgrades and monitoring capacity.
Scope and evidence

Provider packages differ: the reviewed AWS AMI is v7.4.16, the Azure guide uses a 7.4 example, and DigitalOcean lists older 6.x images. Upstream 8.0.0 does not make those images current. Recheck supported branches/OS and patch before use; single appliances do not establish HA or retention sizing.

  • Zabbix Server on AWS — Zabbix documents launching the official server image into the customer's selected AWS VPC and subnet.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Zabbix Server on Azure — The current Azure deployment guide launches the server appliance in the customer subscription. Its 7.4 example does not include infrastructure redundancy and is distinct from current upstream 8.0.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Zabbix Server on Google Cloud — Zabbix documents deployment from Google Cloud Marketplace into the customer's project.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Official Zabbix DigitalOcean image — DigitalOcean lists full Zabbix Server Droplet packages, including 6.0.17 (image 131398452, slug zabbix-zabbixserver60). These older images require supported-branch/patch/OS review; they are not current upstream 8.0 packages.

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

Deployment evidence and category fit

Cloud Carbon Footprint

Open-source cloud-usage, energy and carbon-estimation application.

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.

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

Cloud evidence reviewed 2026-11-19. Full listing and qualifications

Coroot Community Edition

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

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.

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

Cloud evidence reviewed 2026-11-20. Full listing and qualifications

Datadog BYOC Logs

The customer-cloud Logs engine ingests, indexes, stores and queries operational logs. Datadog hosts the Log Explorer and pipeline configuration UI.

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.

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

Cloud evidence reviewed 2026-11-20. Full listing and qualifications

Elastic Cloud Enterprise

Operates Elastic Stack deployments used to ingest, search and analyze logs, metrics, traces and security telemetry.

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.

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

Cloud evidence reviewed 2026-11-15. Full listing and qualifications

Elastic Cloud on Kubernetes

Elastic Stack collects and analyzes logs, metrics and traces; exact integrations and features depend on the selected license.

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.

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

Cloud evidence reviewed 2026-11-17. Full listing and qualifications

Langfuse Self-Hosted

Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

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.

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

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

MLflow Tracking Server Self-Hosted

Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

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.

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

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

OpenObserve Enterprise Self-Hosted

Collects and analyzes application and infrastructure telemetry, with dashboards and alerts for operational monitoring.

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.

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

Cloud evidence reviewed 2026-11-20. Full listing and qualifications

SigNoz Self-Hosted

Application observability over OpenTelemetry traces, metrics and logs; applications must be instrumented and collection configured.

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.

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

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Splunk Enterprise

Ingests, indexes and searches machine data for operational monitoring, troubleshooting, dashboards and alerting.

This entry covers customer-managed Splunk Enterprise, not Splunk Cloud Platform. Splunk documents customer-managed BYOL architectures on AWS, Azure and Google Cloud. Current installation documentation limits supported container deployments to standalone and single-server topologies, so distributed production deployments should follow supported package-based validated architectures. Confirm supported operating systems, instance types, object-store throughput, cache sizing and clustering requirements. Splunk advance notice SVD-2026-1101 says forthcoming November disclosures are fixed in Enterprise 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 and strongly recommends those or later releases. Final CVE-specific disclosures were not live during this review; 10.6.0 Universal Forwarder users should move to 10.6.1 or later.

  • Splunk Enterprise 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.

Cloud evidence reviewed 2026-11-16. Full listing and qualifications

SUSE Observability Self-Hosted

Collects, correlates and visualizes Kubernetes topology, metrics, events and related operational signals in a customer-operated deployment.

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.

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

Cloud evidence reviewed 2026-11-17. Full listing and qualifications

SUSE Security (NeuVector)

Provides workload, network and security-event visibility for Kubernetes clusters.

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.

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

Cloud evidence reviewed 2026-11-18. Full listing and qualifications

ThingsBoard Self-Hosted

Source-available IoT device, telemetry and dashboard platform.

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.

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

Cloud evidence reviewed 2026-11-19. Full listing and qualifications

Zabbix Server

Monitors infrastructure, networks, applications, logs and service availability through a customer-operated server and agents.

Provider packages differ: the reviewed AWS AMI is v7.4.16, the Azure guide uses a 7.4 example, and DigitalOcean lists older 6.x images. Upstream 8.0.0 does not make those images current. Recheck supported branches/OS and patch before use; single appliances do not establish HA or retention sizing.

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

Cloud evidence reviewed 2026-11-18. Full listing and qualifications

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.

Plan this deployment

Account boundary: Google Cloud project. Access: IAM policies and service accounts. Network: VPC network.

Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.

Compare this category across clouds · Search these listings · Compare 2–4 listings