
# Observability

Operational dashboards, application traces, monitoring and alerting.

Canonical page: https://launchinyourcloud.com/categories/observability/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




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


Operational dashboards, application traces, monitoring and alerting.

21 listings.


## AVEVA PI System (BYOL)

Commercial industrial data collection, historian and visualization system with an AWS architecture.

- Listing: https://launchinyourcloud.com/directory/aveva-pi-system/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: AWS Outposts edge components plus regional EC2 application, database and visualization services.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The reviewed AWS Guidance includes Outposts for core collection/historian components; it is not a region-only VM installation. PI component versions and licences are separate. Industrial telemetry does not itself supply environmental-compliance document management.

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

AWS Outposts edge components plus regional EC2 application, database and visualization services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Commercial industrial data collection, historian and visualization system with an AWS architecture.

- observability: Commercial industrial data collection, historian and visualization system with an AWS architecture.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Guidance (aws): https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/
  AWS Outposts edge components plus regional EC2 application, database and visualization services. The reviewed AWS Guidance includes Outposts for core collection/historian components; it is not a region-only VM installation. PI component versions and licences are separate. Industrial telemetry does not itself supply environmental-compliance document management.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Guidance: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/

- AVEVA Licensing Policy Index (Commercial EULA): https://www.aveva.com/en/legal/policies-compliance/

- Clickwrap EULA: https://www.aveva.com/en/legal/aveva-general-terms-and-conditions-eula/

- Software Lifecycle Policy (Apr 2026): https://www.aveva.com/content/dam/aveva/documents/legal/policies/AVEVA-Software-Lifecycle-and-Retirement-Policy.pdf

- PI Data Infra Amazon RDS (Sep 2025): https://www.aveva.com/en/about/news/press-releases/2025/aveva-expands-its-offerings-for-aveva-pi-data-infrastructure-with-amazon-rds/

- AVEVA World 2026 (May 2026): https://www.aveva.com/en/about/news/press-releases/2026/aveva-announces-new-capabilities-to-embed-ai-across-industrial-organizations-and-data-infrastructure-at-aveva-world-2026/

### Licensing sources

- https://www.aveva.com/en/legal/policies-compliance/

- https://www.aveva.com/en/legal/aveva-general-terms-and-conditions-eula/

### Infrastructure sources

- https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. AVEVA documents PI Vision user authentication through Windows Integrated Security/Kerberos, and its public extensibility guide describes PI Vision/PI Web API 2023 OIDC with AVEVA Identity Manager. Configure service principals/delegation or the selected OIDC flow and component permissions. This confirms the visualization/web path, not identical SSO behavior across every PI component or release. Scope: Scoped PI Vision web-user authentication; not AWS IAM or a blanket PI System protocol entitlement. Source: https://docs.aveva.com/bundle/pi-vision/page/1009076.html (reviewed 2026-11-20). Supporting source: Official PI Vision/PI Web API OIDC and SSO integration — https://github.com/AVEVA/AVEVA-Samples-PI-System/blob/main/docs/PI-Vision-Extensibility-Docs/PI%20Vision%20Extensibility%20Guide.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. AWS documents a multi-zone PI System architecture with PI Vision, Asset Framework, Data Archive, SQL Server and edge connectivity. This architecture diagram does not identify the entitled application installers, exact component versions or a complete deployable IaC bundle. Obtain the licensed media and version-matched installation/migration sequence. Scope: Provider architecture confirmed; actual entitled application/deployment artifacts remain unconfirmed. Source: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/ (reviewed 2026-11-20).

- Minimum footprint / sizing: Sources checked — unresolved. The AWS guidance separates PI Vision, Asset Framework, Data Archive and SQL/edge roles but does not provide a current CPU/RAM/storage baseline for each selected component/version. Size PI points/events, ingestion, archive growth, concurrent displays and HA. Hardware figures for other AVEVA products are not PI System sizing evidence. Scope: Provider topology, not a workload-sized bill of materials; full production sizing remains unconfirmed. Source: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: AVEVA PI System (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.aveva.com/en/legal/policies-compliance/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Cloud Carbon Footprint

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

- Listing: https://launchinyourcloud.com/directory/cloud-carbon-footprint/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://cloudcarbonfootprint.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

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

Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

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

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

### Deployment boundaries


- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudcarbonfootprint.org/docs/deploying/ (checked 2026-11-19). 


### Cloud deployment evidence

- GCP App Engine (gcp): https://www.cloudcarbonfootprint.org/docs/deploying/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes camcash17, dtoakley, 4upz, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/graphs/contributors

- Upstream project: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint

### Sources

- GCP App Engine: https://www.cloudcarbonfootprint.org/docs/deploying/

- app.yaml: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/app.yaml

- appengine-deploy.sh: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/appengine-deploy.sh

- Apache-2.0: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/LICENSE

- Releases: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/releases

### Licensing sources

- https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/LICENSE

### Infrastructure sources

- https://www.cloudcarbonfootprint.org/docs/deploying/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed API authentication middleware logs success and calls next without validating a user. Cloud-account credentials in its configuration authenticate usage-data collection, not dashboard users. A supported external IdP login, account/role mapping and protection of both UI/API remain unconfirmed; an identity-aware proxy would need a separately reviewed design. Scope: Actual upstream middleware on moving trunk; cloud-source IAM is separate from application-user SSO. Source: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/src/utils/auth.ts (reviewed 2026-11-20). Supporting source: Cloud data-source authentication configuration — https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/common/src/Config.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Cloud Carbon Footprint deployment example; review the full linked installation instructions. Source: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/app.yaml (reviewed 2026-11-19). Deployment artifact: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/app.yaml. Artifact reference: trunk (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The current API App Engine recipe selects instance class B2 with basic scaling capped at one instance. This is a deployment example, not a complete UI/API/cache capacity or HA baseline. Query range, account/project count, billing-data processing and cache/database growth need sizing; do not treat one small API instance as a validated 100-user HA design. Scope: Current API example allocation on moving trunk; complete workload sizing remains unconfirmed. Source: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/app.yaml (reviewed 2026-11-20). Supporting source: Application and frontend deployment steps — https://www.cloudcarbonfootprint.org/docs/deploying/.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The project publishes a moving latest release marker. The reviewed repository remains active, but this marker does not identify an immutable production application release or support duration. Scope: Cloud Carbon Footprint upstream application; verify compatibility with the selected package. Source: https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/releases/tag/latest (reviewed 2026-11-19).







## Coroot Community Edition

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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


### Cloud deployment evidence

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

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

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

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


### Community and maintenance

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

Reviewed 2026-11-20.

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

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

### Sources

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### Licensing sources

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

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Single sign-on: Explicitly unsupported. The authentication guide explicitly reserves native SAML/OIDC single sign-on for Coroot Enterprise. Community has local users with Admin, Editor and Viewer roles. An external authentication proxy would be a separate configuration, not native Community SSO. Scope: Native Coroot Community authentication; Enterprise is a separate edition. Source: https://docs.coroot.com/configuration/authentication/ (reviewed 2026-11-20).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Security controls: Documented. Community provides local-user authentication, three predefined roles and API-key service accounts. Set the initial admin password before exposure and review anonymous-mode settings. Node agents need privileged eBPF/host access; review the operator ClusterRole and its optional restriction on global secret access. Scope: Configured Community access controls and privileged collector/operator boundary. Source: https://docs.coroot.com/configuration/authentication/ (reviewed 2026-11-20). Supporting source: Node-agent privilege requirements — https://docs.coroot.com/installation/kubernetes/. Supporting source: Inspected operator permissions/configuration — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected coroot-ce 0.3.3 chart creates a Community custom resource and requires a separately installed operator; the reviewed operator chart is 0.10.8 (operator application 1.10.8). Neither chart version identifies the Coroot server release. Pin server, node-agent and cluster-agent images to prevent the documented automatic upgrades. Scope: Community custom resource plus separately versioned operator and component images. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20). Deployment artifact: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz. Artifact reference: coroot-ce 0.3.3; sha256:e6213b27a4e73924d2fe03c12aa815ebd8ec806436c3a5ab9bd4a8801c18e6f3; operator chart 0.10.8 / operator 1.10.8. Supporting source: Operator package — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz. Supporting source: Published chart index — https://coroot.github.io/helm-charts/index.yaml.

- Minimum footprint / sizing: Documented. The inspected Community chart defaults to 10 GiB Coroot storage, 10 GiB Prometheus storage and 100 GiB per ClickHouse instance. Its default ClickHouse layout is one shard/replica; the installation guide overrides this to two shards and two replicas. Operator requests are 100m CPU/64 MiB. These are component defaults, not total cluster CPU/RAM minima or an HA capacity guarantee. Scope: Chart-specific storage and operator request baseline; server/agent/database sizing remains workload-dependent. Source: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz (reviewed 2026-11-20). Supporting source: Separate operator requests — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz. Supporting source: Installation layout and replica override — https://docs.coroot.com/installation/kubernetes/. Supporting source: Kernel and orchestrator prerequisites — https://docs.coroot.com/installation/requirements/.

- License pricing: Documented. Coroot Community v1.29.4 is licensed under Apache-2.0. This establishes the software licence rather than a per-seat subscription; Enterprise features/support, dependencies and infrastructure have separate costs. Scope: Upstream Community code; excludes Enterprise subscriptions. Source: https://github.com/coroot/coroot/blob/v1.29.4/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed Coroot Community server snapshot is v1.29.4, published November 18, 2026. Operator, server, agents and charts are independently versioned; this snapshot does not guarantee support or pin the complete installation. Scope: Upstream Community server release. Source: https://github.com/coroot/coroot/releases/tag/v1.29.4 (reviewed 2026-11-20).







## Datadog BYOC Logs

Datadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.

- Listing: https://launchinyourcloud.com/directory/datadog-byoc-logs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated · vendor control plane
- Infrastructure IDs: servers
- License: Commercial Datadog software and service. Confirm BYOC Logs activation and commercial terms with the account team.
- Licensing model: commercial-only
- Installation: Install the BYOC Logs engine and Observability Pipelines Worker with Helm. An operator-managed installation is documented on Amazon EKS.
- Architecture: Customer-operated Kubernetes engine and pipeline workers use object storage for log data and PostgreSQL for index metadata. Datadog hosts the UI and routes queries.
- Operations: The customer provisions and sizes the cluster, manages storage, database, IAM and network connectivity, and applies validated engine and Worker version pairs. Datadog maintains the hosted UI.
- Product website: https://docs.datadoghq.com/byoc-logs/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

Log ingestion, indexing and storage run in the customer's account. Matching query results travel to Datadog for display. The default connection is outbound from searcher pods to Datadog. Confirm service-site availability and account activation. A Docker path is documented for local evaluation. Docker is evaluation-only, and the Operator path is EKS-only. Engine v0.1.36/chart 0.6.0 needs the documented StatefulSet policy migration on existing clusters. Hosted Datadog SSO/SCIM and compliance boundaries remain distinct from the customer engine.

The offering requires a Datadog account and the vendor's terms. Account activation and the customer's applicable pricing and entitlement should be confirmed with Datadog.

Production workload uses Kubernetes, object storage and PostgreSQL. The listing's runtime describes the customer-operated engine and workers.


### Category fit

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/aws_eks/ (checked 2026-11-20). 

- azure: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/azure_aks/ (checked 2026-11-20). 

- gcp: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/gcp_gke/ (checked 2026-11-20). 

Operating responsibility: The customer installs and operates log processing, indexing and storage in its infrastructure. The Datadog-hosted UI submits queries and receives results; storing logs locally does not establish a disconnected or wholly customer-operated management plane. Source: https://docs.datadoghq.com/byoc-logs/introduction.md (checked 2026-11-20). Supporting source: Customer deployment and cluster configuration — https://docs.datadoghq.com/byoc-logs/install.md.


### Cloud deployment evidence

- Datadog BYOC Logs on Amazon EKS (aws): https://docs.datadoghq.com/byoc-logs/install/aws_eks/
  Vendor guide installs the engine in the customer's EKS cluster using S3 and PostgreSQL. Helm and the EKS-specific Datadog Operator are documented.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Datadog BYOC Logs on Azure AKS (azure): https://docs.datadoghq.com/byoc-logs/install/azure_aks/
  Vendor guide installs the engine into the customer's AKS cluster with Azure Blob Storage and PostgreSQL Flexible Server.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Datadog BYOC Logs on Google GKE (gcp): https://docs.datadoghq.com/byoc-logs/install/gcp_gke/
  Vendor guide installs the engine in the customer's Google Cloud project with GKE, Cloud Storage, PostgreSQL and Workload Identity.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Sources

- BYOC Logs install options and account activation: https://docs.datadoghq.com/byoc-logs/install/

- Architecture and query-result boundary: https://docs.datadoghq.com/byoc-logs/introduction/architecture/

- Connections and network data flow: https://docs.datadoghq.com/byoc-logs/introduction/network/

- Validated engine and worker updates: https://docs.datadoghq.com/byoc-logs/operate/updates/

- Datadog End-User License Agreement: https://www.datadoghq.com/legal/eula/

- BYOC Logs account configuration and activation: https://docs.datadoghq.com/byoc-logs/configure/

- Datadog BYOC Logs on Amazon EKS: https://docs.datadoghq.com/byoc-logs/install/aws_eks/

- Datadog BYOC Logs on Azure AKS: https://docs.datadoghq.com/byoc-logs/install/azure_aks/

- Datadog BYOC Logs on Google GKE: https://docs.datadoghq.com/byoc-logs/install/gcp_gke/

- Buyer evidence: scim: https://docs.datadoghq.com/account_management/scim/

- Separate Worker artifact; not asserted to be a validated pair: https://github.com/DataDog/helm-charts/releases/download/observability-pipelines-worker-2.26.0/observability-pipelines-worker-2.26.0.tgz

- Engine release and StatefulSet migration: https://docs.datadoghq.com/byoc-logs/release_notes/

- Buyer evidence: sso: https://docs.datadoghq.com/account_management/saml/

- Buyer evidence: footprint: https://docs.datadoghq.com/byoc-logs/operate/sizing/

### Licensing sources

- https://www.datadoghq.com/legal/eula/

- https://docs.datadoghq.com/byoc-logs/configure/

### Infrastructure sources

- https://docs.datadoghq.com/byoc-logs/install/

- https://docs.datadoghq.com/byoc-logs/introduction/architecture/


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Single sign-on: Documented. The hosted Datadog organization used for Log Explorer supports SAML SSO with a configured identity provider. This authenticates users to Datadog’s hosted UI; the customer-side engine connection instead uses Datadog API credentials and the selected network configuration. Scope: Datadog hosted account/control-plane identity; not an independent engine login. Source: https://docs.datadoghq.com/account_management/saml/ (reviewed 2026-11-20). Supporting source: BYOC query and control-plane boundary — https://docs.datadoghq.com/byoc-logs/introduction/architecture/.

- SCIM provisioning: Edition-dependent. Datadog documents SCIM user/team/role provisioning for Infrastructure Pro, Infrastructure Enterprise and Startup plans. Confirm the organization’s plan entitlement; BYOC Logs activation alone does not establish it. The endpoint manages hosted Datadog organization identities, not local engine users. Scope: Plan-dependent hosted Datadog organization provisioning. Source: https://docs.datadoghq.com/account_management/scim/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Security controls: Documented. The default searcher-initiated reverse connection uses outbound HTTPS/WebSocket access to Datadog and carries queries, results and index-management messages without a public query ingress. The optional public ingress uses mTLS. Review API credentials, storage IAM, network restrictions and the resulting query-result egress. Scope: BYOC query/control-plane connectivity and configurable customer-side controls. Source: https://docs.datadoghq.com/byoc-logs/introduction/network/ (reviewed 2026-11-20).

- Air-gapped operation: Explicitly unsupported. The documented BYOC workflow depends on a connection to the hosted Datadog UI/control plane. Searchers maintain outbound connections by default, or Datadog connects through an optional ingress. This connected offering does not provide a documented fully disconnected mode. Scope: Complete documented Datadog BYOC Logs workflow, including hosted UI. Source: https://docs.datadoghq.com/byoc-logs/introduction/network/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected cloudprem chart 0.6.0 packages engine v0.1.36. The separately indexed Worker chart is 2.26.0; observing both artifacts does not establish a validated engine/Worker pair. Select the vendor-approved combination. Chart 0.6.0 changes the indexer StatefulSet pod-management default; existing installations need the documented migration or an OrderedReady override. Scope: BYOC engine artifact plus separate Worker and cloud dependencies. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20). Deployment artifact: https://github.com/DataDog/helm-charts/releases/download/cloudprem-0.6.0/cloudprem-0.6.0.tgz. Artifact reference: cloudprem 0.6.0 / engine v0.1.36; sha256:7cf894e6c9fd3dc4e28f120fd354847151ea414e7885b7724d73fe2f1babae73. Supporting source: Separate Worker artifact; not asserted to be a validated pair — https://github.com/DataDog/helm-charts/releases/download/observability-pipelines-worker-2.26.0/observability-pipelines-worker-2.26.0.tgz. Supporting source: Vendor update/compatibility policy — https://docs.datadoghq.com/byoc-logs/operate/updates/. Supporting source: Engine release and StatefulSet migration — https://docs.datadoghq.com/byoc-logs/release_notes/.

- Minimum footprint / sizing: Documented. The sizing guide starts indexers at 2 vCPUs per TB/day, compactors at 1 vCPU per 2 TB/day and searchers near twice the indexer CPU, with query-driven adjustment. It separately sizes control services, Workers and PostgreSQL and recommends Multi-AZ database availability. Its 1 TB/day example assumes 30-day retention and roughly 6x compression; 1 TB stored is a different input. Scope: Vendor sizing model and assumptions; not a universal minimum or measured workload/cost estimate. Source: https://docs.datadoghq.com/byoc-logs/operate/sizing/ (reviewed 2026-11-20).

- License pricing: Documented. BYOC Logs is commercial Datadog software/service and requires activation through the account team. The reviewed materials do not establish an all-in public BYOC unit price or a customer quote; organization plan entitlements, engine/Worker billing and customer cloud charges must be confirmed separately. Scope: Commercial activation/licensing boundary, not an operating-cost estimate. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20). Supporting source: Datadog EULA — https://www.datadoghq.com/legal/eula/.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed BYOC engine snapshot is v0.1.36, dated November 3, 2026 and bundled in cloudprem chart 0.6.0. Engine, Worker and charts have separate versions; use the vendor-validated combination. Datadog states an engine release cadence of at least monthly, which is a vendor policy rather than a support guarantee from this directory. Scope: BYOC engine snapshot and separately documented update policy. Source: https://docs.datadoghq.com/byoc-logs/release_notes/ (reviewed 2026-11-20). Supporting source: Vendor version-pair and update policy — https://docs.datadoghq.com/byoc-logs/operate/updates/.




### Security and lifecycle reviews

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

- Datadog BYOC chart 0.6.0 indexer policy transition (lifecycle): Chart 0.6.0 defaults indexer podManagementPolicy to Parallel, an immutable StatefulSet field. Existing deployments need an override or the documented migration. Scope: BYOC engine v0.1.36 packaged in cloudprem chart 0.6.0; chart and application versions are separate. Conditions: Clusters running nodes older than engine v0.1.33 also need the documented gossip protocol compatibility setting during the transition. Action: Retain OrderedReady explicitly or follow the indexer StatefulSet migration. Keep gossip protocol 0 while older nodes remain, then apply the vendor-approved engine/Worker versions. Source: https://docs.datadoghq.com/byoc-logs/release_notes/; reviewed 2026-11-20.




## Elastic Cloud Enterprise

Commercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.

- Listing: https://launchinyourcloud.com/directory/elastic-cloud-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Elastic Cloud Enterprise license required after the trial.
- Licensing model: commercial-only
- Installation: Official ECE installation script on prepared AWS, Azure or Google Cloud Linux hosts
- Architecture: Multi-host orchestration layer with coordinators, proxies, allocators and managed Elasticsearch and Kibana deployments
- Operations: Customer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.
- Product website: https://www.elastic.co/cloud/cloud-enterprise
- Source review: 2026-11-19; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers Elastic Cloud Enterprise, not Elastic Cloud Hosted or Elastic Cloud Serverless. ECE requires supported Linux and container-engine combinations, dedicated storage planning and coordinated host maintenance; automatic cloud VM patching can disrupt the platform. Elastic Cloud Enterprise 3.8.6 and 4.2.1 fix seven platform-role, retained credential and CA key, cross-deployment symlink, role-token, and platform-setting issues. Certificate-rotation users must complete the documented cleanup after upgrade, and operators should review or revoke persistent role tokens. Elastic's CVE-2026-114938 advisory states Elasticsearch 7.17.3 and later can be affected on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Planned ECE 4.2.2 and 3.8.7 were not yet released at review time; until fixed images are available, apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's rollout guidance.

ECE starts with a 30-day trial and then requires a valid Elastic Cloud Enterprise orchestration license.

ECE uses multiple persistent Linux hosts for orchestration, proxies and workload allocators and then runs Elastic Stack clusters on those hosts.


### Category fit

- data-analytics: Orchestrates self-managed Elasticsearch and Kibana deployments for search, analytical and data-exploration workloads.

- databases-vector: Operates Elasticsearch clusters that provide document, full-text and vector search in customer infrastructure.

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (checked 2026-11-15). 


### Cloud deployment evidence

- Elastic Cloud Enterprise on public cloud hosts (aws, azure, gcp): https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install
  Elastic's current ECE installation guide explicitly supports public-cloud hosts on AWS, Google Cloud and Microsoft Azure and installs ECE on customer-prepared virtual machines.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Install Elastic Cloud Enterprise: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install

- Elastic Cloud Enterprise overview: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise

- Manage an Elastic Cloud Enterprise license: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece

- Elastic Cloud Enterprise release notes: https://www.elastic.co/docs/release-notes/cloud-enterprise

- Elastic Cloud Enterprise 4.2.1 security update ESA-2026-216: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263

- Elastic Java4Shell advisory for ECE: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703

### Licensing sources

- https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece

### Infrastructure sources

- https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. ECE supports SAML 2.0 Web Browser SSO for the orchestrator/Cloud UI, with attribute and role mappings. It does not apply to ordinary API clients or automatically configure every hosted Elasticsearch/Kibana deployment; those access policies are separate. Scope: Self-managed ECE orchestrator browser federation. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cloud-enterprise-orchestrator/saml (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization. Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens. Current review: CVE-2026-114938 can affect Elasticsearch 7.17.3 and later on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Elastic planned ECE 4.2.2 and 3.8.7 but had not released them when reviewed. Use -XX:-UseBASE64Intrinsics, restart every deployment and follow the vendor advisory until fixed ECE images are available. Scope: ECE-hosted Elasticsearch deployments on affected x86-64 AVX512_VBMI hardware; planned ECE versions are not recorded as released. Source: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263. Supporting source: ESA-2026-211 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260. Supporting source: ESA-2026-212 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-212/391261. Supporting source: ESA-2026-215 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-215/391262. Supporting source: ESA-2026-218 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-218/391264. Supporting source: ESA-2026-221 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-221/391265. Supporting source: ESA-2026-222 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. ECE installation prepares supported Linux hosts, Docker or Podman, XFS quotas and mount points before installing the orchestrator. Follow the supported OS/container-engine matrix and deployment-specific prerequisites; generic cloud VMs alone are insufficient. Scope: Elastic Cloud Enterprise installation guide; orchestrator hosts, not Elastic Cloud Hosted. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. ECE lists an 8-GB installation floor per host role, but recommends 128–256 GB for allocator hosts and distinct control/proxy sizing. HA needs at least three hosts across three availability zones. Fast SSDs, deployment memory/storage ratios and cluster workloads materially affect the footprint; the installer floor is not production capacity. Scope: ECE host-role requirements; hosted deployment capacity and HA additional. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/ece-hardware-prereq (reviewed 2026-11-20).

- License pricing: Documented. ECE requires an Elastic-issued licence; installation activates a 30-day trial. A full ECE licence enables managed deployments at the stated Enterprise subscription feature/support level for their stack version. The page does not quote a price; obtain ECE terms separately from hosted Elastic Cloud rates and infrastructure. Scope: Commercial ECE platform/deployment licensing; numeric price requires a quote. Source: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Elastic Cloud Enterprise 4.2.1 was released October 20, 2026; 3.8.6 is the parallel fixed release for that maintained line. The updates address multiple platform-role, credential, certificate, token, and cross-deployment issues. Scope: Elastic Cloud Enterprise 3.8 and 4.2 maintained lines. Source: https://www.elastic.co/docs/release-notes/cloud-enterprise (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Elastic Cloud Enterprise 3.8.6 and 4.2.1 security update (security-advisory): ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization. Scope: Most issues affect releases through 3.8.5 and 4.2.0. ESA-2026-222 affects 4.1.0 through 4.2.0 when Enterprise Search is present. Fixed releases are 3.8.6 and 4.2.1. Conditions: Several issues require particular platform roles, certificate rotation, persistent tokens, symlink paths, or Enterprise Search. Multiple advisories have no workaround. Action: Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens. Source: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263; reviewed 2026-11-18. Supporting source: ESA-2026-211 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260. Supporting source: ESA-2026-212 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-212/391261. Supporting source: ESA-2026-215 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-215/391262. Supporting source: ESA-2026-218 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-218/391264. Supporting source: ESA-2026-221 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-221/391265. Supporting source: ESA-2026-222 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266.

- Elastic Cloud Enterprise CVE-2026-114938 guidance (security-advisory): Elastic says affected Elasticsearch on x86-64 AVX512_VBMI CPUs can permit authenticated RCE and unauthenticated denial of service. Scope: ECE-hosted Elasticsearch 7.17.3 and later on affected hardware; planned ECE 4.2.2 and 3.8.7 were not yet released when reviewed. Conditions: CPU features, JDK and deployed Elasticsearch version determine exposure. Action: Apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's advisory until fixed ECE images are released and deployed. Source: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703; reviewed 2026-11-19.




## Elastic Cloud on Kubernetes

Elastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.

- Listing: https://launchinyourcloud.com/directory/elastic-cloud-on-kubernetes/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support.
- Licensing model: source-available
- Installation: Official ECK Helm chart or Kubernetes manifests on EKS, AKS or GKE
- Architecture: Customer-operated Kubernetes operator and Elastic Stack stateful workloads with persistent storage.
- Operations: Customer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.
- Product website: https://www.elastic.co/elastic-cloud-kubernetes
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers self-managed Elastic Cloud on Kubernetes, not Elastic Cloud Hosted or Elastic Cloud Enterprise. ECK automates application lifecycle but does not transfer cluster, storage, backup or upgrade responsibility to Elastic. The free Basic license and paid Enterprise feature set differ; optional Cloud Connect services create separate external dependencies. ECK 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. CVE-2026-72648 has no workaround; after upgrading, rotate the affected service token as Elastic directs.

The ECK and Elastic Stack distribution is governed by Elastic License 2.0 rather than an OSI-approved open-source license. A free Basic tier is available; Enterprise features and support require a subscription.

ECK manages persistent Elasticsearch and related container workloads on customer Kubernetes with durable volumes and operator reconciliation.


### Category fit

- databases-vector: Elasticsearch provides distributed document storage, full-text search and vector search in a customer cluster.

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

- data-analytics: Search, aggregations and Kibana visualizations support interactive analysis of indexed data.

- ai-tools: Vector search and licensed machine-learning capabilities support retrieval and AI-oriented workloads.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 


### Cloud deployment evidence

- Elastic Cloud on Kubernetes on EKS, AKS and GKE (aws, azure, gcp): https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s
  Elastic documents ECK for managed Kubernetes services including Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. The customer owns and operates the cluster and persistent storage.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Deploy Elastic Cloud on Kubernetes: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s

- Install ECK with Helm or manifests: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install

- Manage the ECK license: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck

- Self-managed Elastic pricing and editions: https://www.elastic.co/pricing/self-managed

- ECK 3.5.0 security update ESA-2026-113: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493

- ECK 3.5.0 security update ESA-2026-145: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105

- ECK 3.5.0 security update ESA-2026-146: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106

### Licensing sources

- https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck

- https://www.elastic.co/pricing/self-managed

### Infrastructure sources

- https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s

- https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install


### Buyer diligence


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

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


- Marketplace delivery: Edition-dependent. Elastic documents an ECK BYOL offering inside Google Distributed Cloud air-gapped Marketplace. This is a specific isolated GDC deployment route, not proof that an Elastic Cloud Hosted marketplace subscription delivers ECK in a customer AWS account. Scope: ECK in GDC air-gapped Marketplace; separate from hosted Elastic procurement. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. A GDC air-gapped BYOL Marketplace route does not establish AWS Marketplace commitment treatment for a self-managed ECK Enterprise subscription. Scope: Reviewed public evidence for Elastic Cloud on Kubernetes; unresolved within this edition/deployment. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. ECK deployments can configure Elasticsearch/Kibana external SAML or OIDC realms, with the applicable self-managed subscription. Elastic Cloud organization SSO is a separate control plane. Scope: ECK application authentication; subscription eligibility must be checked. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17). Supporting source: Self-managed subscription feature matrix — https://www.elastic.co/pricing/self-managed.

- SCIM provisioning: Sources checked — unresolved. ECK documents external realms and native/file user management, but a native ECK application SCIM provisioning endpoint was not established. Ingesting another product’s SCIM audit logs is not SCIM support. Scope: Reviewed public evidence for Elastic Cloud on Kubernetes; unresolved within this edition/deployment. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Elastic Cloud on Kubernetes material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17).

- Security controls: Documented. ECK manages credentials in Kubernetes secrets and supports rotation and disabling the default elastic superuser when using external identity. Restrict secret/RBAC access and configure application roles. Current advisory review: ESA-2026-113, 145, and 146 fix service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Upgrade to ECK 3.5.0 or later and rotate the service token where directed. Scope: ECK managed credentials and external realms Affected ECK releases before 3.5.0; exact component and configuration ranges follow the three advisories.. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck. Supporting source: ESA-2026-145 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105. Supporting source: ESA-2026-146 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106.

- Air-gapped operation: Documented. ECK documents offline operation with locally mirrored operator and Elastic Stack images. Integrations also need local package, artifact and endpoint repositories; mirroring the operator alone is insufficient. Scope: ECK isolated deployment with all selected dependencies staged. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/air-gapped-install (reviewed 2026-11-17). Supporting source: Additional offline dependency repositories — https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch.

- Deployment artifact / IaC: Documented. Elastic supplies ECK installation through Helm or Kubernetes manifests. Pin the operator and compatible Elastic application versions and configure persistent storage and RBAC; the operator is not a vendor-operated service. Scope: Self-managed ECK operator installation. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. HA guidance calls for three master-eligible nodes, multiple nodes per data tier and at least one index replica. CPU, memory, shard layout and disk headroom depend on indexing/search workload; no universal 100-user minimum is established. Scope: ECK availability topology, not benchmarked resource sizing. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration (reviewed 2026-11-17).

- License pricing: Documented. The ECK and Elastic Stack distribution is governed by Elastic License 2.0 rather than an OSI-approved open-source license. A free Basic tier is available; Enterprise features and support require a subscription. Scope: Elastic Cloud on Kubernetes: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 1,428.76/month. Three 8-vCPU/64-GiB workers across three AZs host three master/data nodes and two Kibana replicas. The storage assumption is 1,000 GB primary indexed data plus one replica, with 3,000 GB total data capacity and 150 GB boot capacity. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Editorial ECK scenario; load/ingest rate and indexed-data expansion must be measured. Separate shard/zone placement and failure testing are required. No Savings Plans, Spot or credits.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-17). Supporting source: Product topology/sizing basis — https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration. Supporting source: Current AWS documentation: us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: EKS standard versus extended support pricing — https://aws.amazon.com/eks/pricing/.

- Release snapshot / cadence: Documented. Elastic Cloud on Kubernetes 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Rotate the service token after upgrade where ESA-2026-113 requires it. Scope: ECK operator 3.5.0 security update. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Elastic Cloud on Kubernetes 3.5.0 security update (security-advisory): ESA-2026-113, 145, and 146 fix service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Scope: Affected ECK releases before 3.5.0; exact component and configuration ranges follow the three advisories. Conditions: Namespace boundaries, service tokens, and managed resource lifecycle determine exposure. CVE-2026-72648 has no workaround. Action: Upgrade to ECK 3.5.0 or later and rotate the service token where directed. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493; reviewed 2026-11-18. Supporting source: ESA-2026-145 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105. Supporting source: ESA-2026-146 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106.




## Grafana OSS Self-Hosted

Self-hosted dashboards, visualization and alerting for operational data.

- Listing: https://launchinyourcloud.com/directory/grafana/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 OSS; Enterprise distribution/plugins have separate licensing
- Licensing model: open-source
- Installation: Official Linux packages, Docker image or Kubernetes Helm deployment.
- Architecture: Customer-operated Grafana application and database connected to telemetry sources
- Operations: Customer maintains the Grafana server, database, plugins, access controls and data-source integrations.
- Product website: https://grafana.com/oss/grafana/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers Grafana OSS, not Grafana Cloud. The Enterprise Docker image and plugins can have different terms and entitlements. Grafana queries configured data sources; it is not by itself a complete logs/metrics storage backend. Grafana 13.3.1 fixes multiple authorization, impersonation, path-traversal, and denial-of-service CVEs; coordinated patches were also published for maintained 13.2, 13.1, 13.0, and 12.4 branches. Upgrade to a patched release for the deployed branch and review plugin compatibility.

This entry specifically covers AGPL-licensed Grafana OSS. Grafana Enterprise and separately licensed enterprise plugins are outside that OSS scope.

The documented self-hosted runtime uses an application server or container with persistent state services. Hosted vendor editions are outside this listing.


### Category fit

- observability: Visualization, dashboards and alerting over connected telemetry and other data sources; storage backends are configured separately.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/blogs/containers/part-2-observing-and-scaling-mlops-infrastructure-on-amazon-eks/ (checked 2026-11-12). 


### Cloud deployment evidence

- Self-managed Grafana OSS in an EKS monitoring stack (aws): https://aws.amazon.com/blogs/containers/part-2-observing-and-scaling-mlops-infrastructure-on-amazon-eks/
  AWS documents kube-prometheus-stack pods in a customer EKS cluster, including the Prometheus Server StatefulSet and Grafana application. This evidence covers those self-managed components, not Amazon Managed Grafana or Amazon Managed Service for Prometheus. Review persistence, retention, authentication and cluster operating costs.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker installation: https://grafana.com/docs/grafana/latest/setup-grafana/installation/docker/

- Production installation requirements: https://grafana.com/docs/grafana/latest/setup-grafana/installation/

- Visualization capabilities: https://grafana.com/oss/grafana/

- OSS license: https://github.com/grafana/grafana/blob/main/LICENSE

- Grafana 13.3.1 security release: https://github.com/grafana/grafana/releases/tag/v13.3.1

- Grafana security advisories: https://grafana.com/security/security-advisories/

### Licensing sources

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

- https://grafana.com/docs/grafana/latest/setup-grafana/installation/docker/

### Infrastructure sources

- https://grafana.com/docs/grafana/latest/setup-grafana/installation/docker/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Grafana OSS supports Generic OAuth, including compatible OIDC providers, and named OAuth integrations. Configure trusted identity claims, account linking and organization roles. SAML and some synchronization/policy features remain Enterprise/Cloud-only; their paid scope does not make all OSS SSO edition-dependent. Scope: Grafana OSS user login; clarifies free OAuth versus paid SAML/advanced synchronization. Source: https://grafana.com/docs/grafana/latest/setup-grafana/configure-access/configure-authentication/generic-oauth/ (reviewed 2026-11-20). Supporting source: Authentication method and feature comparison — https://grafana.com/docs/grafana/latest/setup-grafana/configure-access/configure-authentication/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide runs the Grafana OSS image with persistent data and configuration; packages and Helm are separate paths. Pin the released OSS image, configure the database, credentials, plugins, TLS/reverse proxy and backups. The Grafana application does not deploy its metrics, logs or traces backends for you. Scope: Official OSS application installation, not the separately licensed Enterprise image or a complete observability stack. Source: https://grafana.com/docs/grafana/latest/setup-grafana/installation/docker/ (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/grafana/grafana. Artifact reference: select the OSS image tag matching the reviewed application release; v13.3.1 release snapshot.

- Minimum footprint / sizing: Documented. The install guide treats 1 core/512 MB as an evaluation floor. Its small application tier starts at 2 cores and 2–4 GB RAM; medium examples use larger, load-balanced instances and an external database. Metrics/log/trace stores and rendering capacity are separate, so these figures do not size 1 TB of telemetry or the full HA observability stack. Scope: Grafana server sizing tiers only; database and observability backends require separate capacity. Source: https://grafana.com/docs/grafana/latest/setup-grafana/installation/ (reviewed 2026-11-20).

- License pricing: Documented. The published Grafana v13.3.1 OSS application uses AGPLv3. Grafana Enterprise/Cloud features, commercial plugins and support have separate terms; an Enterprise download or marketplace offer does not change the OSS licence or include a commercial entitlement. Budget data backends and infrastructure separately. Scope: Grafana OSS application software terms, distinct from Enterprise/Cloud services. Source: https://github.com/grafana/grafana/blob/v13.3.1/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Grafana maintained-branch security patches (security-advisory): The 13.3.1 release and coordinated branch patches address multiple authorization, impersonation, path and availability issues. Scope: Grafana 13.3.1; use the vendor advisory for the exact fix on maintained 13.2, 13.1, 13.0 or 12.4 lines. Conditions: Plugin and deployment configuration matter. This review does not assign one affected-version range to all CVEs. Action: Apply the applicable branch patch and validate plugin compatibility against the individual advisories. Source: https://github.com/grafana/grafana/releases/tag/v13.3.1; reviewed 2026-11-17. Supporting source: Vendor advisory index — https://grafana.com/security/security-advisories/.




## Langfuse Self-Hosted

Self-hosted LLM observability, evaluations and prompt-management platform.

- Listing: https://launchinyourcloud.com/directory/langfuse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
- Licensing model: open-source
- Installation: Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.
- Architecture: Application and worker containers with PostgreSQL, ClickHouse, Redis/Valkey and object storage
- Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
- Product website: https://langfuse.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.

The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.

The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.


Cloud evidence scope: Documented provider-specific deployment

### Category fit

- ai-observability: LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.

- ai-tools: Self-hosted LLM observability, evaluations and prompt-management platform.

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

### Deployment boundaries


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

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

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

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

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


### Cloud deployment evidence

- Langfuse customer cloud deployment on AWS (aws): https://langfuse.com/self-hosting/deployment/aws
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Azure (azure): https://langfuse.com/self-hosting/deployment/azure
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Google Cloud (gcp): https://langfuse.com/self-hosting/deployment/gcp
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v3 community Railway deployment (railway): https://langfuse.com/self-hosting/deployment/railway
  The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v4 community Render Blueprint (render): https://langfuse.com/self-hosting/deployment/render
  The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker Compose on a VM: https://langfuse.com/self-hosting/deployment/docker-compose

- Self-hosting architecture and provider dependencies: https://langfuse.com/self-hosting

- AWS account Terraform deployment: https://langfuse.com/self-hosting/deployment/aws

- Azure account Terraform deployment: https://langfuse.com/self-hosting/deployment/azure

- Google Cloud account Terraform deployment: https://langfuse.com/self-hosting/deployment/gcp

- Core and enterprise licensing: https://github.com/langfuse/langfuse/blob/main/LICENSE

- Licensing and edition terms: https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

- Langfuse v3 community Railway deployment: https://langfuse.com/self-hosting/deployment/railway

- Langfuse v4 community Render Blueprint: https://langfuse.com/self-hosting/deployment/render

- Langfuse v4.82.0 release: https://github.com/langfuse/langfuse/releases/tag/v4.82.0

### Licensing sources

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

- https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

### Infrastructure sources

- https://langfuse.com/self-hosting/deployment/docker-compose

- https://langfuse.com/self-hosting/deployment/aws

- https://langfuse.com/self-hosting/deployment/azure

- https://langfuse.com/self-hosting/deployment/gcp


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review. Scope: Self-hosted OAuth/OIDC sign-in. Source: https://langfuse.com/self-hosting/security/authentication-and-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports. Scope: Upstream Compose recipe; supporting-service operations remain customer responsibilities. Source: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint. Scope: Langfuse Web/Worker resource recommendation; backing services additional. Source: https://langfuse.com/self-hosting/deployment/infrastructure/containers (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/langfuse/langfuse/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Scope: Upstream Langfuse self-hosted release. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Langfuse GitHub Enterprise SSO SSRF fix (security-advisory): Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note. Conditions: Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target. Action: Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0; reviewed 2026-11-18.




## MLflow Tracking Server Self-Hosted

Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.

- Listing: https://launchinyourcloud.com/directory/mlflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.
- Licensing model: open-source
- Installation: Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment.
- Architecture: Customer-operated tracking/API server with configurable metadata database and artifact storage
- Operations: Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.
- Product website: https://mlflow.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Traces can capture model inputs, outputs and intermediate metadata. Point clients at the customer-hosted server and review recording/redaction settings. Applications, evaluators and optional model integrations may still call external providers; hosting the tracking server does not host all training or inference runtimes. Production database, storage and security configuration differ from a local quickstart.

The upstream self-hosted tracking server is Apache-2.0 licensed. This classification does not extend to separate managed MLflow distributions, connected model providers or their commercial services.

The tracking server runs as a Python service or container with metadata/artifact stores. A local SQLite example is not a production architecture; separately plan persistent database, storage and application-runtime infrastructure.


### Category fit

- ai-observability: Experiment tracking and LLM/agent tracing server. This entry describes customer-hosted tracking/observability services, not every model runtime, managed MLflow product or inference backend.

- ai-tools: Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/ (checked 2026-11-12). 


### Cloud deployment evidence

- Self-hosted MLflow deployment on AWS (aws): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/
  The project documents deployment of the MLflow server, metadata database and artifact storage on AWS. This does not refer to a managed MLflow edition or to model serving alone.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Self-hosted MLflow deployment on Azure (azure): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/
  The project documents deployment of the MLflow server, metadata database and artifact storage on Azure. This does not refer to a managed MLflow edition or to model serving alone.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Self-hosted MLflow deployment on Google Cloud (gcp): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/
  The project documents deployment of the MLflow server, metadata database and artifact storage on Google Cloud. This does not refer to a managed MLflow edition or to model serving alone.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting server and deployment methods: https://mlflow.org/docs/latest/self-hosting/

- LLM/agent tracing and captured data: https://mlflow.org/docs/latest/genai/tracing/

- Apache 2.0 license: https://github.com/mlflow/mlflow/blob/master/LICENSE.txt

### Licensing sources

- https://github.com/mlflow/mlflow/blob/master/LICENSE.txt

### Infrastructure sources

- https://mlflow.org/docs/latest/self-hosting/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official guide documents the community-maintained mlflow-oidc-auth plugin and an SSO reverse-proxy pattern. This provides UI/API OIDC integration, but plugin maintenance, MLflow-version compatibility and client token behavior require separate review; it is not a claim of vendor-operated identity support. Scope: Officially documented community-plugin/proxy integration. Source: https://mlflow.org/docs/latest/self-hosting/security/sso/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The self-hosting guide links an upstream Compose bundle with MLflow, PostgreSQL and object storage, plus an official Helm option. Configure production credentials and persistence rather than retaining development defaults. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://mlflow.org/docs/latest/self-hosting/ (reviewed 2026-11-14). Deployment artifact: https://github.com/mlflow/mlflow/tree/master/docker-compose. Artifact reference: master Compose bundle (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted guide documents the UI/API tracking server, metadata backend and artifact-store configuration, but not a universal production CPU/RAM minimum. Size runs/traces, request concurrency, database, artifact storage and redundancy; starting the default local SQLite server does not establish production or HA capacity. Scope: Self-hosted tracking-server topology; numeric production sizing unresolved. Source: https://mlflow.org/docs/latest/self-hosting/architecture/tracking-server/ (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/mlflow/mlflow/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Nagios XI

Commercial infrastructure and network monitoring server deployed on customer-controlled Linux infrastructure.

- Listing: https://launchinyourcloud.com/directory/nagios-xi/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial perpetual node-based license; limited free and 30-day trial modes are available.
- Licensing model: commercial-only
- Installation: Official Nagios XI Amazon EC2 AMI or package installation on a supported Linux server
- Architecture: Customer-operated Nagios XI Linux server with Nagios Core engine, XI web application, database, plugins and monitoring data
- Operations: Customer manages compute, plugins, credentials, monitored endpoints, upgrades, backups, availability and notification delivery.
- Product website: https://www.nagios.com/products/nagios-xi/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Nagios Core is open source, but the XI interface and system frameworks are commercially licensed. The AWS badge covers the official EC2 AMI, not a managed Nagios service. The cloud guide installs and compiles the application at first boot, so the AMI is not a durable application-version snapshot. The current reviewed upstream release is 2026R2, with command/SQL injection fixes; verify the actual build and change initial database/system credentials.

The selected XI product is proprietary commercial software despite its Nagios Core foundation and capped free mode.

Nagios XI runs as a persistent customer-operated Linux monitoring server or appliance.


### Category fit

- observability: Provides self-hosted infrastructure, network and service monitoring with checks, alerts, dashboards, reporting and an API.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf (checked 2026-11-19). 


### Cloud deployment evidence

- Official Nagios XI Amazon EC2 AMI (aws): https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf
  Nagios's 2026 guide directs the customer to select the official public AMI, choose instance, network and key-pair settings, and launch Nagios XI in the customer's AWS account.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026R1 documentation.


### Sources

- Nagios XI product and licensing: https://www.nagios.com/products/nagios-xi/

- Official Nagios XI Amazon EC2 AMI guide: https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf

- Nagios XI license composition: https://support.nagios.com/nagios-xi-resources/

- Buyer evidence: iac: https://assets.nagios.com/downloads/nagiosxi/versions.php

- Manual installer procedure and supported method: https://assets.nagios.com/downloads/nagiosxi/docs/Manual-Install-Instructions-for-Nagios-XI-2026.pdf

- Reviewed deployment artifact reference: https://assets.nagios.com/downloads/nagiosxi/2026/xi-2026R2.tar.gz

- Buyer evidence: release: https://www.nagios.com/changelog/nagios-xi/

### Licensing sources

- https://www.nagios.com/products/nagios-xi/

- https://support.nagios.com/nagios-xi-resources/

### Infrastructure sources

- https://www.nagios.com/products/nagios-xi/

- https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: Nagios XI: selected customer-operated edition. Source: https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: Nagios XI: selected customer-operated edition. Source: https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: Nagios XI: selected customer-operated edition. Source: https://www.nagios.com/products/nagios-xi/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Nagios XI: selected customer-operated edition. Source: https://www.nagios.com/products/nagios-xi/ (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: Nagios XI: selected customer-operated edition. Source: https://www.nagios.com/products/nagios-xi/ (reviewed 2026-11-19).

- Security controls: Documented. The EC2 guide disables root password SSH login, uses the operator’s key and ec2-user, and requires changing initial database/system passwords. Restrict SSH/HTTPS and any monitoring ingress to the intended sources; check the application version downloaded at first boot. These operator requirements are not proof of a hardened or attested installation. Scope: Nagios XI EC2 deployment and initial-credential responsibilities. Source: https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: Nagios XI: selected customer-operated edition. Source: https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The vendor download index publishes the versioned XI 2026R2 Linux installer and checksum. It is separate from the regional EC2 AMIs: the cloud guide says the application is installed and compiled at first boot. Review privileged installer changes, supported OS and commercial entitlement, and verify the actual running build. The large installer archive was not downloaded or executed in this review. Scope: Vendor-published Linux installer reference, not an assertion that every EC2 AMI has the same build. Source: https://assets.nagios.com/downloads/nagiosxi/versions.php (reviewed 2026-11-19). Deployment artifact: https://assets.nagios.com/downloads/nagiosxi/2026/xi-2026R2.tar.gz. Artifact reference: xi-2026R2.tar.gz; published SHA-256 7587a72491bf531107699cfb2eccaefabb4f343fa1c68bc92eb7fcab91bd8616; regional AMI/first-boot version separate. Supporting source: Manual installer procedure and supported method — https://assets.nagios.com/downloads/nagiosxi/docs/Manual-Install-Instructions-for-Nagios-XI-2026.pdf.

- Minimum footprint / sizing: Documented. The official EC2 guide recommends at least 4 CPU cores and 8 GB RAM for Nagios XI. This is an instance baseline; monitored endpoints, plugins, retention, storage, backups and HA require separate sizing. Scope: Nagios XI EC2 single-instance recommendation, not a complete production workload or HA design. Source: https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf (reviewed 2026-11-19).

- License pricing: Edition-dependent. Nagios XI is commercially licensed with limited free and trial modes. Confirm the monitored-node tier, maintenance and support entitlement; Nagios Core's open-source license does not license the XI application. Scope: Nagios XI: selected customer-operated edition. Source: https://www.nagios.com/products/nagios-xi/ (reviewed 2026-11-19).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: Nagios XI: selected customer-operated edition. Source: https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. Nagios XI 2026R2 was released September 23, 2026. It includes command-injection fixes in CCM Command Test and Upload MIB and a V2-dashboard SQL-injection fix. The EC2 guide does not establish a fixed 2026R1.7 AMI: it installs the application at first boot. Verify the actual instance build and upgrade entitlement. Scope: Upstream XI application release, distinct from regional AMI metadata and first-boot download behavior. Source: https://www.nagios.com/changelog/nagios-xi/ (reviewed 2026-11-19). Supporting source: Cloud first-boot installation behavior — https://assets.nagios.com/downloads/nagiosxi/docs/Using-Nagios-XI-In-Amazon-EC2-Cloud.pdf.




### Security and lifecycle reviews

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

- Nagios XI 2026R2 command and SQL injection fixes (security-advisory): The 2026R2 changelog fixes command injection in CCM Command Test and Upload MIB and SQL injection in the V2-dashboard endpoint. Scope: The management/dashboard paths named in the 2026R2 release; no universal affected-version range or CVE is asserted. Conditions: Installed application build and access to the affected features determine applicability. An AMI or first-boot download needs its own installed-version check. Action: Upgrade to 2026R2 or an appropriate later supported build, review the changed role/wizard behavior and verify the actual instance version. Apply the deployment guide’s credential and management-network requirements separately. Source: https://www.nagios.com/changelog/nagios-xi/; reviewed 2026-11-19.




## OpenObserve Enterprise Self-Hosted

Self-hosted observability platform for ingesting, searching and analyzing logs, metrics and traces.

- Listing: https://launchinyourcloud.com/directory/openobserve-enterprise-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Enterprise End User License Agreement. The vendor publishes a free tier through 50 GB/day of ingestion, with a license required above that threshold.
- Licensing model: commercial-only
- Installation: Install the Enterprise Helm chart and CloudNativePG operator, then configure the cluster, object storage and application settings for the selected provider.
- Architecture: Customer-operated Kubernetes workloads use PostgreSQL for metadata, NATS for coordination and cloud object storage for Parquet telemetry.
- Operations: The customer runs the cluster, configures storage credentials and ingestion endpoints, sizes components, manages backups and retention, and applies chart and application upgrades.
- Product website: https://openobserve.ai/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

The documented paths cover Enterprise Edition. Feature access depends on the enterprise entitlement. OpenObserve documents outbound product usage reporting and a ZO_TELEMETRY opt-out. Plan for separate recovery of telemetry objects and PostgreSQL metadata. The reviewed chart 1.1.7 pins Enterprise image v1.1.2; do not substitute an OSS or release-candidate tag by name alone. Dex is optional and must be configured. The EKS node example is a sizing starting point, not an HA workload benchmark. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example.

The reviewed Enterprise build is proprietary under the vendor EULA. The separate open-source distribution uses AGPL-3.0.

Application services and dependencies run in Kubernetes. The provider-specific examples use object storage and persistent PostgreSQL and NATS workloads.


### Category fit

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openobserve.ai/docs/enterprise-setup/amazon-eks/ (checked 2026-11-20). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openobserve.ai/docs/enterprise-setup/azure-aks/ (checked 2026-11-20). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openobserve.ai/docs/enterprise-setup/google-gke/ (checked 2026-11-20). 


### Cloud deployment evidence

- OpenObserve Enterprise on Amazon EKS (aws): https://openobserve.ai/docs/enterprise-setup/amazon-eks/
  The vendor walkthrough deploys the Enterprise application to the customer's EKS cluster, with S3 for telemetry and IAM permissions for storage access. The linked cluster sample pins Kubernetes 1.30; verify AWS availability and application compatibility and update that example version before use.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- OpenObserve Enterprise on Azure AKS (azure): https://openobserve.ai/docs/enterprise-setup/azure-aks/
  The vendor walkthrough deploys the Enterprise application to the customer's AKS cluster, with Azure Blob Storage, CloudNativePG and clustered NATS.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- OpenObserve Enterprise on Google GKE (gcp): https://openobserve.ai/docs/enterprise-setup/google-gke/
  The vendor walkthrough deploys the Enterprise application to a Standard GKE cluster in the customer's Google Cloud project. The documented Cloud Storage configuration uses S3 interoperability and HMAC credentials.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Sources

- Enterprise installation and architecture: https://openobserve.ai/docs/enterprise-setup/

- Enterprise EULA: https://openobserve.ai/legal/enterprise-license/

- Enterprise licensing, limits and feature entitlements: https://openobserve.ai/docs/enterprise-setup/license-and-pricing/

- Edition comparison and download channels: https://openobserve.ai/downloads/

- Application configuration and usage telemetry: https://openobserve.ai/docs/administration/configuration/environment-variables/

- OpenObserve Enterprise on Amazon EKS: https://openobserve.ai/docs/enterprise-setup/amazon-eks/

- OpenObserve Enterprise on Azure AKS: https://openobserve.ai/docs/enterprise-setup/azure-aks/

- OpenObserve Enterprise on Google GKE: https://openobserve.ai/docs/enterprise-setup/google-gke/

- Published chart index: https://charts.openobserve.ai/index.yaml

- Buyer evidence: sso: https://openobserve.ai/docs/user-guide/account-administration/identity-and-access-management/sso/

- Enterprise access-control features: https://openobserve.ai/docs/features/enterprise/

- EKS example node configuration: https://raw.githubusercontent.com/openobserve/eks-openobserve/main/o2-eks.yaml

- Capacity planning inputs: https://openobserve.ai/docs/enterprise-setup/capacity-planning/

- Inspected Enterprise-capable chart: https://charts.openobserve.ai/openobserve-1.1.7.tgz

- Current EKS version availability and lifecycle: https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html

### Licensing sources

- https://openobserve.ai/legal/enterprise-license/

- https://openobserve.ai/docs/enterprise-setup/license-and-pricing/

- https://openobserve.ai/downloads/

### Infrastructure sources

- https://openobserve.ai/docs/enterprise-setup/


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Single sign-on: Documented. Enterprise supports SSO through Dex with external identity providers. Configure the Dex client, redirect/callback URLs and provider connector; the EKS guide enables Dex explicitly. The feature is not available in the separate OSS edition. Scope: Configured self-hosted Enterprise authentication and licensed features. Source: https://openobserve.ai/docs/user-guide/account-administration/identity-and-access-management/sso/ (reviewed 2026-11-20).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Security controls: Documented. Enterprise documentation describes OpenFGA-based RBAC, Dex SSO and configurable secure authentication cookies. The cloud guides scope storage credentials through provider IAM. Operators must configure these controls and review telemetry, external connectors and optional AI/reporting services. Scope: Configurable Enterprise controls, not an independent deployment attestation. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20). Supporting source: Enterprise access-control features — https://openobserve.ai/docs/features/enterprise/. Supporting source: Configuration and telemetry opt-out — https://openobserve.ai/docs/administration/configuration/environment-variables/.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected Enterprise-capable Helm package is openobserve 1.1.7. Its values pin the Enterprise image to v1.1.2; chart, application, report-server and optional AI images have separate versions. Install CloudNativePG and provider storage prerequisites separately. Scope: Helm package and Enterprise image settings; not a complete production approval. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20). Deployment artifact: https://charts.openobserve.ai/openobserve-1.1.7.tgz. Artifact reference: openobserve 1.1.7; Enterprise image v1.1.2; sha256:394886d2c521acfc25012190d99c788814bf0a6f944674febd993ec8be40abe2. Supporting source: Published chart index — https://charts.openobserve.ai/index.yaml.

- Minimum footprint / sizing: Documented. The vendor-linked EKS example provisions three m7i.xlarge nodes, with desired/minimum count 3 and maximum 6, alongside a managed EKS control plane. PostgreSQL, NATS, storage and enabled application roles also require sizing. This example is not a universal minimum or a measured fit for 100 users/1 TB. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example. Scope: Reviewed AWS example, not a production workload benchmark. Source: https://openobserve.ai/docs/enterprise-setup/amazon-eks/ (reviewed 2026-11-20). Supporting source: EKS example node configuration — https://raw.githubusercontent.com/openobserve/eks-openobserve/main/o2-eks.yaml. Supporting source: Capacity planning inputs — https://openobserve.ai/docs/enterprise-setup/capacity-planning/. Supporting source: Current EKS version availability and lifecycle — https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html.

- License pricing: Documented. The Enterprise EULA and licensing guide describe a free tier up to 50 GB/day of ingestion, with registration/licensing above that level and feature-specific entitlements. The guide permits three monthly over-limit occurrences before restricting search. Infrastructure, operating labor and support are separate. Scope: Enterprise software entitlement and documented usage limits, not cloud operating cost. Source: https://openobserve.ai/docs/enterprise-setup/license-and-pricing/ (reviewed 2026-11-20). Supporting source: Enterprise EULA — https://openobserve.ai/legal/enterprise-license/.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment. Source: https://openobserve.ai/docs/enterprise-setup/ (reviewed 2026-11-20).

- Release snapshot / cadence: Sources checked — unresolved. Chart 1.1.7 pins o2cr.ai/openobserve/openobserve-enterprise:v1.1.2. This establishes a reviewed deployable image reference, but not its publication timestamp, a current Enterprise release/support designation or parity with public OSS/prerelease tags. Request the applicable Enterprise release notes and compatibility matrix. Scope: Partial Enterprise package/image evidence; application publication and supported bundle unresolved. Source: https://charts.openobserve.ai/index.yaml (reviewed 2026-11-20). Supporting source: Inspected Enterprise-capable chart — https://charts.openobserve.ai/openobserve-1.1.7.tgz.







## OpenSearch

Distributed search and analytics engine with vector retrieval, operational-data analysis and OpenSearch Dashboards visualizations.

- Listing: https://launchinyourcloud.com/directory/opensearch/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms.
- Licensing model: open-source
- Installation: Run official Docker images and customize the documented Docker Compose examples; native package and tarball installations are also documented.
- Architecture: Customer-operated distributed cluster with index shards and replicas on persistent storage, plus optional Dashboards and ingestion components
- Operations: Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.
- Product website: https://opensearch.org/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Sample deployments and demo security settings require production configuration. Official images distributed through Amazon ECR are not evidence of an AWS-specific deployment. The listing covers self-operated OpenSearch; Amazon OpenSearch Service and other managed services are separate delivery models. Embeddings and AI connectors can involve external models or services. OpenSearch 3.10.0 removes experimental Views and macOS x64 archives and fixes remote-store data-loss or stall paths, bulk-index corruption, heap leaks, snapshot queue stalls, remote-translog issues, and OOM behavior. Validate plugins, Dashboards, and storage recovery before upgrading.

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

Official Docker images run OpenSearch nodes and Dashboards on compatible container hosts. Persistent index storage and host memory and kernel settings are operational requirements; distribution through a cloud registry does not establish a provider deployment badge.


### Category fit

- databases-vector: Indexes and searches vectors alongside metadata, with lexical, nearest-neighbor, semantic and hybrid retrieval. Embedding generation requires an appropriate configured model or externally generated vectors.

- data-analytics: Distributed search and aggregation engine with OpenSearch Dashboards for exploring and visualizing indexed data.

- observability: Search and analytics over ingested operational data, including log analysis and monitoring; collection, ingestion and dashboard configuration remain deployment work.

- ai-tools: Vector storage, semantic search and retrieval for AI applications and RAG. Embedding generation and model connectors have separately configured runtimes and data flows.

### Deployment boundaries


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


### Cloud deployment evidence

- Self-operated OpenSearch and Dashboards on Railway (railway): https://railway.com/deploy/opensearch-analytics
  The community recipe deploys OpenSearch 3 and Dashboards as customer-project services, with the search API on private networking. Its wrappers derive from upstream OpenSearch images. Review node count, heap/storage sizing, security plugin configuration, TLS and backups; this is separate from Amazon OpenSearch Service and does not imply high availability.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The OpenSearch Software Foundation is organized under the Linux Foundation. Official release records show OpenSearch 3.9.0 released on 29 September 2026 and continuing maintenance planning. Project case studies describe production adoption by Atlassian, LINE and other organizations; managed-service case studies demonstrate project adoption rather than proving self-hosted account boundaries.

Reviewed 2026-11-10.

- OpenSearch Software Foundation: https://opensearch.org/foundation/

- Current releases and maintenance policy: https://opensearch.org/releases/

- Current released artifacts: https://opensearch.org/downloads/

- Named production case studies: https://opensearch.org/case-studies/

### Sources

- OpenSearch Core capabilities and architecture: https://opensearch.org/platform/opensearch-core/

- Vector search documentation: https://docs.opensearch.org/latest/vector-search/

- Official Docker installation: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- Security demo configuration: https://docs.opensearch.org/latest/security/configuration/demo-configuration/

- Release downloads and Apache-2.0 licensing: https://opensearch.org/downloads/

- Upstream Apache-2.0 license: https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

- OpenSearch 3.10.0 release: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0

### Licensing sources

- https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

### Infrastructure sources

- https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- https://opensearch.org/platform/opensearch-core/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The Security plugin supports the SAML 2.0 browser SSO profile, primarily for OpenSearch Dashboards. This is not a general authentication method for every direct OpenSearch client/API call. Scope: OpenSearch Security plugin and Dashboards browser login. Source: https://docs.opensearch.org/latest/security/authentication-backends/saml/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker installation guide provides official images and Compose examples. Configure the required administrator password, persistent data and security settings; demo certificates/settings are not a production security baseline. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide sets a default 1-GB JVM heap and recommends allocating about half of system RAM to heap. It does not establish one complete production minimum: data/index size, roles, replicas, ingestion, Dashboards, vectors and storage performance must be sized separately. A JVM default is not HA capacity. Scope: Upstream JVM/install defaults; full production footprint unresolved. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/index/ (reviewed 2026-11-20).

- License pricing: Documented. The OpenSearch core is Apache-2.0 licensed. Plugins and bundled components require their own licence review; commercial support, managed Amazon OpenSearch Service, model services and infrastructure have separate prices. Scope: Upstream OpenSearch core licence; managed service pricing excluded. Source: https://raw.githubusercontent.com/opensearch-project/OpenSearch/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. OpenSearch 3.10.0 was published November 18, 2026. It removes experimental Views and macOS x64 archives and contains material remote-store, indexing, heap, snapshot, translog, and OOM fixes; match OpenSearch Dashboards and plugins to 3.10. Scope: Upstream OpenSearch 3.10 release. Source: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0 (reviewed 2026-11-18).







## Parseable OSS

Self-hosted telemetry data lake for querying logs, metrics and traces stored in columnar files.

- Listing: https://launchinyourcloud.com/directory/parseable-oss/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 for the OSS project. Standalone and distributed OSS deployment guides are available; Enterprise software/support has separate terms.
- Licensing model: open-source
- Installation: Install OSS with Helm in standalone or distributed mode on the documented AWS path, or use the Railway standalone template. Pin application/chart versions and review the migration requirements for older charts.
- Architecture: Customer-operated standalone server or separate OSS ingestor/querier workloads use local staging and durable object storage for Parquet telemetry.
- Operations: The customer manages credentials, data ingestion, persistent staging, object storage, access configuration, retention, backups and upgrades.
- Product website: https://www.parseable.com/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

The standalone example is a single pod; distributed OSS has a separate vendor guide and is not automatically an HA guarantee. Chart 3.2.4 defaults to application v3.2.3, whereas the reviewed upstream release is v3.2.7. Existing standalone charts through 3.0.2 need a new 3.1.0+ installation and verified data migration. Railway uses a moving edge image, paid Buckets and a persistent staging volume. Disable optional usage statistics with P_SEND_ANONYMOUS_USAGE_DATA=false when required; this alone does not establish air-gapped operation.

AGPL-3.0 applies to the reviewed OSS release. Official guides cover both standalone and distributed OSS; Enterprise entitlements remain separate.

Standalone or distributed OSS runs in customer-operated persistent containers/Kubernetes workloads, with durable object storage and staging configured independently.


### Category fit

- observability: The application ingests and queries operational telemetry and provides dashboards and alerting.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks (checked 2026-11-20). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/railway (checked 2026-11-20). 


### Cloud deployment evidence

- Parseable OSS on Amazon EKS (aws): https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks
  The vendor documents EKS application hosting and IAM roles for the S3-backed installation. Pair the provider-specific settings with the standalone OSS Helm guide.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Parseable OSS on Railway (railway): https://www.parseable.com/docs/self-hosted/installation/standalone/railway
  The upstream template runs the application in the customer's Railway project with a Railway Bucket for durable objects and a persistent volume for staged events.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Community and maintenance

The upstream project has sustained public contributor history (including nikhilsinhaparseable, nitisht, trueleo) and a reviewed dated v3.2.7 release. This establishes maintenance/community participation rather than a production suitability, support or capacity guarantee.

Reviewed 2026-11-20.

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

- Reviewed dated upstream release: https://github.com/parseablehq/parseable/releases/tag/v3.2.7

### Sources

- Parseable OSS source and AGPL-3.0 license: https://github.com/parseablehq/parseable

- Standalone OSS Helm installation: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

- AWS deployment overview: https://www.parseable.com/docs/self-hosted/aws

- Upstream Parseable releases: https://github.com/parseablehq/parseable/releases

- Usage statistics and opt-out: https://www.parseable.com/docs/self-hosted/telemetry

- Parseable OSS on Amazon EKS: https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks

- Parseable OSS on Railway: https://www.parseable.com/docs/self-hosted/installation/standalone/railway

- Distributed OSS configuration: https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss

- Official Railway template: https://railway.com/deploy/parseable-1

- Buyer evidence: sso: https://www.parseable.com/docs/user-guide/openid

- Explicit OSS feature inclusion: https://www.parseable.com/pricing

- Buyer evidence: securityControls: https://www.parseable.com/docs/user-guide/rbac

- Runtime configuration and telemetry: https://www.parseable.com/docs/self-hosted/configuration

- Buyer evidence: licensePricing: https://github.com/parseablehq/parseable/blob/v3.2.7/LICENSE

- Buyer evidence: release: https://github.com/parseablehq/parseable/releases/tag/v3.2.7

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

### Licensing sources

- https://github.com/parseablehq/parseable

- https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

### Infrastructure sources

- https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

- https://www.parseable.com/docs/self-hosted/installation/standalone/railway


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Single sign-on: Documented. Parseable OSS supports OIDC sign-in. Configure the issuer, client credentials, redirect URI and OIDC environment for the selected standalone/distributed mode; Parseable roles still control authorization after login. This does not establish SCIM provisioning. Scope: Configured OSS OIDC login; enterprise support and SCIM are separate. Source: https://www.parseable.com/docs/user-guide/openid (reviewed 2026-11-20). Supporting source: Explicit OSS feature inclusion — https://www.parseable.com/pricing.

- SCIM provisioning: Sources checked — unresolved. The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Security controls: Documented. OSS documentation provides OIDC authentication, role/privilege controls and API keys. Apply object-store least privilege and protect ingestion/query endpoints. The Railway template uses a moving edge image and a generated admin password when one is not supplied; pin and review the deployed version. Usage-statistics opt-out is separate from identity, storage and optional external integrations. Scope: Configured OSS access controls and deployment credentials. Source: https://www.parseable.com/docs/user-guide/rbac (reviewed 2026-11-20). Supporting source: OSS OIDC configuration — https://www.parseable.com/docs/user-guide/openid. Supporting source: Railway admin credentials and moving image — https://www.parseable.com/docs/self-hosted/installation/standalone/railway. Supporting source: Runtime configuration and telemetry — https://www.parseable.com/docs/self-hosted/configuration.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected Parseable chart 3.2.4 supports OSS standalone and distributed values; its default appVersion is v3.2.3, separate from the reviewed v3.2.7 upstream release. Override an image only after compatibility checks. Standalone chart 3.0.2 or older requires a separate 3.1.0+ installation, verified data migration and traffic cutover rather than an in-place upgrade. The Railway template uses a moving edge image. Scope: Versioned OSS Helm artifact and explicitly moving Railway template. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss (reviewed 2026-11-20). Deployment artifact: https://charts.parseable.com/helm-releases/parseable-3.2.4.tgz. Artifact reference: parseable chart 3.2.4; default appVersion v3.2.3; sha256:02e96d14ca94b55cacb8d30964ee42bf58b3c3add4ecaf571838463c95d8cbdf. Supporting source: Distributed OSS configuration — https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss. Supporting source: Official Railway template — https://railway.com/deploy/parseable-1. Supporting source: Railway image/storage details — https://www.parseable.com/docs/self-hosted/installation/standalone/railway.

- Minimum footprint / sizing: Documented. The standalone OSS example requests 250m CPU/1 GiB and limits 500m CPU/4 GiB for the application, with example 5 GiB staging/data volumes depending on storage mode. The distributed example separates ingestors and queriers. These are example requests, not HA throughput minima; object storage, replicated infrastructure and workload capacity are additional. Scope: Vendor example application resources; excludes production HA/database and object-storage sizing. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss (reviewed 2026-11-20). Supporting source: Distributed OSS topology — https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss.

- License pricing: Documented. Parseable OSS v3.2.7 uses AGPL-3.0, and the pricing page lists the OSS software tier at $0. Enterprise licensing/support and the customer’s infrastructure and operating labor are separate. Scope: Versioned upstream OSS licence and software-price tier. Source: https://github.com/parseablehq/parseable/blob/v3.2.7/LICENSE (reviewed 2026-11-20). Supporting source: OSS pricing and OIDC inclusion — https://www.parseable.com/pricing.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed upstream Parseable OSS snapshot is v3.2.7, published November 17, 2026. Helm chart 3.2.4 defaults to the older v3.2.3 application image, while the Railway template uses edge. Treat application, chart and template versions separately. Scope: Upstream OSS application; packaging defaults and moving templates may lag or differ. Source: https://github.com/parseablehq/parseable/releases/tag/v3.2.7 (reviewed 2026-11-20).




### Security and lifecycle reviews

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

- Parseable standalone chart migration boundary (lifecycle): Standalone installations using chart 3.0.2 or earlier require a separate 3.1.0+ installation and data migration; the vendor warns against a direct chart upgrade. Scope: Existing OSS standalone installations through chart 3.0.2; new installations are not affected by this transition. Conditions: The guide also distinguishes PVC/temporary staging choices and immutable StatefulSet volume templates. Action: Create a separate target installation, migrate and verify data, and switch traffic after verification. Follow storage expansion/migration instructions for the selected backend. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss; reviewed 2026-11-20.




## Prometheus

Metrics monitoring and time-series database for instrumented services and infrastructure.

- Listing: https://launchinyourcloud.com/directory/prometheus/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Prometheus components.
- Licensing model: open-source
- Installation: Run official server binaries or the documented Prometheus container with persistent storage and a configured scrape file.
- Architecture: Customer-operated metrics server and local time-series storage, with optional Alertmanager and exporters
- Operations: Customer manages scrape targets, storage retention, alerting, access controls, exporters, backups and upgrades.
- Product website: https://prometheus.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The sample Docker configuration is not a complete production monitoring deployment. Exporters, remote-write destinations and alert integrations may be outside the account; capacity and retention remain operational choices.

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

Customer-operated metrics server and local time-series storage, with optional Alertmanager and exporters. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- observability: Metrics collection, time-series storage and PromQL analysis/alert evaluation. Log storage and distributed tracing require other components.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/blogs/containers/part-2-observing-and-scaling-mlops-infrastructure-on-amazon-eks/ (checked 2026-11-12). 


### Cloud deployment evidence

- Self-managed Prometheus in an EKS monitoring stack (aws): https://aws.amazon.com/blogs/containers/part-2-observing-and-scaling-mlops-infrastructure-on-amazon-eks/
  AWS documents kube-prometheus-stack pods in a customer EKS cluster, including the Prometheus Server StatefulSet and Grafana application. This evidence covers those self-managed components, not Amazon Managed Grafana or Amazon Managed Service for Prometheus. Review persistence, retention, authentication and cluster operating costs.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Prometheus is a CNCF Graduated project with public steering governance, established instrumentation/integration participation and a maintained upstream release stream.

Reviewed 2026-11-10.

- Community governance: https://prometheus.io/governance/

- Graduation and ecosystem context: https://prometheus.io/

- Current maintenance releases: https://github.com/prometheus/prometheus/releases

### Sources

- Official installation and runtime: https://prometheus.io/docs/prometheus/latest/installation/

- Upstream project and capabilities: https://github.com/prometheus/prometheus

- Current upstream license: https://prometheus.io/

### Licensing sources

- https://prometheus.io/

### Infrastructure sources

- https://prometheus.io/docs/prometheus/latest/installation/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed server authentication page documents TLS and Basic authentication. It does not establish a native enterprise SSO/provisioning integration; an external identity-aware proxy would need a separately reviewed design. Scope: Native server authentication page only; no claim that SSO is impossible. Source: https://prometheus.io/docs/prometheus/latest/configuration/https/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The server supports TLS and HTTP Basic authentication through a web configuration file. Client certificates and network restrictions require explicit settings; this is not proof of enterprise SSO or compliance certification. Scope: Prometheus server transport and web authentication configuration. Source: https://prometheus.io/docs/prometheus/latest/configuration/https/ (reviewed 2026-11-14).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide provides binaries and a server container. Use persistent metrics storage and a configured scrape file; adding container command-line parameters replaces the default argument list. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://prometheus.io/docs/prometheus/latest/installation/ (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/prom/prometheus. Artifact reference: select a released Prometheus image tag.

- Minimum footprint / sizing: Sources checked — unresolved. The storage guide estimates disk from retention seconds × ingested samples/second × roughly 1–2 bytes/sample, and reserves 15–20% disk headroom for compaction. It does not establish a universal CPU/RAM or HA minimum. Active-series cardinality, scrape rate, queries, WAL and remote storage require a workload-specific plan. Scope: Official local-TSDB capacity model; whole-system compute and HA sizing remain unconfirmed. Source: https://prometheus.io/docs/prometheus/latest/storage/ (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## SigNoz Self-Hosted

OpenTelemetry-based application observability platform for traces, metrics and logs.

- Listing: https://launchinyourcloud.com/directory/signoz/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Expat for core code; ee/ enterprise code has its own separate license.
- Licensing model: open-source
- Installation: Use the supported Foundry workflow to generate and run the Docker Compose stack; the older bundled install script/deploy files are deprecated.
- Architecture: Customer-operated observability services, OpenTelemetry collection and persistent analytical storage
- Operations: Customer manages collectors, storage capacity, retention, authentication, backups, alert API and operator migrations, and platform upgrades.
- Product website: https://signoz.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

The reviewed guide is explicitly for self-hosted Community without a license. Commercial features require their stated terms. Instrumentation can capture sensitive payloads, so configure capture and retention according to the data being monitored. SigNoz v0.150.0 automatically migrates stored alert rules to v2alpha1 but removes the v1 rule APIs and GET /api/v2/rules. Update API scripts, move Terraform configurations from signoz_alert to signoz_rule, use SigNoz Operator v0.0.5 or newer, and back up the metastore before upgrading. The release also begins dual-ingesting log bodies into native JSON storage; plan additional collector, ClickHouse, and log-disk capacity before rollout.

MIT Expat for core code; ee/ enterprise code has its own separate license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated observability services, OpenTelemetry collection and persistent analytical storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. From v0.150.0, log bodies are dual-ingested during migration. The vendor recommends 25% OpenTelemetry Collector CPU and memory headroom, 15% ClickHouse CPU headroom, and log-disk growth approximately equal to the existing body column.


### Category fit

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://signoz.io/docs/install/kubernetes/aws/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://signoz.io/docs/install/kubernetes/aks/ (checked 2026-11-12). 

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


### Cloud deployment evidence

- SigNoz self-hosting on Amazon EKS (aws): https://signoz.io/docs/install/kubernetes/aws/
  Official self-hosting instructions install SigNoz and its storage components on Amazon EKS; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- SigNoz self-hosting on Azure Kubernetes Service (azure): https://signoz.io/docs/install/kubernetes/aks/
  Official self-hosting instructions install SigNoz and its storage components on Azure Kubernetes Service; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- SigNoz self-hosting on Google Kubernetes Engine (gcp): https://signoz.io/docs/install/kubernetes/gcp/
  Official self-hosting instructions install SigNoz and its storage components on Google Kubernetes Engine; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The active release stream records recent maintenance and multiple named contributors and first-time contributions across releases.

Reviewed 2026-11-10.

- Maintenance and community contributor credits: https://github.com/SigNoz/signoz/releases

- Public upstream project: https://github.com/SigNoz/signoz

### Sources

- Official installation and runtime: https://signoz.io/docs/install/docker/

- Upstream project and capabilities: https://github.com/SigNoz/signoz

- Current upstream license: https://raw.githubusercontent.com/SigNoz/signoz/develop/LICENSE

- SigNoz v0.150.0 breaking changes: https://github.com/SigNoz/signoz/releases/tag/v0.150.0

- SigNoz v0.150.0 alert-rule upgrade guide: https://signoz.io/docs/operate/migration/upgrade-0-150/

- SigNoz JSON log migration capacity guidance: https://signoz.io/guides/json-logs-migration/

### Licensing sources

- https://raw.githubusercontent.com/SigNoz/signoz/develop/LICENSE

### Infrastructure sources

- https://signoz.io/docs/install/docker/

- https://signoz.io/docs/operate/migration/upgrade-0-150/

- https://signoz.io/guides/json-logs-migration/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML and OIDC require Enterprise Self-Hosted. Google Workspace OAuth2 is also documented for Community Edition. Login-time account creation is distinct from automated deprovisioning. Scope: Self-hosted SigNoz edition-specific protocols. Source: https://signoz.io/docs/manage/administrator-guide/sso/overview/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The supported Docker workflow uses Foundry to generate/manage the Compose deployment. The older install.sh and bundled deploy files are deprecated from v0.130.0; do not use them as the current installation artifact. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://signoz.io/docs/install/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The supported Foundry/Docker installation requires at least 4 GB allocated to Docker for its local stack. Production ingestion rate, ClickHouse/Keeper topology, retention and replicas can raise capacity substantially; this is an installation baseline, not a 1 TB HA telemetry sizing guarantee. Scope: Current supported Docker installation requirements; application, storage and collector roles require workload sizing. Source: https://signoz.io/docs/install/docker/ (reviewed 2026-11-20).

- License pricing: Documented. The v0.150.0 licence applies MIT terms to the core and explicitly excludes ee/ and cmd/enterprise/, which have separate Enterprise terms. Community source rights do not grant paid SAML/OIDC features or commercial support. Self-hosted licence, ingestion/storage infrastructure and SigNoz Cloud charges are separate. Scope: Published Community/Enterprise source boundary; not a hosted usage-price quote. Source: https://github.com/SigNoz/signoz/blob/v0.150.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Splunk Enterprise

Customer-managed platform for ingesting, indexing, searching and visualizing machine data.

- Listing: https://launchinyourcloud.com/directory/splunk-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions.
- Licensing model: commercial-only
- Installation: Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies.
- Architecture: Standalone or distributed customer-operated search heads, indexers and management components, with local storage or optional SmartStore object storage
- Operations: Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.
- Product website: https://www.splunk.com/en_us/products/splunk-enterprise.html
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

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

Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition.

Splunk Enterprise runs persistent standalone or distributed search, indexing and management services on customer-managed hosts. SmartStore can move indexed data to customer object storage, but the search and indexing tiers remain long-running server workloads.


### Category fit

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

- data-analytics: Provides search, dashboards, reports and statistical analysis over indexed machine-generated data.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 


### Cloud deployment evidence

- Splunk Enterprise reference hardware for AWS, Azure and Google Cloud (aws, azure, gcp): https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware
  Splunk explicitly states that Splunk Enterprise can be deployed on Amazon Web Services, Microsoft Azure and Google Cloud Platform, including named government, local and distributed variants. Customers must still select supported host specifications and size each deployment for its workload.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Customer-managed Splunk Enterprise BYOL architecture (aws, azure, gcp): https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform
  Splunk describes customer-managed cloud deployments as BYOL on AWS, Google Cloud or Azure and provides provider-specific SmartStore architecture guidance. This evidence concerns customer-operated Splunk Enterprise, not Splunk Cloud Platform; validate instance, network, object-store and cache requirements for the selected topology.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Splunk Enterprise installation overview: https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview

- Splunk Enterprise reference hardware: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware

- Customer-managed BYOL SmartStore architectures: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform

- Splunk Enterprise license types: https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses

- Splunk November 2026 advance notice: https://advisory.splunk.com/advisories/SVD-2026-1101

- Splunk Enterprise 10.6 release notes: https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6

### Licensing sources

- https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses

- https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.6/install-a-splunk-enterprise-license/install-a-license

### Infrastructure sources

- https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview

- https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware

- https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform


### Buyer diligence


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

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


- Marketplace delivery: Documented. Splunk publishes an AWS AMI with a 60-day Enterprise trial. Continued paid software use requires an external license; the AMI is not a paid Enterprise subscription or proof of software-spend commitment credit. Verify its packaged version separately from upstream releases. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-l6oos72bsyaks (reviewed 2026-11-16). Offer prodview-l6oos72bsyaks: Splunk; EC2 AMI with trial; commercial license purchased outside Marketplace; https://aws.amazon.com/marketplace/pp/prodview-l6oos72bsyaks.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Enterprise 10.6 documents SAML 2.0 SSO, supported IdP connectivity, role/realName/mail attributes and administrator change_authentication capability. Encrypted assertions can be decrypted when configured; this does not establish SCIM provisioning. Scope: Customer-managed Splunk Enterprise 10.6 SAML configuration. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-single-sign-on-with-saml (reviewed 2026-11-16).

- SCIM provisioning: Documented. Enterprise 10.6 documents SCIM-based deletion of SAML users with a compatible Okta integration. Its release notes identify Entra ID de-provisioning as controlled availability. These sources establish scoped de-provisioning, not unrestricted SCIM user creation, updates or group synchronization. Scope: Splunk Enterprise 10.6 SAML user-removal workflow; identity-provider and availability conditions apply. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-sso-with-okta-as-your-identity-provider (reviewed 2026-11-16). Supporting source: 10.6 controlled-availability Entra ID feature — https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6.

- Compliance attestations: Documented. Splunk’s 10.6 guide identifies OpenSSL FIPS Provider certificate 4985 for FIPS 140-3. NIST lists that module as active, with sunset 2030-03-10 and approved-mode conditions. This is a cryptographic-module validation; deployment OS, mode, TLS and app prerequisites remain essential and it is not a blanket Splunk deployment attestation. Scope: Splunk 10.6 documented module plus NIST validation status checked 2026-11-16. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/establish-and-maintain-compliance-with-fips-and-common-criteria-in-splunk-enterprise/secure-splunk-enterprise-with-fips (reviewed 2026-11-16). Supporting source: NIST CMVP certificate 4985 — https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4985.

- Security controls: Documented. FIPS mode requires a supported x86-64 OS running in FIPS mode, TLS 1.2+ between nodes and compatible apps. The guide lists the older FIPS 140-2 certificate as expired in September 2026; select the supported 140-3 path and validate the full configuration. Scope: Enterprise 10.6 FIPS configuration prerequisites; not automatic security or regulatory compliance. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/establish-and-maintain-compliance-with-fips-and-common-criteria-in-splunk-enterprise/secure-splunk-enterprise-with-fips (reviewed 2026-11-16).

- Air-gapped operation: Documented. Splunk explicitly offers Enterprise for private-cloud/on-premises deployment, including air-gapped environments. This establishes the vendor’s deployment option; the selected apps, license delivery, updates, trust material and data integrations still need a disconnected operating procedure. Scope: Commercial Splunk Enterprise deployment option; not Splunk Cloud or every add-on. Source: https://www.splunk.com/en_us/products/pricing.html (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. Splunk supplies operating-system-specific Enterprise installers. Select the required platform/version and verify the published checksum. The installation guide limits Docker to supported standalone and single-server uses; a download is not a complete distributed infrastructure template. Scope: Splunk Enterprise 10.6 installation guidance; topology and platform determine the artifact. Source: https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview (reviewed 2026-11-16). Supporting source: Enterprise packages and checksums — https://www.splunk.com/en_us/download/splunk-enterprise.html.

- Minimum footprint / sizing: Documented. The Enterprise 10.6 single-instance reference specifies 12 physical cores or 24 vCPU at 2 GHz+, 12 GB RAM and a 1 Gb NIC. Storage, search concurrency, ingest volume and distributed roles require separate sizing. Scope: S1 single-instance production reference; not a multi-tier total or operating-cost estimate. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (reviewed 2026-11-16).

- License pricing: Documented. Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition. Scope: Splunk Enterprise: software license terms; infrastructure and operating costs are separate. Source: https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.6/install-a-splunk-enterprise-license/install-a-license.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Splunk Enterprise 10.6.1 was released October 16, 2026. The release page warns against Universal Forwarder 10.6.0, while SVD-2026-1101 names 10.6.1 and maintained parallel branches as forthcoming November fix targets. Scope: Splunk Enterprise 10.6 release line; advance notice is not a final CVE matrix. Source: https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6 (reviewed 2026-11-18). Supporting source: November 2026 advance notice — https://advisory.splunk.com/advisories/SVD-2026-1101.







## SUSE Observability Self-Hosted

Commercial observability platform installed by Helm into a dedicated customer Kubernetes cluster.

- Listing: https://launchinyourcloud.com/directory/suse-observability-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SUSE Observability self-hosted subscription and license key required.
- Licensing model: commercial-only
- Installation: SUSE Observability server Helm chart on EKS, AKS, GKE or Alibaba ACK, with provider-specific storage configuration
- Architecture: Persistent observability services, ingestion and storage components on a dedicated customer Kubernetes cluster.
- Operations: Customer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.
- Product website: https://www.suse.com/products/observability/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers the self-hosted server product, not SUSE Cloud Observability SaaS. Installation requires a license key, compatible Helm and Kubernetes versions, persistent storage and dedicated sizing. High-availability and non-high-availability profiles are not interchangeable after installation, so choose the production topology before deployment. SUSE Observability 2.13.0 includes authentication, disk, and backup fixes and requires the documented sequential upgrade path. Version 2.10 reached end of support on November 12, 2026; move through supported intermediate releases as required.

The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering.

SUSE Observability runs persistent stateful services on a dedicated Kubernetes cluster with durable storage and substantial capacity requirements.


### Category fit

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html (checked 2026-11-17). 


### Cloud deployment evidence

- SUSE Observability on EKS, AKS and GKE (aws, azure, gcp): https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html
  The server-installation guide explicitly covers the Observability server on EKS, AKS and GKE and supplies the Helm installation. The customer operates the dedicated server cluster, default storage class, persistent volumes and ingress; monitored-cluster agent integrations are separate.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SUSE Observability server installation on Alibaba ACK (alibaba): https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html
  The server guide supplies ACK-specific Helm values for stateful backend PVCs, each at least 20 GiB. This is server deployment evidence, distinct from monitoring an ACK cluster with an agent. Apply the selected HA sizing profile and provider storage requirements.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Install SUSE Observability self-hosted: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html

- Kubernetes quick start and named-cloud integrations: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/k8s-quick-start-guide.html

- SUSE subscription terms: https://www.suse.com/products/subscription_terms.pdf

- Alibaba ACK server Helm installation and PVC minimums: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html

- SUSE Observability 2.13.0 release notes: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/release-notes/v2.13.0.html

- SUSE product lifecycle: https://www.suse.com/lifecycle/

### Licensing sources

- https://www.suse.com/products/subscription_terms.pdf

- https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html

### Infrastructure sources

- https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The reviewed server guide supplies a licensed Helm repository, not a cloud-provider billing offer. A current Marketplace offer for this self-hosted server was not established. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/installing-suse-obs.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The self-hosted SUSE subscription and Helm installation do not establish an eligible offer or contract-specific cloud commitment treatment. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://www.suse.com/products/subscription_terms.pdf (reviewed 2026-11-17).

- Single sign-on: Documented. The server supports OIDC, including Rancher and Keycloak configurations, or LDAP as the selected authentication mechanism. Only one mechanism is configured at a time; map external groups to the intended server roles. Scope: SUSE Observability server authentication. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The server supports selected OIDC/LDAP authentication and role mappings, but a SCIM provisioning endpoint and lifecycle operations were not established. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SUSE Observability Self-Hosted material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Security controls: Documented. The default shared administrator password is explicitly not production-ready. Configure an external identity method, limit administrator roles and review RBAC before production use. Scope: Server identity and role hardening; not monitored-cluster agent settings. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Air-gapped operation: Documented. SUSE supplies an air-gapped server installation workflow: download the charts/images, transfer them to the isolated network, load a private registry and apply the licensed Helm configuration. Configure registry credentials and preserve the chosen sizing profile. Scope: Licensed self-hosted Observability server, not agents only. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/k8s-suse-rancher-prime-air-gapped.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The server installer uses the SUSE Observability Helm repository, licence key and a selected sizing profile. It provisions the Observability backend on EKS/AKS/GKE; agent installation is a separate workflow. Scope: Self-hosted server Helm installation. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/installing-suse-obs.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The smallest HA profile (150-ha) requests 49.8 CPU and 130.7 GiB RAM across at least three workers, with 2,595 GiB default storage. It is based on observed default-node capacity, not users; spare rolling-update capacity is additional. Scope: Observability 150-ha resource requests, not CPU limits or physical-node counts. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/requirements.html (reviewed 2026-11-17).

- License pricing: Documented. The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering. Scope: SUSE Observability Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.suse.com/products/subscription_terms.pdf (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 3,656.44/month. Three 32-vCPU/128-GiB workers price the minimum 150-ha profile, plus its 2,595 GiB default PVC request and 150 GB boot allowance. For this illustration each requested GiB is budgeted as one EBS billing GB. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Smallest documented HA profile, not a conversion from 100 users/1 TB into monitored-node capacity. It exceeds a 1 TB storage allowance before boot volumes. 96 vCPU/384 GiB fleet leaves nominal CPU/memory capacity after one worker loss; scheduling, AZ/storage failover and rolling updates still need validation.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-17). Supporting source: Product topology/sizing basis — https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/requirements.html. Supporting source: Current AWS documentation: us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: EKS standard versus extended support pricing — https://aws.amazon.com/eks/pricing/.

- Release snapshot / cadence: Documented. The self-hosted Helm chart v2.13.0 release notes are dated November 12, 2026. They list SUSE Observability 2.13.0, Values helper chart 1.4.13 (deprecated since 2.8.0), Agent 1.7.64 and CLI 3.9.0. Component versions are separate; apply every version-specific upgrade step from the installed version through 2.13.0, including the changed scheduling precedence. Scope: Dated SUSE Observability self-hosted Helm release snapshot; the deprecated Values helper chart is not a universal installation requirement. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/release-notes/v2.13.0.html (reviewed 2026-11-18).







## SUSE Security (NeuVector)

Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.

- Listing: https://launchinyourcloud.com/directory/suse-security-neuvector/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.
- Licensing model: open-source
- Installation: SUSE Security Helm chart or manifests on public-cloud Kubernetes
- Architecture: Manager, controller and scanner services plus an enforcer DaemonSet inside the customer Kubernetes cluster.
- Operations: Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
- Product website: https://www.suse.com/products/security/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.

NeuVector is Apache-2.0 licensed. SUSE subscriptions can add entitled delivery, integrations and support.

SUSE Security runs controller, scanner and enforcement workloads on customer Kubernetes nodes.


### Category fit

- devops: Adds runtime security, vulnerability scanning and policy enforcement to customer Kubernetes delivery environments.

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 


### Cloud deployment evidence

- SUSE Security on six named public-cloud Kubernetes services (aws, azure, gcp, ibm, alibaba, oci): https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html
  SUSE explicitly names AWS EKS, Azure AKS, Google Cloud, IBM Cloud Kubernetes, Alibaba Cloud and Oracle Cloud and links full Kubernetes/Helm application deployment. Confirm tested platform versions and privileges. GKE Autopilot requires allowlists; AWS ECS is no longer supported in the requirements guide.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

NeuVector publishes contribution/governance instructions and maintained public application and Helm releases. This is sustained upstream participation rather than a star-count threshold; commercial SUSE support remains a separately purchased entitlement.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/blob/main/CONTRIBUTING.md

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/releases/tag/v5.6.4

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4

### Sources

- Deploy SUSE Security on public-cloud Kubernetes: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html

- Deploy SUSE Security with Helm: https://documentation.suse.com/cloudnative/security/latest/en/helm.html

- SUSE Security support matrix: https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/

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

### Licensing sources

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

### Infrastructure sources

- https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html


### Buyer diligence


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

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


- Marketplace delivery: Edition-dependent. SUSE’s security guide routes AWS procurement through its multi-product Rancher/SUSE subscription offer. The current offer is a private-offer commercial contract labelled SaaS delivery; it is not a standalone upstream OSS AMI or proof of included NeuVector support. Confirm the Security entitlement in the order. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html (reviewed 2026-11-18). Supporting source: Actual SUSE Cloud Marketplace Program offer — https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw. Offer prodview-b6es6ar6n4siw: SUSE; SaaS-labelled multi-product private-offer subscription; https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw.

- Cloud commitment eligibility: Sources checked — unresolved. The multi-product private-offer route does not settle the buyer’s commitment eligibility or whether SUSE Security is included in the selected contract. Confirm exact entitlement, billable dimensions and cloud agreement. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. The v5.6 guide documents SAML 2.0 SSO, including Okta and group-to-role mapping. Signed assertions are required; encrypted assertions are not supported by this documented configuration. Set a deliberate default role rather than assuming group import grants appropriate access. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. SAML group-to-role mapping does not establish a SCIM server or provisioning/deprovisioning operations. Confirm a current endpoint and user-removal behavior for the selected OSS or subscription-delivered edition. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- Compliance attestations: Documented. LRQA certificate 10726335 covers SUSE’s ISO/IEC 27001:2022 ISMS and ISO/IEC 27701:2019 PIMS; schedule page 28 explicitly includes NeuVector, LLC. Issued November 4, 2025, it expires November 3, 2028. This is organisational information/privacy management assurance, not certification of a customer’s NeuVector cluster, protected workloads, configuration or operations. Scope: SUSE organisational management systems including the scheduled NeuVector entity; not a customer-deployment attestation. Source: https://www.suse.com/support/security/certifications/SUSE-ISO-27001-ISO-27701.pdf (reviewed 2026-11-18). Supporting source: Official SUSE certificate index — https://www.suse.com/support/security/certifications/isoiec-certification/.

- Security controls: Documented. NeuVector documents SAML role mapping and signed-assertion requirements. Enforcers run on cluster nodes and controllers coordinate security policy, so deployment needs the documented privileged access and network visibility. Scope cluster roles and protect console/controller access. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18). Supporting source: Runtime and component requirements — https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html. Supporting source: Cloud network and topology requirements — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- Air-gapped operation: Documented. The air-gap guide mirrors charts and images using Skopeo/zstd, transfers them and deploys from an internal registry. Its example versions are older than the current 5.6 line; resolve matching current application/chart/scanner versions and arrange offline vulnerability-database updates. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/airgap.html (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. NeuVector maintains a Helm chart for manager/controller/enforcer/scanner deployment. The reviewed chart release is v2.11.4, separate from application v5.6.4. Pin image tags and check values/privileges; air-gap documentation’s historical chart example is not a current version pin. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/latest/en/helm.html (reviewed 2026-11-18). Deployment artifact: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4. Artifact reference: NeuVector Helm chart v2.11.4.

- Minimum footprint / sizing: Documented. The requirements recommend three controllers for HA, an enforcer on each worker and separate scanner/manager resources. Controller minimum is 1 CPU/2 GB; an enforcer needs 1+ CPU/1 GB and a scanner 1 CPU/2 GB before workload growth. The public-cloud guide warns against multiple managers behind a load balancer because of session state, while requirements suggest manager redundancy; resolve that design before claiming full HA. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Manager scaling caveat and cloud topology — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- License pricing: Documented. Upstream NeuVector is Apache 2.0 licensed. SUSE subscription-delivered images, support and Rancher Prime integrations may require commercial entitlements. The multi-product AWS order is distinct from the free upstream code licence. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/blob/main/LICENSE (reviewed 2026-11-18). Supporting source: SUSE commercial procurement path — https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html.

- Operating cost estimate: Sources checked — unresolved. Size by protected Kubernetes node count, network throughput, container/image scan volume, registry retention and HA controller/scanner design, not directory users. Include per-node enforcers, scan capacity, persistent configuration and any SUSE support subscription. The manager redundancy conflict also needs resolution. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. NeuVector v5.6.4 was published October 27, 2026; chart v2.11.4 is a separate release. When upgrading from before v5.6.0, SUSE requires restarting/redeploying existing scanner pods for critical CVE severity handling. Maintenance releases on older branches are not a newer major-line snapshot. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/releases/tag/v5.6.4 (reviewed 2026-11-18). Supporting source: 5.6.4 upgrade and scanner requirements — https://documentation.suse.com/cloudnative/security/5.6/en/5x.html. Supporting source: Separate chart release — https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4.




### Security and lifecycle reviews

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

- NeuVector scanner restart required for critical-severity results (security-advisory): SUSE requires existing scanner pods to restart or redeploy when upgrading from before 5.6.0 to 5.6.4 or later, so cached capabilities recognize critical CVE severity. Scope: Upgrades from pre-5.6.0 controllers with existing scanner pods; not a claim of a new exploitable vulnerability in every NeuVector installation. Conditions: Older scanners cache the controller capability response. SUSE also calls for current scanner/CVE database content for PHP vulnerability checks. Action: Follow the 5.6.4 scanner restart and database-update instructions, including the transfer process in isolated environments. Source: https://documentation.suse.com/cloudnative/security/5.6/en/5x.html; reviewed 2026-11-18.




## ThingsBoard Self-Hosted

Source-available IoT device, telemetry and dashboard platform.

- Listing: https://launchinyourcloud.com/directory/thingsboard/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.
- Licensing model: source-available
- Installation: Kubernetes manifests
- Architecture: ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://thingsboard.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.

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

ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Source-available IoT device, telemetry and dashboard platform.

- observability: Source-available IoT device, telemetry and dashboard platform.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://thingsboard.io/docs/installation/azure/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://thingsboard.io/docs/installation/gcp/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS (aws): https://thingsboard.io/docs/installation/aws/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure (azure): https://thingsboard.io/docs/installation/azure/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP (gcp): https://thingsboard.io/docs/installation/gcp/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS: https://thingsboard.io/docs/installation/aws/

- Azure: https://thingsboard.io/docs/installation/azure/

- GCP: https://thingsboard.io/docs/installation/gcp/

- v4.4 Unification: https://thingsboard.io/docs/pe/installation/upgrade-from-ce/

- Smart Energy: https://thingsboard.io/use-cases/smart-energy/

- BUSL-1.1: https://github.com/thingsboard/thingsboard/blob/master/LICENSE

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

### Licensing sources

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

### Infrastructure sources

- https://thingsboard.io/docs/installation/aws/

- https://thingsboard.io/docs/installation/azure/

- https://thingsboard.io/docs/installation/gcp/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The ThingsBoard guide configures OAuth2/OIDC clients and domain-specific callbacks for Web UI or mobile login, including Keycloak, Okta, Azure and social providers. Configure issuer/JWKS, trusted claims, tenant/customer mapping and account-creation policy. Device transport credentials and API tokens are separate; the selected release licence still applies. Scope: Current self-hosted ThingsBoard user login and identity mapping, distinct from device authentication. Source: https://thingsboard.io/docs/user-guide/oauth-2-support/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The current Ubuntu guide installs a versioned application package, Java and database, then initializes the schema and starts the service. AWS guidance separates single-VM, EKS monolith and microservice topologies. Select matching application/manifests and dependencies, replace sample secrets, and configure TLS, persistence, mail and licence activation. Scope: Official native package installation; AWS reference topologies and provider images have separate versions. Source: https://thingsboard.io/docs/user-guide/install/ubuntu/ (reviewed 2026-11-20). Deployment artifact: https://github.com/thingsboard/thingsboard/releases/tag/v4.4.0.2. Artifact reference: v4.4.0.2 application package release; match provider image/manifests separately. Supporting source: Official AWS deployment choices — https://thingsboard.io/docs/installation/aws/.

- Minimum footprint / sizing: Documented. The Ubuntu guide distinguishes a 1-core/4 GB/20 GB proof of concept from small production at 2 cores/8 GB/50 GB SSD and a larger starting tier at 4+ cores/16+ GB/100+ GB SSD. Queue/database choices add resources; the heap example is not total host capacity. Device/message rate, retention and HA require separate sizing. Scope: Current single-host tier recommendations; not a 1 TB microservice/HA sizing guarantee. Source: https://thingsboard.io/docs/user-guide/install/ubuntu/ (reviewed 2026-11-20).

- License pricing: Edition-dependent. Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions. Scope: ThingsBoard Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/thingsboard/thingsboard/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Wazuh Self-Hosted

Open-source security monitoring platform launched from Wazuh's official all-in-one AWS image.

- Listing: https://launchinyourcloud.com/directory/wazuh-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source Wazuh components under GPL-2.0 and Apache-2.0 licenses.
- Licensing model: open-source
- Installation: Official Wazuh All-In-One AMI from AWS Marketplace
- Architecture: Customer EC2 instance containing Wazuh server, indexer, dashboard and Filebeat; distributed production topology is a separate design.
- Operations: Customer manages EC2, networking, storage, agents, TLS, backups, retention, upgrades and capacity.
- Product website: https://wazuh.com/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

The vendor’s all-in-one AMI is explicitly single-node/testing oriented and does not provide HA or professional support. A production design should evaluate distributed server/indexer/dashboard components and match supported versions. Cloud-monitoring integrations alone do not establish hosting on additional providers.

Wazuh publishes open-source components under GPL-2.0 and Apache-2.0; support services and Marketplace infrastructure are separate.

The Wazuh AMI runs persistent server, indexer and dashboard components on a customer EC2 instance.


### Category fit

- observability: Collects and analyzes security telemetry, events, file integrity, vulnerabilities and alerts through customer-operated central services.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.wazuh.com/current/deployment-options/amazon-machine-images/amazon-machine-images.html (checked 2026-11-18). 


### Cloud deployment evidence

- Wazuh All-In-One AMI in customer AWS (aws): https://documentation.wazuh.com/current/deployment-options/amazon-machine-images/amazon-machine-images.html
  Wazuh documents launching the vendor All-In-One AMI in customer EC2. The current offer packages v4.14.10-1 and describes a single-node testing/lab deployment without professional support; it is not an HA production architecture.
  Source type: marketplace-offer; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

Wazuh documents an active community/contribution ecosystem, named customer deployments and current stable releases. These support meaningful adoption and maintenance; Wazuh Cloud customers do not expand the self-hosted cloud badges.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://wazuh.com/community/

- Official maintenance and adoption evidence: https://wazuh.com/our-customers/

- Official maintenance and adoption evidence: https://github.com/wazuh/wazuh/releases/tag/v4.14.10

### Sources

- Wazuh Amazon Machine Images: https://documentation.wazuh.com/current/deployment-options/amazon-machine-images/amazon-machine-images.html

- Wazuh installation guide: https://documentation.wazuh.com/current/installation-guide/index.html

- Wazuh deployment options: https://documentation.wazuh.com/current/deployment-options/index.html

### Licensing sources

- https://github.com/wazuh/wazuh

- https://github.com/wazuh/wazuh-indexer

### Infrastructure sources

- https://documentation.wazuh.com/current/deployment-options/amazon-machine-images/amazon-machine-images.html


### Buyer diligence


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

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


- Marketplace delivery: Documented. Wazuh Inc. publishes the free self-managed All-In-One AMI, package v4.14.10-1 on Amazon Linux 2023. The offer describes a single-node testing/lab deployment and excludes professional support. It is not an HA production service. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-eju4flv5eqmgq (reviewed 2026-11-18). Offer prodview-eju4flv5eqmgq: Wazuh Inc.; Amazon Machine Image (AMI); package v4.14.10-1; https://aws.amazon.com/marketplace/pp/prodview-eju4flv5eqmgq.

- Cloud commitment eligibility: Explicitly unsupported. The exact reviewed Wazuh self-managed AWS AMI is free of charge in Marketplace. It supplies no billed software amount to apply toward a software-spend commitment through this offer. EC2/EBS, paid support, other editions and separately negotiated offers have separate charges and require the buyer’s applicable order and AWS agreement; the free software finding does not settle those charges. Scope: Software amount through the exact free AWS AMI prodview-eju4flv5eqmgq; infrastructure, paid support, other editions and private offers assessed separately. Source: https://aws.amazon.com/marketplace/pp/prodview-eju4flv5eqmgq (reviewed 2026-11-18). Supporting source: AWS product-by-product commitment qualifications — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. Wazuh documents SAML SSO for the dashboard with indexer security configuration and backend-role mappings. Configure both sides and preserve an administrative recovery path. Identity-provider groups and local authorization are distinct configuration steps. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://documentation.wazuh.com/current/user-manual/user-administration/single-sign-on/index.html (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. Dashboard SAML and backend-role mappings do not establish a Wazuh SCIM endpoint or user/group lifecycle operations. Confirm provisioning, deactivation and active-session removal for the selected IdP and component versions. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://documentation.wazuh.com/current/user-manual/user-administration/single-sign-on/index.html (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. Wazuh publishes a SOC 2 Type 2 completion letter for the May 1, 2025–April 30, 2026 examination of Wazuh, Inc.’s internal controls. The letter does not supply the report’s system boundary, exclusions or customer controls, so it cannot establish coverage of this customer-operated server/indexer/dashboard/agent deployment. Obtain the full report and any bridge letter; compliance-monitoring features are not certification. Scope: Public organisational examination completion letter; self-hosted system/report boundary still unconfirmed. Source: https://wazuh.com/docs/Wazuh_A-LIGN_cert_SOC-2-Type-2.pdf (reviewed 2026-11-18). Supporting source: Self-managed versus vendor-managed service boundaries — https://documentation.wazuh.com/current/cloud-service/index.html.

- Security controls: Documented. The installation procedure generates certificates and passwords and configures authenticated component communication. SAML configuration separately maps dashboard identities to indexer roles. Protect certificate archives and credentials, and keep server/indexer/dashboard versions compatible. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://documentation.wazuh.com/current/deployment-options/offline-installation/index.html (reviewed 2026-11-18). Supporting source: SAML and authorization configuration — https://documentation.wazuh.com/current/user-manual/user-administration/single-sign-on/index.html.

- Air-gapped operation: Documented. The official offline procedure supports all-in-one or distributed installation by downloading packages and generating configuration/certificates on a connected host, then transferring them to isolated targets. Prepare matching component packages and plan manual vulnerability-feed and software updates. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://documentation.wazuh.com/current/deployment-options/offline-installation/index.html (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The offline deployment guide uses the Wazuh installation assistant and transferred package/configuration archives. The /4.14/ script URL is a moving maintenance path, not an immutable 4.14.10 artifact. Record resolved package versions/checksums before installation. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://documentation.wazuh.com/current/deployment-options/offline-installation/index.html (reviewed 2026-11-18). Deployment artifact: https://packages.wazuh.com/4.14/wazuh-install.sh. Artifact reference: Moving Wazuh 4.14 maintenance installer; reviewed 2026-11-18.

- Minimum footprint / sizing: Documented. The all-in-one quickstart estimates 4 vCPU/8 GiB/50 GB for 1–25 agents, 8 vCPU/8 GiB/100 GB for 26–50, and 8 vCPU/8 GiB/200 GB for 51–100, with 90 days of indexed alerts. These are agent/event-retention examples, not internal-user or HA sizing. Distributed server/indexer clusters add capacity. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://documentation.wazuh.com/current/quickstart.html (reviewed 2026-11-18).

- License pricing: Documented. The self-managed AMI has no software fee; Wazuh components use open-source licences, including GPLv2 and Apache 2.0. Professional support and vendor-hosted Wazuh Cloud are separate purchases. AWS compute/storage charges remain. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-eju4flv5eqmgq (reviewed 2026-11-18).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 1,212.96/month. Only three 8-vCPU/32-GiB indexer VMs are priced. Each has 1,500 GB data capacity plus 50 GB boot gp3 (4,650 GB total), assuming 1 TB primary indexed data and one configured replica, with spare disk capacity for recovery. Wazuh server/dashboard tiers and whole-system HA remain unpriced. This is not a complete operating-cost estimate or validated capacity/SLA claim. Scope: Editorial indexer layer across three AZs; configure shard/replica placement and failure tests. The 1 TB input is assumed to mean primary indexed data, not raw logs. Provisioned capacity includes illustrative recovery headroom; agents, alerts/second, index expansion, retention and actual disk watermarks still need validation.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-18). Supporting source: Product topology/sizing basis — https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/step-by-step.html. Supporting source: Current AWS us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: Per-indexer CPU/RAM recommendations and APS-dependent storage — https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/index.html.

- Release snapshot / cadence: Documented. Wazuh v4.14.10 was published November 9, 2026 with rootcheck command-injection, path-handling and authorization-rule fixes. Later v4.14.11 and v5.0 release candidates are not stable. The AMI package is v4.14.10-1; match central components and agents to the supported upgrade sequence. Scope: Wazuh Self-Hosted: selected customer-operated edition. Source: https://github.com/wazuh/wazuh/releases/tag/v4.14.10 (reviewed 2026-11-18). Supporting source: 4.14.10 security and correctness fixes — https://documentation.wazuh.com/current/release-notes/release-4-14-10.html. Supporting source: AMI package version — https://aws.amazon.com/marketplace/pp/prodview-eju4flv5eqmgq.




### Security and lifecycle reviews

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

- Wazuh 4.14.10 command, path and authorization fixes (security-advisory): The stable release fixes rootcheck OS command injection, agent diff-folder traversal, symlink handling and run_as/MATCH authorization-rule issues. Scope: Named fixes in the Wazuh 4.14.10 manager/agent release notes; those notes do not establish a single affected-version range or CVE for the combined findings. Conditions: The enabled checks, local filesystem paths, API access and authorization rules determine which fixes apply. A central-server upgrade alone does not update every monitored agent. Action: Review the supported central-component and agent upgrade order, apply relevant fixes and recheck custom authorization rules and enabled collectors. Source: https://documentation.wazuh.com/current/release-notes/release-4-14-10.html; reviewed 2026-11-18.




## Zabbix Server

Open-source monitoring platform deployed from official Zabbix cloud images into customer accounts.

- Listing: https://launchinyourcloud.com/directory/zabbix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 for Zabbix 7.0+; older releases such as the reviewed DigitalOcean 6.x packages use GPLv2. Provider images/support can be separately charged.
- Licensing model: open-source
- Installation: Official Zabbix VM images from AWS, Azure, Google Cloud or DigitalOcean marketplaces
- Architecture: Customer-operated Zabbix server, web frontend and database on a cloud virtual machine.
- Operations: Customer manages VM, database, storage, agents, networking, TLS, retention, backups, upgrades and monitoring capacity.
- Product website: https://www.zabbix.com/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

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

Zabbix 7.0 and later are AGPLv3; professional support is optional and separate.

Zabbix runs persistent monitoring and database services on customer virtual-machine capacity.


### Category fit

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.zabbix.com/documentation/current/en/manual/installation/install/aws_deployment_guide (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.zabbix.com/documentation/current/en/manual/installation/install/cloud_google (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/ (checked 2026-11-18). 


### Cloud deployment evidence

- Zabbix Server on AWS (aws): https://www.zabbix.com/documentation/current/en/manual/installation/install/aws_deployment_guide
  Zabbix documents launching the official server image into the customer's selected AWS VPC and subnet.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Zabbix Server on Azure (azure): https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide
  The current Azure deployment guide launches the server appliance in the customer subscription. Its 7.4 example does not include infrastructure redundancy and is distinct from current upstream 8.0.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Zabbix Server on Google Cloud (gcp): https://www.zabbix.com/documentation/current/en/manual/installation/install/cloud_google
  Zabbix documents deployment from Google Cloud Marketplace into the customer's project.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Official Zabbix DigitalOcean image (digitalocean): https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/
  DigitalOcean lists full Zabbix Server Droplet packages, including 6.0.17 (image 131398452, slug zabbix-zabbixserver60). These older images require supported-branch/patch/OS review; they are not current upstream 8.0 packages.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

Zabbix maintains a named user/case-study catalog and dated current/LTS release histories, providing adoption and maintenance evidence beyond downloads. Provider images retain their own versions, licences and support terms.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://www.zabbix.com/users

- Official maintenance and adoption evidence: https://www.zabbix.com/release_notes

### Sources

- Zabbix cloud images: https://www.zabbix.com/cloud_images

- AWS deployment guide: https://www.zabbix.com/documentation/current/en/manual/installation/install/aws_deployment_guide

- Azure deployment guide: https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide

- Google Cloud deployment guide: https://www.zabbix.com/documentation/current/en/manual/installation/install/cloud_google

- Zabbix license: https://www.zabbix.com/license

- DigitalOcean Droplet package catalog: https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/

### Licensing sources

- https://www.zabbix.com/license

### Infrastructure sources

- https://www.zabbix.com/cloud_images


### Buyer diligence


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

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


- Marketplace delivery: Documented. Zabbix publishes an AWS Server AMI, currently package v7.4.16 on Rocky Linux 10.2, with usage pricing after its trial. DigitalOcean’s catalog separately lists older 6.0/6.2/6.4 images. Neither package should be represented as the current upstream 8.0.0 release. Scope: Zabbix Server: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4 (reviewed 2026-11-18). Supporting source: DigitalOcean image IDs and versions — https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/. Offer prodview-jf4elxhe5llj4: Zabbix; Amazon Machine Image (AMI); package v7.4.16; https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4.

- Cloud commitment eligibility: Sources checked — unresolved. The paid AWS image does not establish the buyer’s software commitment eligibility. Direct source/package installation, support contracts and provider images have different charging paths; verify the chosen order and agreement. Scope: Zabbix Server: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4 (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. Zabbix documents SAML 2.0 frontend authentication with IdP mapping and optional just-in-time provisioning. Configure group/role mappings and login permissions. This is distinct from agent/proxy authentication. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml (reviewed 2026-11-18).

- SCIM provisioning: Documented. SCIM 2.0 is documented with SAML just-in-time provisioning enabled, a Super admin API token and api_scim.php. Only users provisioned through the SAML/JIT path are continuously updated; existing local users are not automatically imported. Review deprovisioned-group mapping and the privileged token. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. Zabbix’s year-in-review reports three-year ISO 27001/27017 recertification in 2025. Its public BM PDF MSC-27-849 still expires December 27, 2025. These sources distinguish a renewal claim from the older certificate; neither supplies the renewed issuer record and current assessed scope here. Obtain that document/status before relying on current supplier assurance, and assess the customer monitoring environment separately. The old PDF is not proof that certification lapsed. Scope: Vendor-reported renewal plus an older issuer certificate; current certificate/issuer validity and assessed scope remain unconfirmed. Source: https://blog.zabbix.com/zabbix-in-2025-a-year-of-growth-community-and-innovation/32470/ (reviewed 2026-11-18). Supporting source: Current vendor security-policy statement — https://www.zabbix.com/zabbix_security_policy. Supporting source: Older published issuer certificate — https://assets.zabbix.com/img/about/Zabbix_ISO_27001_ISO_27017_Certificate_EN_2024.pdf. Supporting source: Issuer directs management-system checks to IAF CertSearch — https://bmcertification.com/about-us/certificate-check/.

- Security controls: Documented. The frontend provides SAML role/group mappings and privileged-token controls for SCIM. Zabbix separately documents certificate/PSK encryption for component connections. Configure each transport and access boundary; SSO does not secure agent/proxy traffic by itself. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml (reviewed 2026-11-18). Supporting source: Component encryption guide — https://www.zabbix.com/documentation/current/en/manual/encryption.

- Air-gapped operation: Documented. Zabbix explicitly describes fully on-premises, air-gapped monitoring without external cloud services. The current server setting AllowSoftwareUpdateCheck=0 disables software-update checks. Stage OS/application packages, database, agents, templates and updates for the isolated network; external notification channels and cloud integrations need reachable internal replacements or must be omitted. Scope: Self-hosted Zabbix with prepared packages and local monitoring/database dependencies; not every optional external integration. Source: https://blog.zabbix.com/showcasing-our-potential-at-europol-industry-and-research-days/32733/ (reviewed 2026-11-18). Supporting source: Current update-check setting and server configuration — https://www.zabbix.com/documentation/current/en/manual/concepts/server/server_params.

- Deployment artifact / IaC: Documented. The Azure guide deploys a Zabbix appliance VM into the customer subscription but uses a 7.4 example without infrastructure redundancy. AWS and DigitalOcean provide separately versioned images. Pin the actual image ID/version and supply database/HA automation rather than treating an appliance as a complete HA artifact. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide (reviewed 2026-11-18). Supporting source: AWS image/package — https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4. Supporting source: DigitalOcean image IDs — https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/.

- Minimum footprint / sizing: Documented. The requirements table gives an illustrative small installation at 1,000 metrics with 2 CPUs/8 GiB RAM and medium at 10,000 metrics with 4 CPUs/16 GiB. History/trend retention, polling frequency and database design dominate storage. These are metric-count examples, not user-count or fully redundant database sizing. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/documentation/current/en/manual/installation/requirements (reviewed 2026-11-18).

- License pricing: Documented. Zabbix 7.0+ is AGPLv3; older releases including the DigitalOcean 6.x images use GPLv2. Direct open-source software, paid support and provider-image usage charges are separate. The reviewed AWS AMI is usage-priced despite open-source upstream licensing. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/license (reviewed 2026-11-18). Supporting source: AWS image usage terms — https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4. Supporting source: Older DigitalOcean release packages — https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/.

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 144.96/month. Only two 2-vCPU/8-GiB application VMs and 30 GB boot gp3 each are priced. Native server HA is active/standby and shares a database. The HA database, all 1 TB monitoring/history data, frontend and proxies are unpriced; this is not the paid appliance AMI price. This is not a complete operating-cost estimate or validated capacity/SLA claim. Scope: Editorial Zabbix native-server HA application layer across two AZs, with a separately designed reachable HA database. Two CPUs/8 GiB mirrors the small 1,000-metric illustration, not a 100-user or throughput benchmark. No data volume or database service is included.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-18). Supporting source: Product topology/sizing basis — https://www.zabbix.com/documentation/current/en/manual/concepts/server/ha. Supporting source: Current AWS us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: Metric-count sizing illustrations — https://www.zabbix.com/documentation/current/en/manual/installation/requirements.

- Release snapshot / cadence: Documented. Zabbix 8.0.0 was released November 5, 2026. The reviewed AWS AMI remains v7.4.16 and DigitalOcean offers older 6.x images. A current upstream release does not mean every provider package has been refreshed. Scope: Zabbix Server: selected customer-operated edition. Source: https://www.zabbix.com/release_notes (reviewed 2026-11-18). Supporting source: AWS packaged version — https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4. Supporting source: DigitalOcean packaged versions — https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/.






